diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 95f46eafd..69a49ed6c 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -548,260 +548,276 @@ msgstr "" msgid "Odoo static files are located in each module's :file:`static/` folder, so static files can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) in the various addons paths." msgstr "" -#: ../../content/administration/install/deploy.rst:443 -msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise and the :option:`--addons-path ` is ``'/usr/lib/python3/dist-packages/odoo/addons'``." +#: ../../content/administration/install/deploy.rst:442 +msgid "It is recommended to set the ``Content-Security-Policy: default-src 'none'`` header on all images delivered by the web server. It is not strictly necessary as users cannot modify/inject content inside of modules' :file:`static/` folder and existing images are final (they do not fetch new resources by themselves). However, it is good practice." msgstr "" -#: ../../content/administration/install/deploy.rst:446 -#: ../../content/administration/install/deploy.rst:468 -msgid "Using the above NGINX (https) configuration, the following location block should be added to serve static files via NGINX." +#: ../../content/administration/install/deploy.rst:447 +msgid "Using the above NGINX (https) configuration, the following ``map`` and ``location`` blocks should be added to serve static files via NGINX." msgstr "" -#: ../../content/administration/install/deploy.rst:463 -msgid "Say Odoo has been installed via the **source**. The two git repositories for Community and Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively and the :option:`--addons-path ` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +#: ../../content/administration/install/deploy.rst:474 +msgid "The actual ``root`` and ``try_files`` directives are dependant on your installation, specifically on your :option:`--addons-path `." msgstr "" -#: ../../content/administration/install/deploy.rst:485 -msgid "The actual NGINX configuration you need is highly dependent on your own installation. The two above snippets only highlight two possible configurations and may not be used as-is." +#: ../../content/administration/install/deploy.rst:481 +msgid "Debian package" msgstr "" -#: ../../content/administration/install/deploy.rst:489 -msgid "Serving attachments" +#: ../../content/administration/install/deploy.rst:483 +msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise, and that the :option:`--addons-path ` is ``'/usr/lib/python3/dist-packages/odoo/addons'``." msgstr "" -#: ../../content/administration/install/deploy.rst:491 -msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not." +#: ../../content/administration/install/deploy.rst:487 +#: ../../content/administration/install/deploy.rst:501 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:494 +msgid "Git sources" msgstr "" #: ../../content/administration/install/deploy.rst:496 +msgid "Say Odoo has been installed via the **sources**, that both the Community and Enterprise git repositories were cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-path ` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/install/deploy.rst:509 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/install/deploy.rst:511 +msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/install/deploy.rst:516 msgid "Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving files to the static web server, the `X-Sendfile `_ (apache) or `X-Accel `_ (nginx) extensions must be enabled and configured on the static web server. Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and X-Accel)." msgstr "" -#: ../../content/administration/install/deploy.rst:506 +#: ../../content/administration/install/deploy.rst:526 msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration." msgstr "" -#: ../../content/administration/install/deploy.rst:508 +#: ../../content/administration/install/deploy.rst:528 msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:" msgstr "" -#: ../../content/administration/install/deploy.rst:517 +#: ../../content/administration/install/deploy.rst:537 msgid "In case you don't know what is the path to your filestore, start Odoo with the :option:`--x-sendfile ` option and navigate to the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message contains the configuration you need." msgstr "" -#: ../../content/administration/install/deploy.rst:526 +#: ../../content/administration/install/deploy.rst:546 msgid "Security" msgstr "" -#: ../../content/administration/install/deploy.rst:528 +#: ../../content/administration/install/deploy.rst:548 msgid "For starters, keep in mind that securing an information system is a continuous process, not a one-shot operation. At any moment, you will only be as secure as the weakest link in your environment." msgstr "" -#: ../../content/administration/install/deploy.rst:532 +#: ../../content/administration/install/deploy.rst:552 msgid "So please do not take this section as the ultimate list of measures that will prevent all security problems. It's only intended as a summary of the first important things you should be sure to include in your security action plan. The rest will come from best security practices for your operating system and distribution, best practices in terms of users, passwords, and access control management, etc." msgstr "" -#: ../../content/administration/install/deploy.rst:538 +#: ../../content/administration/install/deploy.rst:558 msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" msgstr "" -#: ../../content/administration/install/deploy.rst:541 +#: ../../content/administration/install/deploy.rst:561 msgid "Always set a strong super-admin admin password, and restrict access to the database management pages as soon as the system is set up. See :ref:`db_manager_security`." msgstr "" -#: ../../content/administration/install/deploy.rst:544 +#: ../../content/administration/install/deploy.rst:564 msgid "Choose unique logins and strong passwords for all administrator accounts on all databases. Do not use 'admin' as the login. Do not use those logins for day-to-day operations, only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases." msgstr "" -#: ../../content/administration/install/deploy.rst:549 +#: ../../content/administration/install/deploy.rst:569 msgid "Do **not** install demo data on internet-facing servers. Databases with demo data contain default logins and passwords that can be used to get into your systems and cause significant trouble, even on staging/dev systems." msgstr "" -#: ../../content/administration/install/deploy.rst:553 +#: ../../content/administration/install/deploy.rst:573 msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d ` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend." msgstr "" -#: ../../content/administration/install/deploy.rst:560 +#: ../../content/administration/install/deploy.rst:580 msgid "Once your ``db_name`` and ``db_filter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list ` command-line option)" msgstr "" -#: ../../content/administration/install/deploy.rst:566 +#: ../../content/administration/install/deploy.rst:586 msgid "Make sure the PostgreSQL user (:option:`--db_user `) is *not* a super-user, and that your databases are owned by a different user. For example they could be owned by the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``. See also :ref:`setup/deploy/odoo`." msgstr "" -#: ../../content/administration/install/deploy.rst:571 +#: ../../content/administration/install/deploy.rst:591 msgid "Keep installations updated by regularly installing the latest builds, either via GitHub or by downloading the latest version from https://www.odoo.com/page/download or http://nightly.odoo.com" msgstr "" -#: ../../content/administration/install/deploy.rst:575 +#: ../../content/administration/install/deploy.rst:595 msgid "Configure your server in multi-process mode with proper limits matching your typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." msgstr "" -#: ../../content/administration/install/deploy.rst:578 +#: ../../content/administration/install/deploy.rst:598 msgid "Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate, in order to prevent eavesdropping on cleartext communications. SSL certificates are cheap, and many free options exist. Configure the web proxy to limit the size of requests, set appropriate timeouts, and then enable the :option:`proxy mode ` option. See also :ref:`https_proxy`." msgstr "" -#: ../../content/administration/install/deploy.rst:585 +#: ../../content/administration/install/deploy.rst:605 msgid "If you need to allow remote SSH access to your servers, make sure to set a strong password for **all** accounts, not just `root`. It is strongly recommended to entirely disable password-based authentication, and only allow public key authentication. Also consider restricting access via a VPN, allowing only trusted IPs in the firewall, and/or running a brute-force detection system such as `fail2ban` or equivalent." msgstr "" -#: ../../content/administration/install/deploy.rst:591 +#: ../../content/administration/install/deploy.rst:611 msgid "Consider installing appropriate rate-limiting on your proxy or firewall, to prevent brute-force attacks and denial of service attacks. See also :ref:`login_brute_force` for specific measures." msgstr "" -#: ../../content/administration/install/deploy.rst:595 +#: ../../content/administration/install/deploy.rst:615 msgid "Many network providers provide automatic mitigation for Distributed Denial of Service attacks (DDOS), but this is often an optional service, so you should consult with them." msgstr "" -#: ../../content/administration/install/deploy.rst:599 +#: ../../content/administration/install/deploy.rst:619 msgid "Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production." msgstr "" -#: ../../content/administration/install/deploy.rst:603 +#: ../../content/administration/install/deploy.rst:623 msgid "If your public-facing Odoo server has access to sensitive internal network resources or services (e.g. via a private VLAN), implement appropriate firewall rules to protect those internal resources. This will ensure that the Odoo server cannot be used accidentally (or as a result of malicious user actions) to access or disrupt those internal resources. Typically this can be done by applying an outbound default DENY rule on the firewall, then only explicitly authorizing access to internal resources that the Odoo server needs to access. `Systemd IP traffic access control `_ may also be useful to implement per-process network access control." msgstr "" -#: ../../content/administration/install/deploy.rst:614 +#: ../../content/administration/install/deploy.rst:634 msgid "If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer, a transparent DDoS protection service (like CloudFlare) or a similar network-level device, you may wish to avoid direct access to the Odoo system. It is generally difficult to keep the endpoint IP addresses of your Odoo servers secret. For example they can appear in web server logs when querying public systems, or in the headers of emails posted from Odoo. In such a situation you may want to configure your firewall so that the endpoints are not accessible publicly except from the specific IP addresses of your WAF, load-balancer or proxy service. Service providers like CloudFlare usually maintain a public list of their IP address ranges for this purpose." msgstr "" -#: ../../content/administration/install/deploy.rst:625 +#: ../../content/administration/install/deploy.rst:645 msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques." msgstr "" -#: ../../content/administration/install/deploy.rst:628 +#: ../../content/administration/install/deploy.rst:648 msgid "Setup daily backups of your databases and filestore data, and copy them to a remote archiving server that is not accessible from the server itself." msgstr "" -#: ../../content/administration/install/deploy.rst:631 +#: ../../content/administration/install/deploy.rst:651 msgid "Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless to deploy on a Windows platform, a thorough security hardening review of the server should be conducted and is outside of the scope of this guide." msgstr "" -#: ../../content/administration/install/deploy.rst:639 +#: ../../content/administration/install/deploy.rst:659 msgid "Blocking Brute Force Attacks" msgstr "" -#: ../../content/administration/install/deploy.rst:641 +#: ../../content/administration/install/deploy.rst:661 msgid "For internet-facing deployments, brute force attacks on user passwords are very common, and this threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt is performed, and reports the result: success or failure, along with the target login and source IP." msgstr "" -#: ../../content/administration/install/deploy.rst:645 +#: ../../content/administration/install/deploy.rst:665 msgid "The log entries will have the following form." msgstr "" -#: ../../content/administration/install/deploy.rst:647 +#: ../../content/administration/install/deploy.rst:667 msgid "Failed login::" msgstr "" -#: ../../content/administration/install/deploy.rst:651 +#: ../../content/administration/install/deploy.rst:671 msgid "Successful login::" msgstr "" -#: ../../content/administration/install/deploy.rst:656 +#: ../../content/administration/install/deploy.rst:676 msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`." msgstr "" -#: ../../content/administration/install/deploy.rst:658 +#: ../../content/administration/install/deploy.rst:678 msgid "For example, the following fail2ban filter definition should match a failed login::" msgstr "" -#: ../../content/administration/install/deploy.rst:665 +#: ../../content/administration/install/deploy.rst:685 msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)." msgstr "" -#: ../../content/administration/install/deploy.rst:667 +#: ../../content/administration/install/deploy.rst:687 msgid "Here is what it could look like for blocking the IP for 15 minutes when 10 failed login attempts are detected from the same IP within 1 minute::" msgstr "" -#: ../../content/administration/install/deploy.rst:681 +#: ../../content/administration/install/deploy.rst:701 msgid "Database Manager Security" msgstr "" -#: ../../content/administration/install/deploy.rst:683 +#: ../../content/administration/install/deploy.rst:703 msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." msgstr "" -#: ../../content/administration/install/deploy.rst:685 +#: ../../content/administration/install/deploy.rst:705 msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)." msgstr "" -#: ../../content/administration/install/deploy.rst:688 +#: ../../content/administration/install/deploy.rst:708 msgid "If the management screens must not be accessible at all, you should set ``list_db`` configuration option to ``False``, to block access to all the database selection and management screens." msgstr "" -#: ../../content/administration/install/deploy.rst:694 +#: ../../content/administration/install/deploy.rst:714 msgid "It is strongly recommended to disable the Database Manager for any internet-facing system! It is meant as a development/demo tool, to make it easy to quickly create and manage databases. It is not designed for use in production, and may even expose dangerous features to attackers. It is also not designed to handle large databases, and may trigger memory limits." msgstr "" -#: ../../content/administration/install/deploy.rst:700 +#: ../../content/administration/install/deploy.rst:720 msgid "On production systems, database management operations should always be performed by the system administrator, including provisioning of new databases and automated backups." msgstr "" -#: ../../content/administration/install/deploy.rst:703 +#: ../../content/administration/install/deploy.rst:723 msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``db_filter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves." msgstr "" -#: ../../content/administration/install/deploy.rst:708 +#: ../../content/administration/install/deploy.rst:728 msgid "If the management screens must only be accessible from a selected set of machines, use the proxy server's features to block access to all routes starting with ``/web/database`` except (maybe) ``/web/database/selector`` which displays the database-selection screen." msgstr "" -#: ../../content/administration/install/deploy.rst:712 +#: ../../content/administration/install/deploy.rst:732 msgid "If the database-management screen should be left accessible, the ``admin_passwd`` setting must be changed from its ``admin`` default: this password is checked before allowing database-alteration operations." msgstr "" -#: ../../content/administration/install/deploy.rst:716 +#: ../../content/administration/install/deploy.rst:736 msgid "It should be stored securely, and should be generated randomly e.g." msgstr "" -#: ../../content/administration/install/deploy.rst:722 +#: ../../content/administration/install/deploy.rst:742 msgid "which will generate a 32 characters pseudorandom printable string." msgstr "" -#: ../../content/administration/install/deploy.rst:725 +#: ../../content/administration/install/deploy.rst:745 msgid "Supported Browsers" msgstr "" -#: ../../content/administration/install/deploy.rst:727 +#: ../../content/administration/install/deploy.rst:747 msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers." msgstr "" -#: ../../content/administration/install/deploy.rst:730 +#: ../../content/administration/install/deploy.rst:750 msgid "Here are the supported browsers:" msgstr "" -#: ../../content/administration/install/deploy.rst:732 +#: ../../content/administration/install/deploy.rst:752 msgid "Google Chrome" msgstr "" -#: ../../content/administration/install/deploy.rst:733 +#: ../../content/administration/install/deploy.rst:753 msgid "Mozilla Firefox" msgstr "" -#: ../../content/administration/install/deploy.rst:734 +#: ../../content/administration/install/deploy.rst:754 msgid "Microsoft Edge" msgstr "" -#: ../../content/administration/install/deploy.rst:735 +#: ../../content/administration/install/deploy.rst:755 msgid "Apple Safari" msgstr "" -#: ../../content/administration/install/deploy.rst:737 +#: ../../content/administration/install/deploy.rst:757 msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report." msgstr "" -#: ../../content/administration/install/deploy.rst:742 +#: ../../content/administration/install/deploy.rst:762 msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." msgstr "" -#: ../../content/administration/install/deploy.rst:745 +#: ../../content/administration/install/deploy.rst:765 msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software." msgstr "" -#: ../../content/administration/install/deploy.rst:748 +#: ../../content/administration/install/deploy.rst:768 msgid "technically a tool like socat_ can be used to proxy UNIX sockets across networks, but that is mostly for software which can only be used over UNIX sockets" msgstr "" -#: ../../content/administration/install/deploy.rst:752 +#: ../../content/administration/install/deploy.rst:772 msgid "or be accessible only over an internal packet-switched network, but that requires secured switches, protections against `ARP spoofing`_ and precludes usage of WiFi. Even over secure packet-switched networks, deployment over HTTPS is recommended, and possible costs are lowered as \"self-signed\" certificates are easier to deploy on a controlled environment than over the internet." msgstr "" @@ -893,8 +909,9 @@ msgstr "" #: ../../content/administration/install/online.rst:14 #: ../../content/administration/maintain/domain_names.rst:166 #: ../../content/administration/maintain/domain_names.rst:236 -#: ../../content/administration/maintain/supported_versions.rst:31 -#: ../../content/administration/upgrade/odoo_online.rst:3 +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:92 +#: ../../content/administration/upgrade.rst:309 msgid "Odoo Online" msgstr "" @@ -975,7 +992,7 @@ msgstr "" #: ../../content/administration/install/packages.rst:57 #: ../../content/administration/install/source.rst:412 -msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.5 `_ for it to support headers and footers. Check out the `wkhtmltopdf wiki `_ for more details on the various versions." +msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.6 `_ for it to support headers and footers. Check out the `wkhtmltopdf wiki `_ for more details on the various versions." msgstr "" #: ../../content/administration/install/packages.rst:63 @@ -1982,9 +1999,10 @@ msgstr "" #: ../../content/administration/maintain/domain_names.rst:171 #: ../../content/administration/maintain/domain_names.rst:250 -#: ../../content/administration/maintain/supported_versions.rst:32 +#: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/odoo_sh.rst:5 -#: ../../content/administration/upgrade/odoo_sh.rst:3 +#: ../../content/administration/upgrade.rst:122 +#: ../../content/administration/upgrade.rst:320 msgid "Odoo.sh" msgstr "" @@ -3004,7 +3022,7 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:293 #: ../../content/administration/odoo_sh/getting_started/settings.rst:77 #: ../../content/administration/odoo_sh/getting_started/settings.rst:113 -#: ../../content/administration/upgrade.rst:10 +#: ../../content/administration/upgrade.rst:3 msgid "Upgrade" msgstr "" @@ -3013,7 +3031,7 @@ msgid "Trigger a database upgrade." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:33 -msgid "For more information about the upgrade process, check out the :doc:`Odoo Online upgrade documentation <../upgrade/odoo_online>`." +msgid "For more information about the upgrade process, check out the :ref:`Odoo Online upgrade documentation `." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:39 @@ -3309,70 +3327,64 @@ 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/supported_versions.rst:6 -#: ../../content/administration/upgrade.rst:208 +#: ../../content/administration/maintain/supported_versions.rst:7 msgid "Supported versions" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:8 +#: ../../content/administration/maintain/supported_versions.rst:9 msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:11 +#: ../../content/administration/maintain/supported_versions.rst:12 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 +#: ../../content/administration/maintain/supported_versions.rst:16 msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:16 +#: ../../content/administration/maintain/supported_versions.rst:17 msgid "Online versions are *not* released for Odoo.sh and On-Premise installations." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:17 +#: ../../content/administration/maintain/supported_versions.rst:18 msgid "Online versions are listed below as *SaaS*." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:20 -msgid "What's the support status of my Odoo?" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:22 msgid "This matrix shows the support status of every version." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:24 +#: ../../content/administration/maintain/supported_versions.rst:22 msgid "**Major releases are in bold type.**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:33 -#: ../../content/administration/upgrade/on_premise.rst:3 +#: ../../content/administration/maintain/supported_versions.rst:31 msgid "On-Premise" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:34 +#: ../../content/administration/maintain/supported_versions.rst:32 msgid "Release date" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:33 msgid "End of support" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:36 -msgid "Odoo saas~16.4" +#: ../../content/administration/maintain/supported_versions.rst:34 +msgid "**Odoo 17.0**" msgstr "" +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:36 #: ../../content/administration/maintain/supported_versions.rst:37 -#: ../../content/administration/maintain/supported_versions.rst:61 -#: ../../content/administration/maintain/supported_versions.rst:62 -#: ../../content/administration/maintain/supported_versions.rst:63 -#: ../../content/administration/maintain/supported_versions.rst:79 -#: ../../content/administration/maintain/supported_versions.rst:80 -#: ../../content/administration/maintain/supported_versions.rst:81 +#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:65 +#: ../../content/administration/maintain/supported_versions.rst:66 +#: ../../content/administration/maintain/supported_versions.rst:67 +#: ../../content/administration/maintain/supported_versions.rst:83 +#: ../../content/administration/maintain/supported_versions.rst:84 #: ../../content/administration/maintain/supported_versions.rst:85 -#: ../../content/administration/maintain/supported_versions.rst:86 -#: ../../content/administration/maintain/supported_versions.rst:87 #: ../../content/administration/odoo_sh/getting_started/settings.rst:58 #: ../../content/administration/odoo_sh/getting_started/settings.rst:59 #: ../../content/administration/odoo_sh/getting_started/settings.rst:62 @@ -3404,161 +3416,172 @@ msgid "|green|" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:93 +msgid "November 2023" +msgstr "" + #: ../../content/administration/maintain/supported_versions.rst:39 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:45 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:51 -#: ../../content/administration/maintain/supported_versions.rst:56 -#: ../../content/administration/maintain/supported_versions.rst:57 -#: ../../content/administration/maintain/supported_versions.rst:68 -#: ../../content/administration/maintain/supported_versions.rst:69 -#: ../../content/administration/maintain/supported_versions.rst:74 -#: ../../content/administration/maintain/supported_versions.rst:75 -msgid "N/A" +msgid "November 2026 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:40 -msgid "August 2023" +msgid "Odoo saas~16.4" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:42 -msgid "Odoo saas~16.3" +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:60 +#: ../../content/administration/maintain/supported_versions.rst:61 +#: ../../content/administration/maintain/supported_versions.rst:72 +#: ../../content/administration/maintain/supported_versions.rst:73 +#: ../../content/administration/maintain/supported_versions.rst:78 +#: ../../content/administration/maintain/supported_versions.rst:79 +msgid "N/A" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:43 -#: ../../content/administration/maintain/supported_versions.rst:49 -#: ../../content/administration/maintain/supported_versions.rst:55 -#: ../../content/administration/maintain/supported_versions.rst:67 -#: ../../content/administration/maintain/supported_versions.rst:73 -#: ../../content/administration/maintain/supported_versions.rst:91 -#: ../../content/administration/maintain/supported_versions.rst:92 -#: ../../content/administration/maintain/supported_versions.rst:93 -msgid "|red|" +#: ../../content/administration/maintain/supported_versions.rst:44 +msgid "August 2023" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:46 +msgid "Odoo saas~16.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:53 +#: ../../content/administration/maintain/supported_versions.rst:59 +#: ../../content/administration/maintain/supported_versions.rst:71 +#: ../../content/administration/maintain/supported_versions.rst:77 +#: ../../content/administration/maintain/supported_versions.rst:89 +#: ../../content/administration/maintain/supported_versions.rst:90 +#: ../../content/administration/maintain/supported_versions.rst:91 +#: ../../content/administration/maintain/supported_versions.rst:95 +#: ../../content/administration/maintain/supported_versions.rst:96 +#: ../../content/administration/maintain/supported_versions.rst:97 +#: ../../content/administration/maintain/supported_versions.rst:101 +#: ../../content/administration/maintain/supported_versions.rst:102 +#: ../../content/administration/maintain/supported_versions.rst:103 +msgid "|red|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:50 msgid "June 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:52 msgid "Odoo saas~16.2" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:56 msgid "March 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:58 msgid "Odoo saas~16.1" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:62 msgid "February 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:60 +#: ../../content/administration/maintain/supported_versions.rst:64 msgid "**Odoo 16.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:64 -#: ../../content/administration/maintain/supported_versions.rst:95 +#: ../../content/administration/maintain/supported_versions.rst:68 +#: ../../content/administration/maintain/supported_versions.rst:99 msgid "October 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:65 -msgid "October 2025 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:66 -msgid "Odoo saas~15.2" +#: ../../content/administration/maintain/supported_versions.rst:69 +msgid "November 2025 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:70 +msgid "Odoo saas~15.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:74 msgid "March 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:71 +#: ../../content/administration/maintain/supported_versions.rst:75 msgid "January 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:72 +#: ../../content/administration/maintain/supported_versions.rst:76 msgid "Odoo saas~15.1" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:76 +#: ../../content/administration/maintain/supported_versions.rst:80 msgid "February 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:77 +#: ../../content/administration/maintain/supported_versions.rst:81 msgid "July 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:78 +#: ../../content/administration/maintain/supported_versions.rst:82 msgid "**Odoo 15.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:82 +#: ../../content/administration/maintain/supported_versions.rst:86 msgid "October 2021" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:83 -msgid "October 2024 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:84 -msgid "**Odoo 14.0**" +#: ../../content/administration/maintain/supported_versions.rst:87 +msgid "November 2024 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:88 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:92 msgid "October 2020" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:89 -msgid "November 2023 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:90 +#: ../../content/administration/maintain/supported_versions.rst:94 msgid "**Odoo 13.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:94 +#: ../../content/administration/maintain/supported_versions.rst:98 msgid "October 2019" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:99 -msgid "|green| Supported version" +#: ../../content/administration/maintain/supported_versions.rst:100 +msgid "Older versions" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:101 -msgid "|red| End-of-support" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:103 -msgid "N/A Never released for this platform" +#: ../../content/administration/maintain/supported_versions.rst:104 +msgid "Before 2019" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:105 -msgid "šŸ Future version, not released yet" +msgid "Before 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:107 +msgid "Legend" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:109 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:111 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:113 +msgid "N/A Never released for this platform" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:116 -msgid "I run an older version of Odoo/OpenERP/TinyERP" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:118 -msgid "Odoo 12.0, 11.0, 10.0, 9.0, and 8.0 are not supported anymore, on any platform." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:120 -msgid "OpenERP 7.0, 6.1, 6.0 and 5.0 are not supported anymore, on any platform." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:122 -msgid "TinyERP 4.0, 3.0, 2.0 and 1.0 are not supported anymore, on any platform." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:124 msgid "Even though we don't support older versions, you can always `upgrade from any version `_." msgstr "" @@ -3727,7 +3750,6 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:6 #: ../../content/administration/odoo_sh/getting_started/status.rst:6 #: ../../content/administration/odoo_sh/overview.rst:5 -#: ../../content/administration/upgrade/odoo_sh.rst:8 msgid "Overview" msgstr "" @@ -4418,7 +4440,7 @@ msgid "Available for production and staging branches for valid projects." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:298 -msgid ":doc:`Upgrade - Odoo.sh <../../upgrade/odoo_sh>`" +msgid ":doc:`Upgrade documentation <../../upgrade>`" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:303 @@ -5960,958 +5982,511 @@ msgstr "" msgid "The documentation will help you go live with your Odoo.sh project in no time." msgstr "" -#: ../../content/administration/upgrade.rst:20 -msgid "An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0)." +#: ../../content/administration/upgrade.rst:7 +msgid "An upgrade is the process of moving your database from an older version to a newer :doc:`supported version ` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes with new and improved features, bug fixes, and security patches." msgstr "" -#: ../../content/administration/upgrade.rst:22 -msgid "An upgrade does not cover:" -msgstr "" - -#: ../../content/administration/upgrade.rst:24 -msgid "Changing :ref:`editions ` (i.e., Community to Enterprise edition)" -msgstr "" - -#: ../../content/administration/upgrade.rst:25 -msgid "Switching :ref:`hosting type ` (i.e., On-Premise to Odoo Online or Odoo.sh)" -msgstr "" - -#: ../../content/administration/upgrade.rst:27 -msgid "Migration from another ERP to Odoo" -msgstr "" - -#: ../../content/administration/upgrade.rst:29 -#: ../../content/administration/upgrade.rst:148 -#: ../../content/administration/upgrade.rst:259 -#: ../../content/administration/upgrade/faq.rst:81 -#: ../../content/administration/upgrade/faq.rst:92 -#: ../../content/administration/upgrade/faq.rst:119 -msgid "|assistance-contact|" -msgstr "" - -#: ../../content/administration/upgrade.rst:32 -msgid ":ref:`upgrade/sla`" -msgstr "" - -#: ../../content/administration/upgrade.rst:37 -msgid "Process workflow" -msgstr "" - -#: ../../content/administration/upgrade.rst:39 -msgid "The upgrade process in a nutshell:" -msgstr "" - -#: ../../content/administration/upgrade.rst:41 -msgid "You create a test upgrade request." -msgstr "" - -#: ../../content/administration/upgrade.rst:42 -msgid "Odoo processes the request automatically by running the database through an upgrade script, which takes between 20 and 120 minutes." -msgstr "" - -#: ../../content/administration/upgrade.rst:44 -msgid "Odoo delivers a test database." -msgstr "" - -#: ../../content/administration/upgrade.rst:45 -msgid "You test your database for possible discrepancies (see :ref:`upgrade/test-guidance`)." -msgstr "" - -#: ../../content/administration/upgrade.rst:46 -msgid "If there are any discrepancies, you report them to the Upgrade support team via the help portal (see :ref:`upgrade/test-assistance`)." -msgstr "" - -#: ../../content/administration/upgrade.rst:48 -msgid "We fix the issues and send you a new test database." -msgstr "" - -#: ../../content/administration/upgrade.rst:49 -msgid "Once you have completed the testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the production upgrade." -msgstr "" - -#: ../../content/administration/upgrade.rst:52 -msgid "Odoo delivers the production database through the automated process." -msgstr "" - -#: ../../content/administration/upgrade.rst:53 -msgid "You restore it in your Production environment a few short hours later and continue working on the newly upgraded database (this is done automatically on Odoo Online)." -msgstr "" - -#: ../../content/administration/upgrade.rst:57 -msgid ":doc:`Upgrade process for Odoo Online `" -msgstr "" - -#: ../../content/administration/upgrade.rst:58 -msgid ":doc:`Upgrade process for Odoo.sh `" -msgstr "" - -#: ../../content/administration/upgrade.rst:59 -msgid ":doc:`Upgrade process for On-Premise `" -msgstr "" - -#: ../../content/administration/upgrade.rst:64 -msgid "Testing" -msgstr "" - -#: ../../content/administration/upgrade.rst:66 -msgid "This phase allows you to review an upgraded version of your database without affecting your production database in any way. We suggest that you run the test upgrade process at least once, but you can do it as many times as you need (one at a time)." -msgstr "" - -#: ../../content/administration/upgrade.rst:70 -msgid "Once you receive your upgraded test database, check that all data, processes, and functionality are still correct and working as expected." -msgstr "" - -#: ../../content/administration/upgrade.rst:73 -msgid "If you do find discrepancies, :ref:`report your issues ` and :ref:`request a new test database ` when the reported issues are fixed in the upgrade script." -msgstr "" - -#: ../../content/administration/upgrade.rst:77 -msgid "If you do not find any discrepancies, you can move on to the upgrade of your production database." -msgstr "" - -#: ../../content/administration/upgrade.rst:80 -msgid "A test database is only intended for testing and remains completely unrelated to your present or future production database. Any data you add, or changes you make, will not be reflected in your upgraded production database." -msgstr "" - -#: ../../content/administration/upgrade.rst:85 -msgid "Test databases are neutered and features are disabled to prevent them from having an impact on the production database:" -msgstr "" - -#: ../../content/administration/upgrade.rst:88 -msgid "The serial number of the database is modified (to prevent it from sending information as if it was the production database)." -msgstr "" - -#: ../../content/administration/upgrade.rst:90 -msgid "The :ref:`base URL of the database ` is reset to ``http://localhost:8069`` and the email domain to ``localhost``." -msgstr "" - -#: ../../content/administration/upgrade.rst:92 -msgid "Scheduled actions are disabled (the calendar synchronization, the bank statement synchronization, the planned automated actions, the fetching of incoming mail servers, etc.)." -msgstr "" - -#: ../../content/administration/upgrade.rst:94 -msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake/non-working one." -msgstr "" - -#: ../../content/administration/upgrade.rst:96 -msgid "Payment providers and delivery carriers are reset to test environment." -msgstr "" - -#: ../../content/administration/upgrade.rst:97 -msgid "Accounting localization Electronic Data Interchange (EDI) services are disabled." -msgstr "" - -#: ../../content/administration/upgrade.rst:98 -msgid "A system parameter is set to tell the database has been neutered." -msgstr "" - -#: ../../content/administration/upgrade.rst:103 -msgid "Request a test database" -msgstr "" - -#: ../../content/administration/upgrade.rst:105 -msgid "Follow the instructions available per hosting type on the `website form `_ and select *Testing* purpose." -msgstr "" - -#: ../../content/administration/upgrade.rst:-1 -msgid "Selection of the \"Testing\" purpose in the upgrade form on Odoo" -msgstr "" - -#: ../../content/administration/upgrade.rst:115 -msgid "Test guidance" -msgstr "" - -#: ../../content/administration/upgrade.rst:117 -msgid "Every business and organization has its own operational needs and has to test its specific Odoo database individually. We recommend you look at `the test scenario `_ for further information." -msgstr "" - -#: ../../content/administration/upgrade.rst:122 -msgid "Todo" -msgstr "" - -#: ../../content/administration/upgrade.rst:122 -msgid "change link \"test scenario\" once the related doc is published" -msgstr "" - -#: ../../content/administration/upgrade.rst:127 -#: ../../content/administration/upgrade.rst:172 -msgid "Assistance" -msgstr "" - -#: ../../content/administration/upgrade.rst:129 -msgid "If you encounter an issue in the **test database**, please get in touch with Odoo Upgrade Support via the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade.rst:132 -msgid "Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type." +#: ../../content/administration/upgrade.rst:15 +msgid "The Rolling Release process allows Odoo Online customers to upgrade their database directly from a message prompt sent to the database administrator as soon as a new version is released. The invitation to upgrade is only sent if no issues are detected during the automatic tests." msgstr "" #: ../../content/administration/upgrade.rst:0 -msgid "Selection of \"An issue related to my upgrade\" as Ticket Type in the support form on Odoo" +msgid "The upgrade message prompt on the top right of the database" 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." +#: ../../content/administration/upgrade.rst:22 +msgid "It is strongly recommended to manually :ref:`test the upgrade first `. Clicking :guilabel:`I want to test first` redirects to `the database manager `_, where it is possible to request an upgraded test database and check it for any discrepancies." msgstr "" -#: ../../content/administration/upgrade.rst:142 -#: ../../content/administration/upgrade.rst:185 -msgid "Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue). This will avoid clarifying questions and speed up the resolution process significantly." +#: ../../content/administration/upgrade.rst:27 +msgid "It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it immediately triggers the live production database upgrade." msgstr "" -#: ../../content/administration/upgrade.rst:146 -msgid "The purpose of the test phase is not to correct existing data or configurations in your database." +#: ../../content/administration/upgrade.rst:30 +msgid "If the Rolling Release process detects an issue with the upgrade, it will be deactivated until the issue is resolved." msgstr "" -#: ../../content/administration/upgrade.rst:153 -msgid "The production launch" +#: ../../content/administration/upgrade.rst:33 +msgid "An upgrade does not cover:" msgstr "" -#: ../../content/administration/upgrade.rst:155 -msgid "The production upgrade request is when you decide to upgrade your current database with all your production data (invoices, VAT returns, inventories, current orders) to a new version of your choice." +#: ../../content/administration/upgrade.rst:35 +msgid "Downgrading to a previous version of Odoo" msgstr "" -#: ../../content/administration/upgrade.rst:159 -msgid "After your :ref:`tests ` are completed to your satisfaction, submit the request to upgrade your production database via our `website form `_. Select *Production* purpose." +#: ../../content/administration/upgrade.rst:36 +msgid ":doc:`Switching editions ` (e.g., from Community to Enterprise)" msgstr "" -#: ../../content/administration/upgrade.rst:164 -msgid "Going into production without first testing may lead to:" +#: ../../content/administration/upgrade.rst:37 +msgid ":doc:`Changing hosting type ` (e.g., from on-premise to Odoo Online)" msgstr "" -#: ../../content/administration/upgrade.rst:166 -msgid "business interruptions (e.g., no longer having the possibility to validate an action)" +#: ../../content/administration/upgrade.rst:39 +msgid "Migrating from another ERP to Odoo" msgstr "" -#: ../../content/administration/upgrade.rst:167 -msgid "poor customer experiences (e.g., an eCommerce website that does not work correctly)" +#: ../../content/administration/upgrade.rst:42 +msgid "If your database contains a **custom module**, you must first upgrade its source code to be compatible with the new version of Odoo **before upgrading**." msgstr "" -#: ../../content/administration/upgrade.rst:174 -msgid "If you encounter issues or problems in the **production database**, please get in touch with **Odoo Support**:" +#: ../../content/administration/upgrade.rst:49 +msgid "Upgrading in a nutshell" msgstr "" -#: ../../content/administration/upgrade.rst:177 -msgid "Connect to our `Odoo Support page `_." +#: ../../content/administration/upgrade.rst:51 +msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database `)." msgstr "" -#: ../../content/administration/upgrade.rst:178 -msgid "Under the *Ticket Description* section, select the appropriate type related to your issue but **do not select** the option *An issue related to my upgrade*." +#: ../../content/administration/upgrade.rst:54 +msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database `)." msgstr "" -#: ../../content/administration/upgrade.rst:182 -msgid "After upgrading to production, the support will be provided by the Support team instead of the Upgrade team." +#: ../../content/administration/upgrade.rst:57 +msgid "Report any issue encountered during the testing to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:189 -msgid "If you choose *An issue related to my upgrade* as ticket type, the request will be redirected to another team than the support one and will slow down the processing and response time." +#: ../../content/administration/upgrade.rst:60 +msgid "(If applicable) : upgrade the source code of your custom module to be compatible with the new version of Odoo." msgstr "" -#: ../../content/administration/upgrade.rst:195 -msgid "Help" +#: ../../content/administration/upgrade.rst:63 +msgid "Once all issues are resolved and you are confident that the upgraded database can be used as your main database without any issues, plan the upgrade of your production database." msgstr "" -#: ../../content/administration/upgrade.rst:200 -msgid "Contact our upgrade service support" +#: ../../content/administration/upgrade.rst:66 +msgid "Request the upgrade for the production database, rendering it unavailable for the time it takes to complete the process (see :ref:`upgrading the production database `)." msgstr "" -#: ../../content/administration/upgrade.rst:202 -msgid "Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo Upgrade Team `_. We will be happy to answer it as soon as possible." +#: ../../content/administration/upgrade.rst:69 +msgid "Report any issue encountered during the upgrade to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:210 -msgid "Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo." +#: ../../content/administration/upgrade.rst:78 +msgid "Obtaining an upgraded test database" msgstr "" -#: ../../content/administration/upgrade.rst:213 -msgid "This is a factor to take into consideration before upgrading. If you are on an older version, we suggest you to prefer the most recent version to benefit from longer support (before having to upgrade again)." +#: ../../content/administration/upgrade.rst:80 +msgid "The `Upgrade page `_ is the main platform for requesting an upgraded database. However, depending on the hosting type, you can upgrade from the command line (on-premise), the `Odoo Online database manager `_, or your `Odoo.sh project `_." msgstr "" -#: ../../content/administration/upgrade.rst:218 -msgid ":doc:`maintain/supported_versions`" +#: ../../content/administration/upgrade.rst:86 +msgid "The Upgrade platform follows the same `Privacy Policy `_ as the other Odoo.com services. Visit the `General Data Protection Regulation page `_ to learn more about how Odoo handles your data and privacy." msgstr "" -#: ../../content/administration/upgrade.rst:223 -msgid "Service-level agreement (SLA)" +#: ../../content/administration/upgrade.rst:94 +msgid "Odoo Online databases can be manually upgraded via the `database manager `_." msgstr "" -#: ../../content/administration/upgrade.rst:225 -msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database." +#: ../../content/administration/upgrade.rst:97 +msgid "The database manager displays all databases associated with the user's account. Databases not on the most recent version of Odoo display an arrow in a circle icon next to their name, indicating that they can be upgraded." msgstr "" -#: ../../content/administration/upgrade.rst:228 -msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement `. However, this section clarifies what upgrade services you can expect." +#: ../../content/administration/upgrade.rst:0 +msgid "The database manager with an upgrade button next to the name of a database." msgstr "" -#: ../../content/administration/upgrade.rst:233 -msgid "Upgrade services covered by the SLA" +#: ../../content/administration/upgrade.rst:104 +msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:" msgstr "" -#: ../../content/administration/upgrade.rst:235 -msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:" +#: ../../content/administration/upgrade.rst:106 +msgid "The **version** of Odoo you want to upgrade to, usually the latest version" msgstr "" -#: ../../content/administration/upgrade.rst:238 -msgid "the upgrade of all **standard applications**;" +#: ../../content/administration/upgrade.rst:107 +msgid "The **email** address that should receive the link to the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:239 -msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and" +#: ../../content/administration/upgrade.rst:108 +msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request" msgstr "" -#: ../../content/administration/upgrade.rst:241 -msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." msgstr "" -#: ../../content/administration/upgrade.rst:244 -msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade." +#: ../../content/administration/upgrade.rst:114 +msgid "The :guilabel:`Upgrade in progress` tag is displayed next to the database name until completion. Once the process succeeds, an email containing a link to the upgraded test database is sent to the address provided. The database can also be accessed from the database manager by clicking the dropdown arrow before the database name." msgstr "" -#: ../../content/administration/upgrade.rst:248 -msgid "Upgrade services not covered by the SLA" +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." msgstr "" -#: ../../content/administration/upgrade.rst:250 -msgid "The following upgrade-related services are **not** included:" +#: ../../content/administration/upgrade.rst:124 +msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process." msgstr "" -#: ../../content/administration/upgrade.rst:252 -msgid "the **cleaning** of pre-existing data and configurations while upgrading;" -msgstr "" - -#: ../../content/administration/upgrade.rst:253 -msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" -msgstr "" - -#: ../../content/administration/upgrade.rst:254 -msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code `; and" -msgstr "" - -#: ../../content/administration/upgrade.rst:257 -msgid "**training** on using the upgraded version's features and workflows." -msgstr "" - -#: ../../content/administration/upgrade.rst:262 -msgid ":doc:`Upgrade FAQ `" -msgstr "" - -#: ../../content/administration/upgrade.rst:263 -msgid ":doc:`Odoo.sh documentation `" -msgstr "" - -#: ../../content/administration/upgrade.rst:264 -msgid ":doc:`Supported Odoo versions `" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:8 -msgid "FAQ" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:13 -msgid "Why upgrade" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:15 -msgid "You benefit from the latest features of the :ref:`new major version ` released by Odoo." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:17 -msgid "If you are in an :ref:`unsupported version `, you get a new version with support." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:23 -msgid "When to upgrade" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:25 -msgid "Whenever you want. You can make your upgrade request as soon as a new version is released or when your version turns unsupported, and you still wish to enjoy support." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:31 -msgid "Availability of the new version" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:33 -msgid "As soon as Odoo announces the release of a new major version, you can create a test upgrade request to try the latest version. Please note that at this point, the upgrade scripts will only have been tested with demo data. Please report any issue you might encounter while testing via the `Odoo Support page `_ and make sure to be happy with your test version before requesting the upgrade of your database in production." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:42 -msgid "Duration of the upgrade" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:44 -msgid "It is impossible to give time estimates for every upgrade request." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:46 -msgid "In general, the \"smaller\" the database, the quickest the upgrade request is completed. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase, and Manufacturing." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:50 -msgid "You can expect the time it takes for the platform to upgrade the test database to be similar to the production upgrade." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:56 -msgid "Duration of the upgrade project" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:58 -msgid "It depends on the user involvement (the time spent on testing, reporting problems, etc.) and the issues encountered that might need to be addressed by our technical team." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:61 -msgid "So, in a nutshell, what can impact your upgrade lead time?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:63 -msgid "Source & targeted versions" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:64 -msgid "Installed apps" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:65 -msgid "Volume of data" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:66 -msgid "Amount of customization (models, fields, methods, workflows, reports, website, etc.)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:67 -msgid "Installation of new apps or configuration changes after the start of the test phase" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:68 -msgid "User commitment" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:73 -msgid "Upgrade of the custom modules" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:75 -msgid "As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional service is subject to additional fees." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:78 -msgid "Depending on your situation, the custom code could be upgraded by our services, by one of our partners, or you can do it yourself." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:86 -msgid "Upgrade or Migration" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:88 -msgid "An upgrade is switching to a newer version of Odoo, while a migration reflects the change of :ref:`editions ` or change of :ref:`hosting type `." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:97 -msgid "Editions change (from Community to Enterprise)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:99 -msgid "The upgrade always returns an Enterprise edition of Odoo, whether the database you sent was a community or enterprise edition. It is required to have an enterprise subscription to upgrade." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:103 -msgid "If you need assistance on this matter, please contact us via the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:107 -msgid "`Editions `_" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:112 -msgid "Switching the hosting types (On-premise vs. Odoo Online vs. Odoo.sh)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:114 -msgid "An upgrade does not cover a change of `Hosting types `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:116 -msgid "Open the following link to get :doc:`more information about how to change your hosting type <../maintain/hosting_changes>`." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:124 -msgid "The Upgrade Report" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:126 -msgid "When an upgrade request completes successfully (test or production), you receive an email notification about it that includes an 'Upgrade Report'. This report is also sent to you via the Discuss app. It contains valuable information regarding changes that occurred during the upgrade. While it serves as a guide to possible issues to look out for, it is not an exhaustive list. It remains imperative that you test the upgraded database thoroughly and report any discrepancies you might find, before you decide to upgrade your production database." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:136 -msgid "Custom views" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:138 -msgid "During the upgrade, some custom views might get disabled for technical reasons. Therefore they might have to be fixed after the upgrade. The :ref:`Upgrade Report ` that is generated after the upgrade is available in the Discuss app, and lists all the custom views that might be impacted by this." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:146 -msgid "Release Notes by version" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:148 -msgid "Open our `Release Note `_ page to get a summary of the new features and improvements made in each version." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:152 -msgid "How long is my test available for" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:154 -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 -msgid "How many tests to perform before upgrading to production?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:160 -msgid "As many as needed. When you are comfortable with the database, run a last test upgrade 48 hours before requesting your production upgrade and test your workflows one last time." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:164 -msgid "How to/Where to report upgrade issues?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:166 -msgid "If you encounter issues during the upgrade process, please contact the Odoo Support through the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:169 -msgid "To report an issue discovered during the testing phase, please select **An issue related to my upgrade (test phase)**." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:171 -msgid "To report an issue discovered post-upgrade, please select **An issue related to my upgrade (production)**." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:175 -msgid "Upgrading to production" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:177 -msgid "Once you have completed testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the production upgrade." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:182 -msgid "How is my data handled in the Upgrade Platform?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:184 -msgid "The Odoo Upgrade platform uses the same Privacy Policy as the rest of Odoo.com services." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:186 -msgid "Your data is hosted on servers that follow our security guidelines, namely:" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:188 -msgid "SSL - All web connections to client instances are protected with 256-bit SSL encryption (HTTPS with a 2048-bit modulus SSL certificate), and running behind Grade A SSL stacks. All our certificate chains are using SHA-2 already." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:191 -msgid "Safe System - Our servers are running recent Linux distribution with up-to-date security patches, with firewall and intrusion countermeasures (not disclosed for obvious reasons)." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:194 -msgid "Servers are located at the same locations as our Cloud providers with the following services:" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:196 -msgid "Restricted perimeter, physically accessed by authorized data center employees only" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:197 -msgid "Physical access control with security badges or biometrical security" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:198 -msgid "Security cameras monitoring the data center locations 24/7" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:199 -msgid "Security personnel on-site 24/7" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:201 -msgid "The uploaded and migrated databases uploaded to the Upgrade platform are kept for up to 3 months and are permanently deleted following that period." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:204 -msgid "You can learn more about privacy and data handling at Odoo by visiting our `General Data Protection Regulation page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:208 -msgid "Rolling Release (applicable to Odoo Online databases)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:210 -msgid "This feature allows customers to upgrade their database directly from a message prompt sent to the database administrator as soon as the new version is released. Odoo first tests the upgrade to the next version. The rolling release upgrade option is displayed if the automated tests are successful. The message offers two options:" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:215 -msgid "To 'Upgrade Now', which immediately triggers the upgrade of your live production database." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:217 -msgid "To take you to your `database manager `_ where you can `request an upgraded test database `_ and check the upgraded test database for any discrepancies." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:221 -msgid "When you choose to proceed with the production upgrade directly, make sure all users have saved their work and are logged out. The upgrade takes approximately 15 minutes. During this time your database is unreachable. If you notice any problem after the upgrade, please report it via the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:227 -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:5 -msgid "Odoo databases can be manually upgraded directly from the main Odoo website. To upgrade an Odoo database, navigate to the `database manager `_ page and sign in." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:8 -msgid "The database manager page displays all of the Odoo databases associated with the user's account. Any databases that are not already on the most recent version of Odoo display an **arrow in a circle** icon next to the database name, indicating that the database can be upgraded." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "The database manager page with an upgrade button next to the name of a database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:17 -msgid "If the database's version is **lower** than the latest major release: the database must be upgraded within two months. After these two months, an automatic upgrade is initiated." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:19 -msgid "If the database's version is **equal** to or **higher** than the latest major release: you can disregard the invitation to upgrade, as the database probably would not benefit from new features every two months." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:23 -msgid "If a database is *not* on the latest online version, its administrator should receive an invitation to upgrade on the database's dashboard, displayed as an **arrow in a circle**." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "Invitation to upgrade on the database dashboard." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:30 -msgid "Versions that are not supported anymore become deprecated and must be updated to avoid security issues. It is recommended to initiate the upgrade yourself and not wait for the automatic upgrade, as the former method allows you to request a test upgrade of the database to check for any discrepancies." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:36 -msgid "Test database" -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:38 -msgid "Click on the **arrow in a circle** icon to start the upgrade process. On the :guilabel:`Upgrade your database` pop-up, select the version of Odoo that the platform will be upgraded to. In the :guilabel:`Email to notify` field, enter an email address that will receive email notifications about the database upgrade." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:43 -msgid "There is also a :guilabel:`Purpose` section on the pop-up that is used to specify the reason for the upgrade. However, at this stage of the process, the only selectable option is :guilabel:`Test`, as Odoo requires users to create a test copy of the upgraded database before converting the actual database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "The \"Upgrade your database\" pop-up." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:52 -msgid "After filling out the form, click the :guilabel:`Upgrade` button. The pop-up disappears and the database being upgraded shows a red :guilabel:`Upgrade in progress` tag next to its name. An email confirming that the upgrade is in progress is also sent to the email address specified on the pop-up." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "The \"Upgrade in progress\" tag next to the database name." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:61 -msgid "Once the upgrade is complete, a new test database appears on the `database manager `_ page. To access the test database, click the drop-down arrow (:guilabel:`āƆ`) to the left of the main database's name. Doing so makes the test version appear below it. Finally, click the green :guilabel:`Connect` button on the right side of the test version's row to go to the database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "A test database on the database manager page." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:71 -msgid "Except for being on the newer version of Odoo, the test database is an exact copy of the one being upgraded. It is important to do extensive testing in this database to ensure that the upgrade has not altered or corrupted any data, and that all workflows still proceed as expected." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:76 -msgid "Production database" -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:78 -msgid "After confirming the integrity of the new version, return to the `database manager `_ page. Once again, click on the **arrow in a circle** icon next to the database being upgraded. The :guilabel:`Upgrade your database` pop-up appears as before, except that there is now a :guilabel:`Production` option under the :guilabel:`Purpose` section." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:83 -msgid "Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` to begin the upgrade process. As before, a notification email is sent to the email address provided and a red :guilabel:`Upgrade in progress` tag appears next to the name of the database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:87 -msgid "The production database is then taken offline and will be upgraded automatically. The time it takes to upgrade the production database should be similar to the time that was necessary to upgrade the test database. Make sure to inform database users of the scheduled downtime." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:91 -msgid "After the upgrade is finished, the :guilabel:`Upgrade in progress` tag disappears and the database is upgraded to the version specified." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:10 -msgid "Odoo.sh is integrated with the upgrade platform to make the upgrade process easier." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:13 -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:-1 -msgid "Click on the upgrade menu" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:20 -msgid "The suggested upgrade steps on Odoo.sh are:" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:22 -msgid "On a :guilabel:`Development` branch, upgrade your custom modules to keep them compatible with the new version and thoroughly **test them**." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:24 -msgid "Switch that branch to the :guilabel:`Staging` branch, **upgrade** the last daily production backup and **test it**. Write upgrade scripts if necessary." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:26 -msgid "Trigger the production upgrade from your :guilabel:`Production` branch and sit tight." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:29 -msgid ":doc:`../../administration/upgrade`" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:30 -msgid ":doc:`Upgrade FAQ <../upgrade/faq>`" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:31 -msgid ":doc:`Introduction to Odoo.sh <../odoo_sh/overview/introduction>`" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:36 -msgid "Upgrade your custom modules" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:38 -msgid "The first step is to upgrade your custom modules to keep them compatible with the new version. Fork your :guilabel:`Production` branch in the :guilabel:`Development` stage, then go to the settings of your :guilabel:`Development` branch and select the Odoo version you target. If needed, modify your code to be compatible with the new version. Make sure to **test** your features are still working correctly." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:45 -msgid "Depending on your contract, the upgrade of your custom modules can be done by yourself, by your Partner or by Odoo (if you hold a subscription including maintenance of customizations)." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:51 -msgid "Upgrade your database on a staging branch" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:53 -msgid "Take the upgraded development branch and drag & drop it to :guilabel:`Staging`." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:55 -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:-1 +#: ../../content/administration/upgrade.rst:0 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." +#: ../../content/administration/upgrade.rst:129 +msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform `_." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:66 -msgid "You can follow the upgrade process by going to the :guilabel:`Upgrade` menu of your :guilabel:`Production` branch." +#: ../../content/administration/upgrade.rst:132 +msgid "Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is put in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup and an **update of all the custom modules** occur. This allows you to test your custom modules on a pristine copy of the upgraded database. The log file of the upgrade process can be found in your newly upgraded staging build by going to :file:`~/logs/upgrade.log`." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:69 -msgid "When the upgraded backup is ready on the `upgrade platform `_, it is automatically downloaded back to your project." +#: ../../content/administration/upgrade.rst:140 +msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. If there are none, the \"update on commit\" mode is skipped, the upgraded database is built as soon as it is transferred from the upgrade platform, and the upgrade mode is exited." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:72 -msgid "The branch is now in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup occurs, and an **update of all the custom modules** happens. This allows you to quickly iterate on your custom modules upgrade scripts. The log file of the upgrade process can be found at :file:`~/logs/upgrade.log` in your newly upgraded staging build." +#: ../../content/administration/upgrade.rst:152 +#: ../../content/administration/upgrade.rst:344 +msgid "On-premise" msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:78 -msgid "The **special upgrade mode** is automatically closed after 30 days." +#: ../../content/administration/upgrade.rst:154 +msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:" msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:79 -#: ../../content/administration/upgrade/odoo_sh.rst:128 -msgid "It may happen that custom modules are no longer needed after an upgrade. Custom modules in the upgraded database are set to be updated. If the modules are missing in the code, the update fails, thus failing the whole process. An empty module with a manifest and possibly some custom upgrade script are necessary to clean up the database. The complete removal of the module has to be handled afterwards." +#: ../../content/administration/upgrade.rst:161 +msgid "The following command can be used to display the general help and the main commands:" msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:86 -msgid "Functionally test your upgraded database" +#: ../../content/administration/upgrade.rst:167 +msgid "An upgraded test database can also be requested via the `Upgrade page `_." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:88 -msgid "Now that the test upgraded database is available on your staging branch, **thoroughly test it** and make sure everything runs as it's supposed to. Once you are satisfied with the result, you are ready to upgrade your production database." +#: ../../content/administration/upgrade.rst:171 +msgid "For security reasons, only the person who submitted the upgrade request can download it." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:93 -msgid "Production upgrade" +#: ../../content/administration/upgrade.rst:172 +msgid "For storage reasons, the database's copy is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:95 -msgid "Once you are happy with your testing, you can start the process on the :guilabel:`Production` branch." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:98 -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:-1 -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 "" - -#: ../../content/administration/upgrade/odoo_sh.rst:110 -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:-1 -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 "" - -#: ../../content/administration/upgrade/odoo_sh.rst:121 -msgid "If anything goes wrong, the platform automatically reverts the upgrade, the same as it would be for a regular update. In case of success, a backup is always made." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:124 -msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:6 -msgid "Test upgrade request" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:8 -msgid "There are two ways to create your upgrade request." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:11 -msgid "Upgrade request via command line" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:13 -msgid "For technically-advanced users and partners, the upgrade process can be initiated via the following command line on the server where the database is hosted:" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:16 -msgid ":command:`python <(curl -s https://upgrade.odoo.com/upgrade) test -d -t `" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:19 -msgid "The above command creates the database dump, sends it to the upgrade platform, and initiates the automated upgrade process. During the upgrade, you can follow the live logs on your screen. Once the upgrade process is completed successfully, the upgraded database is restored onto the server (as a duplicate test database)." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:25 -msgid "Upgrade request via the Odoo Upgrade Portal" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:27 -msgid "Download a recent copy of your database and select the option :guilabel:`pg_dump custom format (without filestore)`." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:29 -msgid "Upload this dump file at https://upgrade.odoo.com and select *Testing* as the aim. Odoo performs the automated upgrade process. Once it is completed, you receive an email with a link to download the upgrade database dump file." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:32 -msgid "Import the upgraded database into your on-premise environment and manually test all processes and workflows." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:36 -msgid "For security reasons, only the person who submitted the upgrade request is able to download it." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:37 -msgid "Any problem found during testing should be reported via the `helpdesk `_." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:39 -msgid "For storage reasons, the copy of your database is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:41 +#: ../../content/administration/upgrade.rst:174 msgid "Before restoring the upgraded database, its filestore must be merged with the production filestore to be able to perform tests in the same conditions as it would be in the new version." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:43 +#: ../../content/administration/upgrade.rst:177 msgid "The upgraded database contains:" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:45 -msgid "A `dump.sql` file containing the upgraded database." +#: ../../content/administration/upgrade.rst:179 +msgid "A `dump.sql` file containing the upgraded database" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:46 -msgid "A `filestore` folder containing files that were extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (like new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore." +#: ../../content/administration/upgrade.rst:180 +msgid "A `filestore` folder containing files extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (e.g., new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:52 -msgid "Upgrade your production database" +#: ../../content/administration/upgrade.rst:187 +msgid "You can request multiple test databases if you wish to test an upgrade more than once." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:54 -msgid "Once you have completed the testing successfully, you can proceed to upgrade your live database in production. Download your upgraded database from the link in the email and import it onto your live environment." +#: ../../content/administration/upgrade.rst:192 +msgid "When an upgrade request is completed, an upgrade report is attached to the successful upgrade email, and it becomes available in the Discuss app for users who are part of the \"Administration / Settings\" group. This report provides important information about the changes introduced by the new version." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:59 -msgid "Same as in the test phase, when requesting an upgrade for production purposes, the copy of your database is submitted without a filestore." +#: ../../content/administration/upgrade.rst:200 +msgid "Testing the new version of the database" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:61 -msgid "Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version." +#: ../../content/administration/upgrade.rst:202 +msgid "It is essential to spend some time testing the upgraded test database to ensure that you are not stuck in your day-to-day activities by a change in views, behavior, or an error message once the upgrade goes live." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:65 -msgid "Custom modules (if applicable)" +#: ../../content/administration/upgrade.rst:207 +msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:67 -msgid "The upgrade of a database that contains custom modules is a two-step process." +#: ../../content/administration/upgrade.rst:210 +msgid "Scheduled actions are disabled." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:69 -msgid "The standard upgrade is done when your upgrade request is completed." +#: ../../content/administration/upgrade.rst:211 +msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:70 -msgid "Your custom modules also need to be upgraded to keep them compatible with the new version." +#: ../../content/administration/upgrade.rst:212 +msgid "Payment providers and delivery carriers are reset to the test environment." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:72 -msgid "Depending on your contract, the upgrade of your custom modules can be done" +#: ../../content/administration/upgrade.rst:213 +msgid "Bank synchronization is disabled. Should you want to test the synchronization, contact your bank synchronization provider to get sandbox credentials." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:74 -msgid "by yourself." +#: ../../content/administration/upgrade.rst:216 +msgid "Testing as many of your business flows as possible is strongly recommended to ensure they are working correctly and to get more familiar with the new version." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:75 -msgid "by your Partner." +#: ../../content/administration/upgrade.rst:219 +msgid "Basic test checklist" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:76 -msgid "by Odoo (if you hold a subscription to 'Maintenance of Customizations')." +#: ../../content/administration/upgrade.rst:221 +msgid "Are there views that are deactivated in your test database but active in your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:223 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:224 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:225 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:226 +msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:228 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:229 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:230 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:235 +msgid "Checking a random product in your product catalog and comparing its test and production data to verify everything is the same (product category, selling price, cost price, vendor, accounts, routes, etc.)." +msgstr "" + +#: ../../content/administration/upgrade.rst:238 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "Checking if the route to receive this product is the same in your production database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:243 +msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:245 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:246 +msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:248 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:249 +msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:251 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Making an online order (Website apps) from the product selection in your shop until the checkout process and checking if everything behaves as in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:256 +msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to testing the upgrade. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:263 +msgid "You might encounter significant differences with standard views, features, fields, and models during testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced by a new version breaks a customization, it is the responsibility of the maintainer of your custom module to make it compatible with the new version of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "Workflows between different apps (online sales with eCommerce, converting a lead all the way to a sales order, delivery of products, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:276 +msgid "Server actions in the action menu on form views, as well as by selecting multiple records on list views" +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:284 +msgid "Once the :ref:`tests ` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page `__." +msgstr "" + +#: ../../content/administration/upgrade.rst:289 +msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal." +msgstr "" + +#: ../../content/administration/upgrade.rst:292 +msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. Fully rehearsing the upgrade process the day before upgrading the production database is also recommended." +msgstr "" + +#: ../../content/administration/upgrade.rst:298 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:300 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Business interruptions (e.g., no longer having the possibility to validate an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:304 +msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:311 +msgid "The process is similar to :ref:`obtaining an upgraded test database `, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`." +msgstr "" + +#: ../../content/administration/upgrade.rst:316 +msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version." +msgstr "" + +#: ../../content/administration/upgrade.rst:322 +msgid "The process is similar to :ref:`obtaining an upgraded test database ` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately." +msgstr "" + +#: ../../content/administration/upgrade.rst:334 +msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created." +msgstr "" + +#: ../../content/administration/upgrade.rst:338 +msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production." +msgstr "" + +#: ../../content/administration/upgrade.rst:346 +msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:" +msgstr "" + +#: ../../content/administration/upgrade.rst:353 +msgid "An upgraded production database can also be requested via the `Upgrade page `_. Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process." +msgstr "" + +#: ../../content/administration/upgrade.rst:360 +msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version." +msgstr "" + +#: ../../content/administration/upgrade.rst:364 +msgid "In case of an issue with your production database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to the upgrade in production." +msgstr "" + +#: ../../content/administration/upgrade.rst:372 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:374 +msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database." +msgstr "" + +#: ../../content/administration/upgrade.rst:377 +msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement `. However, this section clarifies what upgrade services you can expect." +msgstr "" + +#: ../../content/administration/upgrade.rst:382 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:384 +msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:" +msgstr "" + +#: ../../content/administration/upgrade.rst:387 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:388 +msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:390 +msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:393 +msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:397 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +msgid "the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:402 +msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" +msgstr "" + +#: ../../content/administration/upgrade.rst:403 +msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code `; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:406 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:409 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:410 +msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index 89bd32c1d..34511e72e 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-12 13:54+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2392,7 +2392,7 @@ msgid "Alert blocks (admonitions)" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:470 -msgid "Seealso" +msgid "See also" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:476 diff --git a/locale/sources/developer.pot b/locale/sources/developer.pot index c2c4f1327..9035d2166 100644 --- a/locale/sources/developer.pot +++ b/locale/sources/developer.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -528,11 +528,6 @@ msgid "This is achieved with security rules based on `company_ids`, which contai msgstr "" #: ../../content/developer/howtos/company.rst:229 -#: ../../content/developer/howtos/provide_iap_services.rst:118 -#: ../../content/developer/howtos/provide_iap_services.rst:222 -#: ../../content/developer/howtos/provide_iap_services.rst:406 -#: ../../content/developer/howtos/provide_iap_services.rst:408 -#: ../../content/developer/howtos/provide_iap_services.rst:511 #: ../../content/developer/howtos/translations.rst:19 #: ../../content/developer/howtos/website_themes/building_blocks.rst:77 #: ../../content/developer/howtos/website_themes/building_blocks.rst:332 @@ -541,10 +536,10 @@ msgstr "" #: ../../content/developer/howtos/website_themes/pages.rst:194 #: ../../content/developer/howtos/website_themes/shapes.rst:125 #: ../../content/developer/reference/backend/actions.rst:176 -#: ../../content/developer/reference/backend/orm.rst:636 -#: ../../content/developer/reference/backend/orm.rst:638 -#: ../../content/developer/reference/backend/orm.rst:827 -#: ../../content/developer/reference/backend/orm.rst:980 +#: ../../content/developer/reference/backend/orm.rst:633 +#: ../../content/developer/reference/backend/orm.rst:635 +#: ../../content/developer/reference/backend/orm.rst:824 +#: ../../content/developer/reference/backend/orm.rst:977 #: ../../content/developer/reference/backend/security.rst:28 #: ../../content/developer/reference/backend/security.rst:186 #: ../../content/developer/reference/backend/views.rst:13 @@ -1044,700 +1039,6 @@ msgstr "" msgid "Declare the :ref:`view ` in the arch." msgstr "" -#: ../../content/developer/howtos/provide_iap_services.rst:3 -msgid "Provide IAP services" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:5 -msgid "In-App Purchase (IAP) allows providers of ongoing services through Odoo apps to be compensated for ongoing service use rather than ā€” and possibly instead of ā€” a sole initial purchase." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:9 -msgid "In that context, Odoo acts mostly as a *broker* between a client and an Odoo App Developer:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:12 -msgid "Users purchase service tokens from Odoo." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:13 -msgid "Service providers draw tokens from the user's Odoo account when service is requested." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:18 -msgid "This document is intended for *service providers* and presents the latter, which can be done either via direct JSON-RPC2_ or if you are using Odoo using the convenience helpers it provides." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:23 -#: ../../content/developer/reference/extract_api.rst:22 -#: ../../content/developer/reference/frontend/javascript_reference.rst:17 -#: ../../content/developer/reference/frontend/services.rst:144 -#: ../../content/developer/reference/frontend/services.rst:182 -#: ../../content/developer/reference/frontend/services.rst:362 -#: ../../content/developer/reference/frontend/services.rst:408 -#: ../../content/developer/reference/frontend/services.rst:522 -#: ../../content/developer/reference/frontend/services.rst:612 -#: ../../content/developer/reference/frontend/services.rst:708 -#: ../../content/developer/reference/frontend/services.rst:759 -#: ../../content/developer/reference/frontend/services.rst:834 -#: ../../content/developer/reference/user_interface/scss_inheritance.rst:6 -msgid "Overview" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:28 -msgid "The Players" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:30 -msgid "The Service Provider is (probably) you the reader, you will be providing value to the client in the form of a service paid per-use." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:32 -msgid "The Client installed your Odoo App, and from there will request services." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:33 -msgid "Odoo brokers crediting, the Client adds credit to their account, and you can draw credits from there to provide services." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:35 -msgid "The External Service is an optional player: *you* can either provide a service directly, or you can delegate the actual service acting as a bridge/translator between an Odoo system and the actual service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:43 -msgid "The Credits" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:45 -msgid "The credits went from integer to float value starting **October 2018**. Integer values are still supported." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:48 -msgid "Every service provided through the IAP platform can be used by the clients with tokens or *credits*. The credits are an float unit and their monetary value depends on the service and is decided by the provider. This could be:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:53 -msgid "for an sms service: 1 credit = 1 sms;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:54 -msgid "for an ad service: 1 credit = 1 ad; or" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:55 -msgid "for a postage service: 1 credit = 1 post stamp." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:57 -msgid "A credit can also simply be associated with a fixed amount of money to palliate the variations of price (e.g. the prices of sms and stamps may vary following the countries)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:61 -msgid "The value of the credits is fixed with the help of prepaid credit packs that the clients can buy on https://iap.odoo.com (see :ref:`Packs `)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:64 -msgid "In the following explanations we will ignore the External Service, they are just a detail of the service you provide." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:70 -msgid "'Normal' service flow" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:72 -msgid "If everything goes well, the normal flow is the following:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:74 -msgid "The Client requests a service of some sort." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:75 -msgid "The Service Provider asks Odoo if there are enough credits for the service in the Client's account, and creates a transaction over that amount." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:78 -msgid "The Service Provider provides the service (either on their own or calling to External Services)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:80 -msgid "The Service Provider goes back to Odoo to capture (if the service could be provided) or cancel (if the service could not be provided) the transaction created at step 2." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:83 -msgid "Finally, the Service Provider notifies the Client that the service has been rendered, possibly (depending on the service) displaying or storing its results in the client's system." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:90 -msgid "Insufficient credits" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:92 -msgid "However, if the Client's account lacks credits for the service, the flow will be as follows:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:94 -msgid "The Client requests a service as previously." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:95 -msgid "The Service Provider asks Odoo if there are enough credits on the Client's account and gets a negative reply." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:97 -msgid "This is signaled back to the Client." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:98 -msgid "Who is redirected to their Odoo account to credit it and re-try." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:102 -msgid "Building your service" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:104 -msgid "For this example, the service we will provide is ~~mining dogecoins~~ burning 10 seconds of CPU for a credit. For your own services, you could, for example:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:107 -msgid "provide an online service yourself (e.g. convert quotations to faxes for business in Japan);" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:109 -msgid "provide an *offline* service yourself (e.g. provide accountancy service); or" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:110 -msgid "act as intermediary to an other service provider (e.g. bridge to an MMS gateway)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:116 -msgid "Register the service on Odoo" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:118 -msgid "complete this part with screenshots" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:120 -msgid "The first step is to register your service on the IAP endpoint (production and/or test) before you can actually query user accounts. To create a service, go to your *Portal Account* on the IAP endpoint (https://iap.odoo.com for production, https://iap-sandbox.odoo.com for testing, the endpoints are *independent* and *not synchronized*). Alternatively, you can go to your portal on Odoo (https://iap.odoo.com/my/home) and select *In-App Services*." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:129 -msgid "On production, there is a manual validation step before the service can be used to manage real transactions. This step is automatically passed when on sandbox to ease the tests." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:133 -msgid "Log in then go to :menuselection:`My Account --> Your In-App Services`, click Create and provide the information of your service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:137 -msgid "The service has *seven* important fields:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:139 -msgid ":samp:`name` - :class:`ServiceName`: This is the string you will need to provide inside the client's :ref:`app ` when requesting a transaction from Odoo. (e.g. `self.env['iap.account].get(name)`). As good practice, this should match the technical name of your app." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:144 -msgid ":samp:`label` - :class:`Label`: The name displayed on the shopping portal for the client." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:149 -msgid "Both the :class:`ServiceName` and :class:`Label` are unique. As good practice, the :class:`ServiceName` should usually match the name of your Odoo Client App." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:152 -msgid ":samp:`icon` - :class:`Icon`: A generic icon that will serve as default for your :ref:`packs `." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:155 -msgid ":samp:`key` - :class:`ServiceKey`: The developer key that identifies you in IAP (see :ref:`your service `) and allows to draw credits from the client's account. It will be shown only once upon creation of the service and can be regenerated at will." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:161 -msgid "Your :class:`ServiceKey` *is a secret*, leaking your service key allows other application developers to draw credits bought for your service(s)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:165 -msgid ":samp:`trial credits` - :class:`Float`: This corresponds to the credits you are ready to offer upon first use to your app users. Note that such service will only be available to clients that have an active enterprise contract." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:169 -msgid ":samp:`privacy policy` - :class:`PrivacyPolicy`: This is an url to the privacy policy of your service. This should explicitly mention the **information you collect**, how you **use it, its relevance** to make your service work and inform the client on how they can **access, update or delete their personal information**." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:186 -msgid "You can then create *credit packs* which clients can purchase in order to use your service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:192 -msgid "Packs" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:194 -msgid "A credit pack is essentially a product with five characteristics:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:196 -msgid "Name: name of the pack," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:197 -msgid "Icon: specific icon for the pack (if not provided, it will fallback on the service icon)," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:198 -msgid "Description: details on the pack that will appear on the shop page as well as the invoice," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:200 -msgid "Amount: amount of credits the client is entitled to when buying the pack," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:201 -msgid "Price: price in EUR (for the time being, USD support is planned)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:205 -msgid "Odoo takes a 25% commission on all pack sales. Adjust your selling price accordingly." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:210 -msgid "Depending on the strategy, the price per credit may vary from one pack to another." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:220 -msgid "Odoo App" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:222 -msgid "does this actually require apps?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:224 -msgid "The second step is to develop an `Odoo App`_ which clients can install in their Odoo instance and through which they can *request* the services you provide. Our app will just add a button to the Partners form which lets a user request burning some CPU time on the server." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:229 -msgid "First, we will create an *odoo module* depending on ``iap``. IAP is a standard V11 module and the dependency ensures a local account is properly set up and we will have access to some necessary views and useful helpers." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:233 -#: ../../content/developer/howtos/provide_iap_services.rst:248 -msgid "`coalroller/__manifest__.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:243 -msgid "Second, the \"local\" side of the integration. Here we will only be adding an action button to the partners view, but you can of course provide significant local value via your application and additional parts via a remote service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:261 -msgid "`coalroller/views/res_partner_views.xml`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:286 -msgid "We can now implement the action method/callback. This will *call our own server*." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:289 -msgid "There are no requirements when it comes to the server or the communication protocol between the app and our server, but ``iap`` provides a :func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc` helper to call a JSON-RPC2_ endpoint on an other Odoo instance and transparently re-raise relevant Odoo exceptions (:class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError`, :class:`odoo.exceptions.AccessError` and :class:`odoo.exceptions.UserError`)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:296 -msgid "In that call, we will need to provide:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:298 -msgid "any relevant client parameter (none here)," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:299 -msgid "the :class:`token ` of the current client that is provided by the ``iap.account`` model's ``account_token`` field. You can retrieve the account for your service by calling :samp:`env['iap.account'].get({service_name})` where :class:`service_name ` is the name of the service registered on IAP endpoint." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:305 -msgid "`coalroller/models/res_partner.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:333 -msgid "``iap`` automatically handles :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` coming from the action and prompts the user to add credits to their account." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:337 -msgid ":func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc` takes care of re-raising :class:`~odoo.addons.iap.models.iap.InsufficientCreditError` for you." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:342 -msgid "If you are not using :func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc` you *must* be careful to re-raise :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` in your handler otherwise the user will not be prompted to credit their account, and the next call will fail the same way." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:351 -#: ../../content/developer/reference/frontend/javascript_reference.rst:876 -msgid "Service" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:353 -msgid "Though that is not *required*, since ``iap`` provides both a client helper for JSON-RPC2_ calls (:func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc`) and a service helper for transactions (:class:`~odoo.addons.iap.tools.iap_tools.iap_charge`) we will also be implementing the service side as an Odoo module:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:358 -#: ../../content/developer/howtos/provide_iap_services.rst:448 -msgid "`coalroller_service/__manifest__.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:368 -msgid "Since the query from the client comes as JSON-RPC2_ we will need the corresponding controller which can call :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` and perform the service within:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:372 -#: ../../content/developer/howtos/provide_iap_services.rst:461 -msgid "`coalroller_service/controllers/main.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:406 -msgid "for the actual IAP will the \"portal\" page be on odoo.com or iap.odoo.com?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:408 -msgid "\"My Account\" > \"Your InApp Services\"?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:411 -msgid "The :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` helper will:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:413 -msgid "authorize (create) a transaction with the specified number of credits, if the account does not have enough credits it will raise the relevant error" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:416 -msgid "execute the body of the ``with`` statement" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:417 -msgid "if the body of the ``with`` executes successfully, update the price of the transaction if needed" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:419 -msgid "capture (confirm) the transaction" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:420 -msgid "otherwise, if an error is raised from the body of the ``with``, cancel the transaction (and release the hold on the credits)" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:425 -msgid "By default, :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` contacts the *production* IAP endpoint, https://iap.odoo.com. While developing and testing your service you may want to point it towards the *development* IAP endpoint https://iap-sandbox.odoo.com." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:430 -msgid "To do so, set the ``iap.endpoint`` config parameter in your service Odoo: in debug/developer mode, :menuselection:`Setting --> Technical --> Parameters --> System Parameters`, just define an entry for the key ``iap.endpoint`` if none already exists)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:435 -msgid "The :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` helper has two additional optional parameters we can use to make things clearer to the end-user." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:440 -#: ../../content/developer/reference/backend/reports.rst:198 -#: ../../content/developer/reference/extract_api.rst:509 -msgid "``description``" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:439 -msgid "is a message which will be associated with the transaction and will be displayed in the user's dashboard, it is useful to remind the user why the charge exists." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:446 -msgid "``credit_template``" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:443 -msgid "is the name of a :ref:`reference/qweb` template which will be rendered and shown to the user if their account has less credit available than the service provider is requesting, its purpose is to tell your users why they should be interested in your IAP offers." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:488 -msgid "`coalroller_service/views/no-credit.xml`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:511 -msgid "how do you test your service?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:514 -msgid "JSON-RPC2_ Transaction API" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:519 -msgid "The IAP transaction API does not require using Odoo when implementing your server gateway, calls are standard JSON-RPC2_." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:521 -msgid "Calls use different *endpoints* but the same *method* on all endpoints (``call``)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:523 -msgid "Exceptions are returned as JSON-RPC2_ errors, the formal exception name is available on ``data.name`` for programmatic manipulation." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:526 -msgid "`iap.odoo.com documentation`_ for additional information." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:529 -#: ../../content/developer/howtos/provide_iap_services.rst:775 -msgid "Authorize" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:533 -msgid "Verifies that the user's account has at least as ``credit`` available *and creates a hold (pending transaction) on that amount*." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:536 -msgid "Any amount currently on hold by a pending transaction is considered unavailable to further authorize calls." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:539 -msgid "Returns a :class:`TransactionToken` identifying the pending transaction which can be used to capture (confirm) or cancel said transaction (`iap.odoo.com documentation`_)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:0 -#: ../../content/developer/reference/backend/mixins.rst:0 -#: ../../content/developer/reference/frontend/framework_overview.rst:0 -#: ../../content/developer/reference/frontend/qweb.rst:0 -msgid "Parameters" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:545 -msgid "optional, helps users identify the reason for charges on their account" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:547 -msgid "optional, allows the user to benefit from trial credits if his database is eligible (see :ref:`Service registration `)" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:549 -msgid "optional, transaction time to live in hours. If the credit are not captured when the transaction expires, the transaction is cancelled. The default value is set to 4320 hours (= 180 days)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:0 -#: ../../content/developer/reference/backend/mixins.rst:0 -#: ../../content/developer/reference/frontend/assets.rst:0 -#: ../../content/developer/reference/frontend/framework_overview.rst:0 -#: ../../content/developer/reference/frontend/hooks.rst:0 -#: ../../content/developer/reference/frontend/javascript_reference.rst:0 -#: ../../content/developer/reference/frontend/mobile.rst:0 -#: ../../content/developer/reference/frontend/qweb.rst:0 -#: ../../content/developer/reference/frontend/registries.rst:0 -#: ../../content/developer/reference/frontend/services.rst:0 -msgid "Returns" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:551 -msgid ":class:`TransactionToken` if the authorization succeeded" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:0 -msgid "raises" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:552 -msgid ":class:`~odoo.exceptions.AccessError` if the service token is invalid" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:553 -msgid ":class:`~odoo.addons.iap.models.iap.InsufficientCreditError` if the account does not have enough credits" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:554 -msgid "``TypeError`` if the ``credit`` value is not an integer or a float" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:577 -#: ../../content/developer/howtos/provide_iap_services.rst:855 -msgid "Capture" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:581 -msgid "Confirms the specified transaction, transferring the reserved credits from the user's account to the service provider's." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:584 -msgid "Capture calls are idempotent: performing capture calls on an already captured transaction has no further effect." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:589 -msgid "optional parameter to capture a smaller amount of credits than authorized" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:590 -#: ../../content/developer/howtos/provide_iap_services.rst:622 -msgid ":class:`~odoo.exceptions.AccessError`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:610 -#: ../../content/developer/howtos/provide_iap_services.rst:817 -msgid "Cancel" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:614 -msgid "Cancels the specified transaction, releasing the hold on the user's credits." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:617 -msgid "Cancel calls are idempotent: performing capture calls on an already cancelled transaction has no further effect." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:640 -#: ../../content/developer/tutorials/getting_started/04_basicmodel.rst:134 -msgid "Types" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:642 -msgid "Exceptions aside, these are *abstract types* used for clarity, you should not care how they are implemented." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:647 -msgid "String identifying your service on https://iap.odoo.com (production) as well as the account related to your service in the client's database." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:652 -msgid "Identifier generated for the provider's service. Each key (and service) matches a token of a fixed value, as generated by the service provide." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:655 -msgid "Multiple types of tokens correspond to multiple services. As an exampe, SMS and MMS could either be the same service (with an MMS being 'worth' multiple SMS) or could be separate services at separate price points." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:659 -msgid "Your service key *is a secret*, leaking your service key allows other application developers to draw credits bought for your service(s)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:665 -msgid "Identifier for a user account." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:669 -msgid "Transaction identifier, returned by the authorization process and consumed by either capturing or cancelling the transaction." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:674 -msgid "Raised during transaction authorization if the credits requested are not currently available on the account (either not enough credits or too many pending transactions/existing holds)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:681 -msgid "Raised by:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:683 -msgid "any operation to which a service token is required, if the service token is invalid; or" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:684 -msgid "any failure in an inter-server call. (typically, in :func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc`)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:689 -msgid "Raised by any unexpected behaviour at the discretion of the App developer (*you*)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:693 -msgid "Test the API" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:695 -msgid "In order to test the developed app, we propose a sandbox platform that allows you to:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:697 -msgid "Test the whole flow from the client's point of view - Actual services and transactions that can be consulted. (again this requires to change the endpoint, see the danger note in :ref:`Service `)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:700 -msgid "Test the API." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:702 -msgid "The latter consists in specific tokens that will work on **IAP-Sandbox only**." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:704 -msgid "Token ``000000``: Represents a non-existing account. Returns an :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` on authorize attempt." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:706 -msgid "Token ``000111``: Represents an account without sufficient credits to perform any service. Returns an :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` on authorize attempt." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:708 -msgid "Token ``111111``: Represents an account with enough credits to perform any service. An authorize attempt will return a dummy transaction token that is processed by the capture and cancel routes." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:714 -msgid "Those tokens are only active on the IAP-Sanbox server." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:715 -msgid "The service key is completely ignored with this flow, If you want to run a robust test of your service, you should ignore these tokens." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:719 -msgid "Odoo Helpers" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:721 -msgid "For convenience, if you are implementing your service using Odoo the ``iap`` module provides a few helpers to make IAP flow even simpler." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:727 -msgid "Charging" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:731 -msgid "A *context manager* for authorizing and automatically capturing or cancelling transactions for use in the backend/proxy." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:734 -msgid "Works much like e.g. a cursor context manager:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:736 -msgid "immediately authorizes a transaction with the specified parameters;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:737 -msgid "executes the ``with`` body;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:738 -msgid "if the body executes in full without error, captures the transaction;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:739 -msgid "otherwise cancels it." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:741 -#: ../../content/developer/howtos/provide_iap_services.rst:781 -#: ../../content/developer/howtos/provide_iap_services.rst:823 -#: ../../content/developer/howtos/provide_iap_services.rst:861 -msgid "used to retrieve the ``iap.endpoint`` configuration key" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:779 -msgid "Will authorize everything." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:821 -msgid "Will cancel an authorized transaction." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:859 -msgid "Will capture the amount ``credit`` on the given transaction." -msgstr "" - #: ../../content/developer/howtos/scss_tips.rst:3 msgid "Write lean easy-to-maintain CSS" msgstr "" @@ -2937,8 +2238,8 @@ msgid "Create a task." msgstr "" #: ../../content/developer/howtos/website_themes/forms.rst:75 -#: ../../content/developer/reference/extract_api.rst:194 -#: ../../content/developer/reference/extract_api.rst:712 +#: ../../content/developer/reference/extract_api.rst:183 +#: ../../content/developer/reference/extract_api.rst:284 msgid "Success" msgstr "" @@ -4083,7 +3384,7 @@ msgstr "" #: ../../content/developer/howtos/website_themes/setup.rst:42 #: ../../content/developer/reference/backend/orm.rst:114 -#: ../../content/developer/reference/backend/orm.rst:855 +#: ../../content/developer/reference/backend/orm.rst:852 #: ../../content/developer/reference/backend/views.rst:36 msgid "Fields" msgstr "" @@ -4317,7 +3618,7 @@ msgid ":option:`--addons-path `" msgstr "" #: ../../content/developer/howtos/website_themes/setup.rst:213 -#: ../../content/developer/reference/cli.rst:789 +#: ../../content/developer/reference/cli.rst:803 msgid "Comma-separated list of directories in which modules are stored. These directories are scanned for modules." msgstr "" @@ -5278,7 +4579,7 @@ msgstr "" #: ../../content/developer/reference/backend/views.rst:2160 #: ../../content/developer/reference/external_api.rst:1104 #: ../../content/developer/reference/external_api.rst:1268 -#: ../../content/developer/reference/extract_api.rst:529 +#: ../../content/developer/reference/extract_api.rst:511 #: ../../content/developer/reference/frontend/services.rst:871 #: ../../content/developer/tutorials/web.rst:1320 msgid "``name``" @@ -5586,9 +4887,8 @@ msgstr "" #: ../../content/developer/reference/backend/data.rst:232 #: ../../content/developer/reference/backend/data.rst:242 #: ../../content/developer/reference/backend/views.rst:675 -#: ../../content/developer/reference/extract_api.rst:171 -#: ../../content/developer/reference/extract_api.rst:290 -#: ../../content/developer/reference/extract_api.rst:697 +#: ../../content/developer/reference/extract_api.rst:168 +#: ../../content/developer/reference/extract_api.rst:264 msgid "``id``" msgstr "" @@ -5693,7 +4993,7 @@ msgid "``ir.model.fields`` to set in the concerned model (``crud_model_id`` for msgstr "" #: ../../content/developer/reference/backend/actions.rst:304 -#: ../../content/developer/reference/backend/orm.rst:928 +#: ../../content/developer/reference/backend/orm.rst:925 #: ../../content/developer/reference/backend/views.rst:1233 msgid "``value``" msgstr "" @@ -6305,7 +5605,7 @@ msgid "comma-separated list of group :term:`external identifiers`" msgstr "" #: ../../content/developer/reference/backend/data.rst:253 -#: ../../content/developer/reference/extract_api.rst:380 +#: ../../content/developer/reference/extract_api.rst:364 msgid "``page``" msgstr "" @@ -6620,9 +5920,8 @@ msgid "Routing" msgstr "" #: ../../content/developer/reference/backend/http.rst:64 -#: ../../content/developer/reference/extract_api.rst:78 -#: ../../content/developer/reference/extract_api.rst:244 -#: ../../content/developer/reference/extract_api.rst:563 +#: ../../content/developer/reference/extract_api.rst:74 +#: ../../content/developer/reference/extract_api.rst:220 msgid "Request" msgstr "" @@ -6631,9 +5930,8 @@ msgid "The request object is automatically set on :data:`odoo.http.request` at t msgstr "" #: ../../content/developer/reference/backend/http.rst:81 -#: ../../content/developer/reference/extract_api.rst:165 -#: ../../content/developer/reference/extract_api.rst:280 -#: ../../content/developer/reference/extract_api.rst:691 +#: ../../content/developer/reference/extract_api.rst:162 +#: ../../content/developer/reference/extract_api.rst:254 msgid "Response" msgstr "" @@ -6685,6 +5983,12 @@ msgstr "" msgid "Post a new message in an existing thread, returning the new mail.message ID." msgstr "" +#: ../../content/developer/reference/backend/mixins.rst:0 +#: ../../content/developer/reference/frontend/framework_overview.rst:0 +#: ../../content/developer/reference/frontend/qweb.rst:0 +msgid "Parameters" +msgstr "" + #: ../../content/developer/reference/backend/mixins.rst:84 msgid "body of the message, usually raw HTML that will be sanitized" msgstr "" @@ -6705,6 +6009,18 @@ msgstr "" msgid "extra keyword arguments will be used as default column values for the new mail.message record" msgstr "" +#: ../../content/developer/reference/backend/mixins.rst:0 +#: ../../content/developer/reference/frontend/assets.rst:0 +#: ../../content/developer/reference/frontend/framework_overview.rst:0 +#: ../../content/developer/reference/frontend/hooks.rst:0 +#: ../../content/developer/reference/frontend/javascript_reference.rst:0 +#: ../../content/developer/reference/frontend/mobile.rst:0 +#: ../../content/developer/reference/frontend/qweb.rst:0 +#: ../../content/developer/reference/frontend/registries.rst:0 +#: ../../content/developer/reference/frontend/services.rst:0 +msgid "Returns" +msgstr "" + #: ../../content/developer/reference/backend/mixins.rst:93 msgid "ID of newly created mail.message" msgstr "" @@ -7895,854 +7211,854 @@ msgstr "" msgid "TransientModel" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:126 +#: ../../content/developer/reference/backend/orm.rst:123 msgid "Basic Fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:139 +#: ../../content/developer/reference/backend/orm.rst:136 msgid "Advanced Fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:156 +#: ../../content/developer/reference/backend/orm.rst:153 msgid "Date(time) Fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:158 +#: ../../content/developer/reference/backend/orm.rst:155 msgid ":class:`Dates ` and :class:`Datetimes ` are very important fields in any kind of business application. Their misuse can create invisible yet painful bugs, this section aims to provide Odoo developers with the knowledge required to avoid misusing these fields." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:164 +#: ../../content/developer/reference/backend/orm.rst:161 msgid "When assigning a value to a Date/Datetime field, the following options are valid:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:166 +#: ../../content/developer/reference/backend/orm.rst:163 msgid "A `date` or `datetime` object." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:167 +#: ../../content/developer/reference/backend/orm.rst:164 msgid "A string in the proper server format:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:169 +#: ../../content/developer/reference/backend/orm.rst:166 msgid "``YYYY-MM-DD`` for :class:`~odoo.fields.Date` fields," msgstr "" -#: ../../content/developer/reference/backend/orm.rst:170 +#: ../../content/developer/reference/backend/orm.rst:167 msgid "``YYYY-MM-DD HH:MM:SS`` for :class:`~odoo.fields.Datetime` fields." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:172 +#: ../../content/developer/reference/backend/orm.rst:169 msgid "`False` or `None`." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:174 +#: ../../content/developer/reference/backend/orm.rst:171 msgid "The Date and Datetime fields class have helper methods to attempt conversion into a compatible type:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:177 +#: ../../content/developer/reference/backend/orm.rst:174 msgid ":func:`~odoo.fields.Date.to_date` will convert to a :class:`datetime.date`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:178 +#: ../../content/developer/reference/backend/orm.rst:175 msgid ":func:`~odoo.fields.Datetime.to_datetime` will convert to a :class:`datetime.datetime`." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:182 +#: ../../content/developer/reference/backend/orm.rst:179 msgid "To parse date/datetimes coming from external sources::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:186 +#: ../../content/developer/reference/backend/orm.rst:183 msgid "Date / Datetime comparison best practices:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:188 +#: ../../content/developer/reference/backend/orm.rst:185 msgid "Date fields can **only** be compared to date objects." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:189 +#: ../../content/developer/reference/backend/orm.rst:186 msgid "Datetime fields can **only** be compared to datetime objects." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:191 +#: ../../content/developer/reference/backend/orm.rst:188 msgid "Strings representing dates and datetimes can be compared between each other, however the result may not be the expected result, as a datetime string will always be greater than a date string, therefore this practice is **heavily** discouraged." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:197 +#: ../../content/developer/reference/backend/orm.rst:194 msgid "Common operations with dates and datetimes such as addition, subtraction or fetching the start/end of a period are exposed through both :class:`~odoo.fields.Date` and :class:`~odoo.fields.Datetime`. These helpers are also available by importing `odoo.tools.date_utils`." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:202 +#: ../../content/developer/reference/backend/orm.rst:199 msgid "Timezones" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:204 +#: ../../content/developer/reference/backend/orm.rst:201 msgid "Datetime fields are stored as `timestamp without timezone` columns in the database and are stored in the UTC timezone. This is by design, as it makes the Odoo database independent from the timezone of the hosting server system. Timezone conversion is managed entirely by the client side." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:217 +#: ../../content/developer/reference/backend/orm.rst:214 msgid "Relational Fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:231 +#: ../../content/developer/reference/backend/orm.rst:228 msgid "Pseudo-relational fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:240 +#: ../../content/developer/reference/backend/orm.rst:237 #: ../../content/developer/tutorials/getting_started/09_compute_onchange.rst:18 msgid "Computed Fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:242 +#: ../../content/developer/reference/backend/orm.rst:239 msgid "Fields can be computed (instead of read straight from the database) using the ``compute`` parameter. **It must assign the computed value to the field**. If it uses the values of other *fields*, it should specify those fields using :func:`~odoo.api.depends`. ::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:255 +#: ../../content/developer/reference/backend/orm.rst:252 msgid "dependencies can be dotted paths when using sub-fields::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:262 +#: ../../content/developer/reference/backend/orm.rst:259 msgid "computed fields are not stored by default, they are computed and returned when requested. Setting ``store=True`` will store them in the database and automatically enable searching." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:265 +#: ../../content/developer/reference/backend/orm.rst:262 msgid "searching on a computed field can also be enabled by setting the ``search`` parameter. The value is a method name returning a :ref:`reference/orm/domains`. ::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:276 +#: ../../content/developer/reference/backend/orm.rst:273 msgid "The search method is invoked when processing domains before doing an actual search on the model. It must return a domain equivalent to the condition: ``field operator value``." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:282 +#: ../../content/developer/reference/backend/orm.rst:279 msgid "Computed fields are readonly by default. To allow *setting* values on a computed field, use the ``inverse`` parameter. It is the name of a function reversing the computation and setting the relevant fields::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:298 +#: ../../content/developer/reference/backend/orm.rst:295 msgid "multiple fields can be computed at the same time by the same method, just use the same method on all fields and set all of them::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:314 +#: ../../content/developer/reference/backend/orm.rst:311 msgid "While it is possible to use the same compute method for multiple fields, it is not recommended to do the same for the inverse method." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:318 +#: ../../content/developer/reference/backend/orm.rst:315 msgid "During the computation of the inverse, **all** fields that use said inverse are protected, meaning that they can't be computed, even if their value is not in the cache." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:322 +#: ../../content/developer/reference/backend/orm.rst:319 msgid "If any of those fields is accessed and its value is not in cache, the ORM will simply return a default value of `False` for these fields. This means that the value of the inverse fields (other than the one triggering the inverse method) may not give their correct value and this will probably break the expected behavior of the inverse method." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:331 +#: ../../content/developer/reference/backend/orm.rst:328 msgid "Related fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:333 +#: ../../content/developer/reference/backend/orm.rst:330 msgid "A special case of computed fields are *related* (proxy) fields, which provide the value of a sub-field on the current record. They are defined by setting the ``related`` parameter and like regular computed fields they can be stored::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:340 +#: ../../content/developer/reference/backend/orm.rst:337 msgid "The value of a related field is given by following a sequence of relational fields and reading a field on the reached model. The complete sequence of fields to traverse is specified by the ``related`` attribute." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:344 +#: ../../content/developer/reference/backend/orm.rst:341 msgid "Some field attributes are automatically copied from the source field if they are not redefined: ``string``, ``help``, ``required`` (only if all fields in the sequence are required), ``groups``, ``digits``, ``size``, ``translate``, ``sanitize``, ``selection``, ``comodel_name``, ``domain``, ``context``. All semantic-free attributes are copied from the source field." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:351 +#: ../../content/developer/reference/backend/orm.rst:348 msgid "By default, related fields are:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:353 +#: ../../content/developer/reference/backend/orm.rst:350 msgid "not stored" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:354 +#: ../../content/developer/reference/backend/orm.rst:351 msgid "not copied" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:355 +#: ../../content/developer/reference/backend/orm.rst:352 msgid "readonly" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:356 +#: ../../content/developer/reference/backend/orm.rst:353 msgid "computed in superuser mode" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:358 +#: ../../content/developer/reference/backend/orm.rst:355 msgid "Add the attribute ``store=True`` to make it stored, just like computed fields. Related fields are automatically recomputed when their dependencies are modified." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:364 +#: ../../content/developer/reference/backend/orm.rst:361 msgid "You can specify precise field dependencies if you don't want the related field to be recomputed on any dependency change::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:375 +#: ../../content/developer/reference/backend/orm.rst:372 msgid "You cannot chain :class:`~odoo.fields.Many2many` or :class:`~odoo.fields.One2many` fields in ``related`` fields dependencies." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:377 +#: ../../content/developer/reference/backend/orm.rst:374 msgid "``related`` can be used to refer to a :class:`~odoo.fields.One2many` or :class:`~odoo.fields.Many2many` field on another model on the condition that it's done through a ``Many2one`` relation on the current model. ``One2many`` and ``Many2many`` are not supported and the results will not be aggregated correctly::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:400 +#: ../../content/developer/reference/backend/orm.rst:397 msgid "Automatic fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:404 +#: ../../content/developer/reference/backend/orm.rst:401 msgid "Identifier :class:`field `" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:406 +#: ../../content/developer/reference/backend/orm.rst:403 msgid "If length of current recordset is 1, return id of unique record in it." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:408 +#: ../../content/developer/reference/backend/orm.rst:405 msgid "Raise an Error otherwise." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:413 +#: ../../content/developer/reference/backend/orm.rst:410 msgid "Access Log fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:415 +#: ../../content/developer/reference/backend/orm.rst:412 msgid "These fields are automatically set and updated if :attr:`~odoo.models.BaseModel._log_access` is enabled. It can be disabled to avoid creating or updating those fields on tables for which they are not useful." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:420 +#: ../../content/developer/reference/backend/orm.rst:417 msgid "By default, :attr:`~odoo.models.BaseModel._log_access` is set to the same value as :attr:`~odoo.models.BaseModel._auto`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:425 +#: ../../content/developer/reference/backend/orm.rst:422 msgid "Stores when the record was created, :class:`~odoo.fields.Datetime`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:429 +#: ../../content/developer/reference/backend/orm.rst:426 msgid "Stores *who* created the record, :class:`~odoo.fields.Many2one` to a ``res.users``." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:434 +#: ../../content/developer/reference/backend/orm.rst:431 msgid "Stores when the record was last updated, :class:`~odoo.fields.Datetime`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:438 +#: ../../content/developer/reference/backend/orm.rst:435 msgid "Stores who last updated the record, :class:`~odoo.fields.Many2one` to a ``res.users``." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:441 +#: ../../content/developer/reference/backend/orm.rst:438 msgid ":attr:`~odoo.models.BaseModel._log_access` *must* be enabled on :class:`~odoo.models.TransientModel`." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:447 +#: ../../content/developer/reference/backend/orm.rst:444 msgid "Reserved Field names" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:449 +#: ../../content/developer/reference/backend/orm.rst:446 msgid "A few field names are reserved for pre-defined behaviors beyond that of automated fields. They should be defined on a model when the related behavior is desired:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:455 +#: ../../content/developer/reference/backend/orm.rst:452 msgid "default value for :attr:`~odoo.models.BaseModel._rec_name`, used to display records in context where a representative \"naming\" is necessary." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:459 -#: ../../content/developer/reference/backend/orm.rst:503 +#: ../../content/developer/reference/backend/orm.rst:456 +#: ../../content/developer/reference/backend/orm.rst:500 msgid ":class:`~odoo.fields.Char`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:463 +#: ../../content/developer/reference/backend/orm.rst:460 msgid "toggles the global visibility of the record, if ``active`` is set to ``False`` the record is invisible in most searches and listing." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:466 +#: ../../content/developer/reference/backend/orm.rst:463 msgid ":class:`~odoo.fields.Boolean`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:468 +#: ../../content/developer/reference/backend/orm.rst:465 msgid "Special methods:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:483 +#: ../../content/developer/reference/backend/orm.rst:480 msgid "lifecycle stages of the object, used by the ``states`` attribute on :class:`fields `." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:486 +#: ../../content/developer/reference/backend/orm.rst:483 msgid ":class:`~odoo.fields.Selection`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:490 +#: ../../content/developer/reference/backend/orm.rst:487 msgid "default_value of :attr:`~._parent_name`, used to organize records in a tree structure and enables the ``child_of`` and ``parent_of`` operators in domains." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:494 +#: ../../content/developer/reference/backend/orm.rst:491 msgid ":class:`~odoo.fields.Many2one`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:498 +#: ../../content/developer/reference/backend/orm.rst:495 msgid "When :attr:`~._parent_store` is set to True, used to store a value reflecting the tree structure of :attr:`~._parent_name`, and to optimize the operators ``child_of`` and ``parent_of`` in search domains. It must be declared with ``index=True`` for proper operation." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:507 +#: ../../content/developer/reference/backend/orm.rst:504 msgid "Main field name used for Odoo multi-company behavior." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:509 +#: ../../content/developer/reference/backend/orm.rst:506 msgid "Used by `:meth:~odoo.models._check_company` to check multi company consistency. Defines whether a record is shared between companies (no value) or only accessible by the users of a given company." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:513 +#: ../../content/developer/reference/backend/orm.rst:510 msgid ":class:`~odoo.fields.Many2one` :type: :class:`~odoo.addons.base.models.res_company`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:517 +#: ../../content/developer/reference/backend/orm.rst:514 msgid "Recordsets" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:519 +#: ../../content/developer/reference/backend/orm.rst:516 msgid "Interactions with models and records are performed through recordsets, an ordered collection of records of the same model." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:522 +#: ../../content/developer/reference/backend/orm.rst:519 msgid "Contrary to what the name implies, it is currently possible for recordsets to contain duplicates. This may change in the future." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:525 +#: ../../content/developer/reference/backend/orm.rst:522 msgid "Methods defined on a model are executed on a recordset, and their ``self`` is a recordset::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:535 +#: ../../content/developer/reference/backend/orm.rst:532 msgid "Iterating on a recordset will yield new sets of *a single record* (\"singletons\"), much like iterating on a Python string yields strings of a single characters::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:545 +#: ../../content/developer/reference/backend/orm.rst:542 msgid "Field access" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:547 +#: ../../content/developer/reference/backend/orm.rst:544 msgid "Recordsets provide an \"Active Record\" interface: model fields can be read and written directly from the record as attributes." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:552 +#: ../../content/developer/reference/backend/orm.rst:549 msgid "When accessing non-relational fields on a recordset of potentially multiple records, use :meth:`~odoo.models.BaseModel.mapped`::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:557 +#: ../../content/developer/reference/backend/orm.rst:554 msgid "Field values can also be accessed like dict items, which is more elegant and safer than ``getattr()`` for dynamic field names. Setting a field's value triggers an update to the database::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:572 +#: ../../content/developer/reference/backend/orm.rst:569 msgid "Trying to read a field on multiple records will raise an error for non relational fields." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:575 +#: ../../content/developer/reference/backend/orm.rst:572 msgid "Accessing a relational field (:class:`~odoo.fields.Many2one`, :class:`~odoo.fields.One2many`, :class:`~odoo.fields.Many2many`) *always* returns a recordset, empty if the field is not set." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:580 +#: ../../content/developer/reference/backend/orm.rst:577 msgid "Record cache and prefetching" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:582 +#: ../../content/developer/reference/backend/orm.rst:579 msgid "Odoo maintains a cache for the fields of the records, so that not every field access issues a database request, which would be terrible for performance. The following example queries the database only for the first statement::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:589 +#: ../../content/developer/reference/backend/orm.rst:586 msgid "To avoid reading one field on one record at a time, Odoo *prefetches* records and fields following some heuristics to get good performance. Once a field must be read on a given record, the ORM actually reads that field on a larger recordset, and stores the returned values in cache for later use. The prefetched recordset is usually the recordset from which the record comes by iteration. Moreover, all simple stored fields (boolean, integer, float, char, text, date, datetime, selection, many2one) are fetched altogether; they correspond to the columns of the model's table, and are fetched efficiently in the same query." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:598 +#: ../../content/developer/reference/backend/orm.rst:595 msgid "Consider the following example, where ``partners`` is a recordset of 1000 records. Without prefetching, the loop would make 2000 queries to the database. With prefetching, only one query is made::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:607 +#: ../../content/developer/reference/backend/orm.rst:604 msgid "The prefetching also works on *secondary records*: when relational fields are read, their values (which are records) are subscribed for future prefetching. Accessing one of those secondary records prefetches all secondary records from the same model. This makes the following example generate only two queries, one for partners and one for countries::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:622 +#: ../../content/developer/reference/backend/orm.rst:619 msgid "Method decorators" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:636 +#: ../../content/developer/reference/backend/orm.rst:633 msgid "With sphinx 2.0 : autodecorator" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:638 +#: ../../content/developer/reference/backend/orm.rst:635 msgid "Add in Views reference * It is possible to suppress the trigger from a specific field by adding ``on_change=\"0\"`` in a view::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:644 +#: ../../content/developer/reference/backend/orm.rst:641 msgid "will not trigger any interface update when the field is edited by the user, even if there are function fields or explicit onchange depending on that field." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:651 +#: ../../content/developer/reference/backend/orm.rst:648 #: ../../content/developer/reference/frontend/framework_overview.rst:96 msgid "Environment" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:668 +#: ../../content/developer/reference/backend/orm.rst:665 msgid "When creating a recordset from an other recordset, the environment is inherited. The environment can be used to get an empty recordset in an other model, and query that model:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:679 +#: ../../content/developer/reference/backend/orm.rst:676 msgid "Some lazy properties are available to access the environment (contextual) data:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:687 +#: ../../content/developer/reference/backend/orm.rst:684 msgid "Useful environment methods" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:695 +#: ../../content/developer/reference/backend/orm.rst:692 msgid "Altering the environment" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:712 +#: ../../content/developer/reference/backend/orm.rst:709 msgid "SQL Execution" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:714 +#: ../../content/developer/reference/backend/orm.rst:711 msgid "The :attr:`~odoo.api.Environment.cr` attribute on environments is the cursor for the current database transaction and allows executing SQL directly, either for queries which are difficult to express using the ORM (e.g. complex joins) or for performance reasons::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:722 +#: ../../content/developer/reference/backend/orm.rst:719 msgid "Executing raw SQL bypasses the ORM and, by consequent, Odoo security rules. Please make sure your queries are sanitized when using user input and prefer using ORM utilities if you don't really need to use SQL queries." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:726 +#: ../../content/developer/reference/backend/orm.rst:723 msgid "One important thing to know about models is that they don't necessarily perform database updates right away. Indeed, for performance reasons, the framework delays the recomputation of fields after modifying records. And some database updates are delayed, too. Therefore, before querying the database, one has to make sure that it contains the relevant data for the query. This operation is called *flushing* and performs the expected database updates." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:743 +#: ../../content/developer/reference/backend/orm.rst:740 msgid "Before every SQL query, one has to flush the data needed for that query. There are three levels for flushing, each with its own API. One can flush either everything, all the records of a model, or some specific records. Because delaying updates improves performance in general, we recommend to be *specific* when flushing." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:755 +#: ../../content/developer/reference/backend/orm.rst:752 msgid "Because models use the same cursor and the :class:`~odoo.api.Environment` holds various caches, these caches must be invalidated when *altering* the database in raw SQL, or further uses of models may become incoherent. It is necessary to clear caches when using ``CREATE``, ``UPDATE`` or ``DELETE`` in SQL, but not ``SELECT`` (which simply reads the database)." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:773 +#: ../../content/developer/reference/backend/orm.rst:770 msgid "Just like flushing, one can invalidate either the whole cache, the cache of all the records of a model, or the cache of specific records. One can even invalidate specific fields on some records or all records of a model. As the cache improves performance in general, we recommend to be *specific* when invalidating." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:785 +#: ../../content/developer/reference/backend/orm.rst:782 msgid "The methods above keep the caches and the database consistent with each other. However, if computed field dependencies have been modified in the database, one has to inform the models for the computed fields to be recomputed. The only thing the framework needs to know is *what* fields have changed on *which* records." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:807 +#: ../../content/developer/reference/backend/orm.rst:804 msgid "One has to figure out which records have been modified. There are many ways to do this, possibly involving extra SQL queries. In the example above, we take advantage of the ``RETURNING`` clause of PostgreSQL to retrieve the information without an extra query. After making the cache consistent by invalidation, invoke the method ``modified`` on the modified records with the fields that have been updated." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:820 +#: ../../content/developer/reference/backend/orm.rst:817 msgid "Common ORM methods" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:825 +#: ../../content/developer/reference/backend/orm.rst:822 msgid "Create/update" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:827 +#: ../../content/developer/reference/backend/orm.rst:824 msgid "api.model_create_multi information" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:840 +#: ../../content/developer/reference/backend/orm.rst:837 msgid "Search/Read" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:862 +#: ../../content/developer/reference/backend/orm.rst:859 msgid "Search domains" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:864 +#: ../../content/developer/reference/backend/orm.rst:861 msgid "A domain is a list of criteria, each criterion being a triple (either a ``list`` or a ``tuple``) of ``(field_name, operator, value)`` where:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:870 +#: ../../content/developer/reference/backend/orm.rst:867 msgid "``field_name`` (``str``)" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:868 +#: ../../content/developer/reference/backend/orm.rst:865 msgid "a field name of the current model, or a relationship traversal through a :class:`~odoo.fields.Many2one` using dot-notation e.g. ``'street'`` or ``'partner_id.country'``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:924 +#: ../../content/developer/reference/backend/orm.rst:921 msgid "``operator`` (``str``)" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:873 +#: ../../content/developer/reference/backend/orm.rst:870 msgid "an operator used to compare the ``field_name`` with the ``value``. Valid operators are:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:876 +#: ../../content/developer/reference/backend/orm.rst:873 msgid "``=``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:877 +#: ../../content/developer/reference/backend/orm.rst:874 msgid "equals to" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:878 +#: ../../content/developer/reference/backend/orm.rst:875 msgid "``!=``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:879 +#: ../../content/developer/reference/backend/orm.rst:876 msgid "not equals to" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:880 +#: ../../content/developer/reference/backend/orm.rst:877 msgid "``>``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:881 +#: ../../content/developer/reference/backend/orm.rst:878 msgid "greater than" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:882 +#: ../../content/developer/reference/backend/orm.rst:879 msgid "``>=``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:883 +#: ../../content/developer/reference/backend/orm.rst:880 msgid "greater than or equal to" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:884 +#: ../../content/developer/reference/backend/orm.rst:881 msgid "``<``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:885 +#: ../../content/developer/reference/backend/orm.rst:882 msgid "less than" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:886 +#: ../../content/developer/reference/backend/orm.rst:883 msgid "``<=``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:887 +#: ../../content/developer/reference/backend/orm.rst:884 msgid "less than or equal to" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:889 +#: ../../content/developer/reference/backend/orm.rst:886 msgid "``=?``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:889 +#: ../../content/developer/reference/backend/orm.rst:886 msgid "unset or equals to (returns true if ``value`` is either ``None`` or ``False``, otherwise behaves like ``=``)" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:893 +#: ../../content/developer/reference/backend/orm.rst:890 msgid "``=like``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:892 +#: ../../content/developer/reference/backend/orm.rst:889 msgid "matches ``field_name`` against the ``value`` pattern. An underscore ``_`` in the pattern stands for (matches) any single character; a percent sign ``%`` matches any string of zero or more characters." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:896 +#: ../../content/developer/reference/backend/orm.rst:893 msgid "``like``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:896 +#: ../../content/developer/reference/backend/orm.rst:893 msgid "matches ``field_name`` against the ``%value%`` pattern. Similar to ``=like`` but wraps ``value`` with '%' before matching" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:898 +#: ../../content/developer/reference/backend/orm.rst:895 msgid "``not like``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:899 +#: ../../content/developer/reference/backend/orm.rst:896 msgid "doesn't match against the ``%value%`` pattern" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:900 +#: ../../content/developer/reference/backend/orm.rst:897 msgid "``ilike``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:901 +#: ../../content/developer/reference/backend/orm.rst:898 msgid "case insensitive ``like``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:902 +#: ../../content/developer/reference/backend/orm.rst:899 msgid "``not ilike``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:903 +#: ../../content/developer/reference/backend/orm.rst:900 msgid "case insensitive ``not like``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:904 +#: ../../content/developer/reference/backend/orm.rst:901 msgid "``=ilike``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:905 +#: ../../content/developer/reference/backend/orm.rst:902 msgid "case insensitive ``=like``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:907 +#: ../../content/developer/reference/backend/orm.rst:904 msgid "``in``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:907 +#: ../../content/developer/reference/backend/orm.rst:904 msgid "is equal to any of the items from ``value``, ``value`` should be a list of items" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:909 +#: ../../content/developer/reference/backend/orm.rst:906 msgid "``not in``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:910 +#: ../../content/developer/reference/backend/orm.rst:907 msgid "is unequal to all of the items from ``value``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:916 +#: ../../content/developer/reference/backend/orm.rst:913 msgid "``child_of``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:912 +#: ../../content/developer/reference/backend/orm.rst:909 msgid "is a child (descendant) of a ``value`` record (value can be either one item or a list of items)." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:915 -#: ../../content/developer/reference/backend/orm.rst:922 +#: ../../content/developer/reference/backend/orm.rst:912 +#: ../../content/developer/reference/backend/orm.rst:919 msgid "Takes the semantics of the model into account (i.e following the relationship field named by :attr:`~odoo.models.Model._parent_name`)." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:924 +#: ../../content/developer/reference/backend/orm.rst:921 msgid "``parent_of``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:919 +#: ../../content/developer/reference/backend/orm.rst:916 msgid "is a parent (ascendant) of a ``value`` record (value can be either one item or a list of items)." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:927 +#: ../../content/developer/reference/backend/orm.rst:924 msgid "variable type, must be comparable (through ``operator``) to the named field." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:930 +#: ../../content/developer/reference/backend/orm.rst:927 msgid "Domain criteria can be combined using logical operators in *prefix* form:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:933 +#: ../../content/developer/reference/backend/orm.rst:930 msgid "``'&'``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:933 +#: ../../content/developer/reference/backend/orm.rst:930 msgid "logical *AND*, default operation to combine criteria following one another. Arity 2 (uses the next 2 criteria or combinations)." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:935 +#: ../../content/developer/reference/backend/orm.rst:932 msgid "``'|'``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:936 +#: ../../content/developer/reference/backend/orm.rst:933 msgid "logical *OR*, arity 2." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:942 +#: ../../content/developer/reference/backend/orm.rst:939 msgid "``'!'``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:938 +#: ../../content/developer/reference/backend/orm.rst:935 msgid "logical *NOT*, arity 1." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:940 +#: ../../content/developer/reference/backend/orm.rst:937 msgid "Mostly to negate combinations of criteria Individual criterion generally have a negative form (e.g. ``=`` -> ``!=``, ``<`` -> ``>=``) which is simpler than negating the positive." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:946 +#: ../../content/developer/reference/backend/orm.rst:943 msgid "To search for partners named *ABC*, from belgium or germany, whose language is not english::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:954 +#: ../../content/developer/reference/backend/orm.rst:951 msgid "This domain is interpreted as:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:963 +#: ../../content/developer/reference/backend/orm.rst:960 #: ../../content/developer/tutorials/getting_started/13_inheritance.rst:0 msgid "Unlink" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:970 +#: ../../content/developer/reference/backend/orm.rst:967 msgid "Record(set) information" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:976 +#: ../../content/developer/reference/backend/orm.rst:973 msgid "Returns the environment of the given recordset." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:978 +#: ../../content/developer/reference/backend/orm.rst:975 msgid ":class:`~odoo.api.Environment`" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:980 +#: ../../content/developer/reference/backend/orm.rst:977 msgid "Environment documentation" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:993 +#: ../../content/developer/reference/backend/orm.rst:990 #: ../../content/developer/reference/frontend/assets.rst:102 msgid "Operations" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:995 +#: ../../content/developer/reference/backend/orm.rst:992 msgid "Recordsets are immutable, but sets of the same model can be combined using various set operations, returning new recordsets." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1000 +#: ../../content/developer/reference/backend/orm.rst:997 msgid "``record in set`` returns whether ``record`` (which must be a 1-element recordset) is present in ``set``. ``record not in set`` is the inverse operation" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1003 +#: ../../content/developer/reference/backend/orm.rst:1000 msgid "``set1 <= set2`` and ``set1 < set2`` return whether ``set1`` is a subset of ``set2`` (resp. strict)" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1005 +#: ../../content/developer/reference/backend/orm.rst:1002 msgid "``set1 >= set2`` and ``set1 > set2`` return whether ``set1`` is a superset of ``set2`` (resp. strict)" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1007 +#: ../../content/developer/reference/backend/orm.rst:1004 msgid "``set1 | set2`` returns the union of the two recordsets, a new recordset containing all records present in either source" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1009 +#: ../../content/developer/reference/backend/orm.rst:1006 msgid "``set1 & set2`` returns the intersection of two recordsets, a new recordset containing only records present in both sources" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1011 +#: ../../content/developer/reference/backend/orm.rst:1008 msgid "``set1 - set2`` returns a new recordset containing only records of ``set1`` which are *not* in ``set2``" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1014 +#: ../../content/developer/reference/backend/orm.rst:1011 msgid "Recordsets are iterable so the usual Python tools are available for transformation (:func:`python:map`, :func:`python:sorted`, :func:`~python:itertools.ifilter`, ...) however these return either a :class:`python:list` or an :term:`python:iterator`, removing the ability to call methods on their result, or to use set operations." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1020 +#: ../../content/developer/reference/backend/orm.rst:1017 msgid "Recordsets therefore provide the following operations returning recordsets themselves (when possible):" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1024 +#: ../../content/developer/reference/backend/orm.rst:1021 #: ../../content/developer/tutorials/getting_started/07_basicviews.rst:0 msgid "Filter" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1031 +#: ../../content/developer/reference/backend/orm.rst:1028 #: ../../content/developer/reference/backend/views.rst:1798 msgid "Map" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1037 +#: ../../content/developer/reference/backend/orm.rst:1034 msgid "Since V13, multi-relational field access is supported and works like a mapped call:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1046 +#: ../../content/developer/reference/backend/orm.rst:1043 msgid "Sort" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1053 +#: ../../content/developer/reference/backend/orm.rst:1050 msgid "Inheritance and extension" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1055 +#: ../../content/developer/reference/backend/orm.rst:1052 msgid "Odoo provides three different mechanisms to extend models in a modular way:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1057 +#: ../../content/developer/reference/backend/orm.rst:1054 msgid "creating a new model from an existing one, adding new information to the copy but leaving the original module as-is" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1059 +#: ../../content/developer/reference/backend/orm.rst:1056 msgid "extending models defined in other modules in-place, replacing the previous version" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1061 +#: ../../content/developer/reference/backend/orm.rst:1058 msgid "delegating some of the model's fields to records it contains" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1067 +#: ../../content/developer/reference/backend/orm.rst:1064 msgid "Classical inheritance" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1069 +#: ../../content/developer/reference/backend/orm.rst:1066 msgid "When using the :attr:`~odoo.models.Model._inherit` and :attr:`~odoo.models.Model._name` attributes together, Odoo creates a new model using the existing one (provided via :attr:`~odoo.models.Model._inherit`) as a base. The new model gets all the fields, methods and meta-information (defaults & al) from its base." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1097 +#: ../../content/developer/reference/backend/orm.rst:1094 msgid "and using them::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1105 +#: ../../content/developer/reference/backend/orm.rst:1102 msgid "will yield:" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1107 +#: ../../content/developer/reference/backend/orm.rst:1104 msgid "\"This is model 0 record A\" \"This is model 1 record B\"" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1110 +#: ../../content/developer/reference/backend/orm.rst:1107 msgid "the second model has inherited from the first model's ``check`` method and its ``name`` field, but overridden the ``call`` method, as when using standard :ref:`Python inheritance `." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1115 +#: ../../content/developer/reference/backend/orm.rst:1112 msgid "Extension" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1117 +#: ../../content/developer/reference/backend/orm.rst:1114 msgid "When using :attr:`~odoo.models.Model._inherit` but leaving out :attr:`~odoo.models.Model._name`, the new model replaces the existing one, essentially extending it in-place. This is useful to add new fields or methods to existing models (created in other modules), or to customize or reconfigure them (e.g. to change their default sort order)::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1139 +#: ../../content/developer/reference/backend/orm.rst:1136 msgid "will yield::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1146 +#: ../../content/developer/reference/backend/orm.rst:1143 msgid "It will also yield the various :ref:`automatic fields ` unless they've been disabled" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1150 +#: ../../content/developer/reference/backend/orm.rst:1147 msgid "Delegation" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1152 +#: ../../content/developer/reference/backend/orm.rst:1149 msgid "The third inheritance mechanism provides more flexibility (it can be altered at runtime) but less power: using the :attr:`~odoo.models.Model._inherits` a model *delegates* the lookup of any field not found on the current model to \"children\" models. The delegation is performed via :class:`~odoo.fields.Reference` fields automatically set up on the parent model." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1159 +#: ../../content/developer/reference/backend/orm.rst:1156 msgid "The main difference is in the meaning. When using Delegation, the model **has one** instead of **is one**, turning the relationship in a composition instead of inheritance::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1201 +#: ../../content/developer/reference/backend/orm.rst:1198 #: ../../content/developer/reference/frontend/qweb.rst:26 #: ../../content/developer/reference/frontend/qweb.rst:36 #: ../../content/developer/reference/frontend/qweb.rst:330 msgid "will result in::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1206 +#: ../../content/developer/reference/backend/orm.rst:1203 msgid "and it's possible to write directly on the delegated field::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1210 +#: ../../content/developer/reference/backend/orm.rst:1207 msgid "when using delegation inheritance, methods are *not* inherited, only fields" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1215 +#: ../../content/developer/reference/backend/orm.rst:1212 msgid "`_inherits` is more or less implemented, avoid it if you can;" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1216 +#: ../../content/developer/reference/backend/orm.rst:1213 msgid "chained `_inherits` is essentially not implemented, we cannot guarantee anything on the final behavior." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1220 +#: ../../content/developer/reference/backend/orm.rst:1217 msgid "Fields Incremental Definition" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1222 +#: ../../content/developer/reference/backend/orm.rst:1219 msgid "A field is defined as class attribute on a model class. If the model is extended, one can also extend the field definition by redefining a field with the same name and same type on the subclass. In that case, the attributes of the field are taken from the parent class and overridden by the ones given in subclasses." msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1228 +#: ../../content/developer/reference/backend/orm.rst:1225 msgid "For instance, the second class below only adds a tooltip on the field ``state``::" msgstr "" -#: ../../content/developer/reference/backend/orm.rst:1242 +#: ../../content/developer/reference/backend/orm.rst:1239 msgid "Error management" msgstr "" @@ -8758,22 +8074,66 @@ msgstr "" msgid "Translations for translated fields are stored as JSONB values with `#97692 `_ and `#101115 `_. Code translations are no longer stored into the database. They become static and are extracted from the PO files when needed." msgstr "" -#: ../../content/developer/reference/backend/orm/changelog.rst:17 -msgid "Odoo Online version 15.4" +#: ../../content/developer/reference/backend/orm/changelog.rst:15 +msgid ":meth:`~odoo.models.Model.search_count` takes the :attr:`limit` argument into account with `#95589 `_. It limits the number of records to count, improving performance when a partial result is acceptable." msgstr "" #: ../../content/developer/reference/backend/orm/changelog.rst:19 +msgid "Odoo Online version 15.4" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:21 msgid "New API for flushing to the database and invalidating the cache with `#87527 `_. New methods have been added to `odoo.models.Model` and `odoo.api.Environment`, and are less confusing about what is actually done in each case. See the section :ref:`SQL Execution `." msgstr "" -#: ../../content/developer/reference/backend/orm/changelog.rst:26 +#: ../../content/developer/reference/backend/orm/changelog.rst:28 +msgid "Odoo Online version 15.3" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:30 +msgid "The argument `args` is renamed to `domain` for :meth:`~odoo.models.Model.search`, :meth:`~odoo.models.Model.search_count` and :meth:`~odoo.models.Model._search`. `#83687 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:32 +msgid ":meth:`~odoo.models.Model.filtered_domain` conserves the order of the current recordset. `#83687 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:33 +msgid ":meth:`~odoo.models.Model.browse` does not accept :class:`str` as `ids`. `#83687 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:34 +msgid "The methods :meth:`~odoo.models.Model.fields_get_keys` and :meth:`~odoo.models.Model.get_xml_id` on :class:`~odoo.models.Model` are deprecated. `#83687 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:35 +msgid "The method :meth:`~odoo.models.Model._mapped_cache` is removed. `#83687 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:36 +msgid "Remove the :attr:`limit` attribute of :class:`~odoo.fields.One2many` and :class:`~odoo.fields.Many2many`. `#83687 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:39 msgid "Odoo Online version 15.2" msgstr "" -#: ../../content/developer/reference/backend/orm/changelog.rst:28 +#: ../../content/developer/reference/backend/orm/changelog.rst:41 msgid "Specific index types on fields: With `#83274 `_ and `#83015 `_, developers can now define what type of indexes can be used on fields by PostgreSQL. See the :ref:`index property ` of `odoo.fields.Field`." msgstr "" +#: ../../content/developer/reference/backend/orm/changelog.rst:45 +msgid "The :attr:`_sequence` attribute of :class:`~odoo.models.Model` is removed. Odoo lets PostgreSQL use the default sequence of the primary key. `#82727 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:46 +msgid "The method :meth:`~odoo.models.Model._write` does not raise an error for non-existing records. `#82727 `_" +msgstr "" + +#: ../../content/developer/reference/backend/orm/changelog.rst:47 +msgid "The :attr:`column_format` and :attr:`deprecated` attributes of :class:`~odoo.fields.Field` are removed. `#82727 `_" +msgstr "" + #: ../../content/developer/reference/backend/performance.rst:5 msgid "Performance" msgstr "" @@ -9268,7 +8628,7 @@ msgid "record for the current ``user``'s company" msgstr "" #: ../../content/developer/reference/backend/reports.rst:35 -#: ../../content/developer/reference/extract_api.rst:470 +#: ../../content/developer/reference/extract_api.rst:452 msgid "``website``" msgstr "" @@ -9418,6 +8778,11 @@ msgstr "" msgid "only useful as a mnemonic/description of the report when looking for one in a list of some sort" msgstr "" +#: ../../content/developer/reference/backend/reports.rst:198 +#: ../../content/developer/reference/extract_api.rst:491 +msgid "``description``" +msgstr "" + #: ../../content/developer/reference/backend/reports.rst:199 msgid "a small description of your format" msgstr "" @@ -10338,7 +9703,7 @@ msgid "when working on a failing test, it is common to add the debug flag, then msgstr "" #: ../../content/developer/reference/backend/testing.rst:537 -#: ../../content/developer/reference/extract_api.rst:731 +#: ../../content/developer/reference/extract_api.rst:523 msgid "Integration Testing" msgstr "" @@ -12663,7 +12028,6 @@ msgstr "" #: ../../content/developer/reference/backend/views.rst:1295 #: ../../content/developer/reference/backend/views.rst:1305 -#: ../../content/developer/reference/extract_api.rst:581 msgid "``values``" msgstr "" @@ -14146,7 +13510,7 @@ msgid "Control the SSL security of the connection between Odoo and PostgreSQL. V msgstr "" #: ../../content/developer/reference/cli.rst:289 -msgid "Use the unaccent function provided by the database when available." +msgid "Try to enable the unaccent extension when creating new databases" msgstr "" #: ../../content/developer/reference/cli.rst:294 @@ -14278,451 +13642,463 @@ msgid "TCP port for websocket connections in multiprocessing or gevent mode, def msgstr "" #: ../../content/developer/reference/cli.rst:436 -msgid "enables the use of ``X-Forwarded-*`` headers through `Werkzeug's proxy support`_. Only enable this when running behind a trusted web proxy!" +msgid "enables the use of ``X-Forwarded-*`` headers through `Werkzeug's proxy support`_." msgstr "" -#: ../../content/developer/reference/cli.rst:440 -msgid "proxy mode *must not* be enabled outside of a reverse proxy scenario" +#: ../../content/developer/reference/cli.rst:439 +msgid "It ignores all ``X-Forwarded-*`` headers in case ``X-Forwarded-Host`` is missing from the request." msgstr "" -#: ../../content/developer/reference/cli.rst:445 -msgid "delegates serving attachments files to the static web server and sets both ``X-Sendfile`` (apache) and ``X-Accel-*`` (nginx) http headers on stream responses. See :ref:`deploy/streaming` for web server configuration." +#: ../../content/developer/reference/cli.rst:442 +msgid "It always gets the real IP from the last entry of the ``X-Forwarded-For`` chain. Configure your web server accordingly using directives such as nginx's `set_real_ip_from `_ in case there are other trusted proxies along the chain that must be ignored." msgstr "" -#: ../../content/developer/reference/cli.rst:452 -msgid "Logging" +#: ../../content/developer/reference/cli.rst:447 +msgid "``X-Forwarded-Proto`` and ``X-Forwarded-Host`` are used to update the request root URL, which in turn is used to update the ``web.base.url`` system parameter upon a successful admin authentication. This system parameter is used to generate all links for the current database; see :ref:`domain-name/web-base-url`." msgstr "" #: ../../content/developer/reference/cli.rst:454 -msgid "By default, Odoo displays all logging of level_ ``info`` except for workflow logging (``warning`` only), and log output is sent to ``stdout``. Various options are available to redirect logging to other destinations and to customize the amount of logging output." +msgid "proxy mode *must not* be enabled outside of a reverse proxy scenario" msgstr "" -#: ../../content/developer/reference/cli.rst:461 -msgid "sends logging output to the specified file instead of stdout. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" +#: ../../content/developer/reference/cli.rst:459 +msgid "delegates serving attachments files to the static web server and sets both ``X-Sendfile`` (apache) and ``X-Accel-*`` (nginx) http headers on stream responses. See :ref:`deploy/streaming` for web server configuration." +msgstr "" + +#: ../../content/developer/reference/cli.rst:466 +msgid "Logging" msgstr "" #: ../../content/developer/reference/cli.rst:468 -msgid "logs to the system's event logger: `syslog on unices `_ and `the Event Log on Windows `_." -msgstr "" - -#: ../../content/developer/reference/cli.rst:471 -msgid "Neither is configurable" +msgid "By default, Odoo displays all logging of level_ ``info`` except for workflow logging (``warning`` only), and log output is sent to ``stdout``. Various options are available to redirect logging to other destinations and to customize the amount of logging output." msgstr "" #: ../../content/developer/reference/cli.rst:475 -msgid "logs to the ``ir.logging`` model (``ir_logging`` table) of the specified database. The database can be the name of a database in the \"current\" PostgreSQL, or `a PostgreSQL URI`_ for e.g. log aggregation." +msgid "sends logging output to the specified file instead of stdout. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" msgstr "" -#: ../../content/developer/reference/cli.rst:481 -msgid ":samp:`{LOGGER}:{LEVEL}`, enables ``LOGGER`` at the provided ``LEVEL`` e.g. ``odoo.models:DEBUG`` will enable all logging messages at or above ``DEBUG`` level in the models." +#: ../../content/developer/reference/cli.rst:482 +msgid "logs to the system's event logger: `syslog on unices `_ and `the Event Log on Windows `_." msgstr "" #: ../../content/developer/reference/cli.rst:485 -msgid "The colon ``:`` is mandatory" -msgstr "" - -#: ../../content/developer/reference/cli.rst:486 -msgid "The logger can be omitted to configure the root (default) handler" -msgstr "" - -#: ../../content/developer/reference/cli.rst:487 -msgid "If the level is omitted, the logger is set to ``INFO``" +msgid "Neither is configurable" msgstr "" #: ../../content/developer/reference/cli.rst:489 +msgid "logs to the ``ir.logging`` model (``ir_logging`` table) of the specified database. The database can be the name of a database in the \"current\" PostgreSQL, or `a PostgreSQL URI`_ for e.g. log aggregation." +msgstr "" + +#: ../../content/developer/reference/cli.rst:495 +msgid ":samp:`{LOGGER}:{LEVEL}`, enables ``LOGGER`` at the provided ``LEVEL`` e.g. ``odoo.models:DEBUG`` will enable all logging messages at or above ``DEBUG`` level in the models." +msgstr "" + +#: ../../content/developer/reference/cli.rst:499 +msgid "The colon ``:`` is mandatory" +msgstr "" + +#: ../../content/developer/reference/cli.rst:500 +msgid "The logger can be omitted to configure the root (default) handler" +msgstr "" + +#: ../../content/developer/reference/cli.rst:501 +msgid "If the level is omitted, the logger is set to ``INFO``" +msgstr "" + +#: ../../content/developer/reference/cli.rst:503 msgid "The option can be repeated to configure multiple loggers e.g." msgstr "" -#: ../../content/developer/reference/cli.rst:497 +#: ../../content/developer/reference/cli.rst:511 msgid "enables DEBUG logging of HTTP requests and responses, equivalent to ``--log-handler=odoo.http:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:502 +#: ../../content/developer/reference/cli.rst:516 msgid "enables DEBUG logging of SQL querying, equivalent to ``--log-handler=odoo.sql_db:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:507 +#: ../../content/developer/reference/cli.rst:521 msgid "Shortcut to more easily set predefined levels on specific loggers. \"real\" levels (``critical``, ``error``, ``warn``, ``debug``) are set on the ``odoo`` and ``werkzeug`` loggers (except for ``debug`` which is only set on ``odoo``)." msgstr "" -#: ../../content/developer/reference/cli.rst:512 +#: ../../content/developer/reference/cli.rst:526 msgid "Odoo also provides debugging pseudo-levels which apply to different sets of loggers:" msgstr "" -#: ../../content/developer/reference/cli.rst:517 +#: ../../content/developer/reference/cli.rst:531 msgid "``debug_sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:516 +#: ../../content/developer/reference/cli.rst:530 msgid "sets the SQL logger to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:518 +#: ../../content/developer/reference/cli.rst:532 msgid "equivalent to ``--log-sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:521 +#: ../../content/developer/reference/cli.rst:535 msgid "``debug_rpc``" msgstr "" -#: ../../content/developer/reference/cli.rst:520 +#: ../../content/developer/reference/cli.rst:534 msgid "sets the ``odoo`` and HTTP request loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:522 +#: ../../content/developer/reference/cli.rst:536 msgid "equivalent to ``--log-level debug --log-request``" msgstr "" -#: ../../content/developer/reference/cli.rst:527 +#: ../../content/developer/reference/cli.rst:541 msgid "``debug_rpc_answer``" msgstr "" -#: ../../content/developer/reference/cli.rst:524 +#: ../../content/developer/reference/cli.rst:538 msgid "sets the ``odoo`` and HTTP request and response loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:527 +#: ../../content/developer/reference/cli.rst:541 msgid "equivalent to ``--log-level debug --log-request --log-response``" msgstr "" -#: ../../content/developer/reference/cli.rst:531 +#: ../../content/developer/reference/cli.rst:545 msgid "In case of conflict between :option:`--log-level` and :option:`--log-handler`, the latter is used" msgstr "" -#: ../../content/developer/reference/cli.rst:537 +#: ../../content/developer/reference/cli.rst:551 msgid "Multiprocessing" msgstr "" -#: ../../content/developer/reference/cli.rst:541 +#: ../../content/developer/reference/cli.rst:555 msgid "if ``count`` is not 0 (the default), enables multiprocessing and sets up the specified number of HTTP workers (sub-processes processing HTTP and RPC requests)." msgstr "" -#: ../../content/developer/reference/cli.rst:545 +#: ../../content/developer/reference/cli.rst:559 msgid "multiprocessing mode is only available on Unix-based systems" msgstr "" -#: ../../content/developer/reference/cli.rst:547 +#: ../../content/developer/reference/cli.rst:561 msgid "A number of options allow limiting and recycling workers:" msgstr "" -#: ../../content/developer/reference/cli.rst:551 +#: ../../content/developer/reference/cli.rst:565 msgid "Number of requests a worker will process before being recycled and restarted." msgstr "" -#: ../../content/developer/reference/cli.rst:554 +#: ../../content/developer/reference/cli.rst:568 msgid "Defaults to *8196*." msgstr "" -#: ../../content/developer/reference/cli.rst:558 +#: ../../content/developer/reference/cli.rst:572 msgid "Maximum allowed virtual memory per worker in bytes. If the limit is exceeded, the worker is killed and recycled at the end of the current request." msgstr "" -#: ../../content/developer/reference/cli.rst:561 +#: ../../content/developer/reference/cli.rst:575 msgid "Defaults to *2048MiB (2048\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:565 +#: ../../content/developer/reference/cli.rst:579 msgid "Hard limit on virtual memory in bytes, any worker exceeding the limit will be immediately killed without waiting for the end of the current request processing." msgstr "" -#: ../../content/developer/reference/cli.rst:569 +#: ../../content/developer/reference/cli.rst:583 msgid "Defaults to *2560MiB (2560\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:573 +#: ../../content/developer/reference/cli.rst:587 msgid "Prevents the worker from using more than CPU seconds for each request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:576 +#: ../../content/developer/reference/cli.rst:590 msgid "Defaults to *60*." msgstr "" -#: ../../content/developer/reference/cli.rst:580 +#: ../../content/developer/reference/cli.rst:594 msgid "Prevents the worker from taking longer than seconds to process a request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:583 +#: ../../content/developer/reference/cli.rst:597 msgid "Differs from :option:`--limit-time-cpu` in that this is a \"wall time\" limit including e.g. SQL queries." msgstr "" -#: ../../content/developer/reference/cli.rst:586 +#: ../../content/developer/reference/cli.rst:600 msgid "Defaults to *120*." msgstr "" -#: ../../content/developer/reference/cli.rst:590 +#: ../../content/developer/reference/cli.rst:604 msgid "number of workers dedicated to :ref:`cron ` jobs. Defaults to *2*. The workers are threads in multi-threading mode and processes in multi-processing mode." msgstr "" -#: ../../content/developer/reference/cli.rst:593 +#: ../../content/developer/reference/cli.rst:607 msgid "For multi-processing mode, this is in addition to the HTTP worker processes." msgstr "" -#: ../../content/developer/reference/cli.rst:598 +#: ../../content/developer/reference/cli.rst:612 msgid "Configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:602 +#: ../../content/developer/reference/cli.rst:616 msgid "Most of the command-line options can also be specified via a configuration file. Most of the time, they use similar names with the prefix ``-`` removed and other ``-`` are replaced by ``_`` e.g. :option:`--db-template` becomes ``db_template``." msgstr "" -#: ../../content/developer/reference/cli.rst:607 +#: ../../content/developer/reference/cli.rst:621 msgid "Some conversions don't match the pattern:" msgstr "" -#: ../../content/developer/reference/cli.rst:609 +#: ../../content/developer/reference/cli.rst:623 msgid ":option:`--db-filter` becomes ``dbfilter``" msgstr "" -#: ../../content/developer/reference/cli.rst:610 +#: ../../content/developer/reference/cli.rst:624 msgid ":option:`--no-http` corresponds to the ``http_enable`` boolean" msgstr "" -#: ../../content/developer/reference/cli.rst:611 +#: ../../content/developer/reference/cli.rst:625 msgid "logging presets (all options starting with ``--log-`` except for :option:`--log-handler` and :option:`--log-db`) just add content to ``log_handler``, use that directly in the configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:614 +#: ../../content/developer/reference/cli.rst:628 msgid ":option:`--smtp` is stored as ``smtp_server``" msgstr "" -#: ../../content/developer/reference/cli.rst:615 +#: ../../content/developer/reference/cli.rst:629 msgid ":option:`--database` is stored as ``db_name``" msgstr "" -#: ../../content/developer/reference/cli.rst:616 +#: ../../content/developer/reference/cli.rst:630 msgid ":option:`--i18n-import` and :option:`--i18n-export` aren't available at all from configuration files" msgstr "" -#: ../../content/developer/reference/cli.rst:621 +#: ../../content/developer/reference/cli.rst:635 msgid "The default configuration file is :file:`{$HOME}/.odoorc` which can be overridden using :option:`--config `. Specifying :option:`--save ` will save the current configuration state back to that file. The configuration items relative to the command-line are to be specified in the section ``[options]``." msgstr "" -#: ../../content/developer/reference/cli.rst:627 +#: ../../content/developer/reference/cli.rst:641 msgid "Here is a sample file:" msgstr "" -#: ../../content/developer/reference/cli.rst:652 +#: ../../content/developer/reference/cli.rst:666 msgid "Shell" msgstr "" -#: ../../content/developer/reference/cli.rst:654 +#: ../../content/developer/reference/cli.rst:668 msgid "Odoo command-line also allows to launch odoo as a python console environment. This enables direct interaction with the :ref:`orm ` and its functionalities." msgstr "" -#: ../../content/developer/reference/cli.rst:664 +#: ../../content/developer/reference/cli.rst:678 msgid "Specify a preferred REPL to use in shell mode." msgstr "" -#: ../../content/developer/reference/cli.rst:670 +#: ../../content/developer/reference/cli.rst:684 msgid "Scaffolding" msgstr "" -#: ../../content/developer/reference/cli.rst:674 +#: ../../content/developer/reference/cli.rst:688 msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are." msgstr "" -#: ../../content/developer/reference/cli.rst:679 +#: ../../content/developer/reference/cli.rst:693 msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand." msgstr "" -#: ../../content/developer/reference/cli.rst:687 +#: ../../content/developer/reference/cli.rst:701 msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, ā€¦)" msgstr "" -#: ../../content/developer/reference/cli.rst:692 +#: ../../content/developer/reference/cli.rst:706 msgid "directory in which to create the new module, defaults to the current directory" msgstr "" -#: ../../content/developer/reference/cli.rst:697 +#: ../../content/developer/reference/cli.rst:711 msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory" msgstr "" -#: ../../content/developer/reference/cli.rst:701 +#: ../../content/developer/reference/cli.rst:715 msgid "This will create module *my_module* in directory */addons/*." msgstr "" -#: ../../content/developer/reference/cli.rst:706 +#: ../../content/developer/reference/cli.rst:720 msgid "Database Population" msgstr "" -#: ../../content/developer/reference/cli.rst:710 +#: ../../content/developer/reference/cli.rst:724 msgid "Odoo CLI supports database population features. If the feature is :ref:`implemented on a given model `, it allows automatic data generation of the model's records to test your modules in databases containing non-trivial amounts of records." msgstr "" -#: ../../content/developer/reference/cli.rst:721 +#: ../../content/developer/reference/cli.rst:735 msgid "list of models for which the database should be filled" msgstr "" -#: ../../content/developer/reference/cli.rst:725 +#: ../../content/developer/reference/cli.rst:739 msgid "population size, the actual records number depends on the model's `_populate_sizes` attribute. The generated records content is specified by the :meth:`~odoo.models._populate_factories` method of a given model (cf. the :file:`populate` folder of modules for further details)." msgstr "" -#: ../../content/developer/reference/cli.rst:730 +#: ../../content/developer/reference/cli.rst:744 msgid ":ref:`reference/performance/populate`" msgstr "" -#: ../../content/developer/reference/cli.rst:735 +#: ../../content/developer/reference/cli.rst:749 msgid "Cloc" msgstr "" -#: ../../content/developer/reference/cli.rst:739 +#: ../../content/developer/reference/cli.rst:753 msgid "Odoo Cloc is a tool to count the number of relevant lines written in Python, Javascript, CSS, SCSS, or XML. This can be used as a rough metric for pricing maintenance of extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:744 +#: ../../content/developer/reference/cli.rst:758 msgid "Command-line options" msgstr "" -#: ../../content/developer/reference/cli.rst:749 +#: ../../content/developer/reference/cli.rst:763 msgid "Process the code of all extra modules installed on the provided database, and of all server actions and computed fields manually created in the provided database." msgstr "" -#: ../../content/developer/reference/cli.rst:751 +#: ../../content/developer/reference/cli.rst:765 msgid "The :option:`--addons-path` option is required to specify the path(s) to the module folder(s)." msgstr "" -#: ../../content/developer/reference/cli.rst:754 +#: ../../content/developer/reference/cli.rst:768 msgid "If combined with :option:`--path`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:761 +#: ../../content/developer/reference/cli.rst:775 msgid ":ref:`reference/cmdline/cloc/database-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:766 +#: ../../content/developer/reference/cli.rst:780 msgid "Process the files in the provided path." msgstr "" -#: ../../content/developer/reference/cli.rst:769 +#: ../../content/developer/reference/cli.rst:783 msgid "If combined with :option:`--database`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:776 +#: ../../content/developer/reference/cli.rst:790 msgid "Multiple paths can be provided by repeating the option." msgstr "" -#: ../../content/developer/reference/cli.rst:783 +#: ../../content/developer/reference/cli.rst:797 msgid ":ref:`reference/cmdline/cloc/path-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:790 +#: ../../content/developer/reference/cli.rst:804 msgid "Required if the :option:`--database` option is used." msgstr "" -#: ../../content/developer/reference/cli.rst:795 +#: ../../content/developer/reference/cli.rst:809 msgid "Specify a configuration file to use in place of the :option:`--addons-path` option." msgstr "" -#: ../../content/developer/reference/cli.rst:804 +#: ../../content/developer/reference/cli.rst:818 msgid "Show the details of lines counted for each file." msgstr "" -#: ../../content/developer/reference/cli.rst:808 +#: ../../content/developer/reference/cli.rst:822 msgid "Processed files" msgstr "" -#: ../../content/developer/reference/cli.rst:813 +#: ../../content/developer/reference/cli.rst:827 msgid "With the :option:`--database` option" msgstr "" -#: ../../content/developer/reference/cli.rst:815 +#: ../../content/developer/reference/cli.rst:829 msgid "Odoo Cloc counts the lines in each file of extra installed modules in a given database. In addition, it counts the Python lines of server actions and custom computed fields that have been directly created in the database or imported. Finally, it counts the lines of code of Javascript, CSS, and SCSS files, and of QWeb views from imported modules." msgstr "" -#: ../../content/developer/reference/cli.rst:821 +#: ../../content/developer/reference/cli.rst:835 msgid "Some files are excluded from the count by default:" msgstr "" -#: ../../content/developer/reference/cli.rst:823 +#: ../../content/developer/reference/cli.rst:837 msgid "The manifest (:file:`__manifest__.py` or :file:`__openerp__.py`)" msgstr "" -#: ../../content/developer/reference/cli.rst:824 +#: ../../content/developer/reference/cli.rst:838 msgid "The contents of the folder :file:`static/lib`" msgstr "" -#: ../../content/developer/reference/cli.rst:825 +#: ../../content/developer/reference/cli.rst:839 msgid "The tests defined in the folder :file:`tests` and :file:`static/tests`" msgstr "" -#: ../../content/developer/reference/cli.rst:826 +#: ../../content/developer/reference/cli.rst:840 msgid "The migrations scripts defined in the folder :file:`migrations` and `upgrades`" msgstr "" -#: ../../content/developer/reference/cli.rst:827 +#: ../../content/developer/reference/cli.rst:841 msgid "The XML files declared in the ``demo`` or ``demo_xml`` sections of the manifest" msgstr "" -#: ../../content/developer/reference/cli.rst:829 +#: ../../content/developer/reference/cli.rst:843 msgid "For special cases, a list of files that should be ignored by Odoo Cloc can be defined per module. This is specified by the ``cloc_exclude`` entry of the manifest:" msgstr "" -#: ../../content/developer/reference/cli.rst:842 +#: ../../content/developer/reference/cli.rst:856 msgid "The pattern ``**/*`` can be used to ignore an entire module. This can be useful to exclude a module from maintenance service costs." msgstr "" -#: ../../content/developer/reference/cli.rst:844 +#: ../../content/developer/reference/cli.rst:858 msgid "For more information about the pattern syntax, see `glob `_." msgstr "" -#: ../../content/developer/reference/cli.rst:849 +#: ../../content/developer/reference/cli.rst:863 msgid "With the :option:`--path` option" msgstr "" -#: ../../content/developer/reference/cli.rst:851 +#: ../../content/developer/reference/cli.rst:865 msgid "This method works the same as with the :ref:`--database option ` if a manifest file is present in the given folder. Otherwise, it counts all files." msgstr "" -#: ../../content/developer/reference/cli.rst:857 +#: ../../content/developer/reference/cli.rst:871 msgid "Identifying Extra Modules" msgstr "" -#: ../../content/developer/reference/cli.rst:859 +#: ../../content/developer/reference/cli.rst:873 msgid "To distinguish between standard and extra modules, Odoo Cloc uses the following heuristic: modules that are located (real file system path, after following symbolic links) in the same parent directory as the ``base``, ``web`` or ``web_enterprise`` standard modules are considered standard. Other modules are treated as extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:866 +#: ../../content/developer/reference/cli.rst:880 #: ../../content/developer/reference/frontend/services.rst:662 msgid "Error Handling" msgstr "" -#: ../../content/developer/reference/cli.rst:868 +#: ../../content/developer/reference/cli.rst:882 msgid "Some file cannot be counted by Odoo Cloc. Those file are reported at the end of the output." msgstr "" -#: ../../content/developer/reference/cli.rst:872 +#: ../../content/developer/reference/cli.rst:886 msgid "Max file size exceeded" msgstr "" -#: ../../content/developer/reference/cli.rst:874 +#: ../../content/developer/reference/cli.rst:888 msgid "Odoo Cloc rejects any file larger than 25MB. Usually, source files are smaller than 1 MB. If a file is rejected, it may be:" msgstr "" -#: ../../content/developer/reference/cli.rst:877 +#: ../../content/developer/reference/cli.rst:891 msgid "A generated XML file that contains lots of data. It should be excluded in the manifest." msgstr "" -#: ../../content/developer/reference/cli.rst:878 +#: ../../content/developer/reference/cli.rst:892 msgid "A JavaScript library that should be placed in the :file:`static/lib` folder." msgstr "" -#: ../../content/developer/reference/cli.rst:881 +#: ../../content/developer/reference/cli.rst:895 msgid "Syntax Error" msgstr "" -#: ../../content/developer/reference/cli.rst:883 +#: ../../content/developer/reference/cli.rst:897 msgid "Odoo Cloc cannot count the lines of code of a Python file with a syntax problem. If an extra module contains such files, they should be fixed to allow the module to load. If the module works despite the presence of those files, they are probably not loaded and should therefore be removed from the module, or at least excluded in the manifest via ``cloc_exclude``." msgstr "" -#: ../../content/developer/reference/cli.rst:890 +#: ../../content/developer/reference/cli.rst:904 msgid "TSConfig Generator" msgstr "" -#: ../../content/developer/reference/cli.rst:894 +#: ../../content/developer/reference/cli.rst:908 msgid "When working on javascript, there are ways to help your editor providing you with powerful auto-completion. One of those ways is the use of a tsconfig.json file. Originally meant for typescript, editors can use its information with plain javascript also. With this config file, you will now have full auto-completion across modules." msgstr "" -#: ../../content/developer/reference/cli.rst:899 +#: ../../content/developer/reference/cli.rst:913 msgid "The command to generate this files takes as many unnamed arguments as you need. Those are relative paths to your addon directories. In the example below, we move up one folder to save the tsconfig file in the folder containing community and enterprise." msgstr "" @@ -15206,7 +14582,7 @@ msgid "Odoo provides a service to automate the processing of documents of type * msgstr "" #: ../../content/developer/reference/extract_api.rst:8 -msgid "The service scans documents using an :abbr:`OCR (Optical Character Recognition)` engine and then uses :abbr:`AI(Artificial Intelligence)`-based algorithms to extract fields of interest such as the total, due date, or invoice lines for *invoices*, the total, date, payment reference for *expenses*, or the name, email, phone number for *resumes*." +msgid "The service scans documents using an :abbr:`OCR (Optical Character Recognition)` engine and then uses :abbr:`AI(Artificial Intelligence)`-based algorithms to extract fields of interest such as the total, due date, or invoice lines for *invoices*, the total, date for *expenses*, or the name, email, phone number for *resumes*." msgstr "" #: ../../content/developer/reference/extract_api.rst:13 @@ -15217,47 +14593,59 @@ msgstr "" msgid "You can either use this service directly in the Accounting, Expense, or Recruitment App or through the API. The Extract API, which is detailed in the next section, allows you to integrate our service directly into your own projects." msgstr "" +#: ../../content/developer/reference/extract_api.rst:22 +#: ../../content/developer/reference/frontend/javascript_reference.rst:17 +#: ../../content/developer/reference/frontend/services.rst:144 +#: ../../content/developer/reference/frontend/services.rst:182 +#: ../../content/developer/reference/frontend/services.rst:362 +#: ../../content/developer/reference/frontend/services.rst:408 +#: ../../content/developer/reference/frontend/services.rst:522 +#: ../../content/developer/reference/frontend/services.rst:612 +#: ../../content/developer/reference/frontend/services.rst:708 +#: ../../content/developer/reference/frontend/services.rst:759 +#: ../../content/developer/reference/frontend/services.rst:834 +#: ../../content/developer/reference/user_interface/scss_inheritance.rst:6 +msgid "Overview" +msgstr "" + #: ../../content/developer/reference/extract_api.rst:24 msgid "The extract API uses the JSON-RPC2_ protocol; its endpoint routes are located at `https://extract.api.odoo.com`." msgstr "" -#: ../../content/developer/reference/extract_api.rst:28 +#: ../../content/developer/reference/extract_api.rst:30 msgid "Version" msgstr "" -#: ../../content/developer/reference/extract_api.rst:30 +#: ../../content/developer/reference/extract_api.rst:32 msgid "The version of the Extract API is specified in the route." msgstr "" -#: ../../content/developer/reference/extract_api.rst:35 +#: ../../content/developer/reference/extract_api.rst:37 msgid "The latest versions are:" msgstr "" -#: ../../content/developer/reference/extract_api.rst:33 -#: ../../content/developer/reference/extract_api.rst:221 +#: ../../content/developer/reference/extract_api.rst:35 msgid "invoices: 122" msgstr "" -#: ../../content/developer/reference/extract_api.rst:34 -#: ../../content/developer/reference/extract_api.rst:222 +#: ../../content/developer/reference/extract_api.rst:36 msgid "expenses: 132" msgstr "" -#: ../../content/developer/reference/extract_api.rst:35 -#: ../../content/developer/reference/extract_api.rst:223 +#: ../../content/developer/reference/extract_api.rst:37 msgid "applicant: 102" msgstr "" -#: ../../content/developer/reference/extract_api.rst:38 +#: ../../content/developer/reference/extract_api.rst:40 msgid "Flow" msgstr "" -#: ../../content/developer/reference/extract_api.rst:40 -msgid "The flow is the same for the three services." +#: ../../content/developer/reference/extract_api.rst:42 +msgid "The flow is the same for each document type." msgstr "" #: ../../content/developer/reference/extract_api.rst:0 -msgid "Call :ref:`/parse ` to submit your invoices (one call for each invoice). On success, you receive a `document_uuid` in the response." +msgid "Call :ref:`/parse ` to submit your documents (one call for each document). On success, you receive a `document_token` in the response." msgstr "" #: ../../content/developer/reference/extract_api.rst:0 @@ -15268,854 +14656,693 @@ msgstr "" msgid "Alternatively, you can provide a `webhook_url` at the time of the call to :ref:`/parse ` and you will be notified (via a POST request) when the result is ready." msgstr "" -#: ../../content/developer/reference/extract_api.rst:0 -msgid "Once the result is received, you can validate it by calling :ref:`/validate ` and sending the expected values." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:0 -msgid "This step is optional but greatly helps the system to improve." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:53 +#: ../../content/developer/reference/extract_api.rst:52 msgid "The HTTP POST method should be used for all of them. A python implementation of the full flow for invoices can be found :download:`here ` and a token for integration testing is provided in the :ref:`integration testing section `." msgstr "" -#: ../../content/developer/reference/extract_api.rst:60 +#: ../../content/developer/reference/extract_api.rst:59 msgid "Parse" msgstr "" -#: ../../content/developer/reference/extract_api.rst:62 -msgid "Request the processing of a document from the OCR. The route will return a `document_uuid` (it replaces `document_id`, which is deprecated); you can use it to obtain the result of your request." +#: ../../content/developer/reference/extract_api.rst:61 +msgid "Request the processing of a document from the OCR. The route will return a `document_token`, you can use it to obtain the result of your request." msgstr "" -#: ../../content/developer/reference/extract_api.rst:69 -#: ../../content/developer/reference/extract_api.rst:235 -#: ../../content/developer/reference/extract_api.rst:551 +#: ../../content/developer/reference/extract_api.rst:67 +#: ../../content/developer/reference/extract_api.rst:213 msgid "Routes" msgstr "" +#: ../../content/developer/reference/extract_api.rst:69 +msgid "/api/extract/invoice/2/parse" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:70 +msgid "/api/extract/expense/2/parse" +msgstr "" + #: ../../content/developer/reference/extract_api.rst:71 -msgid "/api/extract/invoice/1/parse" +msgid "/api/extract/applicant/2/parse" msgstr "" -#: ../../content/developer/reference/extract_api.rst:72 -msgid "/api/extract/expense/1/parse" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:73 -msgid "/api/extract/applicant/1/parse" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:74 -msgid "|ss| /iap/invoice_extract/parse |se| (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:75 -msgid "|ss| /iap/expense_extract/parse |se| (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:82 -#: ../../content/developer/reference/extract_api.rst:248 -#: ../../content/developer/reference/extract_api.rst:567 +#: ../../content/developer/reference/extract_api.rst:78 +#: ../../content/developer/reference/extract_api.rst:224 msgid "``jsonrpc`` (required)" msgstr "" +#: ../../content/developer/reference/extract_api.rst:79 +#: ../../content/developer/reference/extract_api.rst:81 #: ../../content/developer/reference/extract_api.rst:83 -#: ../../content/developer/reference/extract_api.rst:85 -#: ../../content/developer/reference/extract_api.rst:87 -#: ../../content/developer/reference/extract_api.rst:170 -#: ../../content/developer/reference/extract_api.rst:172 -#: ../../content/developer/reference/extract_api.rst:249 -#: ../../content/developer/reference/extract_api.rst:251 -#: ../../content/developer/reference/extract_api.rst:253 -#: ../../content/developer/reference/extract_api.rst:289 -#: ../../content/developer/reference/extract_api.rst:291 -#: ../../content/developer/reference/extract_api.rst:568 -#: ../../content/developer/reference/extract_api.rst:570 -#: ../../content/developer/reference/extract_api.rst:572 -#: ../../content/developer/reference/extract_api.rst:696 -#: ../../content/developer/reference/extract_api.rst:698 +#: ../../content/developer/reference/extract_api.rst:167 +#: ../../content/developer/reference/extract_api.rst:169 +#: ../../content/developer/reference/extract_api.rst:225 +#: ../../content/developer/reference/extract_api.rst:227 +#: ../../content/developer/reference/extract_api.rst:229 +#: ../../content/developer/reference/extract_api.rst:263 +#: ../../content/developer/reference/extract_api.rst:265 msgid "see JSON-RPC2_" msgstr "" -#: ../../content/developer/reference/extract_api.rst:84 -#: ../../content/developer/reference/extract_api.rst:250 -#: ../../content/developer/reference/extract_api.rst:569 +#: ../../content/developer/reference/extract_api.rst:80 +#: ../../content/developer/reference/extract_api.rst:226 msgid "``method`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:86 -#: ../../content/developer/reference/extract_api.rst:252 -#: ../../content/developer/reference/extract_api.rst:571 +#: ../../content/developer/reference/extract_api.rst:82 +#: ../../content/developer/reference/extract_api.rst:228 msgid "``id`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:136 -#: ../../content/developer/reference/extract_api.rst:264 +#: ../../content/developer/reference/extract_api.rst:131 +#: ../../content/developer/reference/extract_api.rst:238 msgid "``params``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:92 +#: ../../content/developer/reference/extract_api.rst:88 +#: ../../content/developer/reference/extract_api.rst:238 msgid "``account_token`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:92 +#: ../../content/developer/reference/extract_api.rst:88 msgid "The token of the account from which credits will be taken. Each successful call costs one token." msgstr "" -#: ../../content/developer/reference/extract_api.rst:96 -msgid "``version`` (optional)" +#: ../../content/developer/reference/extract_api.rst:91 +#: ../../content/developer/reference/extract_api.rst:233 +msgid "``version`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:95 -msgid "The version will determine the format of your requests and the format of the server response. Some results can be unavailable in older versions. If not specified, the latest version will be used." +#: ../../content/developer/reference/extract_api.rst:91 +msgid "The version will determine the format of your requests and the format of the server response. You should use the :ref:`latest version available `." msgstr "" -#: ../../content/developer/reference/extract_api.rst:102 +#: ../../content/developer/reference/extract_api.rst:97 msgid "``documents`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:99 +#: ../../content/developer/reference/extract_api.rst:94 msgid "The document must be provided as a string in the ASCII encoding. The list should contain only one string. If multiple strings are provided only the first string corresponding to a pdf will be processed. If no pdf is found, the first string will be processed. This field is a list only for legacy reasons. The supported extensions are *pdf*, *png*, *jpg* and *bmp*." msgstr "" -#: ../../content/developer/reference/extract_api.rst:104 +#: ../../content/developer/reference/extract_api.rst:99 msgid "``dbuuid`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:105 +#: ../../content/developer/reference/extract_api.rst:100 msgid "Unique identifier of the Odoo database." msgstr "" -#: ../../content/developer/reference/extract_api.rst:107 +#: ../../content/developer/reference/extract_api.rst:102 msgid "``webhook_url`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:107 -msgid "A webhook URL can be provided. An empty POST request will be sent to ``webhook_url/document_uuid`` when the result is ready." +#: ../../content/developer/reference/extract_api.rst:102 +msgid "A webhook URL can be provided. An empty POST request will be sent to ``webhook_url/document_token`` when the result is ready." msgstr "" -#: ../../content/developer/reference/extract_api.rst:136 +#: ../../content/developer/reference/extract_api.rst:131 msgid "``user_infos`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:110 +#: ../../content/developer/reference/extract_api.rst:105 msgid "Information concerning the person sending the document to the extract service. It can be the client or the supplier (depending on the ``perspective``). This information is not required in order for the service to work but it greatly improves the quality of the result." msgstr "" -#: ../../content/developer/reference/extract_api.rst:116 +#: ../../content/developer/reference/extract_api.rst:111 msgid "``user_company_vat`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:117 +#: ../../content/developer/reference/extract_api.rst:112 msgid "VAT number of the user." msgstr "" -#: ../../content/developer/reference/extract_api.rst:118 +#: ../../content/developer/reference/extract_api.rst:113 msgid "``user_company_name`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:119 +#: ../../content/developer/reference/extract_api.rst:114 msgid "Name of the userā€™s company." msgstr "" -#: ../../content/developer/reference/extract_api.rst:121 +#: ../../content/developer/reference/extract_api.rst:116 msgid "``user_company_country_code`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:121 +#: ../../content/developer/reference/extract_api.rst:116 msgid "Country code of the user. Format: `ISO3166 alpha-2 `_." msgstr "" -#: ../../content/developer/reference/extract_api.rst:123 +#: ../../content/developer/reference/extract_api.rst:118 msgid "``user_lang`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:124 +#: ../../content/developer/reference/extract_api.rst:119 msgid "The user language. Format: *language_code + _ + locale* (e.g. fr_FR, en_US)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:125 +#: ../../content/developer/reference/extract_api.rst:120 msgid "``user_email`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:126 +#: ../../content/developer/reference/extract_api.rst:121 msgid "The user email." msgstr "" -#: ../../content/developer/reference/extract_api.rst:127 +#: ../../content/developer/reference/extract_api.rst:122 msgid "``purchase_order_regex`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:128 +#: ../../content/developer/reference/extract_api.rst:123 msgid "Regex for purchase order identification. Will default to Odoo PO format if not provided." msgstr "" -#: ../../content/developer/reference/extract_api.rst:136 +#: ../../content/developer/reference/extract_api.rst:131 msgid "``perspective`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:132 +#: ../../content/developer/reference/extract_api.rst:127 msgid "Can be ``client`` or ``supplier``. This field is useful for invoices only. ``client`` means that the user information provided are related to the client of the invoice. ``supplier`` means that it's related to the supplier. If not provided, client will be used." msgstr "" -#: ../../content/developer/reference/extract_api.rst:161 +#: ../../content/developer/reference/extract_api.rst:158 msgid "The ``user_infos`` parameter is optional but it greatly improves the quality of the result, especially for invoices. The more information you can provide, the better." msgstr "" -#: ../../content/developer/reference/extract_api.rst:169 -#: ../../content/developer/reference/extract_api.rst:288 -#: ../../content/developer/reference/extract_api.rst:695 +#: ../../content/developer/reference/extract_api.rst:166 +#: ../../content/developer/reference/extract_api.rst:262 msgid "``jsonrpc``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:189 -#: ../../content/developer/reference/extract_api.rst:309 -#: ../../content/developer/reference/extract_api.rst:707 +#: ../../content/developer/reference/extract_api.rst:178 +#: ../../content/developer/reference/extract_api.rst:279 msgid "``result``" msgstr "" +#: ../../content/developer/reference/extract_api.rst:173 +#: ../../content/developer/reference/extract_api.rst:269 +msgid "``status``" +msgstr "" + #: ../../content/developer/reference/extract_api.rst:174 -#: ../../content/developer/reference/extract_api.rst:255 -msgid "Dictionary containing the following content." +#: ../../content/developer/reference/extract_api.rst:270 +msgid "The code indicating the status of the request. See the table below." msgstr "" -#: ../../content/developer/reference/extract_api.rst:179 -msgid "``status`` (replaces ``status_code``)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:179 -msgid "The code indicating the status of the request. \"success\" in case of success. Other values are detailed in the table below." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:181 -#: ../../content/developer/reference/extract_api.rst:301 -#: ../../content/developer/reference/extract_api.rst:704 +#: ../../content/developer/reference/extract_api.rst:175 +#: ../../content/developer/reference/extract_api.rst:271 msgid "``status_msg``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:182 +#: ../../content/developer/reference/extract_api.rst:176 +#: ../../content/developer/reference/extract_api.rst:272 msgid "A string giving verbose details about the request status." msgstr "" -#: ../../content/developer/reference/extract_api.rst:183 -msgid "``document_uuid`` (replaces ``document_id``)" +#: ../../content/developer/reference/extract_api.rst:178 +msgid "``document_token``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:184 -#: ../../content/developer/reference/extract_api.rst:189 -#: ../../content/developer/reference/extract_api.rst:304 +#: ../../content/developer/reference/extract_api.rst:178 +#: ../../content/developer/reference/extract_api.rst:274 msgid "Only present if the request is successful." msgstr "" -#: ../../content/developer/reference/extract_api.rst:186 -#: ../../content/developer/reference/extract_api.rst:707 -msgid "``status_code`` (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:186 -msgid "The code indicating the status of the request. 0 in case of success. Other values are detailed in the table below." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:189 -#: ../../content/developer/reference/extract_api.rst:587 -msgid "``document_id`` (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:192 +#: ../../content/developer/reference/extract_api.rst:181 +#: ../../content/developer/reference/extract_api.rst:282 #: ../../content/developer/tutorials/getting_started/08_relations.rst:244 msgid "status" msgstr "" -#: ../../content/developer/reference/extract_api.rst:192 -#: ../../content/developer/reference/extract_api.rst:710 +#: ../../content/developer/reference/extract_api.rst:181 +#: ../../content/developer/reference/extract_api.rst:282 msgid "status_msg" msgstr "" -#: ../../content/developer/reference/extract_api.rst:192 -#: ../../content/developer/reference/extract_api.rst:710 -msgid "status_code (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:194 -#: ../../content/developer/reference/extract_api.rst:712 +#: ../../content/developer/reference/extract_api.rst:183 +#: ../../content/developer/reference/extract_api.rst:284 msgid "`success`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:194 -#: ../../content/developer/reference/extract_api.rst:712 -msgid "0" +#: ../../content/developer/reference/extract_api.rst:184 +#: ../../content/developer/reference/extract_api.rst:285 +msgid "`error_unsupported_version`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:195 +#: ../../content/developer/reference/extract_api.rst:184 +#: ../../content/developer/reference/extract_api.rst:285 +msgid "Unsupported version" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:185 +#: ../../content/developer/reference/extract_api.rst:286 msgid "`error_internal`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:195 +#: ../../content/developer/reference/extract_api.rst:185 +#: ../../content/developer/reference/extract_api.rst:286 msgid "An error occurred" msgstr "" -#: ../../content/developer/reference/extract_api.rst:195 -msgid "2" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:196 +#: ../../content/developer/reference/extract_api.rst:186 msgid "`error_no_credit`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:196 +#: ../../content/developer/reference/extract_api.rst:186 msgid "You don't have enough credit" msgstr "" -#: ../../content/developer/reference/extract_api.rst:196 -msgid "3" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:197 +#: ../../content/developer/reference/extract_api.rst:187 msgid "`error_unsupported_format`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:197 +#: ../../content/developer/reference/extract_api.rst:187 msgid "Unsupported file format" msgstr "" -#: ../../content/developer/reference/extract_api.rst:197 -#: ../../content/developer/tutorials/define_module_data.rst:183 -msgid "6" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:198 +#: ../../content/developer/reference/extract_api.rst:188 +#: ../../content/developer/reference/extract_api.rst:287 msgid "`error_maintenance`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:198 -msgid "Server is currently under maintenance. Please try again later." +#: ../../content/developer/reference/extract_api.rst:188 +#: ../../content/developer/reference/extract_api.rst:287 +msgid "Server is currently under maintenance, please try again later" msgstr "" -#: ../../content/developer/reference/extract_api.rst:199 -msgid "9" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:217 -msgid "The ``document_id`` field is deprecated and will be removed in the future. Please use ``document_uuid`` instead." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:222 -msgid "Version introducing ``document_uuid``:" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:226 +#: ../../content/developer/reference/extract_api.rst:204 msgid "The API does not actually use the JSON-RPC error scheme. Instead the API has its own error scheme bundled inside a successful JSON-RPC result." msgstr "" -#: ../../content/developer/reference/extract_api.rst:230 +#: ../../content/developer/reference/extract_api.rst:208 msgid "Get results" msgstr "" -#: ../../content/developer/reference/extract_api.rst:237 -msgid "/api/extract/invoice/1/get_result" +#: ../../content/developer/reference/extract_api.rst:215 +msgid "/api/extract/invoice/2/get_result" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:216 +msgid "/api/extract/expense/2/get_result" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:217 +msgid "/api/extract/applicant/2/get_result" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:234 +msgid "The version should match the version passed to the :ref:`/parse ` request." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:235 +msgid "``document_token`` (required)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:236 +msgid "The ``document_token`` for which you want to get the current parsing status." msgstr "" #: ../../content/developer/reference/extract_api.rst:238 -msgid "/api/extract/expense/1/get_result" +msgid "The token of the account that was used to submit the document." msgstr "" -#: ../../content/developer/reference/extract_api.rst:239 -msgid "/api/extract/applicant/1/get_result" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:240 -msgid "|ss| /iap/invoice_extract/get_result |se| (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:241 -msgid "|ss| /iap/expense_extract/get_result |se| (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:259 -msgid "``version`` (required)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:260 -#: ../../content/developer/reference/extract_api.rst:298 -#: ../../content/developer/reference/extract_api.rst:300 -#: ../../content/developer/reference/extract_api.rst:302 -#: ../../content/developer/reference/extract_api.rst:579 -#: ../../content/developer/reference/extract_api.rst:584 -#: ../../content/developer/reference/extract_api.rst:703 -#: ../../content/developer/reference/extract_api.rst:705 -#: ../../content/developer/reference/extract_api.rst:707 -msgid "|SAME_AS_PARSE|" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:261 -msgid "``documents_uuid`` (required, replaces ``documents_id``)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:262 -msgid "The ``document_uuid`` for which you want to get the current parsing status." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:264 -msgid "``documents_id`` (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:264 -msgid "The ``document_id`` for which you want to get the current parsing status." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:282 +#: ../../content/developer/reference/extract_api.rst:256 msgid "When getting the results from the parse, the detected field vary a lot depending on the type of document. Each response is a list of dictionaries, one for each document. The keys of the dictionary are the name of the field and the value is the value of the field." msgstr "" -#: ../../content/developer/reference/extract_api.rst:293 -msgid "Dictionary where each key is a document_id. For each ``document_id``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:297 -#: ../../content/developer/reference/extract_api.rst:702 -msgid "``status``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:299 -msgid "``status_code``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:309 +#: ../../content/developer/reference/extract_api.rst:279 msgid "``results``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:309 +#: ../../content/developer/reference/extract_api.rst:279 msgid "``full_text_annotation``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:309 +#: ../../content/developer/reference/extract_api.rst:279 msgid "Contains the unprocessed full result from the OCR for the document" msgstr "" -#: ../../content/developer/reference/extract_api.rst:333 +#: ../../content/developer/reference/extract_api.rst:288 +msgid "`error_document_not_found`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:288 +msgid "The document could not be found" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:289 +msgid "`error_unsupported_size`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:289 +msgid "The document has been rejected because it is too small" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:290 +msgid "`error_no_page_count`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:290 +msgid "Unable to get page count of the PDF file" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:291 +msgid "`error_pdf_conversion_to_images`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:291 +msgid "Couldn't convert the PDF to images" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:292 +msgid "`error_password_protected`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:292 +msgid "The PDF file is protected by a password" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:293 +msgid "`error_too_many_pages`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:293 +msgid "The document contains too many pages" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:317 msgid "Common fields" msgstr "" -#: ../../content/developer/reference/extract_api.rst:338 +#: ../../content/developer/reference/extract_api.rst:322 msgid "``feature_result``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:340 +#: ../../content/developer/reference/extract_api.rst:324 msgid "Each field of interest we want to extract from the document such as the total or the due date are also called **features**. An exhaustive list of all the extracted features associated to a type of document can be found in the sections below." msgstr "" -#: ../../content/developer/reference/extract_api.rst:344 +#: ../../content/developer/reference/extract_api.rst:328 msgid "For each feature, we return a list of candidates and we spotlight the candidate our model predicts to be the best fit for the feature." msgstr "" -#: ../../content/developer/reference/extract_api.rst:349 +#: ../../content/developer/reference/extract_api.rst:333 msgid "``selected_value`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:350 +#: ../../content/developer/reference/extract_api.rst:334 msgid "The best candidate for this feature." msgstr "" -#: ../../content/developer/reference/extract_api.rst:351 +#: ../../content/developer/reference/extract_api.rst:335 msgid "``selected_values`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:352 +#: ../../content/developer/reference/extract_api.rst:336 msgid "The best candidates for this feature." msgstr "" -#: ../../content/developer/reference/extract_api.rst:354 +#: ../../content/developer/reference/extract_api.rst:338 msgid "``candidates`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:354 +#: ../../content/developer/reference/extract_api.rst:338 msgid "List of all the candidates for this feature ordered by decreasing confidence score." msgstr "" -#: ../../content/developer/reference/extract_api.rst:364 +#: ../../content/developer/reference/extract_api.rst:348 msgid "candidate" msgstr "" -#: ../../content/developer/reference/extract_api.rst:366 +#: ../../content/developer/reference/extract_api.rst:350 msgid "For each candidate we give its representation and position in the document. Candidates are sorted by decreasing order of suitability." msgstr "" -#: ../../content/developer/reference/extract_api.rst:371 +#: ../../content/developer/reference/extract_api.rst:355 msgid "``content``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:372 +#: ../../content/developer/reference/extract_api.rst:356 msgid "Representation of the candidate." msgstr "" -#: ../../content/developer/reference/extract_api.rst:377 +#: ../../content/developer/reference/extract_api.rst:361 msgid "``coords``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:376 +#: ../../content/developer/reference/extract_api.rst:360 msgid "``[center_x, center_y, width, height, rotation_angle]``. The position and dimensions are relative to the size of the page and are therefore between 0 and 1. The angle is a clockwise rotation measured in degrees." msgstr "" -#: ../../content/developer/reference/extract_api.rst:380 +#: ../../content/developer/reference/extract_api.rst:364 msgid "Page of the original document on which the candidate is located (starts at 0)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:395 +#: ../../content/developer/reference/extract_api.rst:379 msgid "Invoices" msgstr "" -#: ../../content/developer/reference/extract_api.rst:397 +#: ../../content/developer/reference/extract_api.rst:381 msgid "Invoices are complex and can have a lot of different fields. The following table gives an exhaustive list of all the fields we can extract from an invoice." msgstr "" -#: ../../content/developer/reference/extract_api.rst:401 -#: ../../content/developer/reference/extract_api.rst:507 -#: ../../content/developer/reference/extract_api.rst:527 +#: ../../content/developer/reference/extract_api.rst:385 +#: ../../content/developer/reference/extract_api.rst:489 +#: ../../content/developer/reference/extract_api.rst:509 msgid "Feature name" msgstr "" -#: ../../content/developer/reference/extract_api.rst:401 -#: ../../content/developer/reference/extract_api.rst:507 -#: ../../content/developer/reference/extract_api.rst:527 +#: ../../content/developer/reference/extract_api.rst:385 +#: ../../content/developer/reference/extract_api.rst:489 +#: ../../content/developer/reference/extract_api.rst:509 msgid "Specifities" msgstr "" -#: ../../content/developer/reference/extract_api.rst:403 +#: ../../content/developer/reference/extract_api.rst:387 msgid "``SWIFT_code``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:403 +#: ../../content/developer/reference/extract_api.rst:387 msgid "``content`` is a dictionary encoded as a string." msgstr "" -#: ../../content/developer/reference/extract_api.rst:405 +#: ../../content/developer/reference/extract_api.rst:389 msgid "It contains information about the detected SWIFT code (or `BIC `_)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:408 +#: ../../content/developer/reference/extract_api.rst:392 msgid "Keys:" msgstr "" -#: ../../content/developer/reference/extract_api.rst:412 +#: ../../content/developer/reference/extract_api.rst:396 msgid "``bic``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:413 +#: ../../content/developer/reference/extract_api.rst:397 msgid "detected BIC (string)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:414 +#: ../../content/developer/reference/extract_api.rst:398 msgid "``name`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:415 +#: ../../content/developer/reference/extract_api.rst:399 msgid "bank name (string)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:416 +#: ../../content/developer/reference/extract_api.rst:400 msgid "``country_code``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:417 +#: ../../content/developer/reference/extract_api.rst:401 msgid "ISO3166 alpha-2 country code of the bank (string)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:418 +#: ../../content/developer/reference/extract_api.rst:402 msgid "``city`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:419 +#: ../../content/developer/reference/extract_api.rst:403 msgid "city of the bank (string)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:421 +#: ../../content/developer/reference/extract_api.rst:405 msgid "``verified_bic``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:421 +#: ../../content/developer/reference/extract_api.rst:405 msgid "True if the BIC has been found in our DB (bool)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:423 +#: ../../content/developer/reference/extract_api.rst:407 msgid "Name and city are present only if verified_bic is true." msgstr "" -#: ../../content/developer/reference/extract_api.rst:425 +#: ../../content/developer/reference/extract_api.rst:409 msgid "``iban``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:425 -#: ../../content/developer/reference/extract_api.rst:427 -#: ../../content/developer/reference/extract_api.rst:429 -#: ../../content/developer/reference/extract_api.rst:436 -#: ../../content/developer/reference/extract_api.rst:438 +#: ../../content/developer/reference/extract_api.rst:409 +#: ../../content/developer/reference/extract_api.rst:411 +#: ../../content/developer/reference/extract_api.rst:413 +#: ../../content/developer/reference/extract_api.rst:420 +#: ../../content/developer/reference/extract_api.rst:422 +#: ../../content/developer/reference/extract_api.rst:424 +#: ../../content/developer/reference/extract_api.rst:428 +#: ../../content/developer/reference/extract_api.rst:430 +#: ../../content/developer/reference/extract_api.rst:432 #: ../../content/developer/reference/extract_api.rst:440 -#: ../../content/developer/reference/extract_api.rst:444 #: ../../content/developer/reference/extract_api.rst:446 #: ../../content/developer/reference/extract_api.rst:448 -#: ../../content/developer/reference/extract_api.rst:458 -#: ../../content/developer/reference/extract_api.rst:464 -#: ../../content/developer/reference/extract_api.rst:466 -#: ../../content/developer/reference/extract_api.rst:468 -#: ../../content/developer/reference/extract_api.rst:470 -#: ../../content/developer/reference/extract_api.rst:509 +#: ../../content/developer/reference/extract_api.rst:450 +#: ../../content/developer/reference/extract_api.rst:452 +#: ../../content/developer/reference/extract_api.rst:491 +#: ../../content/developer/reference/extract_api.rst:493 +#: ../../content/developer/reference/extract_api.rst:495 +#: ../../content/developer/reference/extract_api.rst:499 #: ../../content/developer/reference/extract_api.rst:511 #: ../../content/developer/reference/extract_api.rst:513 +#: ../../content/developer/reference/extract_api.rst:515 #: ../../content/developer/reference/extract_api.rst:517 -#: ../../content/developer/reference/extract_api.rst:529 -#: ../../content/developer/reference/extract_api.rst:531 -#: ../../content/developer/reference/extract_api.rst:533 -#: ../../content/developer/reference/extract_api.rst:535 msgid "``content`` is a string" msgstr "" -#: ../../content/developer/reference/extract_api.rst:427 +#: ../../content/developer/reference/extract_api.rst:411 msgid "``aba``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:429 +#: ../../content/developer/reference/extract_api.rst:413 msgid "``VAT_Number``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:431 +#: ../../content/developer/reference/extract_api.rst:415 msgid "Depending on the value of perspective in the user_infos, this will be the VAT number of the supplier or the client. If perspective is client, it'll be the supplier's VAT number. If it's supplier, it's the client's VAT number." msgstr "" -#: ../../content/developer/reference/extract_api.rst:436 +#: ../../content/developer/reference/extract_api.rst:420 msgid "``qr-bill``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:438 +#: ../../content/developer/reference/extract_api.rst:422 msgid "``payment_ref``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:440 +#: ../../content/developer/reference/extract_api.rst:424 msgid "``purchase_order``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:442 +#: ../../content/developer/reference/extract_api.rst:426 msgid "Uses ``selected_values`` instead of ``selected_value``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:444 -#: ../../content/developer/reference/extract_api.rst:511 +#: ../../content/developer/reference/extract_api.rst:428 +#: ../../content/developer/reference/extract_api.rst:493 msgid "``country``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:446 -#: ../../content/developer/reference/extract_api.rst:517 +#: ../../content/developer/reference/extract_api.rst:430 +#: ../../content/developer/reference/extract_api.rst:499 msgid "``currency``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:448 -#: ../../content/developer/reference/extract_api.rst:513 +#: ../../content/developer/reference/extract_api.rst:432 +#: ../../content/developer/reference/extract_api.rst:495 msgid "``date``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:450 +#: ../../content/developer/reference/extract_api.rst:434 msgid "Format : *YYYY-MM-DD*" msgstr "" -#: ../../content/developer/reference/extract_api.rst:452 +#: ../../content/developer/reference/extract_api.rst:436 msgid "``due_date``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:452 +#: ../../content/developer/reference/extract_api.rst:436 msgid "Same as for ``date``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:454 -msgid "``total_tax_amount`` (previously ``global_taxes_amount``)" +#: ../../content/developer/reference/extract_api.rst:438 +msgid "``total_tax_amount``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:454 -#: ../../content/developer/reference/extract_api.rst:460 -#: ../../content/developer/reference/extract_api.rst:462 -#: ../../content/developer/reference/extract_api.rst:515 +#: ../../content/developer/reference/extract_api.rst:438 +#: ../../content/developer/reference/extract_api.rst:442 +#: ../../content/developer/reference/extract_api.rst:444 +#: ../../content/developer/reference/extract_api.rst:497 msgid "``content`` is a float" msgstr "" -#: ../../content/developer/reference/extract_api.rst:458 +#: ../../content/developer/reference/extract_api.rst:440 msgid "``invoice_id``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:460 +#: ../../content/developer/reference/extract_api.rst:442 msgid "``subtotal``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:462 -#: ../../content/developer/reference/extract_api.rst:515 +#: ../../content/developer/reference/extract_api.rst:444 +#: ../../content/developer/reference/extract_api.rst:497 msgid "``total``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:464 +#: ../../content/developer/reference/extract_api.rst:446 msgid "``supplier``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:466 +#: ../../content/developer/reference/extract_api.rst:448 msgid "``client``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:468 -#: ../../content/developer/reference/extract_api.rst:531 +#: ../../content/developer/reference/extract_api.rst:450 +#: ../../content/developer/reference/extract_api.rst:513 msgid "``email``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:475 +#: ../../content/developer/reference/extract_api.rst:457 msgid "``feature_result`` for the ``invoice_lines`` feature" msgstr "" -#: ../../content/developer/reference/extract_api.rst:477 +#: ../../content/developer/reference/extract_api.rst:459 msgid "It follows a more specific structure. It is basically a list of dictionaries where each dictionary represents an invoice line. Each value follows a :ref:`latestextract_api/get_result/feature_result` structure." msgstr "" -#: ../../content/developer/reference/extract_api.rst:501 +#: ../../content/developer/reference/extract_api.rst:483 msgid "Expense" msgstr "" -#: ../../content/developer/reference/extract_api.rst:503 +#: ../../content/developer/reference/extract_api.rst:485 msgid "The expenses are less complex than invoices. The following table gives an exhaustive list of all the fields we can extract from an expense report." msgstr "" -#: ../../content/developer/reference/extract_api.rst:521 +#: ../../content/developer/reference/extract_api.rst:503 msgid "Applicant" msgstr "" -#: ../../content/developer/reference/extract_api.rst:523 +#: ../../content/developer/reference/extract_api.rst:505 msgid "This third type of document is meant for processing resumes. The following table gives an exhaustive list of all the fields we can extract from a resume." msgstr "" -#: ../../content/developer/reference/extract_api.rst:533 +#: ../../content/developer/reference/extract_api.rst:515 msgid "``phone``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:535 +#: ../../content/developer/reference/extract_api.rst:517 msgid "``mobile``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:540 -msgid "Validate" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:542 -msgid "The validation step is an optional step but is strongly recommended. By telling the system if it were right or wrong for each feature you give an important feedback. It has no direct impact but it helps the system to greatly improve its prediction accuracy for the documents you will send in the future." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:553 -msgid "/api/extract/invoice/1/validate" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:554 -msgid "/api/extract/invoice/1/validate_batch" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:555 -msgid "/api/extract/expense/1/validate" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:556 -msgid "/api/extract/expense/1/validate_batch" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:557 -msgid "/api/extract/applicant/1/validate" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:558 -msgid "/api/extract/applicant/1/validate_batch" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:559 -msgid "|ss| /iap/invoice_extract/validate |se| (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:560 -msgid "|ss| /iap/expense_extract/validate |se| (deprecated)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:587 -msgid "``params`` (``/validate`` route only)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:574 -#: ../../content/developer/reference/extract_api.rst:590 -msgid "dictionary containing the following fields" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:578 -msgid "``document_uuid`` (required, replaces ``document_id``)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:581 -msgid "Contains the validation for each feature. For invoices, the field ``merged_line`` indicates if the lines were merged or not." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:588 -msgid "``invoice_lines`` have been merged or not." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:596 -msgid "``params`` (``/validate_batch`` route only)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:596 -msgid "``documents``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:595 -msgid "Contains the validation for each feature for each document, the ``document_uuid`` are the keys and their values is the content of the ``value`` field of the ``/validate`` route." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:642 -msgid "You don't have to validate all the features in order for the validation to succeed. However :ref:`/validate ` can't be called multiple times for a same document. Therefore you should validate all the features you want to validate at once." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:647 -msgid "validation" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:649 -msgid "A **validation** for a given feature is a dictionary containing the textual representation of the expected value for this given feature. This format apply for all the features except for ``invoice_lines`` which has a more complex validation format." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:660 -msgid "invoice_lines" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:662 -msgid "**lines** is a list of dictionaries. Each dictionary represents an invoice line. The dictionary keys speak for themselves. Note that there is no ``content`` for this feature." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:710 -msgid "`status`" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:713 -msgid "`error_validation_format`" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:713 -msgid "Validation format is incorrect" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:713 -msgid "12" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:733 +#: ../../content/developer/reference/extract_api.rst:525 msgid "You can test your integration by using *integration_token* as ``account_token`` in the :ref:`/parse ` request." msgstr "" -#: ../../content/developer/reference/extract_api.rst:736 +#: ../../content/developer/reference/extract_api.rst:528 msgid "Using this token put you in test mode and allows you to simulate the entire flow without really parsing a document and without being billed one credit for each successful **document** parsing." msgstr "" -#: ../../content/developer/reference/extract_api.rst:739 +#: ../../content/developer/reference/extract_api.rst:531 msgid "The only technical differences in test mode is that the document you send is not parsed by the system and that the response you get from :ref:`/get_result ` is a hard-coded one." msgstr "" -#: ../../content/developer/reference/extract_api.rst:743 +#: ../../content/developer/reference/extract_api.rst:535 msgid "A python implementation of the full flow for invoices can be found :download:`here `." msgstr "" @@ -18365,6 +17592,10 @@ msgstr "" msgid "The service system is organized around three ideas: services, service providers and widgets. The way it works is that widgets trigger (with *trigger_up*) events, these events bubble up to a service provider, which will ask a service to perform a task, then maybe return an answer." msgstr "" +#: ../../content/developer/reference/frontend/javascript_reference.rst:876 +msgid "Service" +msgstr "" + #: ../../content/developer/reference/frontend/javascript_reference.rst:878 msgid "A service is an instance of the *AbstractService* class. It basically only has a name and a few methods. Its job is to perform some work, typically something depending on the environment." msgstr "" @@ -25216,6 +24447,10 @@ msgstr "" msgid "bedrooms" msgstr "" +#: ../../content/developer/tutorials/define_module_data.rst:183 +msgid "6" +msgstr "" + #: ../../content/developer/tutorials/define_module_data.rst:183 msgid "1" msgstr "" @@ -26382,50 +25617,54 @@ msgid ":option:`-u `: Update some modules before running the msgstr "" #: ../../content/developer/tutorials/getting_started/02_setup.rst:122 +msgid "For now you cannot add `../technical-training-sandbox` to your `addons-path` as it is empty and will result into an invalid addons-path folder error, but you will have to add it back later on !" +msgstr "" + +#: ../../content/developer/tutorials/getting_started/02_setup.rst:126 msgid "Log in to Odoo" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:124 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:128 msgid "Open http://localhost:8069/ on your browser. We recommend using `Chrome `_, `Firefox `_, or any other browser with development tools." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:128 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:132 msgid "To log in as the administrator user, use the following credentials:" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:130 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:134 msgid "email: `admin`" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:131 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:135 msgid "password: `admin`" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:134 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:138 msgid "Enable the developer mode" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:136 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:140 msgid "The developer or debug mode is useful for training as it gives access to additional (advanced) tools. In the next chapters, **we will always assume that you have enabled the developer mode**." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:139 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:143 msgid ":ref:`Enable the developer mode ` now. Choose the method that you prefer; they are all equivalent." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:143 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:147 msgid "The main page of the Settings screen is only accessible if at least one application is installed. You will be led into installing your own application in the next chapter." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:147 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:151 msgid "Extra tools" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:150 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:154 msgid "Useful Git commands" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:152 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:156 msgid "Here are some useful Git commands for your day-to-day work." msgstr "" @@ -26437,131 +25676,131 @@ msgstr "" msgid "When you switch branches, both repositories (odoo and enterprise) must be synchronized, i.e. both need to be in the same branch." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:166 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:170 msgid "Fetch and rebase:" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:179 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:183 msgid "Code Editor" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:181 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:185 msgid "If you are working at Odoo, many of your colleagues are using `VSCode `_, `VSCodium `_ (the open source equivalent), `PyCharm `_, or `Sublime Text `_. However, you are free to choose your preferred editor." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:186 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:190 msgid "It is important to configure your linters correctly. Using a linter helps you by showing syntax and semantic warnings or errors. Odoo source code tries to respect Python's and JavaScript's standards, but some of them can be ignored." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:190 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:194 msgid "For Python, we use PEP8 with these options ignored:" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:192 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:196 msgid "`E501`: line too long" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:193 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:197 msgid "`E301`: expected 1 blank line, found 0" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:194 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:198 msgid "`E302`: expected 2 blank lines, found 1" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:196 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:200 msgid "For JavaScript, we use ESLint and you can find a `configuration file example here `_." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:200 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:204 msgid "Administrator tools for PostgreSQL" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:202 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:206 msgid "You can manage your PostgreSQL databases using the command line as demonstrated earlier or using a GUI application such as `pgAdmin `_ or `DBeaver `_." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:206 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:210 msgid "To connect the GUI application to your database we recommend you connect using the Unix socket." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:208 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:212 msgid "Host name/address: `/var/run/postgresql`" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:209 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:213 msgid "Port: `5432`" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:210 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:214 msgid "Username: `$USER`" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:213 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:217 msgid "Python Debugging" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:215 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:219 msgid "When facing a bug or trying to understand how the code works, simply printing things out can go a long way, but a proper debugger can save a lot of time." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:218 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:222 msgid "You can use a classic Python library debugger (`pdb `_, `pudb `_ or `ipdb `_), or you can use your editor's debugger." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:222 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:226 msgid "In the following example we use ipdb, but the process is similar with other libraries." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:224 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:228 msgid "Install the library:" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:230 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:234 msgid "Place a trigger (breakpoint):" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:249 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:253 msgid "Here is a list of commands:" msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:253 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:257 msgid "Print the list of available commands if not argument is supplied. With a command as an argument, print the help about that command." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:258 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:262 msgid "The value of the `expression` is pretty-printed using the `pprint` module." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:262 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:266 msgid "Print a stack trace with the most recent frame at the bottom." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:266 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:270 msgid "Move the current frame one level down in the stack trace (to a newer frame)." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:270 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:274 msgid "Move the current frame one level up in the stack trace (to an older frame)." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:274 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:278 msgid "Continue the execution until the next line in the current function is reached or it returns." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:278 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:282 msgid "Continue the execution and only stop when a breakpoint is encountered." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:282 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:286 msgid "Execute the current line. Stop at the first possible occasion (either in a function that is called or on the next line in the current function)." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:287 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:291 msgid "Quit the debugger. The program being executed is aborted." msgstr "" -#: ../../content/developer/tutorials/getting_started/02_setup.rst:289 +#: ../../content/developer/tutorials/getting_started/02_setup.rst:293 msgid "Now that your server is running, it's time to start :ref:`writing your own application `!" msgstr "" @@ -26793,6 +26032,10 @@ msgstr "" msgid "The ``name`` field is a :class:`~odoo.fields.Char` which will be represented as a Python unicode ``str`` and a SQL ``VARCHAR``." msgstr "" +#: ../../content/developer/tutorials/getting_started/04_basicmodel.rst:134 +msgid "Types" +msgstr "" + #: ../../content/developer/tutorials/getting_started/04_basicmodel.rst:138 msgid "**Goal**: at the end of this section, several basic fields should have been added to the table ``estate_property``:" msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 185638814..95e63b0de 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,7 +49,7 @@ msgid "Odoo uses the double-entry bookkeeping system, whereby every entry needs msgstr "" #: ../../content/applications/finance/accounting.rst:67 -#: ../../content/applications/finance/accounting.rst:217 +#: ../../content/applications/finance/accounting.rst:216 msgid ":doc:`Accounting Cheat Sheet `" msgstr "" @@ -119,7 +119,8 @@ msgid "The following financial :doc:`reports ` are availab msgstr "" #: ../../content/applications/finance/accounting.rst:127 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:365 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 msgid "Financial reports" msgstr "" @@ -157,10 +158,12 @@ msgid "Audit" msgstr "" #: ../../content/applications/finance/accounting.rst:139 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1076 msgid "General ledger" msgstr "" #: ../../content/applications/finance/accounting.rst:141 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1038 msgid "Trial balance" msgstr "" @@ -178,8 +181,7 @@ msgstr "" #: ../../content/applications/finance/accounting.rst:149 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:138 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:124 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:138 #: ../../content/applications/finance/fiscal_localizations/peru.rst:325 msgid "Partner" msgstr "" @@ -266,38 +268,38 @@ msgid "Both periodic (manual) and perpetual (automated) inventory valuations are msgstr "" #: ../../content/applications/finance/accounting.rst:206 -msgid ":doc:`View the impact of the valuation methods on transactions <../inventory_and_mrp/inventory/management/reporting/inventory_valuation_config>`" +msgid ":doc:`../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config`" msgstr "" -#: ../../content/applications/finance/accounting.rst:210 +#: ../../content/applications/finance/accounting.rst:209 msgid "Retained earnings" msgstr "" -#: ../../content/applications/finance/accounting.rst:212 +#: ../../content/applications/finance/accounting.rst:211 msgid "Retained earnings are the portion of income retained by a business. Odoo calculates current year earnings in real-time, so no year-end journal or rollover is required. The profit and loss balance is automatically reported on the balance sheet report." msgstr "" -#: ../../content/applications/finance/accounting.rst:220 +#: ../../content/applications/finance/accounting.rst:219 msgid "Fiduciaries" msgstr "" -#: ../../content/applications/finance/accounting.rst:222 +#: ../../content/applications/finance/accounting.rst:221 msgid "The :guilabel:`Accounting Firms` mode can be activated by going to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Firms mode`. When enabled:" msgstr "" -#: ../../content/applications/finance/accounting.rst:225 +#: ../../content/applications/finance/accounting.rst:224 msgid "The document's sequence becomes editable on all documents;" msgstr "" -#: ../../content/applications/finance/accounting.rst:226 +#: ../../content/applications/finance/accounting.rst:225 msgid "The :guilabel:`Total (tax incl.)` field appears to speed up and control the encoding by automating line creation with the right account and tax;" msgstr "" -#: ../../content/applications/finance/accounting.rst:228 +#: ../../content/applications/finance/accounting.rst:227 msgid ":guilabel:`Invoice Date` and :guilabel:`Bill Date` are pre-filled when encoding a transaction." msgstr "" -#: ../../content/applications/finance/accounting.rst:229 +#: ../../content/applications/finance/accounting.rst:228 msgid "A :guilabel:`Quick encoding` option is available for customer invoices and vendor bills." msgstr "" @@ -403,6 +405,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 #: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:15 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 #: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 #: ../../content/applications/finance/accounting/payments/batch.rst:11 @@ -430,19 +433,16 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:25 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:25 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:286 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:328 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:20 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 #: ../../content/applications/finance/fiscal_localizations/germany.rst:58 #: ../../content/applications/finance/fiscal_localizations/italy.rst:8 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:6 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:36 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:620 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:726 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:847 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:40 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:653 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:769 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:909 #: ../../content/applications/finance/fiscal_localizations/peru.rst:29 #: ../../content/applications/finance/fiscal_localizations/philippines.rst:6 #: ../../content/applications/finance/fiscal_localizations/romania.rst:6 @@ -457,7 +457,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/authorize.rst:60 #: ../../content/applications/finance/payment_providers/demo.rst:9 #: ../../content/applications/finance/payment_providers/mollie.rst:8 -#: ../../content/applications/finance/payment_providers/paypal.rst:135 +#: ../../content/applications/finance/payment_providers/paypal.rst:140 #: ../../content/applications/finance/payment_providers/sips.rst:9 #: ../../content/applications/finance/payment_providers/wire_transfer.rst:30 msgid "Configuration" @@ -1160,7 +1160,6 @@ msgid "In the tab Journal Entries, the Default Debit and Credit Account can be c msgstr "" #: ../../content/applications/finance/accounting/bank/cash_register.rst:21 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:258 #: ../../content/applications/finance/fiscal_localizations/indonesia.rst:34 msgid "Usage" msgstr "" @@ -1571,7 +1570,7 @@ msgid "Open the model you want to modify, or click on *Create* to create a new o msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:88 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:52 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:41 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:56 msgid "Type" msgstr "" @@ -1747,7 +1746,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:5 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:91 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:346 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:310 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 msgid "Customer invoices" msgstr "" @@ -1772,7 +1771,7 @@ msgid "Invoicing in most countries occurs when a contractual obligation is met. msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:35 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:284 msgid "Invoice creation" msgstr "" @@ -1913,7 +1912,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:109 #: ../../content/applications/finance/accounting/customer_invoices.rst:132 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:168 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:58 msgid "Accounts Receivable" msgstr "" @@ -1940,9 +1939,10 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:167 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:71 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:168 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:194 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:165 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:190 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:368 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:378 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:186 #: ../../content/applications/finance/fiscal_localizations/peru.rst:73 #: ../../content/applications/finance/fiscal_localizations/peru.rst:246 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:124 @@ -1958,7 +1958,6 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:113 #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:16 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:261 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 @@ -1967,13 +1966,13 @@ msgid "Sales" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:113 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 #: ../../content/applications/finance/accounting/taxes.rst:127 msgid "100" msgstr "" @@ -1991,8 +1990,8 @@ msgid "A typical journal entry generated from a payment will look like as follow msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:130 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 #: ../../content/applications/finance/accounting/payments/checks.rst:108 #: ../../content/applications/finance/accounting/payments/checks.rst:127 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:67 @@ -2467,7 +2466,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:101 #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:133 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:135 #: ../../content/applications/finance/accounting/payments/checks.rst:84 msgid "Journal entries" msgstr "" @@ -3535,9 +3534,9 @@ msgid "In this example, an invoice of $1000 has been issued with the following p msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 #: ../../content/applications/finance/accounting/payments/checks.rst:93 #: ../../content/applications/finance/accounting/payments/checks.rst:104 #: ../../content/applications/finance/accounting/payments/checks.rst:123 @@ -3545,10 +3544,10 @@ msgid "Account" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:168 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 #: ../../content/applications/finance/accounting/payments/checks.rst:93 #: ../../content/applications/finance/accounting/payments/checks.rst:104 #: ../../content/applications/finance/accounting/payments/checks.rst:123 @@ -3557,10 +3556,10 @@ msgid "Debit" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:168 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 #: ../../content/applications/finance/accounting/payments/checks.rst:93 #: ../../content/applications/finance/accounting/payments/checks.rst:104 #: ../../content/applications/finance/accounting/payments/checks.rst:123 @@ -3570,8 +3569,8 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:134 #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:136 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 #: ../../content/applications/finance/accounting/payments/checks.rst:95 #: ../../content/applications/finance/accounting/payments/checks.rst:125 msgid "Account Receivable" @@ -3954,348 +3953,719 @@ msgid ":doc:`../fiscal_localizations`" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:190 -msgid "`Odoo Tutorials: Accounting Basics `_" +msgid "`Odoo Tutorials: Accounting and Invoicing - Getting started [video] `_" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:3 -msgid "Inventory average price valuation" +msgid "Average price on returned goods" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:5 -msgid "As stated in the :doc:`inventory valuation page `, one of the possible costing method you can use in perpetual stock valuation, is the average cost." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:8 +msgid "*Average cost valuation* (AVCO) is an inventory valuation method that evaluates cost based on the total cost of goods bought or produced during a period, divided by the total number of items on-hand. Inventory valuation is used to:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:10 -msgid "This document answers to one recurrent question for companies using that method to make their stock valuation: how does a shipping returned to its supplier impact the average cost and the accounting entries? This document is **only** for the specific use case of a perpetual valuation (as opposed to the periodic one) and in average price costing method (as opposed to standard of FIFO)." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:12 +msgid "reflect the value of a company's assets;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:18 -msgid "Definition of average cost" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:13 +msgid "keep track of the amount of unsold goods;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:20 -msgid "The average cost method calculates the cost of ending inventory and cost of goods sold on the basis of weighted average cost per unit of inventory." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:14 +msgid "account for monetary value in goods that have yet to generate profit;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:24 -msgid "The weighted average cost per unit is calculated using the following formula:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:15 +msgid "report on flow of goods throughout the quarter." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:17 +msgid "Because |AVCO| uses the weighted average to evaluate the cost, it is a good fit for companies that sell only a few different products in large quantities. In Odoo, this costing analysis is *automatically updated* each time products are received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:21 +msgid "Thus, when shipments are returned to their supplier, Odoo automatically generates accounting entries to reflect the change in inventory valuation. However, Odoo does **not** automatically update the |AVCO| calculation, because :ref:`this can potentially create inconsistencies with inventory valuation `." msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:27 -msgid "When new products arrive in a warehouse, the new average cost is recomputed as:" +msgid "This document addresses a specific use case for theoretical purposes. Navigate :ref:`here ` for instructions on how to set up and use |AVCO| in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:32 +msgid ":ref:`Using inventory valuation `" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:33 -msgid "When products leave the warehouse: the average cost **does not** change" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 -msgid "Defining the purchase price" +msgid ":ref:`Other inventory valuation methods `" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:38 -msgid "The purchase price is estimated at the reception of the products (you might not have received the vendor bill yet) and reevaluated at the reception of the vendor bill. The purchase price includes the cost you pay for the products, but it may also includes additional costs, like landed costs." +msgid "To use average cost inventory valuation on a product, navigate to :menuselection:`Inventory --> Configuration --> Product Categories` and select the category that will be using |AVCO|. On the product category page, set :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:45 -msgid "Average cost example" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:44 +msgid ":ref:`Inventory valuation configuration `" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:47 +msgid "Using average cost valuation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:49 +msgid "The average cost method adjusts the inventory valuation when products are received in the warehouse. This section explains how it works, but if the explanation is unnecessary, skip to the :ref:`return to supplier use case ` section." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +msgid "Formula" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:58 +msgid "When new products arrive, the new average cost for each product is recomputed using the formula:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:60 +msgid "Avg~Cost = \\frac{(Old~Qty \\times Old~Avg~Cost) + (Incoming~Qty \\times Purchase~Price)}{Final~Qty}\n" +"\n" +"" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:63 +msgid "**Old Qty**: product count in stock before receiving the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:64 +msgid "**Old Avg Cost**: calculated average cost for a single product from the previous inventory valuation;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:66 +msgid "**Incoming Qty**: count of products arriving in the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:67 +msgid "**Purchase Price**: estimated price of products at the reception of products (since vendor bills may arrive later). The amount includes not only the price for the products, but also added costs, such as shipping, taxes, and :ref:`landed costs `. At reception of the vendor bill, this price is adjusted;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:71 +msgid "**Final Qty**: quantity of on-hand stock after the stock move." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:76 +msgid "When products leave the warehouse, the average cost **does not** change. Read about why the average cost valuation is **not** adjusted :ref:`here `." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "Compute average cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +msgid "To understand how the average cost of a product changes with each shipment, consider the following table of warehouse operations and stock moves. Each is a different example of how the average cost valuation is affected." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Operation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -msgid "Delta Value" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +msgid "Incoming Value" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Inventory Value" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Qty On Hand" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Avg Cost" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:50 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "$0" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:50 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 #: ../../content/applications/finance/fiscal_localizations/france.rst:240 msgid "0" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -msgid "Receive 8 Products at $10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "Receive 8 tables at $10/unit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -msgid "+8\\*$10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "8 * $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "$80" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "8" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "$10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -msgid "Receive 4 Products at $16" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "Receive 4 tables at $16/unit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -msgid "+4\\*$16" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "4 * $16" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 msgid "$144" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 #: ../../content/applications/finance/fiscal_localizations/france.rst:88 #: ../../content/applications/finance/fiscal_localizations/france.rst:111 msgid "12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "$12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 -msgid "Deliver 10 Products" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "Deliver 10 tables" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -msgid "-10\\*$12" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "-10 * $12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 msgid "$24" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 msgid "2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:60 -msgid "At the beginning, the Avg Cost is set to 0 set as there is no product in the inventory. When the first reception is made, the average cost becomes logically the purchase price." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +msgid "Ensure comprehension of the above computations by reviewing the \"Receive 8 tables at $10/unit\" example." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:64 -msgid "At the second reception, the average cost is updated because the total inventory value is now ``$80 + 4*$16 = $144``. As we have 12 units on hand, the average price per unit is ``$144 / 12 = $12``." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:106 +msgid "Initially, the product stock is 0, so all values are $0." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:68 -msgid "By definition, the delivery of 10 products does not change the average cost. Indeed, the inventory value is now $24 as we have only 2 units remaining of each ``$24 / 2 = $12``." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:108 +msgid "In the first warehouse operation, `8` tables are received at `$10` each. The average cost is calculated using the :ref:`formula `:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:73 -msgid "Purchase return use case" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:111 +msgid "Avg~Cost = \\frac{0 + 8 \\times $10}{8} = \\frac{$80}{8} = $10\n" +"\n" +"" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:75 -msgid "In case of a product returned to its supplier after reception, the inventory value is reduced using the average cost formulae (not at the initial price of these products!)." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:114 +msgid "Since the *incoming quantity* of tables is `8` and the *purchase price* for each is `$10`," msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:79 -msgid "Which means that the above table will be updated as follow:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:115 +msgid "The inventory value in the numerator is evaluated to `$80`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 -msgid "Return of 1 Product initially bought at $10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:116 +msgid "`$80` is divided by the total amount of tables to store, `8`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -msgid "-1\\*$12" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +msgid "`$10` is the average cost of a single table from the first shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +msgid "To verify this in Odoo, in the *Purchase* app, order `8` quantities of a new product, `Table`, with no previous stock moves, for `$10` each." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:122 +msgid "In the table's :guilabel:`Product Category` field in the :guilabel:`General Information` tab of the product form, click the :guilabel:`āž”ļø (arrow)` icon, to open an :guilabel:`External Link` to edit the product category. Set the :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:127 +msgid "Then, return to the purchase order. Click :guilabel:`Confirm Order`, and click :guilabel:`Receive Products` to confirm receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 +msgid "Next, check the inventory valuation record generated by the product reception by navigating to :menuselection:`Inventory --> Reporting --> Inventory Valuation`. Select the drop-down for `Table`, and view the :guilabel:`Total Value` column for the *valuation layer* (:dfn:`inventory valuation at a specific point in time = on-hand quantity * unit price`). The 8 tables in-stock are worth $80." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show inventory valuation of 8 tables in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:141 +msgid "When the product category's :guilabel:`Costing Method` is set to :guilabel:`AVCO`, then the average cost of a product is also displayed on the :guilabel:`Cost` field, under the :guilabel:`General Information` tab, on the product page itself." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +msgid "Product delivery (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +msgid "For outgoing shipments, :ref:`outbound products have no effect on the average cost valuation `. Although the average cost valuation is not recalculated, the inventory value still decreases because the product is removed from stock and delivered to the customer location." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +msgid "To demonstrate that the average cost valuation is not recalculated, examine the \"Deliver 10 tables\" example." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:157 +msgid "Avg~Cost = \\frac{12 \\times $12 + (-10) \\times $12}{12-10} = \\frac{24}{2} = $12\n" +"\n" +"" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "Because 10 tables are being sent out to customers, the *incoming quantity* is `-10`. The previous average cost (`$12`) is used in lieu of a vendor's *purchase price*;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:162 +msgid "The *incoming inventory value* is `-10 * $12 = -$120`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 +msgid "The old *inventory value* (`$144`) is added to the *incoming inventory value* (`-$120`), so `$144 + -$120 = $24`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:165 +msgid "Only `2` tables remain after shipping out `10` tables from `12`. So the current *inventory value* (`$24`) is divided by the on-hand quantity (`2`);" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:167 +msgid "`$24 / 2 = $12`, which is the same average cost as the previous operation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:169 +msgid "To verify this in Odoo, sell `10` tables in the *Sales* app, validate the delivery, and then review the inventory valuation record by going to in :menuselection:`Inventory --> Reporting --> Inventory Valuation`. In the topmost valuation layer, delivering `10` tables reduces the product's value by `-$120`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:174 +msgid "**Note**: What is not represented in this stock valuation record is the revenue made from this sale, so this decrease is not a loss to the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show how deliveries decrease inventory valuation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:184 +msgid "Return items to supplier (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:186 +msgid "Because the price paid to suppliers can differ from the price the product is valued at with the |AVCO| method, Odoo handles returned items in a specific way." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:189 +msgid "Products are returned to suppliers at the original purchase price, but;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:190 +msgid "The internal cost valuation remains unchanged." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:192 +msgid "The above :ref:`example table ` is updated as follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +msgid "Qty*Avg Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "Return 1 table bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "-1 * $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 #: ../../content/applications/finance/fiscal_localizations/france.rst:242 msgid "1" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:90 -msgid "Explanation: counter example" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +msgid "In other words, returns to vendors are perceived by Odoo as another form of a product exiting the warehouse. To Odoo, because the table is valued at $12 per unit, the inventory value is reduced by `$12` when the product is returned; the initial purchase price of `$10` is unrelated to the table's average cost." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:92 -msgid "Remember the definition of **Average Cost**, saying that we do not update the average cost of a product leaving the inventory. If you break this rule, you may lead to inconsistencies in your inventory." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:208 +msgid "To return a single table that was purchased for `$10`, navigate to the receipt in the *Inventory* app for the :ref:`8 tables purchased in Exercise 1 ` by going to the :guilabel:`Inventory Overview`, clicking on :guilabel:`Receipts`, and selecting the desired receipt." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:96 -msgid "As an example, here is the scenario when you deliver one piece to the customer and return the other one to your supplier (at the cost you purchased it). Here is the operation:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:213 +msgid "Then, click :guilabel:`Return` on the validated delivery order, and modify the quantity to `1` in the reverse transfer window. This creates an outgoing shipment for the table. Select :guilabel:`Validate` to confirm the outgoing shipment." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -msgid "Customer Shipping 1 product" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:217 +msgid "Return to :menuselection:`Inventory --> Reporting --> Inventory Valuation` to see how the outgoing shipment decreases the inventory value by $12." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -msgid "-1\\*$10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Inventory valuation for return." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:227 +msgid "Eliminate stock valuation errors in outgoing products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:229 +msgid "Inconsistencies can occur in a company's inventory when the average cost valuation is recalculated on outgoing shipments." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:232 +msgid "To demonstrate this error, the table below displays a scenario in which 1 table is shipped to a customer and another is returned to a supplier at the purchased price." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +msgid "Qty*Price" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "Ship 1 product to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "-1 \\* $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "Return 1 product initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "-1 \\* $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 msgid "**$2**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 msgid "**0**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:110 -msgid "As you can see in this example, this is not correct: an inventory valuation of $2 for 0 pieces in the warehouse." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 +msgid "In the final operation above, the final inventory valuation for the table is `$2` even though there are `0` tables left in stock." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:113 -msgid "The correct scenario should be to return the goods at the current average cost:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:248 +msgid "Correct method" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -msgid "**$0**" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:250 +msgid "Use the average cost to value the return. This does not mean the company gets $12 back for a $10 purchase; the item returned for $10 is valued internally at $12. The inventory value change represents a product worth $12 no longer being accounted for in company assets." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:126 -msgid "On the other hand, using the average cost to value the return ensure a correct inventory value at all times." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:255 +msgid "Anglo-Saxon accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 -msgid "Further thoughts on anglo saxon mode" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:257 +msgid "In addition to using |AVCO|, companies that use **Anglo-Saxon accounting** also keep a holding account that tracks the amount to be paid to vendors. Once a vendor delivers an order, **inventory value** increases based on the vendor price of the products that have entered the stock. The holding account (called **stock input**) is credited and only reconciled once the vendor bill is received." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:132 -msgid "For people in using the **anglo saxon accounting** principles, there is another concept to take into account: the stock input account of the product, which is intended to hold at any time the value of vendor bills to receive. So the stock input account will increase on reception of incoming shipments and will decrease when receiving the related vendor bills." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:263 +msgid ":ref:`Anglo-Saxon vs. Continental `" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:139 -msgid "Back to our example, we see that when the return is valued at the average price, the amount booked in the stock input account is the original purchase price:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:265 +msgid "The table below reflects journal entries and accounts. The *stock input* account stores the money intended to pay vendors when the vendor bill has not yet been received. To balance accounts when returning products that have a price difference between the price the product is **valued at** and the price it was bought for, a *price difference* account is created." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 -msgid "stock input" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Stock Input" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 -msgid "price diff" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Price Diff" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +msgid "Receive 8 tables at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 msgid "($80)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "Receive vendor bill $80" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +msgid "Receive 4 tables at $16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 msgid "($64)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 msgid "Receive vendor bill $64" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "Deliver 10 tables to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "Return 1 table initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 msgid "**$10**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 msgid "**$12**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "Receive vendor refund $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "$2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 -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." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:293 +msgid "Product reception" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:296 +msgid "Summary" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:298 +msgid "At product reception, Odoo ensures companies can pay for goods that were purchased by preemptively moving an amount matching the price of received goods into the :doc:`liability account `, **Stock Input**. Then, once the bill has been received, the amount in the holding account is transferred to *Accounts Payable*. Transfers into this account means the bill has been paid. **Stock Input** is reconciled once the vendor bill is received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:305 +msgid "Inventory valuation is a method of calculating how much each in-stock product is worth internally. Since there is a difference between the price the product is **valuated at** and the price the product was actually **purchased for**, the **Inventory Valuation** account is unrelated to the crediting and debiting operations of the **Stock Input** account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:310 +msgid "To conceptualize all this, follow the breakdown below." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:313 +msgid "Accounts balanced at received products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:315 +msgid "In this example, a company starts with zero units of a product, `table`, in stock. Then, 8 tables are received from the vendor:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:318 +msgid "The **Stock Input** account stores `$80` of credit owed to the vendor. The amount in this account is unrelated to the inventory value." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:320 +msgid "`$80` worth of tables came **in** (**debit** the *Inventory Value* account `$80`), and" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:321 +msgid "`$80` must be paid **out** for received goods (**credit** the *Stock Input* account `$80`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:324 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:367 +msgid "In Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:326 +msgid "Odoo generates an accounting journal entry when shipments that use |AVCO| costing method are received. Configure a :guilabel:`Price Difference Account` by selecting the :guilabel:`āž”ļø (arrow)` icon next to the :guilabel:`Product Category` field on the product page." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:330 +msgid "Under :guilabel:`Account Properties`, create a new :guilabel:`Price Difference Account` by typing in the name of the account and clicking :guilabel:`Create and Edit`. Then set the account :guilabel:`Type` as `Expenses`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Create price difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:338 +msgid "Then, receive the shipment in the *Purchase* app or *Inventory* app, and navigate to the :menuselection:`Accounting app --> Accounting --> Journal Entries`. In the list, find the :guilabel:`Reference` that matches the warehouse reception operation for the relevant product." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Show accounting entry of 8 tables from the list." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:346 +msgid "Click on the line for 8 tables. This accounting journal entry shows that when the 8 tables were received, the `Stock Valuation` account increased by `$80`. Conversely, the **Stock Input** account (set as `Stock Interim (Received)` account by default) is credited `$80`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Debit stock valuation and credit stock input 80 dollars." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:355 +msgid "Accounts balanced at received vendor bill" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:357 +msgid "In this example, a company starts with zero units of a product, table, in stock. Then, 8 tables are received from the vendor. When the bill is received from vendor for 8 tables:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:360 +msgid "Use `$80` in the **Stock Input** account to pay the bill. This cancels out and the account now holds `$0`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:362 +msgid "Debit **Stock Input** `$80` (to reconcile this account)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:363 +msgid "Credit **Accounts payable** `$80`. This account stores the amount the company owes others, so accountants use the amount to write checks to vendors." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:369 +msgid "Once the vendor requests payment, navigate to the :menuselection:`Purchase app --> Orders --> Purchase` and select the :abbr:`PO (Purchase Order)` for 8 tables. Inside the :abbr:`PO (Purchase Order)`, select :guilabel:`Create Bill`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:373 +msgid "Switch to the :guilabel:`Journal Items` tab to view how `$80` is transferred from the holding account, `Stock Interim (Received)` to `Accounts Payable`. :guilabel:`Confirm` the bill to record the payment to the vendor." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Show bill linked to the purchase order for 8 tables." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:382 +msgid "On product delivery" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:384 +msgid "In the :ref:`above example table `, when 10 products are delivered to a customer, the **Stock Input** account is untouched because there are no new products coming in. To put it simply:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:388 +msgid "**Inventory valuation** is credited `$120`. Subtracting from inventory valuation represents `$120` worth of products exiting the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:390 +msgid "Debit **Accounts Receivable** to record revenue from the sale." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Show journal items linked to sale order." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:398 +msgid "In the accounting journal entry invoicing a customer for 10 tables, the accounts **Product Sales**, **Tax Received**, and **Accounts Receivable** all pertain to the sale of the product. **Accounts Receivable** is the account where the customer payment will be received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:402 +msgid "Anglo-Saxon accounting recognizes the cost of goods sold (COGS) once the sale is made. So, up until the product is sold, scrapped, or returned, costs of keeping the product in stock are not accounted for. The **Expense** account is debited `$120` to log the costs of storing 10 tables during this period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:408 +msgid "On product return" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:410 +msgid "In the :ref:`above example table `, when returning 1 product to a vendor purchased at `$10`, a company expects `$10` in the **Accounts Payable** account from the vendor. However, **Stock Input** account must be debited `$12` because the average cost is `$12` at the time of the return. The missing `$2` is accounted for in the :guilabel:`Price Difference Account`, which is set up in the product's :guilabel:`Product Category`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:417 +msgid "Behavior of *price difference accounts* varies from localization. In this case, the account is intended to store differences between vendor price and *automated* inventory valuation methods." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:420 +msgid "Summary:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:422 +msgid "Debit **Stock Input** account `$10` to move the table from stock to stock input. This move is to indicate that the table is to be processed for an outgoing shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:424 +msgid "Debit **Stock Input** an additional `$2` to account for the **Price Difference**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:425 +msgid "Credit **Stock Valuation** `$12` because the item is leaving the stock." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "2 dollar difference expensed in Price Difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:431 +msgid "Once the vendor's refund is received," +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:433 +msgid "Credit **Stock Input** account `$10` to reconcile the price of the table." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:434 +msgid "Debit **Accounts Payable** `$10` to have the accountants collect and register the payment in their journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Return to get 10 dollars back." msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:3 @@ -4303,9 +4673,10 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:56 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:154 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:141 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:215 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:363 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 #: ../../content/applications/finance/fiscal_localizations/romania.rst:65 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 @@ -4313,134 +4684,101 @@ msgid "Chart of accounts" msgstr "" #: ../../content/applications/finance/accounting/get_started/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. The chart of accounts can be found under :menuselection:`Accounting-->Configuration-->Chart of Accounts`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:8 -msgid "The accounts are usually listed in the order of appearance in the financial reports. Most of the time, they are listed as follows :" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:11 -msgid "Balance Sheet accounts:" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:13 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 -msgid "Assets" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:14 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:79 -msgid "Liabilities" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:15 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:87 -msgid "Equity" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:17 -msgid "Profit & Loss:" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:91 -msgid "Income" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:20 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:95 -msgid "Expense" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/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 :guilabel:`Account Type`." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:9 +msgid "When browsing your chart of accounts, you can sort the accounts by :guilabel:`Code`, :guilabel:`Account Name`, or :guilabel:`Type`, but other options are available in the drop-down menu :guilabel:`(ā‹®)`." msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:-1 msgid "Group the accounts by type in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:30 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:17 msgid "Configuration of an account" msgstr "" -#: ../../content/applications/finance/accounting/get_started/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." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 +msgid "The country you select during the creation of your database (or additional company in your database) determines which :doc:`fiscal localization package <../../fiscal_localizations>` 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/get_started/chart_of_accounts.rst:38 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:24 +msgid "To create a new account, go to :menuselection:`Accounting-->Configuration-->Chart of Accounts`, click :guilabel:`Create`, and fill in (at the minimum) the required fields (:guilabel:`Code, Account Name, Type`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:29 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/get_started/chart_of_accounts.rst:41 -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/get_started/chart_of_accounts.rst:45 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:33 msgid "Code and name" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 -msgid "Each account is identified by its **code** and **name**, which also indicates the account's purpose." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:35 +msgid "Each account is identified by its :guilabel:`Code` and :guilabel:`Name`, which also indicate the account's purpose." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:43 msgid "Correctly configuring the **account type** is critical as it serves multiple purposes:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 msgid "Information on the account's purpose and behavior" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:57 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:46 msgid "Generate country-specific legal and financial reports" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 msgid "Set the rules to close a fiscal year" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:59 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:48 msgid "Generate opening entries" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:61 -msgid "To configure an account type, open the :guilabel:`Type` field's drop-down selector and select the right type among the following list:" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:50 +msgid "To configure an account type, open the :guilabel:`Type` field's drop-down selector and select the corresponding type from the following list:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "Report" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "Category" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "Account Types" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 #: ../../content/applications/finance/accounting/reporting.rst:36 #: ../../content/applications/finance/fiscal_localizations/germany.rst:23 #: ../../content/applications/finance/fiscal_localizations/spain.rst:27 msgid "Balance Sheet" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:59 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:62 msgid "Receivable" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:69 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:68 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:71 msgid "Bank and Cash" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:71 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:74 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:77 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:80 @@ -4448,200 +4786,217 @@ msgstr "" msgid "Current Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:73 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:62 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:86 msgid "Non-current Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:75 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:64 msgid "Prepayments" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:77 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:66 msgid "Fixed Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:79 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 +msgid "Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:65 msgid "Payable" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:81 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 msgid "Credit Card" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:83 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:72 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:89 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:92 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:95 msgid "Current Liabilities" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:85 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:74 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:98 msgid "Non-current Liabilities" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:89 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:76 +msgid "Equity" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:101 msgid "Current Year Earnings" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:91 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 #: ../../content/applications/finance/fiscal_localizations/germany.rst:24 #: ../../content/applications/finance/fiscal_localizations/netherlands.rst:20 msgid "Profit & Loss" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:93 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 +msgid "Income" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 msgid "Other Income" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:97 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 +msgid "Expense" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 msgid "Depreciation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:99 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:88 msgid "Cost of Revenue" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 msgid "Other" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 msgid "Off-Balance Sheet" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:94 msgid "Assets, deferred expenses, and deferred revenues automation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/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." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 +msgid "Some **account types** can **automate** the creation of :ref:`assets ` entries, :ref:`deferred expenses ` entries, and :ref:`deferred revenues ` entries. To **automate** entries, click :guilabel:`Setup` on an account line and go to the :guilabel:`Automation` tab." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:111 -msgid "You have three choices for the :guilabel:`Automation` field:" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +msgid "You have three choices for the :guilabel:`Automation` tab:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:103 msgid ":guilabel:`No`: this is the default value. Nothing happens." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:114 -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." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:104 +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/get_started/chart_of_accounts.rst:116 -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." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:106 +msgid ":guilabel:`Create and validate`: you must also select a :guilabel:`Deferred Expense Model`. Whenever a transaction is posted on the account, an entry is created and immediately validated." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:120 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:110 #: ../../content/applications/finance/accounting/taxes.rst:14 msgid "Default taxes" msgstr "" -#: ../../content/applications/finance/accounting/get_started/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." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:112 +msgid "In the :guilabel:`Setup` menu of an account, select a **default tax** to be applied when this account is chosen for a product sale or purchase." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:116 #: ../../content/applications/finance/documents.rst:58 +#: ../../content/applications/finance/sign.rst:227 msgid "Tags" msgstr "" -#: ../../content/applications/finance/accounting/get_started/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*." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:118 +msgid "Some accounting reports require **tags** to be set on the relevant accounts. To add a tag, under :guilabel:`Setup`, click the :guilabel:`Tags` field and select an existing tag or :guilabel:`Create` a new one." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:132 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:123 msgid "Account groups" msgstr "" -#: ../../content/applications/finance/accounting/get_started/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`." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:125 +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`. You can attribute a specific group to an account in the :guilabel:`Group` field under :guilabel:`Setup`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:140 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:132 msgid "Create account groups manually" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:143 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:135 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/get_started/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." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:138 +msgid "To create a new account group, activate :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/get_started/chart_of_accounts.rst:-1 msgid "Account groups creation." msgstr "" -#: ../../content/applications/finance/accounting/get_started/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`." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:146 +msgid "To display your **Trial Balance** report with your account groups, go to :menuselection:`Accounting-->Reporting-->Trial Balance`, then open the :guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:-1 msgid "Account Groups in the Trial Balance in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:165 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:154 msgid "Allow reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:167 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:156 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/get_started/chart_of_accounts.rst:170 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:159 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/get_started/chart_of_accounts.rst:174 -msgid "To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and save." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:163 +msgid "To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and :guilabel:`Save`; or enable the button from the chart of accounts view." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:177 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:-1 +msgid "Allow reconciliation for accounts in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:170 msgid "Deprecated" msgstr "" -#: ../../content/applications/finance/accounting/get_started/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." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:172 +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: check the :guilabel:`Deprecated` box in the account's settings, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/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/get_started/chart_of_accounts.rst:185 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:177 msgid ":doc:`cheat_sheet`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:186 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:178 msgid ":doc:`../vendor_bills/assets`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:187 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 msgid ":doc:`../vendor_bills/deferred_expenses`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:188 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 msgid ":doc:`../customer_invoices/deferred_revenues`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:189 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 msgid ":doc:`../../fiscal_localizations`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:190 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 msgid "`Odoo Tutorials: Chart of accounts `_" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:191 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 msgid "`Odoo Tutorials: Update your chart of accounts `_" msgstr "" @@ -4777,42 +5132,42 @@ msgstr "" msgid "Balance = Debit - Credit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:135 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:137 msgid "Every financial document of the company (e.g., an invoice, a bank statement, a pay slip, a capital increase contract) is recorded as a journal entry, impacting several accounts." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:138 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:140 msgid "For a journal entry to be balanced, the sum of all its debits must be equal to the sum of all its credits." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:143 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:145 msgid "examples of accounting entries for various transactions. (see entries.js)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:148 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:150 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 msgid "Reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:150 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:152 msgid ":doc:`Reconciliation <../../accounting/bank/reconciliation>` is the process of linking journal items of a specific account and matching credits and debits." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:153 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:155 msgid "Its primary purpose is to link payments to their related invoices to mark them as paid. This is done by doing a reconciliation on the accounts receivable account and/or the accounts payable account." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:156 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:158 msgid "Reconciliation is performed automatically by the system when:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:158 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:160 msgid "the payment is registered directly on the invoice" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:159 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:161 msgid "the links between the payments and the invoices are detected at the bank matching process" msgstr "" @@ -4820,121 +5175,121 @@ msgstr "" msgid "Customer Statement Example" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 msgid "Invoice 1" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 msgid "Partial payment 1/2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 msgid "70" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 msgid "Invoice 2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 msgid "65" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 msgid "Partial payment 2/2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 msgid "30" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 msgid "Payment 2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:182 msgid "Invoice 3" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:184 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:182 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:186 msgid "50" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:184 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:186 msgid "Total to pay" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:188 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:190 #: ../../content/applications/finance/accounting/reporting.rst:149 msgid "Bank Reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:190 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:192 msgid "Bank reconciliation is the matching of bank statement lines (provided by your bank) with transactions recorded internally (payments to suppliers or from customers). For each line in a bank statement, it can be:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:194 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:196 msgid "**matched with a previously recorded payment**: a payment is registered when a check is received from a customer, then matched when checking the bank statement." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:196 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:198 msgid "**recorded as a new payment**: the payment's journal entry is created and reconciled with the related invoice when processing the bank statement." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:198 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:200 msgid "**recorded as another transaction**: bank transfer, direct charge, etc." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:200 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:202 msgid "Odoo should automatically reconcile most transactions; only a few should need manual review. When the bank reconciliation process is finished, the balance on the bank account in Odoo should match the bank statement's balance." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:207 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:209 msgid "Checks Handling" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:209 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:211 msgid "There are two approaches to managing checks and internal wire transfers:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:211 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:213 msgid "Two journal entries and a reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:212 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:214 msgid "One journal entry and a bank reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:216 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:218 msgid "The first journal entry is created by registering the payment on the invoice. The second one is created when registering the bank statement." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 msgid "Invoice ABC" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 msgid "Undeposited funds" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 msgid "Check 0123" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:241 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:243 msgid "A journal entry is created by registering the payment on the invoice. When reconciling the bank statement, the statement line is linked to the existing journal entry." msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 msgid "Bank Statement" msgstr "" -#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 msgid "Statement XYZ" msgstr "" @@ -5024,7 +5379,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:99 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:252 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:255 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:280 #: ../../content/applications/finance/fiscal_localizations/france.rst:194 #: ../../content/applications/finance/fiscal_localizations/india.rst:101 #: ../../content/applications/finance/fiscal_localizations/peru.rst:299 @@ -6019,7 +6374,6 @@ msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" msgstr "" #: ../../content/applications/finance/accounting/payments/multiple.rst:10 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:403 msgid ":doc:`/applications/finance/accounting/bank/reconciliation`" msgstr "" @@ -6993,7 +7347,7 @@ msgid "The subformula allows you to define how the move lines matching the domai msgstr "" #: ../../content/applications/finance/accounting/reporting/customize.rst:104 -#: ../../content/applications/finance/accounting/reporting/customize.rst:234 +#: ../../content/applications/finance/accounting/reporting/customize.rst:270 msgid "`sum`" msgstr "" @@ -7177,55 +7531,115 @@ msgstr "" msgid "This formula matches accounts whose code starts with `21D`, regardless of their balance sign." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:224 -msgid "'External Value' engine" +#: ../../content/applications/finance/accounting/reporting/customize.rst:223 +msgid "In addition to using code prefixes to include accounts, you can also match them with **account tags**. This is especially useful, for example, if your country lacks a standardized chart of accounts, where the same prefix might be used for different purposes across companies." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:226 -msgid "The 'external value' engine is used to refer to **manual** and **carryover values**. Those values are not stored using `account.move.line`, but with `account.report.external.value`. Each of these objects directly points to the expression it impacts, so very little needs to be done about their selection here." +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(25)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "This formula matches accounts whose associated tags contain the one with id *25*." msgstr "" #: ../../content/applications/finance/accounting/reporting/customize.rst:231 -msgid "**Formulas** can be one of the following:" +msgid "If the tag you reference is defined in a data file, an xmlid can be used instead of the id." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:234 -msgid "If the result must be the sum of all the external values in the period." +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)`" msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:237 -msgid "`most_recent`" +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "This formula matches accounts whose associated tags include the tag denoted by *my_module.my_tag*." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:237 -msgid "If the result must be the value of the latest external value in the period." +#: ../../content/applications/finance/accounting/reporting/customize.rst:238 +msgid "You can also use arithmetic expressions with tags, possibly combining them with prefix selections." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:239 -msgid "In addition, **subformulas** can be used in two ways:" +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag) + tag(42) + 10`" msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:242 -msgid "`rounding=X`" -msgstr "" - -#: ../../content/applications/finance/accounting/reporting/customize.rst:242 -msgid "Replacing `X` with a number instructs to round the amount to X decimals." -msgstr "" - -#: ../../content/applications/finance/accounting/reporting/customize.rst:246 -msgid "`editable`" +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "The balances of accounts tagged as *my_module.my_tag* will be summed with those of accounts linked to the tag with ID *42* and accounts with the code prefix `10`" msgstr "" #: ../../content/applications/finance/accounting/reporting/customize.rst:245 -msgid "Indicates this expression can be edited manually, triggering the display of an icon in the report, allowing the user to perform this action." +msgid "`C` and `D` suffixes can be used in the same way with tags." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:249 -msgid "Manual values are created at the `date_to` currently selected in the report." +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)C`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "This formula matches accounts with the tag *my_module.my_tag* and a credit balance." msgstr "" #: ../../content/applications/finance/accounting/reporting/customize.rst:251 +msgid "Prefix exclusion also works with tags." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)\\\\(10)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "This formula matches accounts with the tag *my_module.my_tag* and a code not starting with `10`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:260 +msgid "'External Value' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:262 +msgid "The 'external value' engine is used to refer to **manual** and **carryover values**. Those values are not stored using `account.move.line`, but with `account.report.external.value`. Each of these objects directly points to the expression it impacts, so very little needs to be done about their selection here." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:267 +msgid "**Formulas** can be one of the following:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:270 +msgid "If the result must be the sum of all the external values in the period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:273 +msgid "`most_recent`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:273 +msgid "If the result must be the value of the latest external value in the period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:275 +msgid "In addition, **subformulas** can be used in two ways:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:278 +msgid "`rounding=X`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:278 +msgid "Replacing `X` with a number instructs to round the amount to X decimals." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:282 +msgid "`editable`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:281 +msgid "Indicates this expression can be edited manually, triggering the display of an icon in the report, allowing the user to perform this action." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:285 +msgid "Manual values are created at the `date_to` currently selected in the report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:287 msgid "Both subformulas can be mixed by separating them with a `;`." msgstr "" @@ -7237,19 +7651,19 @@ msgstr "" msgid "is a correct subformula mixing both behaviors." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:258 +#: ../../content/applications/finance/accounting/reporting/customize.rst:294 msgid "'Custom Python Function' engine" msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:260 +#: ../../content/applications/finance/accounting/reporting/customize.rst:296 msgid "This engine is a means for developers to introduce custom computation of expressions on a case-by-case basis. The formula is the name of a **python function** to call, and the subformula is a **key** to fetch in the **dictionary** returned by this function. Use it only if you are making a custom module of your own." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:266 +#: ../../content/applications/finance/accounting/reporting/customize.rst:302 msgid "Columns" msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:268 +#: ../../content/applications/finance/accounting/reporting/customize.rst:304 msgid "Reports can have an **indefinite number** of columns to display. Each column gets its values from the **expressions** declared on the **lines**. The field :guilabel:`expression_label` of the column gives the label of the expressions whose value is displayed. If a line has no **expression** in that field, then nothing is displayed for it in this column. If multiple columns are required, you must use different **expression** labels." msgstr "" @@ -7257,7 +7671,7 @@ msgstr "" msgid "Columns of report." msgstr "" -#: ../../content/applications/finance/accounting/reporting/customize.rst:278 +#: ../../content/applications/finance/accounting/reporting/customize.rst:314 msgid "When using the **period comparison** feature found under the :guilabel:`Options` tab of an accounting report, all columns are repeated in and for each period." msgstr "" @@ -7594,7 +8008,7 @@ msgid "Odoo API key" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:25 -msgid "You can create Odoo external API keys either :ref:`for a single database ` (hosting: Odoo Online, On-premise, and Odoo.sh) or :ref:`for multiple databases managed by a user ` (hosting: Odoo Online)." +msgid "You can create Odoo external API keys either :ref:`for a single database ` (hosting: Odoo Online, On-premise, and Odoo.sh) or :ref:`for all databases managed by a single user ` (hosting: Odoo Online)." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:30 @@ -7602,7 +8016,7 @@ msgid "These API keys are personal and provide full access to your user account. msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:31 -msgid "You can copy the API key only at its creation, and you cannot retrieve it later." +msgid "You can copy the API key only at its creation. It is not possible to retrieve it later." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:32 @@ -7614,11 +8028,11 @@ msgid ":doc:`/developer/reference/external_api`" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:40 -msgid "One key per database" +msgid "Per database" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:42 -msgid "To create a new API key valid for a single database, click on the user menu, then on :guilabel:`My Profile`. Under the :guilabel:`Account Security` tab, click on :guilabel:`New API key`, confirm your password, give a descriptive name to your new key, and copy the new API key." +msgid "To add an API key to a **single** database, connect to the database, enable the :ref:`developer mode `, click on the user menu, and then :guilabel:`My Profile` / :guilabel:`Preferences`. Under the :guilabel:`Account Security` tab, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the API key." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:-1 @@ -7630,11 +8044,15 @@ msgid ":ref:`api/external_api/keys`" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:56 -msgid "One key for multiple databases (fiduciaries)" +msgid "For all databases (fiduciaries)" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:58 -msgid "To create a new API key valid for all the databases of a single user **(the easiest for fiduciaries)**, navigate to `Odoo's website `_ and sign in with your administrator account. Next, open `your account security settings in developer mode `_, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the new API key." +msgid "To add an API key to **all** databases managed by a single user at the same time **(the easiest method for fiduciaries)**, navigate to `Odoo's website `_ and sign in with your administrator account. Next, open `your account security settings in developer mode `_, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the new API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:65 +msgid "Open the `database manager `_ to view all databases that will be linked to the single API key." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:-1 @@ -8415,9 +8833,8 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:63 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:9 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:6 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:6 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:25 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 #: ../../content/applications/finance/fiscal_localizations/peru.rst:6 msgid "Introduction" msgstr "" @@ -9207,6 +9624,7 @@ msgstr "" #: ../../content/applications/finance/accounting/vendor_bills.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:588 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:702 #: ../../content/applications/finance/fiscal_localizations/italy.rst:279 msgid "Vendor bills" msgstr "" @@ -10201,130 +10619,130 @@ msgid "Only two fields are required, the :guilabel:`Product Name` and the :guila msgstr "" #: ../../content/applications/finance/expenses.rst:40 -msgid "The *Sales* app is where specification on the units of measure are created and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the :guilabel:`Units of Measure` internal link to view, create, and edit the units of measure. Refer to :doc:`this document ` to learn more about units of measure and how to configure them." +msgid "The *Sales* app is where specification on the units of measure are created and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the :guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure <../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." msgstr "" -#: ../../content/applications/finance/expenses.rst:51 +#: ../../content/applications/finance/expenses.rst:50 msgid "The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When a specific expense should always be reimbursed for a particular price, enter that amount in the :guilabel:`Cost` field. Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will report the actual cost when submitting an expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:57 +#: ../../content/applications/finance/expenses.rst:56 msgid "The :guilabel:`Cost` field is always visible on the expense category form, but the :guilabel:`Sales Price` field is *only* visible if the :guilabel:`Sales Price` is selected under the :guilabel:`Re-Invoice Expenses` section. Otherwise, the :guilabel:`Sales Price` field is hidden." msgstr "" -#: ../../content/applications/finance/expenses.rst:63 +#: ../../content/applications/finance/expenses.rst:62 msgid "Here are some examples for when to set a specific :guilabel:`Cost` on a product vs. leaving the :guilabel:`Cost` at `0.00`:" msgstr "" -#: ../../content/applications/finance/expenses.rst:66 +#: ../../content/applications/finance/expenses.rst:65 msgid "**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal, they enter the actual amount of the bill and will be reimbursed for that amount. An expense for a meal costing $95.23 would equal a reimbursement for $95.23." msgstr "" -#: ../../content/applications/finance/expenses.rst:69 +#: ../../content/applications/finance/expenses.rst:68 msgid "**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for \"mileage\", they enter the number of miles driven in the :guilabel:`Quantity` field, and are reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for $30.00." msgstr "" -#: ../../content/applications/finance/expenses.rst:73 +#: ../../content/applications/finance/expenses.rst:72 msgid "**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for \"monthly parking\", the reimbursement would be for $75.00." msgstr "" -#: ../../content/applications/finance/expenses.rst:75 +#: ../../content/applications/finance/expenses.rst:74 msgid "**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and the reimbursement would be for $350.00." msgstr "" -#: ../../content/applications/finance/expenses.rst:80 +#: ../../content/applications/finance/expenses.rst:79 msgid "Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It is recommended to check with the accounting department to determine the correct account to reference in this field as it will affect reports." msgstr "" -#: ../../content/applications/finance/expenses.rst:84 +#: ../../content/applications/finance/expenses.rst:83 msgid "Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields, if applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included in Price `. Taxes will be automatically configured if this is set." msgstr "" -#: ../../content/applications/finance/expenses.rst:91 +#: ../../content/applications/finance/expenses.rst:90 msgid "Record expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:94 +#: ../../content/applications/finance/expenses.rst:93 msgid "Manually create a new expense" msgstr "" -#: ../../content/applications/finance/expenses.rst:96 +#: ../../content/applications/finance/expenses.rst:95 msgid "To record a new expense, begin in the main :menuselection:`Expenses` app dashboard, which presents the default :guilabel:`My Expenses` view. This view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`." msgstr "" -#: ../../content/applications/finance/expenses.rst:100 +#: ../../content/applications/finance/expenses.rst:99 msgid "First, click :guilabel:`New`, and then fill out the various fields on the form." msgstr "" -#: ../../content/applications/finance/expenses.rst:102 +#: ../../content/applications/finance/expenses.rst:101 msgid ":guilabel:`Description`: Enter a short description for the expense in the :guilabel:`Description` field. This should be short and informative, such as `lunch with client` or `hotel for conference`." msgstr "" -#: ../../content/applications/finance/expenses.rst:105 +#: ../../content/applications/finance/expenses.rst:104 msgid ":guilabel:`Category`: Select the expense category from the drop-down menu that most closely corresponds to the expense. For example, an airplane ticket would be appropriate for an expense :guilabel:`Category` named :guilabel:`Air Travel`." msgstr "" -#: ../../content/applications/finance/expenses.rst:108 +#: ../../content/applications/finance/expenses.rst:107 msgid ":guilabel:`Total`: Enter the total amount paid for the expense in one of two ways:" msgstr "" -#: ../../content/applications/finance/expenses.rst:110 +#: ../../content/applications/finance/expenses.rst:109 msgid "If the expense is for one single item/expense, and the category selected was for a single item, enter the cost in the :guilabel:`Total` field (the :guilabel:`Quantity` field is hidden)." msgstr "" -#: ../../content/applications/finance/expenses.rst:112 +#: ../../content/applications/finance/expenses.rst:111 msgid "If the expense is for multiples of the same item/expense with a fixed price, the :guilabel:`Unit Price` is displayed. Enter the quantity in the :guilabel:`Quantity` field, and the total cost is automatically updated with the correct total (the :guilabel:`Unit Price` x the :guilabel:`Quantity` = the total). Be advised, the word \"total\" does not appear, the total cost simply appears below the :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/finance/expenses.rst:119 +#: ../../content/applications/finance/expenses.rst:118 msgid "For example, in the case of mileage driven, the :guilabel:`Unit Price` is populated as the cost *per mile*. Set the :guilabel:`Quantity` to the *number of miles* driven, and the total is calculated." msgstr "" -#: ../../content/applications/finance/expenses.rst:123 +#: ../../content/applications/finance/expenses.rst:122 msgid ":guilabel:`Included Taxes`: If taxes were configured on the expense category, the tax percentage and amount appear automatically after entering either the :guilabel:`Total` or the :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/finance/expenses.rst:128 +#: ../../content/applications/finance/expenses.rst:127 msgid "When a tax is configured on an expense category, the :guilabel:`Included Taxes` value will update in real time as the :guilabel:`Total` or :guilabel:`Quantity` is updated." msgstr "" -#: ../../content/applications/finance/expenses.rst:131 +#: ../../content/applications/finance/expenses.rst:130 msgid ":guilabel:`Employee`: Using the drop-down menu, select the employee this expense is for." msgstr "" -#: ../../content/applications/finance/expenses.rst:132 +#: ../../content/applications/finance/expenses.rst:131 msgid ":guilabel:`Paid By`: Click the radio button to indicate who paid for the expense and should be reimbursed. If the employee paid for the expense (and should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the company paid directly instead (e.g. if the company credit card was used to pay for the expense) select :guilabel:`Company`. Depending on the expense category selected, this field may not appear." msgstr "" -#: ../../content/applications/finance/expenses.rst:137 +#: ../../content/applications/finance/expenses.rst:136 msgid ":guilabel:`Bill Reference`: If there is any reference text that should be included for the expense, enter it in this field." msgstr "" -#: ../../content/applications/finance/expenses.rst:139 +#: ../../content/applications/finance/expenses.rst:138 msgid ":guilabel:`Expense Date`: Using the calendar module, enter the date the expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows to navigate to the correct month, then click on the specific day to enter the selection." msgstr "" -#: ../../content/applications/finance/expenses.rst:142 +#: ../../content/applications/finance/expenses.rst:141 msgid ":guilabel:`Account`: Select the expense account that this expense should be logged on from the drop-down menu." msgstr "" -#: ../../content/applications/finance/expenses.rst:144 +#: ../../content/applications/finance/expenses.rst:143 msgid ":guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a customer, select the :abbr:`SO (Sales Order)` and customer that will be invoiced for this expense from the drop-down menu. All sales orders in the drop-down menu list both the :abbr:`SO (Sales Order)` as well as the company the sales order is written for, but after the expense is saved, the customer name disappears and only the :abbr:`SO (Sales Order)` is visible on the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:151 +#: ../../content/applications/finance/expenses.rst:150 msgid "A customer wishes to have an on-site meeting for a custom garden (design and installation) and agrees to pay for the expenses associated with it (such as travel, hotel, meals, etc.). All expenses tied to that meeting would indicate the sales order for the custom garden (which also references the customer) as the :guilabel:`Customer to Reinvoice`." msgstr "" -#: ../../content/applications/finance/expenses.rst:156 +#: ../../content/applications/finance/expenses.rst:155 msgid ":guilabel:`Analytic Distribution`: Select the account(s) the expense should be written against from the drop-down menu for either :guilabel:`Projects`, :guilabel:`Departments`, or both. Multiple accounts can be listed for each category if needed. Adjust the percentage for each analytic account by typing in the percentage value next to the account." msgstr "" -#: ../../content/applications/finance/expenses.rst:160 +#: ../../content/applications/finance/expenses.rst:159 msgid ":guilabel:`Company`: If multiple companies are set up, select the company this expense should be filed for from the drop-down menu. The current company will automatically populate this field." msgstr "" -#: ../../content/applications/finance/expenses.rst:162 +#: ../../content/applications/finance/expenses.rst:161 msgid ":guilabel:`Notes...`: If any notes are needed in order to clarify the expense, enter them in the notes field." msgstr "" @@ -10332,11 +10750,11 @@ msgstr "" msgid "A filled in expense form for a client lunch." msgstr "" -#: ../../content/applications/finance/expenses.rst:170 +#: ../../content/applications/finance/expenses.rst:169 msgid "Attach a receipt" msgstr "" -#: ../../content/applications/finance/expenses.rst:172 +#: ../../content/applications/finance/expenses.rst:171 msgid "After the expense is created, the next step is to attach a receipt. Click the :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the receipt to be attached, and click :guilabel:`Open`. The new receipt is recorded in the chatter, and the number of receipts will appear next to the :guilabel:`šŸ“Ž (paperclip)` icon beneath the expense form. More than one receipt can be attached to an individual expense, as needed. The number of receipts attached to the expense will be noted on the paperclip icon." msgstr "" @@ -10344,15 +10762,15 @@ msgstr "" msgid "Attach a receipt and it appears in the chatter." msgstr "" -#: ../../content/applications/finance/expenses.rst:184 +#: ../../content/applications/finance/expenses.rst:183 msgid "Create new expenses from a scanned receipt" msgstr "" -#: ../../content/applications/finance/expenses.rst:186 +#: ../../content/applications/finance/expenses.rst:185 msgid "Rather than manually inputting all of the information for an expense, expenses can be created by scanning a PDF receipt." msgstr "" -#: ../../content/applications/finance/expenses.rst:189 +#: ../../content/applications/finance/expenses.rst:188 msgid "First, in the main :guilabel:`Expenses` app dashboard view (this view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`), click :guilabel:`Scan`, and a file explorer pops up. Navigate to the receipt to be uploaded, click on it to select it, and then click :guilabel:`Open`." msgstr "" @@ -10361,19 +10779,19 @@ msgid "Create an expense by scanning a receipt. Click Scan at the top of the Exp "view." msgstr "" -#: ../../content/applications/finance/expenses.rst:199 +#: ../../content/applications/finance/expenses.rst:198 msgid "The receipt is scanned, and a new entry is created with today's date as the :guilabel:`Expense Date`, and any other fields it can populate based on the scanned data, such as the total. Click on the new entry to open the individual expense form, and make any changes needed. The scanned receipt appears in the chatter." msgstr "" -#: ../../content/applications/finance/expenses.rst:205 +#: ../../content/applications/finance/expenses.rst:204 msgid "Automatically create new expenses from an email" msgstr "" -#: ../../content/applications/finance/expenses.rst:207 +#: ../../content/applications/finance/expenses.rst:206 msgid "Instead of individually creating each expense in the *Expenses* app, expenses can be automatically created by sending an email to an email alias." msgstr "" -#: ../../content/applications/finance/expenses.rst:210 +#: ../../content/applications/finance/expenses.rst:209 msgid "To do so, first, an email alias needs to be configured. Go to :menuselection:`Expenses app --> Configuration --> Settings`. Ensure :guilabel:`Incoming Emails` is enabled." msgstr "" @@ -10382,19 +10800,19 @@ msgstr "" msgid "Create the domain alias by clicking the link." msgstr "" -#: ../../content/applications/finance/expenses.rst:218 +#: ../../content/applications/finance/expenses.rst:217 msgid "If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath the incoming emails check box instead of the email address field. Refer to this documentation for setup instructions and more information: :doc:`/administration/maintain/domain_names`. Once the domain alias is configured, the email address field will be visible beneath the incoming emails section." msgstr "" -#: ../../content/applications/finance/expenses.rst:224 +#: ../../content/applications/finance/expenses.rst:223 msgid "Next, enter the email address to be used in the email field, and then click :guilabel:`Save`. Now that the email address has been entered, emails can be sent to that alias to create new expenses without having to be in the Odoo database." msgstr "" -#: ../../content/applications/finance/expenses.rst:228 +#: ../../content/applications/finance/expenses.rst:227 msgid "To submit an expense via email, create a new email and enter the product's *internal reference* code (if available) and the amount of the expense in the email subject. Next, attach the receipt to the email. Odoo creates the expense by taking the information in the email subject and combining it with the receipt." msgstr "" -#: ../../content/applications/finance/expenses.rst:233 +#: ../../content/applications/finance/expenses.rst:232 msgid "To check an expense categories internal reference, go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. If an internal reference is listed on the expense category, it is listed in the :guilabel:`Internal Reference` column." msgstr "" @@ -10402,7 +10820,7 @@ msgstr "" msgid "Internal reference numbers are listed in the main Expense Categories view." msgstr "" -#: ../../content/applications/finance/expenses.rst:241 +#: ../../content/applications/finance/expenses.rst:240 msgid "To add an internal reference on an expense category, click on the category to open the form. Enter the internal reference in the field. Beneath the :guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a subject prefix when submitting by email.`" msgstr "" @@ -10410,43 +10828,43 @@ msgstr "" msgid "Internal reference numbers are listed in the main Expense Products view." msgstr "" -#: ../../content/applications/finance/expenses.rst:250 +#: ../../content/applications/finance/expenses.rst:249 msgid "For security purposes, only authenticated employee emails are accepted by Odoo when creating an expense from an email. To confirm an authenticated employee email address, go to the employee card in the :menuselection:`Employees` app, and refer to the :guilabel:`Work Email`" msgstr "" -#: ../../content/applications/finance/expenses.rst:259 +#: ../../content/applications/finance/expenses.rst:258 msgid "If submitting an expense via email for a $25.00 meal during a work trip, the email subject would be `FOOD $25.00`." msgstr "" -#: ../../content/applications/finance/expenses.rst:262 +#: ../../content/applications/finance/expenses.rst:261 msgid "Explanation:" msgstr "" -#: ../../content/applications/finance/expenses.rst:264 +#: ../../content/applications/finance/expenses.rst:263 msgid "The :guilabel:`Internal Reference` for the expense category `Meals` is `FOOD`" msgstr "" -#: ../../content/applications/finance/expenses.rst:265 +#: ../../content/applications/finance/expenses.rst:264 msgid "The :guilabel:`Cost` for the expense is `$25.00`" msgstr "" -#: ../../content/applications/finance/expenses.rst:270 +#: ../../content/applications/finance/expenses.rst:269 msgid "Create an expense report" msgstr "" -#: ../../content/applications/finance/expenses.rst:272 +#: ../../content/applications/finance/expenses.rst:271 msgid "When expenses are ready to submit (such as at the end of a business trip, or once a month), an *expense report* needs to be created. Go to the main :menuselection:`Expenses` app dashboard, which displays a default :guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My Expenses --> My Expenses`." msgstr "" -#: ../../content/applications/finance/expenses.rst:277 +#: ../../content/applications/finance/expenses.rst:276 msgid "Expenses are color coded by status. Any expense with a status of :guilabel:`To Report` (expenses that still need to be added to an expense report) the text appears in blue. All other statuses (:guilabel:`To Submit`, :guilabel:`Submitted`, and :guilabel:`Approved`) the text appears in black." msgstr "" -#: ../../content/applications/finance/expenses.rst:281 +#: ../../content/applications/finance/expenses.rst:280 msgid "First, select each individual expense for the report by clicking the check box next to each entry, or quickly select all the expenses in the list by clicking the check box next to :guilabel:`Expense Date`." msgstr "" -#: ../../content/applications/finance/expenses.rst:285 +#: ../../content/applications/finance/expenses.rst:284 msgid "Another way to quickly add all expenses that are not on an expense report is to click :guilabel:`Create Report` without selecting any expenses, and Odoo will select all expenses with a status of :guilabel:`To Submit` that are not already on a report." msgstr "" @@ -10454,15 +10872,15 @@ msgstr "" msgid "Select the expenses to submit, then create the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:294 +#: ../../content/applications/finance/expenses.rst:293 msgid "Any expense can be selected from the :guilabel:`My Expenses` list, regardless of status. The :guilabel:`Create Report` button is visible as long as there is a minimum of 1 expense with a status of :guilabel:`To Report` selected. When the :guilabel:`Create Report` button is clicked, only expenses with a status of :guilabel:`To Submit` that are *not* currently on another expense report will appear in the newly created expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:300 +#: ../../content/applications/finance/expenses.rst:299 msgid "Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report appears with all the expenses listed in the :guilabel:`Expense` tab. If there is a receipt attached to an individual expense, a :guilabel:`šŸ“Ž (paperclip)` icon appears next to the :guilabel:`Customer to Reinvoice` and :guilabel:`Analytic Distribution` columns." msgstr "" -#: ../../content/applications/finance/expenses.rst:305 +#: ../../content/applications/finance/expenses.rst:304 msgid "When the report is created, the date range for the expenses appears in the :guilabel:`Expense Report Summary` field by default. It is recommended to edit this field with a short summary for each report to help keep expenses organized. Enter a short description for the expense report (such as `Client Trip NYC`, or `Repairs for Company Car`) in the :guilabel:`Expense Report Summary` field. Next, select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report. If needed, the :guilabel:`Journal` can be changed. Use the drop-down menu to select a different :guilabel:`Journal`." msgstr "" @@ -10470,7 +10888,7 @@ msgstr "" msgid "Enter a short description and select a manager for the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:317 +#: ../../content/applications/finance/expenses.rst:316 msgid "If some expenses are not on the report that should be, they can still be added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense` tab. A pop up appears with all the available expenses that can be added to the report (with a status of :guilabel:`To Submit`). Click the check box next to each expense to add, then click :guilabel:`Select`. The items now appear on the report that was just created. If a new expense needs to be added that does *not* appear on the list, click :guilabel:`New` to create a new expense and add it to the report." msgstr "" @@ -10478,39 +10896,39 @@ msgstr "" msgid "Add more expenses to the report before submitting." msgstr "" -#: ../../content/applications/finance/expenses.rst:329 +#: ../../content/applications/finance/expenses.rst:328 msgid "Expense reports can be created in one of three places:" msgstr "" -#: ../../content/applications/finance/expenses.rst:331 +#: ../../content/applications/finance/expenses.rst:330 msgid "Go to the main :menuselection:`Expenses` app dashboard (also accessed by going to :menuselection:`Expenses app --> My Expenses --> My Expenses`)" msgstr "" -#: ../../content/applications/finance/expenses.rst:333 +#: ../../content/applications/finance/expenses.rst:332 msgid "Go to :menuselection:`Expenses app --> My Expenses --> My Reports`" msgstr "" -#: ../../content/applications/finance/expenses.rst:334 +#: ../../content/applications/finance/expenses.rst:333 msgid "Go to :menuselection:`Expenses app --> Expense Reports`" msgstr "" -#: ../../content/applications/finance/expenses.rst:336 +#: ../../content/applications/finance/expenses.rst:335 msgid "In any of these views, click :guilabel:`New` to create a new expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:341 +#: ../../content/applications/finance/expenses.rst:340 msgid "Submit an expense report" msgstr "" -#: ../../content/applications/finance/expenses.rst:343 +#: ../../content/applications/finance/expenses.rst:342 msgid "When an expense report is completed, the next step is to submit the report to a manager for approval. Reports must be individually submitted, and cannot be submitted in batches. Open the specific report from the list of expense reports (if the report is not already open). To view all expense reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`." msgstr "" -#: ../../content/applications/finance/expenses.rst:348 +#: ../../content/applications/finance/expenses.rst:347 msgid "If the list is large, grouping the results by status may be helpful since only reports that have a :guilabel:`To Submit` status need to be submitted, reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." msgstr "" -#: ../../content/applications/finance/expenses.rst:352 +#: ../../content/applications/finance/expenses.rst:351 msgid "The :guilabel:`To Submit` expenses are easily identifiable not just from the :guilabel:`To Submit` status, but the text appears in blue, while the other expenses text appears in black." msgstr "" @@ -10518,71 +10936,71 @@ msgstr "" msgid "Submit the report to the manager." msgstr "" -#: ../../content/applications/finance/expenses.rst:360 +#: ../../content/applications/finance/expenses.rst:359 msgid "The status of each report is shown in the :guilabel:`Status` column on the right. If the :guilabel:`Status` column is not visible, click the :guilabel:`Additional Options (two dots)` icon at the end of the row, and enable :guilabel:`Status`." msgstr "" -#: ../../content/applications/finance/expenses.rst:364 +#: ../../content/applications/finance/expenses.rst:363 msgid "Click on a report to open it, then click :guilabel:`Submit To Manager`. After submitting a report, the next step is to wait for the manager to approve it." msgstr "" -#: ../../content/applications/finance/expenses.rst:368 +#: ../../content/applications/finance/expenses.rst:367 msgid "The :ref:`expenses/approve`, :ref:`expenses/post`, and :ref:`expenses/reimburse` sections are **only** for users with the *necessary rights*." msgstr "" -#: ../../content/applications/finance/expenses.rst:374 +#: ../../content/applications/finance/expenses.rst:373 msgid "Approve expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:376 +#: ../../content/applications/finance/expenses.rst:375 msgid "In Odoo, not just anyone can approve expense reportsā€” only users with the necessary rights (or permissions) can. This means that a user must have at least *Team Approver* rights for the *Expenses* app. Employees with the necessary rights can review expense reports, approve or reject them, and provide feedback thanks to the integrated communication tool." msgstr "" -#: ../../content/applications/finance/expenses.rst:381 +#: ../../content/applications/finance/expenses.rst:380 msgid "To see who has rights to approve, go to the main :menuselection:`Settings` app and click on :guilabel:`Manage Users`." msgstr "" -#: ../../content/applications/finance/expenses.rst:385 +#: ../../content/applications/finance/expenses.rst:384 msgid "If the *Settings* app is not available, then certain rights are not set on the account. Check the :guilabel:`Access Rights` tab of a user's card in the :menuselection:`Settings` app. the :guilabel:`Administration` section (bottom right of the :guilabel:`Access Rights` tab) is set to one of three options:" msgstr "" -#: ../../content/applications/finance/expenses.rst:390 +#: ../../content/applications/finance/expenses.rst:389 msgid ":guilabel:`None (blank)`: The user cannot access the *Settings* app at all." msgstr "" -#: ../../content/applications/finance/expenses.rst:391 +#: ../../content/applications/finance/expenses.rst:390 msgid ":guilabel:`Access Rights`: The user can only view the :guilabel:`User's & Companies` section of the *Settings* app." msgstr "" -#: ../../content/applications/finance/expenses.rst:393 +#: ../../content/applications/finance/expenses.rst:392 msgid ":guilabel:`Settings`: The user has access to the entire *Settings* app with no restrictions." msgstr "" -#: ../../content/applications/finance/expenses.rst:395 +#: ../../content/applications/finance/expenses.rst:394 msgid "Please refer to :doc:`this document ` to learn more about managing users and their access rights." msgstr "" -#: ../../content/applications/finance/expenses.rst:398 +#: ../../content/applications/finance/expenses.rst:397 msgid "Click on an individual to view their card, which displays the :guilabel:`Access Rights` tab in the default view. Scroll down to the :guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are four options:" msgstr "" -#: ../../content/applications/finance/expenses.rst:402 +#: ../../content/applications/finance/expenses.rst:401 msgid ":guilabel:`None (blank)`: A blank field means the user has no rights to view or approve expense reports, and can only view their own." msgstr "" -#: ../../content/applications/finance/expenses.rst:404 +#: ../../content/applications/finance/expenses.rst:403 msgid ":guilabel:`Team Approver`: The user can only view and approve expense reports for their own specific team." msgstr "" -#: ../../content/applications/finance/expenses.rst:406 +#: ../../content/applications/finance/expenses.rst:405 msgid ":guilabel:`All Approver`: The user can view and approve any expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:407 +#: ../../content/applications/finance/expenses.rst:406 msgid ":guilabel:`Administrator`: The user can view and approve any expense report, as well as access the reporting and configuration menus in the *Expenses* app." msgstr "" -#: ../../content/applications/finance/expenses.rst:410 +#: ../../content/applications/finance/expenses.rst:409 msgid "Users who are able to approve expense reports (typically managers) can easily view all expense reports they have access rights to. Go to :menuselection:`Expenses app --> Expense Reports`, and a list appears with all expense reports that have a status of either :guilabel:`To Submit`, :guilabel:`Submitted`, :guilabel:`Approved`, :guilabel:`Posted`, or :guilabel:`Done`. Expense reports with a status of :guilabel:`Refused` are hidden in the default view." msgstr "" @@ -10590,23 +11008,23 @@ msgstr "" msgid "Reports to validate are found on the Reports to Approve page." msgstr "" -#: ../../content/applications/finance/expenses.rst:420 +#: ../../content/applications/finance/expenses.rst:419 msgid "When viewing expense reports, there is a panel of filters that can be enabled or disabled on the left side. The three categories that filters can be applied on are :guilabel:`Status`, :guilabel:`Employee`, and :guilabel:`Company`. To view only expense reports with a particular status, enable the specific status filter to display the expense reports with only that status. Disable the specific status filter to hide the reports with that status. To view expense reports for a particular employee and/or company, enable the specific employee name filter and/or company filter in the :guilabel:`Employee` and :guilabel:`Company` sections." msgstr "" -#: ../../content/applications/finance/expenses.rst:428 +#: ../../content/applications/finance/expenses.rst:427 msgid "Reports can be approved in two ways (individually or several at once) and refused only one way. To approve multiple expense reports at once, remain in the list view. First, select the reports to approve by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list." msgstr "" -#: ../../content/applications/finance/expenses.rst:434 +#: ../../content/applications/finance/expenses.rst:433 msgid "Only reports with a status of :guilabel:`Submitted` can be approved. It is recommended to only display the submitted reports by adjusting the status filter on the left side by only having the :guilabel:`Submitted` filter enabled." msgstr "" -#: ../../content/applications/finance/expenses.rst:438 +#: ../../content/applications/finance/expenses.rst:437 msgid "If a report is selected that is unable to be approved, the :guilabel:`Approve Report` button **will not appear**, indicating there is a problem with the selected report(s)." msgstr "" -#: ../../content/applications/finance/expenses.rst:441 +#: ../../content/applications/finance/expenses.rst:440 msgid "Next, click the :guilabel:`Approve Report` button." msgstr "" @@ -10614,11 +11032,11 @@ msgstr "" msgid "Approve multiple reports by clicking the checkboxes next to each report." msgstr "" -#: ../../content/applications/finance/expenses.rst:447 +#: ../../content/applications/finance/expenses.rst:446 msgid "To approve an individual report, click on a report to go to a detailed view of that report. In this view, several options are presented: :guilabel:`Approve`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:451 +#: ../../content/applications/finance/expenses.rst:450 msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`." msgstr "" @@ -10627,7 +11045,7 @@ msgstr "" msgid "Send messages in the chatter." msgstr "" -#: ../../content/applications/finance/expenses.rst:458 +#: ../../content/applications/finance/expenses.rst:457 msgid "Team managers can easily view all the expense reports for their team members. While in the :guilabel:`Expense Reports` view, click the drop-down arrow in the right-side of the search box, and click on :guilabel:`My Team` in the :guilabel:`Filters` section. This presents all the reports for the manager's team." msgstr "" @@ -10635,19 +11053,19 @@ msgstr "" msgid "Select the My Team filter." msgstr "" -#: ../../content/applications/finance/expenses.rst:468 +#: ../../content/applications/finance/expenses.rst:467 msgid "If more information is needed, such as a missing receipt, communication is easy from the chatter. In an individual report, simply click :guilabel:`Send message` to open the message text box. Type in a message, tagging the proper person (if needed), and post it to the chatter by clicking :guilabel:`Send`. The message is posted in the chatter, and the person tagged will be notified via email of the message, as well as any followers." msgstr "" -#: ../../content/applications/finance/expenses.rst:474 +#: ../../content/applications/finance/expenses.rst:473 msgid "The only people that can be tagged in a message are *followers*. To see who is a follower, click on the :guilabel:`šŸ‘¤ (person)` icon to display the followers of the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:484 +#: ../../content/applications/finance/expenses.rst:483 msgid "Post expenses in accounting" msgstr "" -#: ../../content/applications/finance/expenses.rst:486 +#: ../../content/applications/finance/expenses.rst:485 msgid "Once an expense report is approved, the next step is to post the report to the accounting journal. To view all expense reports, go to :menuselection:`Expenses app --> Expense Reports`. To view only the expense reports that have been approved and need to be posted, adjust the filters on the left side so that only the :guilabel:`Approved` status is enabled." msgstr "" @@ -10655,7 +11073,7 @@ msgstr "" msgid "View reports to post by clicking on expense reports, then reports to post." msgstr "" -#: ../../content/applications/finance/expenses.rst:495 +#: ../../content/applications/finance/expenses.rst:494 msgid "Just like approvals, expense reports can be posted in two ways (individually or several at once). To post multiple expense reports at once, remain in the list view. First, select the reports to post by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Post Entries`." msgstr "" @@ -10663,31 +11081,31 @@ msgstr "" msgid "Post multiple reports at a time from the Expense Reports view, with the Approved filter." msgstr "" -#: ../../content/applications/finance/expenses.rst:504 +#: ../../content/applications/finance/expenses.rst:503 msgid "To post an individual report, click on a report to go to the detailed view of that report. In this view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to post the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:509 +#: ../../content/applications/finance/expenses.rst:508 msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`. Refused reports can be viewed by going to :menuselection:`Expenses app --> Expense Reports`, then adjusting the filters on the left so that only :guilabel:`Refused` is selected. This will only show the refused expense reports." msgstr "" -#: ../../content/applications/finance/expenses.rst:516 +#: ../../content/applications/finance/expenses.rst:515 msgid "To post expense reports to an accounting journal, the user must have following access rights:" msgstr "" -#: ../../content/applications/finance/expenses.rst:518 +#: ../../content/applications/finance/expenses.rst:517 msgid "Accounting: Accountant or Adviser" msgstr "" -#: ../../content/applications/finance/expenses.rst:519 +#: ../../content/applications/finance/expenses.rst:518 msgid "Expenses: Manager" msgstr "" -#: ../../content/applications/finance/expenses.rst:524 +#: ../../content/applications/finance/expenses.rst:523 msgid "Reimburse employees" msgstr "" -#: ../../content/applications/finance/expenses.rst:526 +#: ../../content/applications/finance/expenses.rst:525 msgid "After an expense report is posted to an accounting journal, the next step is to reimburse the employee. To view all the expense reports to pay, go to :menuselection:`Expenses app --> Expense Reports --> Reports To Pay`." msgstr "" @@ -10695,7 +11113,7 @@ msgstr "" msgid "View reports to pay by clicking on expense reports, then reports to pay." msgstr "" -#: ../../content/applications/finance/expenses.rst:534 +#: ../../content/applications/finance/expenses.rst:533 msgid "Just like approvals and posting, expense reports can be paid in two ways (individually or several at once). To pay multiple expense reports at once, remain in the list view. First, select the reports to pay by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Register Payment`." msgstr "" @@ -10703,15 +11121,15 @@ msgstr "" msgid "Post multiple reports by selecting them, clicking the gear, and then post the entries." msgstr "" -#: ../../content/applications/finance/expenses.rst:543 +#: ../../content/applications/finance/expenses.rst:542 msgid "To pay an individual report, click on a report to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee." msgstr "" -#: ../../content/applications/finance/expenses.rst:546 +#: ../../content/applications/finance/expenses.rst:545 msgid "A :guilabel:`Register Payment` pop-up appears, and the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` can be modified, if needed. When the selections are correct, click :guilabel:`Create Payment` to send the payment to the employee." msgstr "" -#: ../../content/applications/finance/expenses.rst:550 +#: ../../content/applications/finance/expenses.rst:549 msgid "To pay an individual report, click on a report in the list view to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee. A :guilabel:`Register Payment` pop-up appears, but when paying an individual expense report instead of several at once, more options appear in the pop-up. In addition to the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` fields, a :guilabel:`Recipient Bank Account`, :guilabel:`Amount`, and :guilabel:`Memo` field appear. Select the employee's bank account from the drop-down menu to directly deposit the payment to their account. When all other selections are correct, click :guilabel:`Create Payment` to send the payment to the employee." msgstr "" @@ -10720,45 +11138,45 @@ msgid "Different options appear when registering an individual expense report ve "expense reports at once." msgstr "" -#: ../../content/applications/finance/expenses.rst:565 +#: ../../content/applications/finance/expenses.rst:564 msgid "Re-invoice expenses to customers" msgstr "" -#: ../../content/applications/finance/expenses.rst:567 +#: ../../content/applications/finance/expenses.rst:566 msgid "If expenses are tracked on customer projects, expenses can be automatically charged back to the customer. This is done by creating an expense, referencing the :abbr:`SO (Sales Order)` the expense should be added to, and then creating the expense report. Next, managers approve the expense report, and the accounting department posts the journal entries. Finally, once the expense report is posted to a journal, the expense(s) appears on the :abbr:`SO (Sales Order)` that was referenced. The sales order can then be invoiced, thus invoicing the customer for the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:575 +#: ../../content/applications/finance/expenses.rst:574 #: ../../content/applications/finance/fiscal_localizations/india.rst:55 #: ../../content/applications/finance/fiscal_localizations/india.rst:195 msgid "Setup" msgstr "" -#: ../../content/applications/finance/expenses.rst:577 +#: ../../content/applications/finance/expenses.rst:576 msgid "First, specify the invoicing policy for each expense category. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. Click on the expense category to open the expense category form. Under the :guilabel:`Invoicing` section, click the radio button next to the desired selection for :guilabel:`Re-Invoicing Expenses`. Options are :guilabel:`None`, :guilabel:`At cost`, and :guilabel:`Sales price`." msgstr "" -#: ../../content/applications/finance/expenses.rst:583 +#: ../../content/applications/finance/expenses.rst:582 msgid ":guilabel:`Re-Invoicing Expenses`:" msgstr "" -#: ../../content/applications/finance/expenses.rst:585 +#: ../../content/applications/finance/expenses.rst:584 msgid ":guilabel:`None`: Expense category will not be re-invoiced." msgstr "" -#: ../../content/applications/finance/expenses.rst:586 +#: ../../content/applications/finance/expenses.rst:585 msgid ":guilabel:`At cost`: Expense category will invoice expenses at their real cost." msgstr "" -#: ../../content/applications/finance/expenses.rst:587 +#: ../../content/applications/finance/expenses.rst:586 msgid ":guilabel:`At sales price`: Expense category will invoice the price set on the sale order." msgstr "" -#: ../../content/applications/finance/expenses.rst:590 +#: ../../content/applications/finance/expenses.rst:589 msgid "Create an expense" msgstr "" -#: ../../content/applications/finance/expenses.rst:592 +#: ../../content/applications/finance/expenses.rst:591 msgid "First, when :ref:`creating a new expense `, the correct information needs to be entered in order to re-invoice a customer. Select the *sales order* the expense will appear on in the :guilabel:`Customer to Reinvoice` section, from the drop-down menu. Next, select the :guilabel:`Analytic Account` the expense will be posted to. After the expense(s) are created, the expense report needs to be :ref:`created ` and :ref:`submitted ` as usual." msgstr "" @@ -10766,31 +11184,31 @@ msgstr "" msgid "Ensure the customer to be invoiced is called out on the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:604 +#: ../../content/applications/finance/expenses.rst:603 msgid "Selecting a :guilabel:`Customer to Reinvoice` when creating an expense is critical, since this is what causes the expenses to be automatically invoiced after an expense report is approved." msgstr "" -#: ../../content/applications/finance/expenses.rst:607 +#: ../../content/applications/finance/expenses.rst:606 msgid "The :guilabel:`Customer to Reinvoice` field can be modified *until an expense report is* **approved**, then the field is no longer able to be modified." msgstr "" -#: ../../content/applications/finance/expenses.rst:611 +#: ../../content/applications/finance/expenses.rst:610 msgid "Validate and post expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:613 +#: ../../content/applications/finance/expenses.rst:612 msgid "Only employees with permissions (typically managers or supervisors) can :ref:`approve expenses `. Before approving an expense report, ensure the :guilabel:`Analytic Distribution` is set on every expense line of a report. If an :guilabel:`Analytic Distribution` is missing, assign the correct account(s) from the drop-down menu, and then click :guilabel:`Approve` or :guilabel:`Refuse`." msgstr "" -#: ../../content/applications/finance/expenses.rst:619 +#: ../../content/applications/finance/expenses.rst:618 msgid "The accounting department is typically responsible for :ref:`posting journal entries `. Once an expense report is approved, it can then be posted. The :abbr:`SO (Sales Order)` is **only** updated *after the journal entries are posted*. One the journal entries are posted, the expenses now appear on the referenced :abbr:`SO (Sales Order)`." msgstr "" -#: ../../content/applications/finance/expenses.rst:625 +#: ../../content/applications/finance/expenses.rst:624 msgid "Invoice expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:627 +#: ../../content/applications/finance/expenses.rst:626 msgid "Once the :abbr:`SO (Sales Order)` has been updated, it is time to invoice the customer. After the expense report has been approved and the journal entries have been posted, click the :guilabel:`Sales Orders` smart button to open the :abbr:`SO (Sales Order)`. The expenses to be re-invoiced are now on the :abbr:`SO (Sales Order)`." msgstr "" @@ -10799,11 +11217,11 @@ msgid "After the expense report is posted to the journal entry, the sales order "by clicking on the sales order number." msgstr "" -#: ../../content/applications/finance/expenses.rst:638 +#: ../../content/applications/finance/expenses.rst:637 msgid "More than one :abbr:`SO (Sales Order)` can be referenced on an expense report. If more than one :abbr:`SO (Sales Order)` is referenced, the :guilabel:`Sales Orders` smart button will list the number of :abbr:`SO (Sales Order)`'s. If multiple :abbr:`SO (Sales Order)`'s are listed, the :guilabel:`Sales Orders` smart button opens a list view of all the :abbr:`SO (Sales Order)`'s on the expense report. Click on a :abbr:`SO (Sales Order)` to open the individual :abbr:`SO (Sales Order)`." msgstr "" -#: ../../content/applications/finance/expenses.rst:645 +#: ../../content/applications/finance/expenses.rst:644 msgid "The expenses are listed in the :abbr:`SO (Sales Order)` :guilabel:`Order Lines` tab." msgstr "" @@ -10811,7 +11229,7 @@ msgstr "" msgid "See the expenses listed on the sales order after clicking into it." msgstr "" -#: ../../content/applications/finance/expenses.rst:651 +#: ../../content/applications/finance/expenses.rst:650 msgid "Next, click :guilabel:`Create Invoice`, and select if the invoice is for a :guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a :guilabel:`Down payment (fixed amount)` by clicking the radio button next to it. Then, click :guilabel:`Create Invoice`. The customer has now been invoiced for the expenses." msgstr "" @@ -11174,7 +11592,6 @@ msgid "Webinars" msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:8 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:20 msgid "Below you can find videos with a general description of the localization, and how to configure it." msgstr "" @@ -11192,10 +11609,9 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:20 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:28 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:23 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:24 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:37 #: ../../content/applications/finance/fiscal_localizations/germany.rst:61 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:57 msgid "Modules installation" msgstr "" @@ -11206,7 +11622,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:29 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:16 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:37 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:32 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:30 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:46 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 #: ../../content/applications/finance/fiscal_localizations/france.rst:182 @@ -11215,9 +11632,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:66 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:98 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:122 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 #: ../../content/applications/finance/fiscal_localizations/romania.rst:14 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:14 @@ -11229,7 +11645,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:30 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:17 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:38 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:31 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:47 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 #: ../../content/applications/finance/fiscal_localizations/india.rst:17 @@ -11237,9 +11654,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:67 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:99 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:123 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:72 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:116 #: ../../content/applications/finance/fiscal_localizations/romania.rst:15 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:15 @@ -11251,7 +11667,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:18 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:39 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 #: ../../content/applications/finance/fiscal_localizations/france.rst:59 @@ -11260,9 +11677,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:68 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:100 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 #: ../../content/applications/finance/fiscal_localizations/romania.rst:16 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 @@ -11322,7 +11738,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:50 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:62 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:70 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:144 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 #: ../../content/applications/finance/fiscal_localizations/peru.rst:47 msgid "Configure your company" msgstr "" @@ -11496,6 +11912,7 @@ msgid "A list showing less common Argentinean tax options, which are labeled as msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:200 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:254 msgid "Document types" msgstr "" @@ -11552,6 +11969,7 @@ msgid "document types grouped by letters." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:243 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:271 msgid "Use on invoices" msgstr "" @@ -11668,6 +12086,7 @@ msgid "When creating :guilabel:`Purchase Journals`, it's possible to define whet msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:330 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:393 #: ../../content/applications/finance/fiscal_localizations/peru.rst:351 msgid "Usage and testing" msgstr "" @@ -12705,6 +13124,7 @@ msgid "The Belgian chart of accounts includes pre-configured accounts as describ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:375 #: ../../content/applications/finance/fiscal_localizations/romania.rst:79 msgid ":doc:`../accounting/get_started/chart_of_accounts`" msgstr "" @@ -12951,8 +13371,8 @@ msgid "Import SODA files" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:290 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:257 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:303 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:263 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:314 msgid "Electronic invoicing" msgstr "" @@ -13299,6 +13719,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:70 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:233 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:234 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 msgid ":guilabel:`Name`" @@ -13333,6 +13754,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:78 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:240 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:235 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:276 msgid ":guilabel:`Email`" @@ -13472,12 +13894,12 @@ msgid "Do not delete taxes, as they are used for the AvaTax tax computation. If msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:200 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:158 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:253 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:246 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:662 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:771 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:251 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:820 msgid "Products" msgstr "" @@ -13515,8 +13937,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:225 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:265 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:178 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:623 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:174 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:656 #: ../../content/applications/finance/fiscal_localizations/philippines.rst:40 msgid "Contacts" msgstr "" @@ -13603,7 +14025,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:276 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:338 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:300 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 msgid "Workflows" msgstr "" @@ -13698,528 +14120,702 @@ msgstr "" msgid "Chile" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:8 -msgid "The Chilean localization has been improved and extended in Odoo v13. In this version, the next modules are available:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:6 +msgid "Watch the two webinar recordings below for a general presentation of the localization, and search the playlist for tutorials to discover practical workflows while using Odoo in Chile." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:9 +msgid "`Webinar: intro and demo `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:10 +msgid "`Webinar: delivery guide `_." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:11 -msgid "**l10n_cl:** Adds accounting features for the Chilean localization, which represent the minimal configuration required for a company to operate in Chile and under the SII (Servicio de Impuestos Internos) regulations and guidelines." +msgid "`Playlist of tutorials `_." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:15 -msgid "**l10n_cl_edi:** Includes all technical and functional requirements to generate and receive Electronic Invoice via web service, based on the SII regulations." +msgid "`Chilean localization app tour `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:18 -msgid "**l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 columnas)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:21 -msgid "`App Tour - LocalizaciĆ³n de Chile `_" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:16 +msgid "`Chilean localization smart tutorial `_" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:22 -msgid "`Smart Tutorial - LocalizaciĆ³n de Chile `_" +msgid "Modules" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:28 -msgid "Install the Chilean localization modules" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:24 +msgid ":ref:`Install ` the following modules to utilize all the features of the Chilean localization." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:30 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:33 +msgid ":guilabel:`Chile - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Chilean module to install on Odoo." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:34 +msgid "`l10n_cl`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:35 +msgid "Adds the minimal accounting features required for a company to operate in Chile under the :abbr:`SII (Servicio de Impuestos Internos)` regulations and guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:37 +msgid ":guilabel:`Chile - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:38 +msgid "`l10n_cl_reports`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:39 -msgid "When you install a database from scratch selecting Chile as country, Odoo will automatically install the base module: Chile - Accounting." +msgid "Adds the *Propuesta F29* and *Balance Tributario (8 columnas)* reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:40 +msgid ":guilabel:`Chile - E-invoiving`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:41 +msgid "`l10n_cl_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:42 +msgid "Includes all technical and functional requirements to generate and receive electronic invoices online based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:44 -msgid "Company Settings" +msgid ":guilabel:`Chile - Electronic Receipt`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:45 +msgid "`l10n_cl_boletas`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:46 -msgid "Once the modules are installed, the first step is to set up your company data. Additional to the basic information, you need to add all the data and elements required for Electronic Invoice, the easiest way to configure it is in :menuselection:`Accounting --> Settings --> Chilean Localization`." +msgid "Includes all technical and functional requirements to generate and receive electronic invoices digitally based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:48 +msgid ":guilabel:`Electronic Esports of Goods for Chile`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:49 +msgid "`l10n_cl_edi_exports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:50 +msgid "Includes technical and functional requirements to generate electronic invoices for exporting goods based on the :abbr:`SII (Servicio de Impuestos Internos)` and customs regulations." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:52 -msgid "All the following configuration and functionality is only available in Odoo if your company already passed the `Certification process `_ in the SII - Sistema de FacturaciĆ³n de Mercado, this certification enables you to generate electronic invoices from your ERP and send them automatically to the SII. If your company has not passed this certification yet, make sure you communicate this to your Account Manager as a special process outside Odoo is required in order to complete this certification." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:56 +msgid ":guilabel:`Chile - E-Invoicing Delivery Guide`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:53 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:57 +msgid "`l10n_cl_edi_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:54 +msgid "Includes all technical and functional requirements to generate delivery guides via web service based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:58 +msgid "Includes all technical and functional requirements to generate delivery guides online based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:62 -msgid "Fiscal Information" +msgid "Odoo automatically installs the appropriate package for the company according to the country selected at the creation of the database." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:64 -msgid "Fill in the fiscal information for your company according to the SII register, follow the instructions on each section." +msgid "The *Chile - E-Invoicing Delivery Guide* module depends on the *Inventory* application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Chilean company fiscal data." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:67 +msgid "All features are only available if the company already completed the `SII Sistema de FacturaciĆ³n de Mercado `_ certification process." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:72 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 -msgid "Electronic Invoice Data" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:41 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:41 +msgid "Company information" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:74 -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." +msgid "Navigate to :menuselection:`Settings --> Companies: Update Info` and ensure the following company information is up-to-date and correctly filled in:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Chilean edi environment settings." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:77 +msgid ":guilabel:`Company Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 +msgid ":guilabel:`Address`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:80 +msgid ":guilabel:`Street`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:81 +msgid ":guilabel:`City`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:82 +msgid ":guilabel:`State`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:83 -msgid "Configure DTE Incoming email server" +msgid ":guilabel:`ZIP`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:85 -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:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:84 +msgid ":guilabel:`Country`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:86 +msgid ":guilabel:`Tax ID`: enter the identification number for the selected :ref:`Taxpayer Type `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:88 +msgid ":guilabel:`Activity Names`: select up to four activity codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:89 +msgid ":guilabel:`Company Activity Description`: enter a short description of the company's activity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:92 +msgid "Accounting settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:94 +msgid "Next, navigate to :menuselection:`Accounting --> Configuration --> Settings --> Chilean Localization` and follow the instructions to configure the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:97 +msgid ":ref:`Fiscal information `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:98 +msgid ":ref:`Electronic invoice data `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:99 +msgid ":ref:`DTE incoming email server `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:100 +msgid ":ref:`Signature certificates `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:105 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 +msgid "Fiscal information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:107 +msgid "Configure the following :guilabel:`Tax payer information`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:109 +msgid ":guilabel:`Taxpayer Type` by selecting the taxpayer type that applies:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:111 +msgid ":guilabel:`VAT Affected (1st Category)`: for invoices that charge taxes to customers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:112 +msgid ":guilabel:`Fees Receipt Issuer (2nd Category)`: for suppliers who issue fees receipt (Boleta)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:113 +msgid ":guilabel:`End consumer`: only issues receipts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:114 +msgid ":guilabel:`Foreigner`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:116 +msgid ":guilabel:`SII Office`: select your company's :abbr:`SII (Servicio de Impuestos Internos)` regional office" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 +msgid "Electronic invoice data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:124 +msgid "Select your :guilabel:`SII Web Services` environment:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 +msgid ":guilabel:`SII - Test`: for test databases using test :abbr:`CAFs (Folio Authorization Code)` obtained from the :abbr:`SII (Servicio de Impuestos Internos)`. In this mode, the direct connection flows can be tested, with the files being sent to the :abbr:`SII (Servicio de Impuestos Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:130 +msgid ":guilabel:`SII - Production`: for production databases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:131 +msgid ":guilabel:`SII - Demo Mode`: files are created and accepted automatically in demo mode but are **not** sent to the :abbr:`SII (Servicio de Impuestos Internos)`. For this reason, rejection errors or *Accepted with Objections* will not appear in this mode. Every internal validation can be tested in demo mode. Avoid selecting this option in a production database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:136 +msgid "Then, enter the :guilabel:`Legal Electronic Invoicing Data`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:138 +msgid ":guilabel:`SII Resolution NĀ°`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:139 +msgid ":guilabel:`SII Resolution Date`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Required information for electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:148 +msgid "DTE incoming email server" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:150 +msgid "The :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` :guilabel:`Email Box Electronic Invoicing` can be defined to receive your customers' claim and acceptance emails. Enabling this option from :menuselection:`Accounting --> Configuration --> Settings --> Chilean Localization` is necessary if you want to use *Email Box Electronic Invoicing* as the :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` incoming email server." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 +msgid "In order to receive your SII documents, it's necessary to set up your own email server. More information on how to do this can be found in this documentation: :doc:`../../general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 +msgid "Begin by clicking :guilabel:`Configure DTE Incoming Email`, then click :guilabel:`New` to add a server and fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 +msgid ":guilabel:`Name`: give the server a name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:165 +msgid ":guilabel:`Server Type`: select the server type used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:167 +msgid ":guilabel:`IMAP Server`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:168 +msgid ":guilabel:`POP Server`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:169 +msgid ":guilabel:`Local Server`: uses a local script to fetch emails and create new records. The script can be found in the :guilabel:`Configuration` section with this option selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:171 +msgid ":guilabel:`Gmail OAuth Authentication`: requires your Gmail API credentials to be configured in the general settings. A direct link to the configuration can be found in the :guilabel:`Login Information` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:175 +msgid ":guilabel:`DTE Server`: enable this option. By checking this option, this email account will be used to receive the electronic invoices from the suppliers, and communications from the :abbr:`SII (Servicio de Impuestos Internos)` regarding the electronic invoices issued. In this case, this email should match both emails declared on the :abbr:`SII (Servicio de Impuestos Internos)` site in the section: *ACTUALIZACION DE DATOS DEL CONTRIBUYENTE*, *Mail Contacto SII* and *Mail Contacto Empresas*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 +msgid "In the :guilabel:`Server & Login` tab (for IMAP and POP servers):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 +msgid ":guilabel:`Server Name`: enter the hostname or IP of the server." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:185 +msgid ":guilabel:`Port`: enter the server port." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:186 +msgid ":guilabel:`SSL/TLS`: enable this option if connections are encrypted using the SSL/TLS protocol." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:187 +msgid ":guilabel:`Username`: enter the server login username." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:188 +msgid ":guilabel:`Password`: enter the server login password." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Incoming email server configuration for Chilean DTE." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:93 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:195 +msgid "Before going live, it is recommended to archive or remove all emails related to vendor bills that are not required to be processed in Odoo from your inbox." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:97 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:201 #: ../../content/applications/finance/fiscal_localizations/peru.rst:219 msgid "Certificate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:99 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:203 +msgid "A digital certificate in `.pfx` format is required to generate the electronic invoice signature. To add one, click :guilabel:`Configure Signature Certificates` under the :guilabel:`Signature Certificates` section. Then, click :guilabel:`New` to configure the certificate:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Digital certificate access." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:207 +msgid ":guilabel:`Certificate Key`: click :guilabel:`Upload your file` and select the `.pfx` file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 +msgid ":guilabel:`Certificate Passkey`: enter the file's passphrase." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:209 +msgid ":guilabel:`Subject Serial Number`: depending on the certificate format, the field might not be automatically populated. In that case, enter the certificate's legal representative :abbr:`RUT (Rol ƚnico Tributario)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:212 +msgid ":guilabel:`Certificate Owner`: select one if you need to restrict the certificate for a specific user. Leave the field empty to share it with all billing users." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Digital certificate configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:110 -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 "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:115 -msgid "In some cases, depending on the certificate format, it is possible that the field Subject Serial Number is not loaded automatically. If this is the case, you can manually edit this field by filling it with the Certificate's legal representative RUT." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:120 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:870 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:556 -msgid "Financial Reports" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 -msgid "The report Propuesta F29 requires two values that need to be defined as part of the company configuration:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Fiscal reports parameters." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:130 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:533 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:220 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:565 #: ../../content/applications/finance/fiscal_localizations/peru.rst:230 msgid "Multicurrency" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:132 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:222 +msgid "The official currency rate is provided by `Chilean mindicador.cl `_. Navigate to :menuselection:`Accounting --> Configuration --> Settings --> Currencies: Automatic Currency Rates` to set an :guilabel:`Interval` for when the rate is automatically updated, or to select another :guilabel:`Service`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Currency reate service for Chile." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:228 +#: ../../content/applications/finance/fiscal_localizations/france.rst:306 +msgid "Partner information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:143 -msgid "The chart of accounts is installed by default as part of the set of data included in the localization module. The accounts are mapped automatically in:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:230 +msgid "Configuring partner contacts is also required to send :abbr:`SII (Servicio de Impuestos Internos)` electronic invoices. Open the :menuselection:`Contacts` app to do so and fill in the following fields on a new or existing contact form." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:146 -msgid "Taxes." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:236 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 +msgid ":guilabel:`Identification Number`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:147 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:74 -msgid "Default Account Payable." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:237 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 +msgid ":guilabel:`Taxpayer Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:148 -msgid "Default Account Receivable." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:238 +msgid ":guilabel:`Activity Description`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:149 -msgid "Transfer Accounts." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:240 +msgid "In the :guilabel:`Electronic Invoicing` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:150 -msgid "Conversion Rate." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:242 +msgid ":guilabel:`DTE Email`: enter the sender's email address for the partner." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:154 -msgid "Master Data" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:243 +msgid ":guilabel:`Delivery Guide Price`: select which price the delivery guide displays, if any." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:160 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:328 -msgid "Identification Type and VAT" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:162 -msgid "As part of the Chilean localization, the identification types defined by the SII are now available on the Partner form. This information is essential for most transactions." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Chilean identification types for partners." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:170 -msgid "TaxpayerType" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:172 -msgid "In Chile, the document type associated with customers and vendors transactions is defined based on the Taxpayer Type. This field should be defined in the partner form, when creating a customer is important you make sure this value is set:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Chilean taxpayer types for partners." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:246 +msgid "The :guilabel:`DTE Email` is the email used for sending electronic documents and must be set in the contact that will be part of an electronic document." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean electronic invoice data for partners." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:196 -msgid "As part of the localization module, the taxes are created automatically with their related financial account and configuration." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:256 +msgid "Accounting documents are categorized by :abbr:`SII (Servicio de Impuestos Internos)`-defined document types." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Chilean taxes list." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:204 -msgid "Taxes Types" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:206 -msgid "Chile has several tax types, the most common ones are:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 -msgid "VAT. Is the regular VAT and it can have several rates." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:209 -msgid "ILA (Impuesto a la Ley de Alcholes). Taxes for alcoholic drinks. It has a different rate." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:213 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:268 -msgid "Fiscal Positions" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:215 -msgid "Based on the purchase transactions, the VAT can have different affections. This will be done in Odoo using the default purchase fiscal positions." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:220 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:277 -msgid "Document Types" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:222 -msgid "In some Latin American countries, including Chile, some accounting transactions like invoices and vendor bills are classified by document types defined by the government fiscal authorities (In Chile case: SII)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:226 -msgid "The document type is essential information that needs to be displayed in the printed reports and that needs to be easily identified within the set of invoices as well of account moves." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:229 -msgid "Each document type can have a unique sequence per company. As part of the localization, the Document Type includes the country on which the document is applicable and the data is created automatically when the localization module is installed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 -msgid "The information required for the document types is included by default so the user doesn't need to fill anything on this view:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:259 +msgid "Document types are created automatically upon installation of the localization module, and can be managed by navigating to :menuselection:`Accounting --> Configuration --> Document Types`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chilean fiscal document types list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:241 -msgid "There are several document types that are inactive by default but can be activated if needed." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:267 +msgid "Several document types are inactive by default but can be activated by toggling the :guilabel:`Active` option." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:245 -msgid "Use on Invoices" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:247 -msgid "The document type on each transaction will be determined by:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:249 -msgid "The Journal related to the Invoice, identifying if the journal uses documents." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:250 -msgid "Condition applied based on the type of Issues and Receiver (ex. Type of fiscal regimen of the buyer and type of fiscal regimen of the vendor)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:263 -msgid "Sales Journals in Odoo usually represent a business unit or location, example:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:265 -msgid "Ventas Santiago." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:266 -msgid "Ventas Valparaiso." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:268 -msgid "For the retail stores is common to have one journal per POS:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:270 -msgid "Cashier 1." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:271 -msgid "Cashier 2." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:273 +msgid "The document type on each transaction is determined by:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:275 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 -#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 -msgid "Purchases" +msgid "The journal related to the invoice, identifying if the journal uses documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:277 -msgid "The transactions purchase can be managed with a single journal, but sometimes companies use more than one in order to handle some accounting transactions that are not related to vendor bills but can be easily registered using this model, for example:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:281 -msgid "Tax Payments to government." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:276 +msgid "The condition applied based on the type of issuer and recipient (e.g., the buyer or vendor's fiscal regime)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:282 -msgid "Employees payments." +msgid "*Sales journals* in Odoo usually represent a business unit or location." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:285 +msgid "Ventas Santiago." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:286 +msgid "Ventas Valparaiso." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:288 -msgid "When creating sales journals the next information must be filled in:" +msgid "For retail stores it is common to have one journal per :abbr:`POS (Point of Sale)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:290 -msgid "**Point of sale type**: If the Sales journal will be used for electronic documents, the option Online must be selected. Otherwise, if the journal is used for invoices imported from a previous system or if you are using the SII portal ā€œFacturaciĆ³n MiPymeā€œ you can use the option Manual." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:291 +msgid "Cashier 1." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:292 +msgid "Cashier 2." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:294 -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." +msgid "The *purchase* transactions can be managed with a single journal, but sometimes companies use more than one journal in order to handle some accounting transactions that are not related to vendor bills. This configuration can easily be set by using the following model." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Document type configuration on Journal." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:299 +msgid "Tax payments to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:300 +msgid "Employees payments." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:303 -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." +msgid "Create a sales journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:305 +msgid "To create a sales journal, navigate to :menuselection:`Accounting --> Configuration --> Journals`. Then, click the :guilabel:`New` button, and fill in the following required information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:308 +msgid ":guilabel:`Type`: select :guilabel:`Sale` from the drop-down menu for customer invoice journals." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:309 +msgid ":guilabel:`Point of sale type`: if the sales journal will be used for electronic documents, the option :guilabel:`Online` must be selected. Otherwise, if the journal is used for invoices imported from a previous system or if you are using the :abbr:`SII (Servicio de Impuestos Internos)` portal *FacturaciĆ³n MiPyme*, you can use the option :guilabel:`Manual`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:313 +msgid ":guilabel:`Use Documents`: check this field if the journal will use document types. This field is only applicable to purchase and sales journals that can be related to the different sets of document types available in Chile. By default, all the sales journals created will use documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:317 +msgid "Next, from the :guilabel:`Jounal Entries` tab, define the :guilabel:`Default Income Account` and :guilabel:`Dedicated Credit Note Squence` in the :guilabel:`Accounting Information` section. Configuring these fields is required for one of the debit notes :ref:`use cases `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:324 msgid "CAF" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:311 -msgid "A CAF (Folio Authorization Code) is required, for each document type that is issued to your customers, the CAF is a file the SII provides to the Emisor with the folio/sequence authorized for the electronic invoice documents." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:326 +msgid "A *folio authorization code* (CAF) is required for each document type that will be issued electronically. The :abbr:`CAF (Folio Authorization Code)` is a file the :abbr:`SII (Servicio de Impuestos Internos)` provides to the issuer with the folios/sequences authorized for the electronic invoice documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:315 -msgid "Your company can make several requests for folios and obtain several CAFs, each one associated with different ranges of folios. The CAFs are shared within all the journals, this means that you only need one active CAF per document type and it will be applied on all journals." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:331 +msgid "Your company can request multiple folios and obtain several :abbr:`CAFs (Folio Authorization Codes)` linked to different folio ranges. These :abbr:`CAFs (Folio Authorization Code)` are shared within all journals, so you only need one active :abbr:`CAF (Folio Authorization Code)` per document type, and it will be applied to all journals." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:319 -msgid "Please refer to the `SII documentation `_ to check the detail on how to acquire the CAF." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:336 +msgid "Please refer to the `SII documentation `_ to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` files." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:323 -msgid "The CAFs required by the SII are different from Production to Test (Certification mode). Make sure you have the correct CAF set depending on your environment." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:330 -msgid "Once you have the CAF files you need to associate them with a document type in Odoo, in order to add a CAF, just follow these steps:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:333 -msgid "Access to :menuselection:`Accounting --> Settings --> CAF`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:334 -msgid "Upload the file." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:335 -msgid "Save the CAF." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Steps to add a new CAF." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:341 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:340 +msgid "The :abbr:`CAFs (Folio Authorization Code)` required by the :abbr:`SII (Servicio de Impuestos Internos)` are different from production to test (certification mode). Make sure you have the correct :abbr:`CAF (Folio Authorization Code)` set depending on your environment." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:345 -msgid "In case you have used some folios in your previous system, make sure you set the next valid folio when the first transaction is created." +msgid "Upload CAF files" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:351 -msgid "Usage and Testing" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:347 +msgid "Once the :abbr:`CAF (Folio Authorization Code)` files have been acquired from the :abbr:`SII (Servicio de Impuestos Internos)` portal, they need to be uploaded in the database by navigating to :menuselection:`Accounting --> Configuration: Chilean SII --> CAFs`. Then, click the :guilabel:`New` begin the configuration. On the :abbr:`CAF (Folio Authorization Code)` form, upload your :abbr:`CAF (Folio Authorization Code)` file by clicking the :guilabel:`Upload your file` button and then click :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:354 -msgid "Electronic Invoice Workflow" +msgid "Once uploaded, the status changes to :guilabel:`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 "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:356 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:358 +msgid "The document types have to be active before uploading the :abbr:`CAF (Folio Authorization Code)` files. In case some folios have been used in the previous system, the next valid folio has to be set when the first transaction is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:365 +msgid "The chart of accounts is installed by default as part of the data set included in the localization module. The accounts are mapped automatically in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:369 +msgid "Default Account Payable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:370 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:75 +msgid "Default Account Receivable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:371 +msgid "Transfer Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:372 +msgid "Conversion Rate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:380 +msgid "As part of the localization module, taxes are created automatically with their related financial account and configuration. These taxes can be managed from :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:384 +msgid "Chile has several tax types, the most common ones are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:386 +msgid "**VAT**: the regular VAT can have several rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:387 +msgid "**ILA**: the tax for alcoholic drinks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:390 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:106 +msgid ":doc:`../accounting/taxes`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:396 +msgid "Electronic invoice workflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:398 +msgid "In the Chilean localization, the electronic invoice workflow includes customer invoice issuance and vendor bill reception. The following diagram explains how information is shared to the :abbr:`SII (Servicio de Impuestos Internos)`, customers, and vendors." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Diagram with Electronic invoice transactions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:366 -msgid "Customer invoice Emission" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:407 +msgid "Customer invoice emission" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:368 -msgid "After the partners and journals are created and configured, the invoices are created in the standard way, for Chile one of the differentiators is the document type which is selected automatically based on the Taxpayer." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:372 -msgid "You can manually change the document type if needed." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:409 +msgid "After the partners and journals are created and configured, the invoices are created in the standard way. For Chile, one of the differences is the document type that is automatically selected based on the taxpayer. The document type can be changed manually if needed on the invoice by navigating to :menuselection:`Accounting --> Customers --> Invoices`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Document type selection on invoices." +msgid "Customer invoice document type selection." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:379 -msgid "Documents type 33: Electronic Invoice must have at least one item with tax, otherwise the SII rejects the document validation." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:419 +msgid ":guilabel:`Documents type 33` electronic invoice must have at least one item with tax, otherwise the :abbr:`SII (Servicio de Impuestos Internos)` rejects the document validation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:385 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:812 -msgid "Validation and DTE Status" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:425 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 +msgid "Validation and DTE status" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:387 -msgid "When all the invoice information is filled, either manually or automatically when it's created from a sales order, proceed to validate the invoice. After the invoice is posted:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:427 +msgid "Once all invoice information is filled, either manually or automatically when generated from a sales order, validate the invoice. After the invoice is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:390 -msgid "The DTE File (Electronic Tax Document) is created automatically and added in the chatter." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:430 +msgid "The :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` file is created automatically and recorded in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:391 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:758 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 -msgid "The DTE SII status is set as: Pending to be sent." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:432 +msgid "The :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` :abbr:`SII (Servicio de Impuestos Internos)` status is set as :guilabel:`Pending` to be sent." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "DTE XML File displayed in chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:397 -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:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:439 +msgid "The :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` status is updated automatically by Odoo with a scheduled action that runs every day at night, if the response from the :abbr:`SII (Servicio de Impuestos Internos)` is needed immediately, you can do it manually as well by following the :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` status workflow:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Transition of DTE statuses." +msgid "Transition of DTE status flow." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:406 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:448 +msgid "The first step is to send the :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` to the :abbr:`SII (Servicio de Impuestos Internos)`. This can be sent manually by clicking the :guilabel:`Enviar Ahora` button. This generates a :guilabel:`SII Tack number` for the invoice, which is used to check the details sent by the :abbr:`SII (Servicio de Impuestos Internos)` via email. Then, the :guilabel:`DTE status` is updated to :guilabel:`Ask for Status`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:411 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:453 +msgid "Once the :abbr:`SII (Servicio de Impuestos Internos)` response is received, Odoo updates the :guilabel:`DTE status`. To do it manually, click on the button :guilabel:`Verify on SII`. The result can either be :guilabel:`Accepted`, :guilabel:`Accepted With Objection` or :guilabel:`Rejected`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "Identification transaction for invoice and Status update." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:420 -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:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:463 +msgid "There are intermediate statuses in the :abbr:`SII (Serviciqo de Impuestos Internos)` before acceptance or rejection. It's recommended to **NOT** continuously click :guilabel:`Verify in SII` for smooth processing." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 -msgid "Descprtion of each DTE status in the chatter." +msgid "Electronic invoice data statuses." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:428 -msgid "The final response from the SII, can take on of these values:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:471 +msgid "The final response from the :abbr:`SII (Servicio de Impuestos Internos)` can take on one of these values:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:430 -msgid "**Accepted:** Indicates the invoice information is correct, our document is now fiscally valid and it's automatically sent to the customer." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:474 +msgid ":guilabel:`Accepted`: indicates the invoice information is correct, our document is now fiscally valid and it's automatically sent to the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:433 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:476 +msgid ":guilabel:`Accepted with objections`: indicates the invoice information is correct, but a minor issue was identified, nevertheless the document is now fiscally valid and it's automatically sent to the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 -msgid "Email track once it is sent to the customer." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:479 +msgid ":guilabel:`Rejected`: indicates the invoice information is incorrect and must be corrected. Details are sent to emails you registered in the :abbr:`SII (Servicio de Impuestos Internos)`. If it is properly configured in Odoo, the details are also retrieved in the chatter once the email server is processed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:441 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:484 +msgid "If the invoice is rejected please follow these steps:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:446 -msgid "If the invoice is Rejected please follow this steps:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:486 +msgid "Change the document to :guilabel:`Draft`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:448 -msgid "Change the document to draft." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:487 +msgid "Make the required corrections based on the message received from the :abbr:`SII (Servicio de Impuestos Internos)` in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:449 -msgid "Make the required corrections based on the message received from the SII." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:450 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:489 msgid "Post the invoice again." msgstr "" @@ -14227,520 +14823,607 @@ msgstr "" msgid "Message when an invoice is rejected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:458 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:496 msgid "Crossed references" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:460 -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:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:498 +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 :guilabel:`Cross-Reference` tab. This tab is commonly used for credit or debit notes, however, in some cases it can be used for customer invoices, as well. In the case of the credit and debit notes, they are set automatically by Odoo." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Invoice tab with origin document number and data." +msgid "Crossed referenced document(s)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:470 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:453 -msgid "Invoice PDF Report" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:510 +#: ../../content/applications/finance/fiscal_localizations/india.rst:133 +#: ../../content/applications/finance/fiscal_localizations/india.rst:271 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 +msgid "Invoice PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:472 -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:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:512 +msgid "Once the invoice is accepted and validated by the :abbr:`SII (Servicio de Impuestos Internos)` and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Barcode and fiscal elements in the invoice report." +msgid "SII Validation fiscal elements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:480 -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``." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:521 +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: :command:`pip install pdf417gen`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:484 -msgid "Commercial Validation" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 +msgid "Commercial validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:486 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 msgid "Once the invoice has been sent to the customer:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:488 -msgid "DTE partner status changes to ā€œSentā€." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 +msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:489 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:531 msgid "The customer must send a reception confirmation email." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:490 -msgid "Subsequently, if all the commercial terms and invoice data are correct, they will send the Acceptance confirmation, otherwise they send a Claim." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 +msgid "Subsequently, if commercial terms and invoice data are correct, an acceptance confirmation is sent; otherwise, a claim is sent." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:492 -msgid "The field DTE acceptation status is updated automatically." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:534 +msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Message with the commercial acceptance from the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:500 -msgid "Processed for Claimed invoices" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:541 +msgid "Processed for claimed invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:502 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:543 +msgid "Once the invoice has been accepted by the :abbr:`SII (Servicio de Impuestos Internos)`, **it can not be cancelled in Odoo**. In case you get a claim for your customer, the correct way to proceed is with a credit note to either cancel the invoice or correct it. Please refer to the :ref:`chile/credit-notes` section for more details." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Invoice Comercial status updated to Claimed." +msgid "Invoice Commercial status updated to claimed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:511 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:429 -msgid "Common Errors" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:553 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 +msgid "Common errors" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:513 -msgid "There are multiple reasons behind a rejection from the SII, but these are some of the common errors you might have and which is the related solution." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:555 +msgid "There are multiple reasons behind a rejection from the :abbr:`SII (Servicio de Impuestos Internos)`, but these are some of the common errors you might have and how to solve them:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:516 -msgid "Error: ``RECHAZO- DTE Sin Comuna Origen.``" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `RECHAZO- DTE Sin Comuna Origen`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:518 -msgid "*Hint:* Make sure the Company Address is properly filled including the State and City." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Hint:** make sure the company address is properly filled including the state and city." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:520 -msgid "Error en Monto: ``- IVA debe declararse.``" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `en Monto - IVA debe declararse`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:522 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 -msgid "*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Hint:** the invoice lines should include one VAT tax, make sure you add one on each invoice line." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 -msgid "Error: ``Rut No Autorizado a Firmar.``" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Rut No Autorizado a Firmar`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 -msgid "Error: ``Fecha/NĆŗmero Resolucion Invalido RECHAZO- CAF Vencido : (Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses.``" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Hint:** the :abbr:`RUT (Rol ƚnico Tributario)` entered is not allowed to invoice electronically, make sure the company :abbr:`RUT (Rol ƚnico Tributario)` is correct and is valid in the :abbr:`SII (Servicio de Impuestos Internos)` to invoice electronically." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:531 -msgid "*Hint:* Try to add a new CAF related to this document as the one you're using is expired." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Fecha/NĆŗmero Resolucion Invalido RECHAZO- CAF Vencido : (Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:533 -msgid "Error: ``Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).``" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Hint:** try to add a new CAF related to this document as the one you're using is expired." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:536 -msgid "*Hint:* Make sure the field Document Type and VAT are set either in the Customer and in the main company." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:539 -msgid "GLOSA: ``Usuario sin permiso de envio.``" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Hint:** Make sure the field :guilabel:`Document Type` and :guilabel:`VAT` are set in the customer and in the main company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:541 -msgid "*Hint:* This error indicates that most likely, your company has not passed the `Certification process `_ in the SII - Sistema de FacturaciĆ³n de Mercado. If this is the case, please contact your Account Manager or Customer Support as this certification is not part of the the Odoo services, but we can give you some alternatives." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Usuario sin permiso de envio.`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:550 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:558 -msgid "Credit Notes" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Hint:** this error indicates that most likely, your company has not passed the `Certification process `_ in the :abbr:`SII (Servicio de Impuestos Internos)` - Sistema de FacturaciĆ³n de Mercado. If this is the case, please contact your Account Manager or Customer Support as this certification is not part of the Odoo services, but we can give you some alternatives. If you already passed the certification process, this error appears when a user different from the owner of the certificate is trying to send :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` files to the :abbr:`SII (Servicio de Impuestos Internos)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:552 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `CARATULA`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Hint:** there are just five reasons why this error could show up and all of them are related to the *Caratula* section of the XML:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 +msgid "The company's :abbr:`RUT (Rol ƚnico Tributario)` number is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:588 +msgid "The certificate owner :abbr:`RUT (Rol ƚnico Tributario)` number is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 +msgid "The :abbr:`SII's (Servicio de Impuestos Internos)` :abbr:`RUT (Rol ƚnico Tributario)` number (this should be correct by default) is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:591 +msgid "The resolution date is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:592 +msgid "The resolution number is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:597 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 +msgid "Credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:599 +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 :abbr:`CAF (Folio Authorization Code)` file is required for the credit note, which is identified as :guilabel:`Document Type` :guilabel:`61` in the :abbr:`SII (Servicio de Impuestos Internos)`. Please refer to the :ref:`CAF section ` for more information on the process to load the :abbr:`CAF (Folio Authorization Code)` on each document type." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Creation of CAF for Credit notes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:562 -msgid "Refer to the :ref:`CAF section ` where we described the process to load the CAF on each document type." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:611 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:667 +msgid "Use cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:566 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:618 -msgid "Use Cases" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:614 +msgid "Cancel referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:569 -msgid "Cancel Referenced document" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:571 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:616 +msgid "In case you need to cancel or invalidate an invoice, navigate to :menuselection:`Accounting --> Customers --> Invoices` and select the desired invoice. Then, use the button :guilabel:`Add Credit Note` and select :guilabel:`Full Refund`, in this case the :abbr:`SII (Servicio de Impuestos Internos)` reference code is automatically set to :guilabel:`Anula Documento de referencia`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Full invoice refund with SII reference code 1." +msgid "Credit note canceling the referenced document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:579 -msgid "Corrects Referenced Document Text" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:626 +msgid "Correct referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:581 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:628 +msgid "If a correction in the invoice information is required, for example the street name on the original invoice is wrong, then use the button :guilabel:`Add Credit Note`, select :guilabel:`Partial Refund` and select the option :guilabel:`Only Text Correction`. In this case the :guilabel:`SII Reference Code` field is automatically set to :guilabel:`Corrects Referenced Document Text`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Partial refund to correct text including the corrected value." +msgid "Credit note correcting referenced document text." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 -msgid "Odoo creates a Credit Note with the corrected text in an invoice and price 0." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:637 +msgid "Odoo creates a credit note with the corrected text in an invoice and :guilabel:`Price` `0.00`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Credit note with the corrected value on the invoice lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:596 -msgid "It's important to define the default credit account in the Sales journal as it is taken for this use case in specific." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:644 +msgid "Make sure to define the :guilabel:`Default Credit Account` in the sales journal specifically for this use case." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:600 -msgid "Corrects Referenced Document Amount" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:648 +msgid "Corrects referenced document amount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:602 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:650 +msgid "When a correction on the amounts is required, use the button :guilabel:`Add Credit note` and select :guilabel:`Partial Refund`. In this case the :guilabel:`SII Reference Code` is automatically set to :guilabel:`Corrige el monto del Documento de Referencia`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Credit note for partial refund to correct amounts, using the SII reference code 3." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:611 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:585 -msgid "Debit Notes" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:613 -msgid "As part of the Chilean localization, besides creating credit notes from an existing document you can also create debit Notes. For this just use the button ā€œAdd Debit Noteā€. The two main use cases for debit notes are detailed below." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:621 -msgid "Add debt on Invoices" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:623 -msgid "The most common use case for debit notes is to increase the value of an existing invoice, you need to select option 3 in the field Reference code SII:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Debit note for partial refund to crrect amounts, using the SII reference code 3." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:631 -msgid "In this case Odoo automatically includes the source invoice in the cross reference section:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Invoice data on crossed reference section for debit notes." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:638 -msgid "Cancel Credit Notes" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:640 -msgid "In Chile the debits notes are used to cancel a validated Credit Note, in this case just select the button Add debit note and select the first option in the wizard: *1: Anula Documentos de referencia.*" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Creating a debit note to cancel a credit note with the SII code reference 1." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:649 -msgid "Vendor Bills" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:651 -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 "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:654 -msgid "Automatically receive the vendor bills DTE and create the vendor bill based on this information." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:655 -msgid "Automatically Send the reception acknowledgement to your vendor." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:656 -msgid "Accept or Claim the document and send this status to your vendor." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/chile.rst:659 -msgid "Reception" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 +msgid "Debit notes" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:661 -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" +msgid "In Chilean localization, debit notes, in addition to credit notes, can be created using the :guilabel:`Add Debit Note` button, with two main use cases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:670 +msgid "Add debt on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:672 +msgid "The primary use case for debit notes is to increase the value of an existing invoice. To do so, select option :guilabel:`3. Corrige el monto del Documento de Referencia` for the :guilabel:`Reference Code SII` field." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Messages recorded in the chatter with the reception notification for the vendor." +msgid "Debit note correcting referenced document amount." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:671 -msgid "Acceptation" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:673 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:680 +msgid "In this case Odoo automatically includes the :guilabel:`Source Invoice` in the :guilabel:`Cross Reference` tab." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Acceptance button in vendor bills to inform vendor the document is comercially accepted." +msgid "Automatic reference to invoice in a debit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:682 -msgid "Claim" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:688 +msgid "You can only add debit notes to an invoice already accepted by the SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:684 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:691 +msgid "Cancel credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:693 +msgid "In Chile, debits notes are used to cancel a valid credit note. To do this, click the :guilabel:`Add Debit Note` button and select the :guilabel:`1: Anula Documentos de referencia` option for the :guilabel:`Reference Code SII` field." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Claim button in vendor bills to inform the vendor all the document is comercially rejected." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:692 -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 "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:697 -msgid "Delivery Guide" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:699 -msgid "To install the Delivery Guide module, go to :menuselection:`Apps` and search for :guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery Guide`." +msgid "Debit note to cancel the referenced document (credit note)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:704 -msgid "*Chile - E-Invoicing Delivery Guide* has a dependency with *Chile - FacturaciĆ³n ElectrĆ³nica*. Odoo will install the dependency automatically when the Delivery Guide module is installed." +msgid "As part of the Chilean localization, you can configure your incoming email server to match the one you have registered in the :abbr:`SII (Servicio de Impuestos Internos)` in order to:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:707 -msgid "The Delivery Guide module includes sending the DTE to SII and the stamp in PDF reports for deliveries." +msgid "Automatically receive the vendor bills :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` and create the vendor bill based on this information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Install Delivery Guide Module" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:709 +msgid "Automatically send the reception acknowledgement to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:714 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:710 +msgid "Accept or claim the document and send this status to your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:713 +msgid "Reception" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:715 +msgid "As soon as the vendor email with the attached :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` is received:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 +msgid "The vendor bill maps all the information included in the XML." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:719 -msgid "Verify the following important information in the *Price for the Delivery Guide* configuration:" +msgid "An email is sent to the vendor with the reception acknowledgement." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 -msgid ":guilabel:`From Sales Order`: Delivery Guide takes the product price from the Sales Order and shows it on the document." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:720 +msgid "The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:723 -msgid ":guilabel:`From Product Template`: Odoo takes the price configured in the product template and shows it on the document." +msgid "Acceptation" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:725 -msgid ":guilabel:`No show price`: no price is shown in the Delivery Guide." +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 :guilabel:`DTE Acceptation Status` changes to :guilabel:`Accepted` and an email of acceptance is sent to the vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:727 -msgid "Electronic delivery guides are used to move stock from one place to another and they can represent sales, sampling, consignment, internal transfers, and basically any product move." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:731 -msgid "Delivery Guide from a Sales Process" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Button for accepting vendor bills." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:734 -msgid "A delivery guide should **not** be longer than one page or contain more than 60 product lines." +msgid "Claim" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:736 -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." +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 :guilabel:`Claim` button. Once this is done, the :guilabel:`DTE Acceptation Status` changes to :guilabel:`Claim` and a rejection email is sent to the vendor." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Create Delivery Guide Button" +msgid "Claim button in vendor bills to inform the vendor all the document is commercially\n" +"rejected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:743 -msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, showing the following:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:746 +msgid "If you claim a vendor bill, the status changes from :guilabel:`Draft` to :guilabel:`Cancel` automatically. Considering this as best practice, all the claimed documents should be canceled as they won't be valid for your accounting records." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "An example sequence error when creating a Delivery Guide in Odoo" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 +msgid "Delivery guide" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:750 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:753 +msgid "To install the :guilabel:`Delivery Guide` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery Guide`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:755 -msgid "After the Delivery Guide is created:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:758 +msgid ":guilabel:`Chile - E-Invoicing Delivery Guide` has a dependency with :guilabel:`Chile - FacturaciĆ³n ElectrĆ³nica`. Odoo will install the dependency automatically when the :guilabel:`Delivery Guide` module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:757 -msgid "The DTE file (Electronic Tax Document) is automatically created and added to the chatter." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:762 +msgid "The *Delivery Guide* module includes the ability to send the :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` to :abbr:`SII (Servicio de Impuestos Internos)` and the stamp in PDF reports for deliveries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "DTE Status in SII and creation of DTE/XML" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:766 +msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), delivery guides need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:828 -msgid "The DTE Status is automatically updated by Odoo with a scheduled action that runs every day at night. To get a response from the SII immediately, press the :guilabel:`Send now to SII` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:767 -msgid "Once the Delivery Guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Printing Delivery Guide PDF" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:772 +msgid "Verify the following important information in the :guilabel:`Price for the Delivery Guide` configuration:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:775 -msgid "Electronic Receipt" +msgid ":guilabel:`From Sales Order`: delivery guide takes the product price from the sales order and shows it on the document." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:777 -msgid "To install the Electronic Receipt module, go to :menuselection:`Apps` and search for :guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." +msgid ":guilabel:`From Product Template`: Odoo takes the price configured in the product template and shows it on the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:782 -msgid "*Chile - Electronic Receipt* has a dependency with *Chile - FacturaciĆ³n ElectrĆ³nica*. Odoo will install the dependency automatically when the E-invoicing Delivery Guide module is installed." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +msgid ":guilabel:`No show price`: no price is shown in the delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 +msgid "Electronic delivery guides are used to move stock from one place to another and they can represent sales, sampling, consignment, internal transfers, and basically any product move." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:785 -msgid "This module contains the electronic receipt and daily sales report, which are automatically sent to SII." +msgid "Delivery guide from a sales process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 +msgid "A delivery guide should **not** be longer than one page or contain more than 60 product lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:790 +msgid "When a sales order is created and confirmed, a delivery order is generated. After validating the delivery order, the option to create a delivery guide is activated." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Install Electronic Receipt module" +msgid "Create Delivery Guide button on a sales process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:792 -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." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:798 +msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, stating the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:797 -msgid "Electronic Receipts are useful when clients do not need an Electronic Invoice. By default, there is a partner in the database called *Anonymous Final Consumer* with a generic RUT 66666666-6 and taxpayer type of *Final Consumer*. This partner can be used for Electronic Receipts or a new record may be created for the same purpose." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:801 +msgid "`No se encontrĆ³ una secuencia para la guĆ­a de despacho. Por favor, establezca el primer nĆŗmero dentro del campo nĆŗmero para la guĆ­a de despacho`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:802 -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:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "First Delivery Guide number warning message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Select type of Document: (39) Boleta ElectrĆ³nica" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:808 +msgid "This warning message means the user needs to indicate the next sequence number Odoo has to take to generate the delivery guide (e.g. next available :abbr:`CAF (Folio Authorization Code)` number), and only happens the first time a delivery guide is created in Odoo. After the first document has been correctly generated, Odoo takes the next available number in the :abbr:`CAF (Folio Authorization Code)` file to generate the following delivery guide." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:814 -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." +msgid "After the delivery guide is created:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:819 -msgid "After the receipt is posted:" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 +msgid "The :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` file (Electronic Tax Document) is automatically created and added to the :guilabel:`chatter`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:821 -msgid "The DTE file (Electronic Tax Document) is created automatically and added to the chatter." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:818 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:888 +msgid "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "DTE status in SII and creation of DTE/XML" +msgid "Chatter notes of Delivery Guide creation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:831 -msgid "Please refer to the :ref:`DTE Workflow ` for Electronic Invoices as the workflow for Electronic Receipt follows the same process." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:824 +msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:828 +msgid "Once the delivery guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Printing Delivery Guide PDF." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:835 -msgid "Daily Sales Report" +msgid "Delivery guide will have fiscal elements that indicate that the document is fiscally valid when printed (if hosted in *Odoo SH* or on *On-premise* remember to manually add the :guilabel:`pdf417gen` library mentioned in the :ref:`Invoice PDF report section `)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:837 -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`." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:841 +msgid "Electronic receipt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:843 +msgid "To install the :guilabel:`Electronic Receipt` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:848 +msgid ":guilabel:`Chile - Electronic Receipt` has a dependency with :guilabel:`Chile - FacturaciĆ³n ElectrĆ³nica`. Odoo will install the dependency automatically when the :guilabel:`E-invoicing Delivery Guide` module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:852 +msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic receipts need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:858 +msgid "Electronic receipts are useful when clients do not need an electronic invoice. By default, there is a partner in the database called :guilabel:`Anonymous Final Consumer` with a generic :abbr:`RUT (Rol ƚnico Tributario)` `66666666-6` and taxpayer type of :guilabel:`Final Consumer`. This partner can be used for electronic receipts or a new record may be created for the same purpose." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Find Electronic Receipts in the Reports menu, under Daily Sales Reports" +msgid "Electronic Receipt module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:845 -msgid "A list of daily reports is displayed with all daily DTE sent to SII." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:867 +msgid "Although electronic receipts should be used for final consumers with a generic :abbr:`RUT (Rol ƚnico Tributario)`, 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 in the invoice form:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "List of Daily Reports" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:851 -msgid "If no Electronic Receipt was made on a particular day, the report is sent but it will not have any receipts in it. The report will also have an answer from the SII if it was accepted or rejected (depending on the company's certificate and validated receipts)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Daily Sales Book example" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:860 -msgid "For Chilean localization, note that the feature tax included in the price is *not* supported for the Electronic Receipt." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:863 -msgid "If a Daily Sales Report has already been created for a specific day in another system, the daily report in Odoo will be rejected due to the sequence number used. If that is the case, the user has to manually click on :guilabel:`Retry` in order for a new sequence number to be generated (this action is automatically done by Odoo). Afterwards, users can manually verify report status with SII or wait for Odoo to update status later at night." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:873 -msgid "Balance Tributario de 8 Columnas" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 -msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time, so that a real and complete knowledge of the status of a company." +msgid "Document type 39 for Electronic Receipts." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:879 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:895 -msgid "You can find this report in :menuselection:`Accounting --> Accounting --> Reports`" +msgid "When all of the electronic receipt information is filled, manually (or automatically) proceed to validate the receipt from the sales order. By default, :guilabel:`Electronic Invoice` is selected as the :guilabel:`Document Type`, however in order to validate the receipt correctly, make sure to edit the :guilabel:`Document Type` and change to :guilabel:`Electronic Receipt`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Columns and data displayed in the report Balance Tributario 8 Columnas." +#: ../../content/applications/finance/fiscal_localizations/chile.rst:884 +msgid "After the receipt is posted:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:886 -msgid "Propuesta F29" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:888 -msgid "The form F29 is a new system that the SII enabled to taxpayers, and that replaces the Purchase and Sales Books. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 -msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the SII." +msgid "The :abbr:`DTE (Documentos Tributarios ElectrĆ³nicos)` file (Electronic Tax Document) is created automatically and added to the :guilabel:`chatter`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "Parameters to required to generate the Report Propuesta F29" +msgid "Electronic Receipts STE creation status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:894 +msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every day at night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:898 +msgid "Please refer to the :ref:`DTE Workflow ` for electronic invoices as the workflow for electronic receipt follows the same process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:902 +msgid "Electronic export of goods" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:904 +msgid "To install the :guilabel:`Electronic Exports of Goods` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Electronic Exports of Goods for Chile`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:909 +msgid ":guilabel:`Chile - Electronic Exports of Goods for Chile` has a dependency with :guilabel:`Chile - FacturaciĆ³n ElectrĆ³nica`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:912 +msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic exports of goods need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:918 +msgid "Electronic invoices for the export of goods are tax documents that are used not only for the :abbr:`SII (Servicio de Impuestos Internos)` but are also used with customs and contain the information required by it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:923 +msgid "Contact configurations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Taxpayer Type needed for the Electronic Exports of Goods module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 +msgid "Chilean customs" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:932 +msgid "When creating an electronic exports of goods invoice, these new fields in the :guilabel:`Other Info` tab are required to comply with Chilean regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Chilean customs fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:940 +msgid "PDF report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:942 +msgid "Once the invoice is accepted and validated by the :abbr:`SII (Servicio de Impuestos Internos)` and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid and a new section needed for customs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "PDF report section for the Electronic Exports of Goods PDF Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:954 +msgid "Balance tributario de 8 columnas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:956 +msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:960 +msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Balance Sheet` and selecting in the :guilabel:`Report` field the option :guilabel:`Chilean Fiscal Balance (8 Columns) (CL)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Location of the Reporte Balance Tributario de 8 Columnas." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Chilean Fiscal Balance (8 Columns)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:973 +msgid "Propuesta F29" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:975 +msgid "The form *F29* is a new system that the :abbr:`SII (Servicio de Impuestos Internos)` enabled to taxpayers, and that replaces the *Purchase and Sales Books*. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:980 +msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the :abbr:`SII (Servicio de Impuestos Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:983 +msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Tax Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta F29 (CL)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Location of the Propuesta F29 (CL) Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:990 +msgid "It is possible to set the :abbr:`PPM (Provisional Monthly Payments rate)` and the :guilabel:`Proportional Factor for the fiscal year` from the :menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:998 +msgid "Or manually in the reports by clicking on the :guilabel:`āœļø (pencil)` icon." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 +msgid "Manual PPM for the Propuesta F29 Report." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:3 @@ -14748,71 +15431,71 @@ msgid "Colombia" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:7 -msgid "Odoo's Colombian localization package provides accounting, fiscal and legal features in Colombia such as chart of accounts, taxes and electronic invoicing." +msgid "Odoo's Colombian localization package provides accounting, fiscal, and legal features for databases in Colombia ā€“ such as chart of accounts, taxes, and electronic invoicing." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:10 -msgid "In addition, we have a series of videos covering how to start from scratch, configuration, main workflows, and specific use cases." +msgid "In addition, a series of videos on the subject is also available. These videos cover how to start from scratch, set up configurations, complete common workflows, and provide in-depth looks at some specific use cases as well." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:14 -msgid "`Odoo Colombian localization videos `_." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:15 +msgid "`Smart Tutorial - Colombian Localization `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:25 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:26 msgid ":ref:`Install ` the following modules to get all the features of the Colombian localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 msgid ":guilabel:`Colombia - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 msgid "`l10n_co`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 -msgid "Default :ref:`fiscal localization package `. This module adds the base accounting features for the Colombian localization: chart of accounts, taxes, withholdings, identification document type." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:40 -msgid ":guilabel:`Colombian - Accounting Reports`" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:38 +msgid "Default :ref:`fiscal localization package `. This module adds the base accounting features for the Colombian localization: chart of accounts, taxes, withholdings, and identification document type." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:41 -msgid "`l10n_co_reports`" +msgid ":guilabel:`Colombian - Accounting Reports`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:42 -msgid "Includes accounting reports for sending certifications to suppliers for withholdings applied." +msgid "`l10n_co_reports`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:43 -msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" +msgid "Includes accounting reports for sending certifications to suppliers for withholdings applied." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:44 -msgid "`l10n_co_edi`" +msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:45 -msgid "This module includes the features that are required for the integration with Carvajal and generates the electronic invoices and support document related to the vendor bills based on |DIAN| regulations." +msgid "`l10n_co_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:48 -msgid ":guilabel:`Colombian - Point of Sale`" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:46 +msgid "This module includes the features required for integration with Carvajal, and generates the electronic invoices and support documents related to the vendor bills, based on |DIAN| regulations." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:49 -msgid "`l10n_co_pos`" +msgid ":guilabel:`Colombian - Point of Sale`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:50 -msgid "Includes Point of Sale Receipt for Colombian Localization." +msgid "`l10n_co_pos`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:53 -msgid "When a database is created from scratch selecting :guilabel:`Colombia` as the country, Odoo automatically installs the base modules *Colombia - Accounting* and *Colombia - Accounting Reports*." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:51 +msgid "Includes Point of Sale receipts for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:54 +msgid "When `Colombia` is selected for a company's :guilabel:`Fiscal Localization`, Odoo automatically installs certain modules." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:58 @@ -14820,246 +15503,348 @@ msgid "Company configuration" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:60 -msgid "To configure your company information, go to the :menuselection:`Contacts` app and search for your company. Alternatively, activate :ref:`developer mode ` and navigate to :menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact form to configure the following information:" +msgid "To configure your company information, go to the :menuselection:`Contacts` app, and search for your company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:65 -msgid ":guilabel:`Company Name`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:66 -msgid ":guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and :guilabel:`Zip Code`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:63 +msgid "Alternatively, activate :ref:`developer mode ` and navigate to :menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact form and configure the following information:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:67 -msgid ":guilabel:`Tax ID`: When it is a `NIT`, it must have the *verification digit* at the end of the ID followed by a hyphen (`-`)." +msgid ":guilabel:`Company Name`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:70 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:68 +msgid ":guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and :guilabel:`ZIP` code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:69 +msgid ":guilabel:`Identification Number`: Select the :guilabel:`Identification Type` (`NIT`, `CĆ©dula de CiudadanĆ­a`, `Registro Civil`, etc.). When the :guilabel:`Identification Type` is `NIT`, the :guilabel:`Identification Number` **must** have the *verification digit* at the end of the ID prefixed by a hyphen (`-`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:74 msgid "Next, configure the :guilabel:`Fiscal Information` in the :guilabel:`Sales & Purchase` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:72 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:147 -msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (:guilabel:`O-13` Gran Contribuyente, :guilabel:`O-15` Autorretenedor, :guilabel:`O-23` Agente de retenciĆ³n IVA, :guilabel:`O-47` Regimen de tributaciĆ³n simple, :guilabel:`R-99-PN` No Aplica)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:75 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:150 -msgid ":guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be selected." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:77 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:152 -msgid ":guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (:guilabel:`IVA`, :guilabel:`INC`, :guilabel:`IVA e INC`, :guilabel:`No Aplica`)" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:76 +msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retenciĆ³n IVA, `O-47` Regimen de tributaciĆ³n simple, `R-99-PN` No Aplica)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:79 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:154 -msgid ":guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be displayed in the invoice." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:173 +msgid ":guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:81 +msgid ":guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (`IVA`, `INC`, `IVA e INC`, or `No Aplica`)" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:83 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:177 +msgid ":guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be displayed in the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:87 msgid "Carjaval credentials configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:85 -msgid "Once the modules installed, the user credentials must be configured in order to connect with Carvajal Web Service. Navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the required configuration information provided by Carvajal:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:90 -msgid ":guilabel:`Username` and :guilabel:`Password`: Correspond to the username and password provided by Carvajal to the company." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:92 -msgid ":guilabel:`Company Registry`: Company's NIT number *without* the verification code." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:93 -msgid ":guilabel:`Account ID`: Company ID followed by `_01`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:89 +msgid "Once the modules are installed, the user credentials **must** be configured, in order to connect with Carvajal Web Service. To do so, navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the required configuration information provided by Carvajal:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:94 -msgid ":guilabel:`Colombia Template Code`: Select one of the two available templates (:guilabel:`CGEN03` or :guilabel:`CGNE04`) to be used in the PDF format of the electronic invoice." +msgid ":guilabel:`Username` and :guilabel:`Password`: Username and password (provided by Carvajal) to the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:96 +msgid ":guilabel:`Company Registry`: Company's NIT number *without* the verification code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:97 +msgid ":guilabel:`Account ID`: Company's NIT number followed by `_01`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:98 +msgid ":guilabel:`Colombia Template Code`: Select one of the two available templates (`CGEN03` or `CGNE04`) to be used in the PDF format of the electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 +msgid "Enable the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:103 +msgid "Once Odoo and Carvajal are fully configured and ready for production, deactivate the :guilabel:`Test mode` checkbox to use the production database." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "Configure credentials for Carvajal web service in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 -msgid "Check the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment. Once Odoo and Carvajal are fully configured and ready for production, uncheck the :guilabel:`Test mode` checkbox to use the production database." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:106 -msgid ":guilabel:`Test mode` must be used **only** on replicated databases, **not** the production environment." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:110 -msgid "Report data configuration" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:112 -msgid "Report data can be defined for the fiscal section and bank information of the PDF as part of the configurable information sent in the XML." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:111 +msgid ":guilabel:`Test mode` must **only** be used on duplicated databases, **not** the production environment." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:115 -msgid "Navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section." +msgid "Report data configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:121 -msgid "Master data configuration" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:117 +msgid "Report data can be defined for the fiscal section and bank information of the PDF as part of the configurable information sent in the XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:120 +msgid "Navigate to :menuselection:`Accounting --> Configuration --> Settings`, and scroll to the :guilabel:`Colombian Electronic Invoicing` section, in order to find the :guilabel:`Report Configuration` fields. Here the header information for each report type can be configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:124 +msgid ":guilabel:`Gran Contribuyente`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:125 +msgid ":guilabel:`Tipo de RĆ©gimen`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:126 +msgid ":guilabel:`Retenedores de IVA`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:127 -msgid "Identification information" +msgid ":guilabel:`Autorretenedores`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:128 +msgid ":guilabel:`ResoluciĆ³n Aplicable`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:129 -msgid "Document types defined by the |DIAN| are available on the partner form as part of the Colombian localization. Colombian partners must have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document Type` set." +msgid ":guilabel:`Actividad EconĆ³mica`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:134 -msgid "When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be configured in Odoo, including the *verification digit*; Odoo splits this number when the data to is sent to the third party." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:130 +msgid ":guilabel:`Bank Information`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:139 -msgid "Fiscal information" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:135 +msgid "Master data configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:141 -msgid "The partner's responsibility codes (section 53 in the RUT document) are included as part of the electronic invoicing module, as it is required by the |DIAN|." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:140 +msgid "Partner contacts can be created in the *Contacts* app. To do so, navigate to :menuselection:`Contacts`, and click the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:144 -msgid "The required fields can be found under :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information`:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:143 +msgid "Then, name the contact, and using the radio buttons, select the contact type, either :guilabel:`Individual` or :guilabel:`Company`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:160 -msgid "In addition to adding general information (in the :guilabel:`General Information` tab) on the product form, either the :guilabel:`UNSPSC Category`, :guilabel:`Barcode`, or :guilabel:`Internal Reference` field must also be configured." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:146 +msgid "Complete the full :guilabel:`Address`, including the :guilabel:`City`, :guilabel:`State`, and :guilabel:`ZIP` code. Then, complete the identification and fiscal information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:150 +msgid "Identification information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:152 +msgid "Identification types, defined by the |DIAN|, are available on the partner form, as part of the Colombian localization. Colombian partners **must** have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document Type` set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:157 +msgid "When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be configured in Odoo, including the *verification digit at the end of the ID, prefixed by a hyphen (`-`)*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:164 +msgid "The partner's responsibility codes (section 53 in the :abbr:`RUT (Registro Ćŗnico tributario)` document) are included as part of the electronic invoicing module, as it is required by the |DIAN|." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:167 -msgid "If sales transactions include products with taxes, the :guilabel:`Value Type` field in the :guilabel:`Advanced Options` tab needs to be configured per tax. To do so, go to :menuselection:`Accounting --> Configuration --> Taxes`, and select the related tax." +msgid "The required fields can be found under :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information section`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:171 -msgid "Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used to display taxes in the invoice PDF correctly." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:170 +msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retenciĆ³n IVA, `O-47` Regimen de tributaciĆ³n simple, or `R-99-PN` No Aplica)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:175 +msgid ":guilabel:`Fiscal Regimen`: Select the tribute name for the company (`IVA`, `INC`, `IVA e INC`, or `No Aplica`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:183 +msgid "To manage products, navigate to :menuselection:`Accounting --> Customers --> Products`, then click on a product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 +msgid "When adding general information on the product form, it is required that either the :guilabel:`UNSPSC Category` (:guilabel:`Accounting` tab), or :guilabel:`Internal Reference` (:guilabel:`General Information` tab) field is configured. Be sure to :guilabel:`Save` the product once configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:194 +msgid "To create or modify taxes, go to :menuselection:`Accounting --> Configuration --> Taxes`, and select the related tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:197 +msgid "If sales transactions include products with taxes, the :guilabel:`Value Type` field in the :guilabel:`Advanced Options` tab needs to be configured per tax. Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used to display taxes correctly in the invoice PDF." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:178 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:209 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:88 msgid "Sales journals" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:182 -msgid "Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution, the sales journals related to the invoice documents must be updated in Odoo. To do so, navigate to :menuselection:`Accounting --> Configuration --> Journals`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:211 +msgid "Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution, the sales journals related to the invoice documents **must** be updated in Odoo. To do so, navigate to :menuselection:`Accounting --> Configuration --> Journals`, and select an existing sales journal, or create a new one with the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 -msgid "Configure the following data in the :guilabel:`Advanced Settings` tab:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:216 +msgid "On the sales journal form, input the :guilabel:`Journal Name`, :guilabel:`Type`, and set a unique :guilabel:`Short Code` in the :guilabel:`Journals Entries` tab. Then, configure the following data in the :guilabel:`Advanced Settings` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:188 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:220 msgid ":guilabel:`Electronic invoicing`: Enable :guilabel:`UBL 2.1 (Colombia)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:189 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:221 msgid ":guilabel:`Invoicing Resolution`: Resolution number issued by |DIAN| to the company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:190 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:222 msgid ":guilabel:`Resolution Date`: Initial effective date of the resolution." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:191 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:223 msgid ":guilabel:`Resolution end date`: End date of the resolution's validity." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:224 msgid ":guilabel:`Range of Numbering (minimum)`: First authorized invoice number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:193 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:225 msgid ":guilabel:`Range of Numbering (maximum)`: Last authorized invoice number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:196 -msgid "The sequence and resolution of the journal must match the one configured in Carvajal and the |DIAN|." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:228 +msgid "The sequence and resolution of the journal **must** match the one configured in Carvajal and the |DIAN|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:200 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:232 msgid "Invoice sequence" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:202 -msgid "The invoice sequence and prefix must be correctly configured when the first document is created." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:205 -msgid "Odoo automatically assigns a prefix and sequence to the following documents." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:208 -msgid "Purchase journals" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:210 -msgid "Once the |DIAN| has assigned the official sequence and prefix for the support document related to vendor bills, the purchase journals related to their supporting documents need to be updated in Odoo. The process is similar to the configuration of the :ref:`sales journals `." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:217 -msgid "The :doc:`chart of accounts ` is installed by default as part of the localization module, the accounts are mapped automatically in taxes, default account payable, and default account receivable. The chart of accounts for Colombia is based on the PUC (Plan Unico de Cuentas)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:226 -msgid "Main workflows" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:229 -msgid "Electronic invoices" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 +msgid "The invoice sequence and prefix **must** be correctly configured when the first document is created." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:237 -msgid "The functional workflow taking place before an invoice validation does not alter the main changes introduced with the electronic invoice." +msgid "Odoo automatically assigns a prefix and sequence to the following invoices." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:240 -msgid "Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web service integration. These documents can be created from your sales order or manually. Go to :menuselection:`Accounting --> Customers --> Invoices` and configure:" +msgid "Purchase journals" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:244 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:242 +msgid "Once the |DIAN| has assigned the official sequence and prefix for the *support document* related to vendor bills, the purchase journals related to their supporting documents need to be updated in Odoo. The process is similar to the configuration of the :ref:`sales journals `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:249 +msgid "The :doc:`chart of accounts ` is installed by default as part of the localization module, the accounts are mapped automatically in taxes, default account payable, and default account receivable. The chart of accounts for Colombia is based on the PUC (Plan Unico de Cuentas)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:257 +msgid "Main workflows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 +msgid "Electronic invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:262 +msgid "The following is a breakdown of the main workflow for electronic invoices with the Colombian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:265 +msgid "Sender creates an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:266 +msgid "Electronic invoice provider generates the legal XML file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:267 +msgid "Electronic invoice provider creates the CUFE (Invoice Electronic Code) with the electronic signature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:269 +msgid "Electronic invoice provider sends a notification to |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:270 +msgid "|DIAN| validates the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:271 +msgid "|DIAN| accepts or rejects the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:272 +msgid "Electronic invoice provider generates the PDF invoice with a QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:273 +msgid "Electronic invoice provider sends invoice to the acquirer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:274 +msgid "Acquirer sends a receipt of acknowledgement, and accepts or rejects the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:275 +msgid "Sender downloads a :file:`.zip` file with the PDF and XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 +msgid "Electronic invoice workflow for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:287 +msgid "The functional workflow taking place before an invoice validation does **not** alter the main changes introduced with the electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:290 +msgid "Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web service integration. These documents can be created from your sales order or manually generated. To create a new invoice, go to :menuselection:`Accounting --> Customers --> Invoices`, and select :guilabel:`Create`. On the invoice form configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:295 msgid ":guilabel:`Customer`: Customer's information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:245 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:296 msgid ":guilabel:`Journal`: Journal used for electronic invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:246 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:297 msgid ":guilabel:`Electronic Invoice Type`: Select the type of document. By default, :guilabel:`Factura de Venta` is selected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:248 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:299 msgid ":guilabel:`Invoice Lines`: Specify the products with the correct taxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:250 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:301 msgid "When done, click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:255 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:306 #: ../../content/applications/finance/fiscal_localizations/india.rst:116 #: ../../content/applications/finance/fiscal_localizations/india.rst:257 #: ../../content/applications/finance/fiscal_localizations/peru.rst:389 msgid "Invoice validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:257 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:308 msgid "After the invoice confirmation, an XML file is created and sent automatically to Carvajal. The invoice is then processed asynchronously by the E-invoicing service UBL 2.1 (Colombia). The file is also displayed in the chatter." msgstr "" @@ -15067,148 +15852,135 @@ msgstr "" msgid "Carvajal XML invoice file in Odoo chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:264 -msgid "The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the :guilabel:`Process Now` button." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:316 +msgid "The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab, with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the :guilabel:`Process Now` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:272 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:324 msgid "Reception of legal XML and PDF" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:274 -msgid "The electronic invoice vendor (Carvajal) receives the XML file and proceeds to validate its structure and information." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:326 +msgid "The electronic invoice vendor (Carvajal) receives the XML file, and proceeds to validate its structure and information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:277 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:329 msgid "After validating the electronic invoice, proceed to generate a legal XML which includes a digital signature and a unique code (CUFE), a PDF invoice that includes a QR code and the CUFE is also generated. If everything is correct the :guilabel:`Electronic Invoicing` field value changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:282 -msgid "A ZIP containing the legal electronic invoice in XML format and the invoice in PDF format is downloaded and displayed in the invoice chatter:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:334 +msgid "A :file:`.zip` containing the legal electronic invoice (in XML format) and the invoice in (PDF format) is downloaded and displayed in the invoice chatter:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "ZIP file displayed in the invoice chatter in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:288 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:341 msgid "The electronic invoice status changes to :guilabel:`Accepted`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:291 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:335 -msgid "Credit notes" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:293 -msgid "The process for credit notes is the same as for invoices. To create a credit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note` and complete the following information:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:297 -msgid ":guilabel:`Credit Method`: Select the type of credit method." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:299 -msgid ":guilabel:`Partial Refund`: Use this option when it is a partial amount." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:300 -msgid ":guilabel:`Full Refund`: Use this option if the credit note is for the full amount." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:301 -msgid ":guilabel:`Full refund and new draft invoice`: Use this option if the credit note is auto-validated and reconciled with the invoice. The original invoice is duplicated as a new draft." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:305 -msgid ":guilabel:`Reason`: Enter the reason for the credit note." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:306 -msgid ":guilabel:`Reversal Date`: Select if you want a specific date for the credit note or if it is the journal entry date." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:308 -msgid ":guilabel:`Use Specific Journal`: Select the journal for your credit note or leave it empty if you want to use the same journal as the original invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:310 -msgid ":guilabel:`Refund Date`: If you chose a specific date, select the date for the refund." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:312 -msgid "Once reviewed, click the :guilabel:`Reverse` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:315 -msgid "Debit notes" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:317 -msgid "The process for debit notes is similar to credit notes. To create a debit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit Note` button and complete the following information:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:321 -msgid ":guilabel:`Reason`: Type the reason for the debit note." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:322 -msgid ":guilabel:`Debit note date`: Select the specific options." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:323 -msgid ":guilabel:`Copy lines`: Select this option if you need to register a debit note with the same lines of invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:325 -msgid ":guilabel:`Use Specific Journal`: Select the printer point for your debit note, or leave it empty if you want to use the same journal as the original invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:328 -msgid "When done, click :guilabel:`Create Debit Note`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:331 -msgid "Support document for vendor bills" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:333 -msgid "With master data, credentials, and the purchase journal configured for support documents related to vendor bills, you can start using support documents." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:336 -msgid "Support documents for vendor bills can be created from your purchase order or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and fill in the following data:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:339 -msgid ":guilabel:`Vendor`: Enter the vendor's information." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:340 -msgid ":guilabel:`Bill Date`: Select the date of the bill." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:341 -msgid ":guilabel:`Journal`: Select the journal for support documents related to the vendor bills." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:342 -msgid ":guilabel:`Invoiced Lines`: Specify the products with the correct taxes." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 -msgid "Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an XML file is created and automatically sent to Carvajal." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:346 +msgid "The process for credit notes is the same as for invoices. To create a credit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note`, and complete the following information:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:350 -msgid "Common errors" +msgid ":guilabel:`Credit Method`: Select the type of credit method." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:352 +msgid ":guilabel:`Partial Refund`: Use this option when it is a partial amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:353 +msgid ":guilabel:`Full Refund`: Use this option if the credit note is for the full amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:354 +msgid ":guilabel:`Full refund and new draft invoice`: Use this option if the credit note is auto-validated and reconciled with the invoice. The original invoice is duplicated as a new draft." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:358 +msgid ":guilabel:`Reason`: Enter the reason for the credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:359 +msgid ":guilabel:`Reversal Date`: Select if you want a specific date for the credit note or if it is the journal entry date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:361 +msgid ":guilabel:`Use Specific Journal`: Select the journal for your credit note or leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:363 +msgid ":guilabel:`Refund Date`: If you chose a specific date, select the date for the refund." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:365 +msgid "Once reviewed, click the :guilabel:`Reverse` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:370 +msgid "The process for debit notes is similar to credit notes. To create a debit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit Note` button, and enter the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:374 +msgid ":guilabel:`Reason`: Type the reason for the debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:375 +msgid ":guilabel:`Debit note date`: Select the specific options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:376 +msgid ":guilabel:`Copy lines`: Select this option if you need to register a debit note with the same lines of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:378 +msgid ":guilabel:`Use Specific Journal`: Select the printer point for your debit note, or leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:381 +msgid "When done, click :guilabel:`Create Debit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:384 +msgid "Support document for vendor bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:386 +msgid "With master data, credentials, and the purchase journal configured for support documents related to vendor bills, you can start using *support documents*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:389 +msgid "Support documents for vendor bills can be created from your purchase order or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and fill in the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:392 +msgid ":guilabel:`Vendor`: Enter the vendor's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:393 +msgid ":guilabel:`Bill Date`: Select the date of the bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:394 +msgid ":guilabel:`Journal`: Select the journal for support documents related to the vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:395 +msgid ":guilabel:`Invoiced Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:397 +msgid "Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an XML file is created and automatically sent to Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:405 msgid "During the XML validation, the most common errors are related to missing master data (*Contact Tax ID*, *Address*, *Products*, *Taxes*). In such cases, error messages are shown in the chatter after updating the electronic invoice status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:356 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:409 msgid "After the master data is corrected, it's possible to reprocess the XML with the new data and send the updated version, using the :guilabel:`Retry` button." msgstr "" @@ -15216,11 +15988,11 @@ msgstr "" msgid "XML validation errors shown in the invoice chatter in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:421 msgid "Certificado de RetenciĆ³n en ICA" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:370 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:423 msgid "This report is a certification to vendors for withholdings made for the Colombian Industry and Commerce (ICA) tax. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de RetenciĆ³n en ICA`." msgstr "" @@ -15228,11 +16000,11 @@ msgstr "" msgid "Certificado de RetenciĆ³n en ICA report in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:378 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:432 msgid "Certificado de RetenciĆ³n en IVA" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:380 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:434 msgid "This report issues a certificate on the amount withheld from vendors for VAT withholding. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de RetenciĆ³n en IVA`." msgstr "" @@ -15240,11 +16012,11 @@ msgstr "" msgid "Certificado de RetenciĆ³n en IVA report in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:388 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:443 msgid "Certificado de RetenciĆ³n en la Fuente" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:390 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:445 msgid "This certificate is issued to partners for the withholding tax that they have made. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de RetenciĆ³n en Fuente`." msgstr "" @@ -15341,14 +16113,6 @@ msgstr "" msgid ":guilabel:`Address`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 -msgid ":guilabel:`Identification Number`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 -msgid ":guilabel:`Taxpayer Type`" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:85 msgid "Upload company logo and save" msgstr "" @@ -16012,6 +16776,10 @@ msgstr "" msgid "The system suggests a VAT withholding of 30% with tax support 01, you can add your VAT withholding of 70% in a new line with the same tax support, the system will allow you as long as the total of the bases matches the total from the :guilabel:`Vendor Bill`." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:556 +msgid "Financial Reports" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:558 msgid "In Ecuador, there are fiscal reports that the company presents to SRI. In Odoo, we have two of the main financial reports used by companies. These are the reports 103 and 104." msgstr "" @@ -16250,11 +17018,6 @@ msgstr "" msgid "`Egyptian eInvoicing & eReceipt SDK - Code Tables `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 -#: ../../content/applications/finance/fiscal_localizations/romania.rst:106 -msgid ":doc:`../accounting/taxes`" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/egypt.rst:130 msgid "Branches" msgstr "" @@ -16324,7 +17087,7 @@ msgid ":guilabel:`Product Type`: storable products, consumables, or services." msgstr "" #: ../../content/applications/finance/fiscal_localizations/egypt.rst:177 -msgid ":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled :doc:`Units of Measure `." +msgid ":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled :doc:`Units of Measure <../../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/egypt.rst:179 @@ -17135,10 +17898,6 @@ msgstr "" msgid "Should this attempt fail, the user is prompted an error message with all the move lines that are supposedly unbalanced." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:306 -msgid "Partner information" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/france.rst:308 msgid "If a line has the partner information specified, the information is copied to the accounting move itself if the targeted Journal is of type *payable* or *receivable*." msgstr "" @@ -17983,12 +18742,6 @@ msgstr "" msgid "You can check the document's :abbr:`EDI (electronic data interchange)` status under the :guilabel:`EDI Document` tab or the :guilabel:`Electronic invoicing` field of the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:133 -#: ../../content/applications/finance/fiscal_localizations/india.rst:271 -#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 -msgid "Invoice PDF report" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/india.rst:135 msgid "Once an invoice is validated and submitted, the invoice PDF report can be printed. The report includes the :abbr:`IRN (Invoice Reference Number)`, :guilabel:`Ack. No` (acknowledgment number) and :guilabel:`Ack. Date` (acknowledgment date), and QR code. These certify that the invoice is a valid fiscal document." msgstr "" @@ -18577,11 +19330,6 @@ msgstr "" msgid "Italian localization modules" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:41 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:41 -msgid "Company information" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/italy.rst:43 msgid "Configuring the company's information ensures your Accounting database is properly set up. To add information, go to :menuselection:`Settings --> General Settings`, and in the :guilabel:`Companies` section, click :guilabel:`Update info`. From here, fill out the fields:" msgstr "" @@ -19410,1276 +20158,1280 @@ msgstr "" msgid "Mexico" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:22 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:20 +msgid "A video on the Mexican localization is also available. This video covers how to implement this localization from scratch, including how to set up the configurations, how to complete common workflows, and provides an in-depth look at several specific use cases, as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:24 msgid "`Video webinar of a complete demo `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 -msgid "Odoo users in Mexico have access to a set of modules that allow them to sign electronic invoices according to the specifications of the |SAT| for `version 4.0 of the CFDI `_ , a legal requirement as of January 1, 2022." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:29 +msgid "The Odoo Mexican localization modules allow for the signing of electronic invoices, according to the specifications of the |SAT| for `version 4.0 of the CFDI `_, a legal requirement, as of January 1, 2022. These modules also add relevant accounting reports (such as: the |DIOT|, enables foreign trade, and the creation of delivery guides)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:32 -msgid "These modules also add relevant accounting reports (such as the |DIOT|, enable foreign trade, and the creation of delivery guides)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:36 +msgid "In order to electronically sign any documents in Odoo, ensure the *Sign* application is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:39 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 msgid "Requirements" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:41 -msgid "Before making the necessary configurations to have the Mexican localization installed in Odoo, it is necessary to meet the following requirements:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:45 +msgid "It is necessary to meet the following requirements before configuring the Mexican localization modules in Odoo:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:46 -msgid "Be registered in the |SAT|, with a valid :abbr:`RFC (Registro Federal de Contribuyentes)`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:50 +msgid "Be registered in the |SAT|, with a valid |RFC|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:47 -msgid "Have a `Certificate of Digital Seal `_ (CSD)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:49 -msgid "Choose a PAC (Proveedor Autorizado de CertificaciĆ³n / Authorized Certification Provider). Currently, Odoo works with the following |PAC|\\s: `SoluciĆ³n Factible `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:51 +msgid "Have a `Certificate of Digital Seal `_ (CSD)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:53 -msgid "Have knowledge and experience with billing, sales, and accounting in Odoo. This documentation contains only the necessary information to use Odoo." +msgid "Choose a PAC (Proveedor Autorizado de CertificaciĆ³n / Authorized Certification Provider). Currently, Odoo works with the following |PAC|\\s: `SoluciĆ³n Factible `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:59 -msgid ":ref:`Install ` the following modules to get the main features of the Mexican localization:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:57 +msgid "Have knowledge and experience with billing, sales, and accounting in Odoo. This documentation **only** contains the necessary information needed to use Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:69 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:61 +msgid "Installing modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:63 +msgid ":ref:`Install ` the following modules to get all the features of the Mexican localization. The :doc:`Accounting <../accounting>` and *Contacts* modules are required to be installed for this configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:74 msgid ":guilabel:`Mexico - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:70 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:75 msgid "`l10n_mx`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 -msgid "The default :doc:`fiscal localization package `, adds accounting characteristics for the Mexican localization, such as the most common taxes and the chart of accounts based on `the SAT account grouping code `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:76 +msgid "The default :doc:`fiscal localization package <../fiscal_localizations>`, adds accounting characteristics for the Mexican localization, such as: the most common taxes and the chart of accounts ā€“ based on `the SAT account grouping code `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:75 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:80 msgid ":guilabel:`EDI for Mexico`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:76 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:81 msgid "`l10n_mx_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:77 -msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents `, based on the technical documentation published by the SAT. This allows you to send invoices (with or without addendas) and payment complements to the government." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:82 +msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents <../accounting/customer_invoices/electronic_invoicing>` ā€” based on the technical documentation published by the |SAT|. This allows you to send invoices (with or without addedums) and payment complements to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:82 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:86 msgid ":guilabel:`EDI v4.0 for Mexico`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:83 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:87 msgid "`l10n_mx_edi_40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:84 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:88 msgid "Necessary to create XML documents with the correct specifications of the CFDI 4.0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:87 -msgid "When you install a database from scratch by selecting :guilabel:`Mexico` as the country, Odoo automatically installs the following modules: :guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and :guilabel:`EDI v4.0 for Mexico`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:91 -msgid "The following modules are needed to add Mexico's Electronic Accounting. They require the :doc:`Accounting ` module to be installed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:101 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:89 msgid ":guilabel:`Odoo Mexican Localization Reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:102 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:90 msgid "`l10n_mx_reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:103 -msgid "Adapts reports for Mexico's Electronic Accounting: Chart of Accounts, Trial Balance, and DIOT." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:91 +msgid "Adapts reports for Mexico's Electronic Accounting: Chart of Accounts, Trial Balance, and |DIOT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:105 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:93 msgid ":guilabel:`Mexico - Localization Reports for Closing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:106 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:94 msgid "`l10n_mx_reports_closing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:107 -msgid "Necessary to create the Closing Entry (Also known as the month 13th move)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:95 +msgid "Necessary to create the Closing Entry (Also known as the *month 13th move*)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:108 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:96 msgid ":guilabel:`Odoo Mexican XML Polizas Export`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:109 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:97 msgid "`l10n_mx_xml_polizas`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:110 -msgid "Lets you export XML files of your Journal Entries for a compulsory audit." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:98 +msgid "Allows the export of XML files of Journal Entries for a compulsory audit." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:111 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:99 msgid ":guilabel:`Odoo Mexican XML Polizas Export Edi bridge`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:112 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:100 msgid "`l10n_mx_xml_polizas_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:113 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:101 msgid "Complements the module `l10n_mx_xml_polizas`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 -msgid "The following modules are optional. It's recommended to install them *only* if you meet a specific requirement. Make sure that they are needed for your business." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:104 +msgid "When installing a database from scratch and selecting :guilabel:`Mexico` as the country, Odoo automatically installs the following modules: :guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and :guilabel:`EDI v4.0 for Mexico`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:125 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:108 +msgid "The following modules are optional. It's recommended to install them *only* if meeting a specific requirement. Make sure that they are needed for the business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:118 msgid ":guilabel:`EDI for Mexico (Advanced Features)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:126 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:119 msgid "`l10n_mx_edi_extended`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:127 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:120 msgid "Adds the external trade complement to invoices: A legal requirement for selling products to foreign countries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:129 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:122 msgid ":guilabel:`EDI v4.0 for Mexico (COMEX)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:123 msgid "`l10n_mx_edi_extended_40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:131 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 msgid "Adapts the module `l10n_mx_edi_extended` for CFDI 4.0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:132 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:125 msgid ":guilabel:`Mexico - Electronic Delivery Guide`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:126 msgid "`l10n_mx_edi_stock`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:134 -msgid "Lets you create a \"Carta Porte\": a bill of lading that proves to the government you are sending goods between A & B with a signed electronic document." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:127 +msgid "Lets you create a *Carta Porte*: A bill of lading that proves to the government you are sending goods between A & B with a signed electronic document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:136 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:129 msgid ":guilabel:`Electronic Delivery Guide for Mexico CFDI 4.0`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 msgid "`l10n_mx_edi_stock_40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:138 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:131 msgid "Adapts the module `l10n_mx_edi_stock` for CFDI 4.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:139 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:132 msgid ":guilabel:`Odoo Mexico Localization for Stock/Landing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:140 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 msgid "`l10n_mx_edi_landing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:141 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:134 msgid "Allows managing customs numbers related to landed costs in electronic documents." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:139 +msgid "After installing the correct modules, the next step is to verify that your company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies`, and select :guilabel:`Update Info` under your company name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:143 +msgid "Enter the full :guilabel:`Address` in the resulting form, including: :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| (:guilabel:`VAT` number)." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/mexico.rst:146 -msgid "After installing the correct modules, you must verify that the company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies` and select :guilabel:`Update Info` under your company name." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:150 -msgid "Enter your full :guilabel:`Address` in the resulting form including :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and RFC (:guilabel:`VAT` number)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:153 -msgid "According to the requirements of the CFDI 4.0, the name of your main contact must coincide to your business name registered in the SAT without the legal entity abbreviation." +msgid "According to the requirements of the CFDI 4.0, the name of the main company contact **must** coincide with your business name registered in the |SAT|, without the legal entity abbreviation." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Requirements for a correct invoicing." +msgid "Main company contact requirements for a correct invoicing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:160 -msgid "From a legal point of view, a Mexican company must use the local currency (MXN). Therefore, Odoo does not provide features to manage an alternative configuration. If you want to manage another currency, let MXN be the default currency and use a :doc:`pricelist ` instead." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:154 +msgid "From a legal point of view, a Mexican company **must** use the local currency (MXN). Therefore, Odoo does not provide features to manage an alternative configuration. If you want to manage another currency, let MXN be the default currency and use a :doc:`pricelist <../../sales/sales/products_prices/prices/pricing>`, instead." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:165 -msgid "Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, and select the regime that applies to your company from the drop-down list." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:159 +msgid "Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, then select the regime that applies to your company from the drop-down list, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Fiscal regime configuration." +msgid "Fiscal regime configuration in the Accounting settings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:172 -msgid "If you want to test the Mexican localization, you can configure the company with a real address within Mexico (including all fields), add `EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the :guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use :guilabel:`General de Ley Personas Morales`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:168 +msgid "If you want to test the Mexican localization, the company can be configured with a real address within Mexico (including all fields), and add `EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the :guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use :guilabel:`General de Ley Personas Morales`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:180 -msgid "To create a contact that can be invoiced, go to :menuselection:`Contacts --> Create`. Then enter the contact's name, full :guilabel:`Address` including :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and RFC (:guilabel:`VAT` number)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:176 +msgid "To create a contact that can be invoiced, go to :menuselection:`Contacts --> Create`. Then, enter the contact name, full :guilabel:`Address` including: :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| (:guilabel:`VAT` number)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:185 -msgid "As with your own company, all of your contacts needs to have their correct business name registered in the |SAT|. This also applies to the :guilabel:`Fiscal Regime` which needs to be added in the :guilabel:`MX EDI` tab." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:181 +msgid "As with your own company, all of your contacts needs to have their correct business name registered in the |SAT|. This also applies to the :guilabel:`Fiscal Regime`, which needs to be added in the :guilabel:`MX EDI` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:188 msgid "Some additional configurations for factor type and tax objects need to be added to the sales taxes in order to properly sign invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:196 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 msgid "Factor type" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:198 -msgid "Go to :menuselection:`Accounting --> Configuration --> Taxes` then enable the :guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for all records with the :guilabel:`Tax Type` set as :guilabel:`Sales`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:202 -msgid "This is pre-loaded in the default taxes. If new ones are created, you need to make sure to fill this field." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:194 +msgid "The *Factor Type* field is pre-loaded in the default taxes. If new taxes are created, you need to make sure to configure this field. To do so, go to :menuselection:`Accounting --> Configuration --> Taxes`, then enable the :guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for all records, with the :guilabel:`Tax Type` set as :guilabel:`Sales`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Taxes configuration." +msgid "Factor Type Sales tax type configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:209 -msgid "Mexico manages two different kinds of 0% VAT: *0% VAT* and *VAT Exempt*. For the former, select the :guilabel:`Factor Type` :guilabel:`Tasa`. For the latter, use :guilabel:`Exento`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:204 +msgid "Mexico manages two different kinds of 0% VAT to accommodate two scenarios:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:213 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:206 +msgid "*0% VAT* set the :guilabel:`Factor Type` as :guilabel:`Tasa`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:207 +msgid "*VAT Exempt* set the :guilabel:`Factor Type` as :guilabel:`Exento`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:210 msgid "Tax object" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:215 -msgid "One requirement of the CFDI 4.0 is that the resulting XML file needs or does not need to break down the taxes of the operation. There are three different possible values that are added depending on specific configurations:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:212 +msgid "One requirement of the CFDI 4.0 is that the resulting XML file needs (or does not need) to break down the taxes of the operation. There are three different possible values that are added in the XML file:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:216 +msgid "`01`: Not subject to tax - this value is added automatically if your invoice line doesn't contain any taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:218 +msgid "`02`: Subject to tax - this is the default configuration of any invoice line that contains taxes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:219 -msgid "`01`: Not subject to tax - your invoice must not contain any taxes." +msgid "`03`: Subject to tax and not forced to break down - this value can be triggered on-demand for certain customers to replace the value 02." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:220 -msgid "`02`: Subject to tax - your invoice contains taxes (default configuration)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:221 -msgid "`03`: Subject to tax and not forced to breakdown - your invoice contains taxes, and the contact configuration has the :guilabel:`No Tax Breakdown` checkbox activated." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:222 +msgid "To use the `03` value, navigate to :menuselection:`Contacts --> your customer's invoice --> MX EDI tab`, and activate the :guilabel:`No Tax Breakdown` checkbox." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Tax Breakdown SAT." +msgid "No Tax Breakdown option on the MX EDI tab of the customer's invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:228 -msgid "The :guilabel:`No Tax Breakdown` value applies only to specific fiscal regimes and/or taxes. Consult your accountant first if it is needed for your business before doing any modification." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:230 +msgid "The :guilabel:`No Tax Breakdown` value applies **only** to specific fiscal regimes and/or taxes. Consult your accountant first to see if it is needed for your business before making any modification." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:232 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:235 msgid "Other tax configurations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:234 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:237 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 :guilabel:`Definition` tab. For such movement, a tax base account will be used: (`Base Imponible de Impuestos en Base a Flujo de Efectivo`) in the journal entry when reclassifying taxes. **Do not delete this account**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:239 -msgid "If you create a new tax, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, `ISR` or `IEPS`). Odoo only supports these three groups of taxes." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:242 +msgid "If you create a new tax in :menuselection:`Accounting --> Configuration --> Taxes`, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, `ISR` or `IEPS`). Odoo **only** supports these three groups of taxes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Taxes accounts." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:248 -msgid "To configure products, go to the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents that product. The process can be done manually or through :doc:`a bulk import `." +msgid "Tax accounts available for Odoo." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 -msgid "All products need to have a |SAT| code associated with them in order to prevent validation errors." +msgid "To configure products, go to :menuselection:`Accounting --> Customers --> Products`, then select a product to configure, or :guilabel:`Create` a new one. In the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents the product. The process can be done manually, or through :doc:`a bulk import <../../general/export_import_data>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:260 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:259 +msgid "All products need to have an |SAT| code associated with them in order to prevent validation errors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:266 msgid "PAC credentials" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:262 -msgid "After you have processed your `Private Key (CSD) `_ with the |SAT|, you must register directly with the :ref:`PAC ` of your choice before you start creating invoices from Odoo." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:268 +msgid "After you have processed your `Private Key (CSD) `_ with the |SAT|, you **must** register directly with the :ref:`PAC ` of your choice before you start creating invoices from Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:267 -msgid "Once you created your account with any of these providers, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:273 +msgid "Once you've created your account with any of these providers, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PAC credentials." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:275 -msgid "If you do not have credentials and want to test the electronic invoicing, you can activate the :guilabel:`Test Environment` checkbox and select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a username or password." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:280 -msgid ".cer and .key certificates" +msgid "Configuring PAC credentials from the Accounting settings." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:282 -msgid "You need to upload the `digital certificates of the company `_ within the section :guilabel:`MX Certificates`. Select :guilabel:`Add a line` and a window will open. Click on :guilabel:`Create`, and from there upload your digital certificate (:file:`.cer` file), your key (:file:`.key` file), and your password. To finish, click on :guilabel:`Save and Close`." +msgid "If you do not have credentials, but want to test the electronic invoicing, you can activate the :guilabel:`MX PAC test environment` checkbox, and select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a username or password for a test environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:287 +msgid ".cer and .key certificates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:289 +msgid "The `digital certificates of the company `_ must be uploaded within the :guilabel:`MX Certificates` section. To do so, navigate to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX Certificates` section, select :guilabel:`Add a line`, and a window will open. Click :guilabel:`Create`, and from there, upload your digital :guilabel:`Certificate` (:file:`.cer` file), your :guilabel:`Certificate Key` (:file:`.key` file), and your :guilabel:`Certificate Password`. To finish, click on :guilabel:`Save & Close`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Certificate and key." +msgid "Certificate and key upload inputs." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:292 -msgid "If you still do not have one of the contracted |PAC|\\s and you want to test electronic invoicing you can use the following |SAT| test certificates:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:303 +msgid "If you still do not have one of the contracted |PAC|\\s and you want to test electronic invoicing, you can use the following |SAT| test certificates:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:295 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:306 msgid ":download:`Certificate `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:296 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:307 msgid ":download:`Certificate Key `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:297 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 msgid "**Password**: ``12345678a``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:305 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:316 msgid "The invoicing process in Odoo is based on `Annex 20 `_ version 4.0 of electronic invoicing of the |SAT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:312 -msgid "To start invoicing from Odoo, a customer invoice must be created using the :doc:`standard invoicing flow `." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:323 +msgid "To start invoicing from Odoo, a customer invoice must be created using the :doc:`standard invoicing flow <../accounting/customer_invoices>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:315 -msgid "When the document is in draft mode, you can make any changes to it (add the correct :guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require, for example.)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:326 +msgid "While the document is in draft mode, changes can be made to it (the correct :guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require can be added, for example.)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:318 -msgid "After you :guilabel:`Confirm` the customer invoice, a blue message appears stating: :guilabel:`The invoice will be processed asynchronously by the following E-invoicing service: CFDI (4.0)`. Pressing the :guilabel:`Process Now` button sends the document to be signed by the government. On success, the :guilabel:`Fiscal Folio` field appears on the document and the XML file is attached in the chatter." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:329 +msgid "After you :guilabel:`Confirm` the customer invoice, a blue message appears stating: :guilabel:`The invoice will be processed asynchronously by the following E-invoicing service: CFDI (4.0)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:325 -msgid "If you press :guilabel:`Retry` in the field :guilabel:`SAT status` of the invoice, you can confirm if the XML file is valid in the SAT." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:328 -msgid "If you are in a testing environment, you will always receive the message :guilabel:`Not Found`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:330 -msgid "To send the signed invoice to your client by mail, you can send the XML together with the PDF file directly from Odoo by clicking the :guilabel:`Send and Print` button. You can also download the PDF file to your computer by clicking the :guilabel:`Print` button and selecting the desired option." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:332 +msgid "Pressing the :guilabel:`Process Now` button sends the document to the government so it can be signed. After receiving the signed document back from the government, the :guilabel:`Fiscal Folio` field appears on the document, and the XML file is attached in the chatter." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:337 -msgid "While an invoice is a document type \"I\" (Ingreso), a credit note is a document type \"E\" (Egreso)." +msgid "If you click :guilabel:`Retry` in the :guilabel:`SAT status` field on the invoice, you can confirm if the XML file is valid in the |SAT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:339 -msgid "The only addition to the :doc:`standard flow for credit notes ` is that, as a requirement of the SAT, there has to be a relation between a credit note and an invoice through the fiscal folio." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:340 +msgid "If you are in a testing environment, you will always receive the message :guilabel:`Not Found`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:343 -msgid "Because of this, the field :guilabel:`CFDI Origin` adds this relation with a `01|`, followed by the fiscal folio of the original invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Creating a credit note." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:342 +msgid "To send the signed invoice to your client by mail, you can send both the XML and PDF files together, directly from Odoo, by clicking the :guilabel:`Send & Print` button. You can also download the PDF file to your computer, by clicking the :guilabel:`Print` button, and selecting the desired print option." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:350 -msgid "For the :guilabel:`CFDI Origin` field to be added automatically, use the button :guilabel:`Add Credit Note` from the invoice instead of creating it manually." +msgid "While an invoice is a document type \"I\" (Ingreso), a credit note is a document type \"E\" (Egreso)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:354 -msgid "Payment complements" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:352 +msgid "The only addition to the :doc:`standard flow for credit notes <../accounting/customer_invoices/credit_notes>` is that, as a requirement of the |SAT|, there has to be a relation between a credit note and an invoice through the fiscal folio." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:357 -msgid "Payment policy" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:356 +msgid "Because of this requirement, the field :guilabel:`CFDI Origin` adds this relation with a `01|`, followed by the fiscal folio of the original invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:359 -msgid "One of the additions of the Mexican Localization is the field :guilabel:`Payment Policy`. `According to the SAT documentation `_, there may be 2 types of payments:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Example CFDI Origin number." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:364 +msgid "For the :guilabel:`CFDI Origin` field to be automatically added, use the :guilabel:`Add Credit Note` button from the invoice, instead of creating it manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:368 +msgid "Payment complements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:373 +msgid "One addition of the Mexican localization is the :guilabel:`Payment Policy` field . `According to the SAT documentation `_, there may be 2 types of payments:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 msgid "`PUE` (Pago en una Sola ExhibiciĆ³n/Payment in a Single Exhibition)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:365 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 msgid "`PPD` (Pago en Parcialidades o Diferido/Payment in Installements or Deferred)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:367 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:381 +msgid ":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:383 msgid "The difference lies in the *Due Date* or *Payment Terms* of the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:369 -msgid "To configure |PUE| invoices, you must select an invoice :guilabel:`Due Date` within the same month or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:385 +msgid "To configure |PUE| invoices, navigatge to :menuselection:`Accounting --> Customers --> Invoices`, and either select an invoice :guilabel:`Due Date` within the same month, or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Example of an invoice with the PUE requirements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 -msgid "Some :guilabel:`Payment Terms` are already installed by default. You can check them in :menuselection:`Accounting --> Configuration --> Payment Terms`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 +msgid "Some :guilabel:`Payment Terms` are already installed by default, and can be managed from :menuselection:`Accounting --> Configuration --> Payment Terms`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 -msgid "To configure |PPD| invoices, you need to choose a :guilabel:`Due Date` after the first day of the following month (this also applies if your :guilabel:`Payment Term` is due in the following month)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:398 +msgid "To configure |PPD| invoices, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select an invoice with a :guilabel:`Due Date` after the first day of the following month. This also applies if your :guilabel:`Payment Term` is due in the following month." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Example of an invoice with the PPD requirements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:387 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:407 msgid "Because the |PPD| policy implies that an invoice is not going to get paid at the moment, the correct :guilabel:`Payment Way` for the |PPD| invoices is :guilabel:`99 - Por Definir` (To define)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:412 msgid "Payment flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:394 -msgid "In both cases, the payment process in Odoo :doc:`is the same `, the main difference would be that payments related to |PPD| invoices trigger the creation of a document type \"P\" (Pago)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:414 +msgid "In both cases, the payment process in Odoo :doc:`is the same <../accounting/customer_invoices>`, the main difference being payments related to |PPD| invoices trigger the creation of a document type \"P\" (Pago)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:398 -msgid "If a payment is related to a |PUE| invoice, it can be registered with the wizard and be associated with the corresponding invoice. Its status will be :guilabel:`In Payment` since the payment is effectively validated when it is bank reconciled." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:418 +msgid "If a payment is related to a |PUE| invoice, it can be registered with the wizard, and be associated with the corresponding invoice. To do so, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select an invoice. Then, click the :guilabel:`Register Payment` button. The invoice status changes to :guilabel:`In Payment`, since the payment is effectively validated when it is bank reconciled." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:405 -msgid "While this process is the same for PPD invoices, the addition of the creation of an :doc:`electronic document ` means that some additional requirements are needed to correctly send the document to the SAT." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:425 +msgid ":doc:`../accounting/bank/reconciliation`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:409 -msgid "You need to confirm the specific :guilabel:`Payment Way` where you received the payment. Because of this, this field cannot be :guilabel:`99 - Por Definir` (To Define)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:427 +msgid "While this process is the same for PPD invoices, the addition of the creating an :doc:`electronic document <../accounting/customer_invoices/electronic_invoicing>` means some additional requirements are needed to correctly send the document to the |SAT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:411 -msgid "If you are going to add a bank account to the customer in the :guilabel:`Accounting` tab of their contact, it needs to have a valid number." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:431 +msgid "From an invoice, you need to confirm the specific :guilabel:`Payment Way` where you received the payment. Because of this, the :guilabel:`Payment Way` field **cannot** be set as `99 - Por Definir (To Define)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:415 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:435 +msgid "If you are going to add a bank account number in the :guilabel:`Accounting` tab of a customer's contact card, it must have a valid account number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:439 msgid "The exact configurations are in the `Anexo 20 of the SAT `_. Usually, the :guilabel:`Bank Account` needs to be 10 or 18 digits for transfers, 16 for credit or debit cards." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:419 -msgid "If a payment is related to a signed invoice with the :guilabel:`Payment Policy` `PPD`, Odoo generates the corresponding payment complement automatically once you press :guilabel:`Process Now`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:443 +msgid "If a payment is related to a signed invoice with the :guilabel:`Payment Policy` `PPD`, Odoo generates the corresponding payment complement automatically, once you click :guilabel:`Process Now`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "CFDI (4.0) E-invoicing service process payment now message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:426 -msgid "A payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment should be separated into multiple payments created using the :guilabel:`Register Payment` button on the corresponding invoices." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:452 +msgid "A payment in MXN **cannot** be used to pay multiple invoices in USD. Instead, the payment should be separated into multiple payments, using the :guilabel:`Register Payment` button on the corresponding invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:431 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:457 msgid "Invoice cancellations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:433 -msgid "It is possible to cancel the EDI documents sent to the SAT. According to the `Reforma Fiscal 2022 `_, since January 1st 2022, there are two requirements for this:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:459 +msgid "It is possible to cancel the EDI documents sent to the |SAT|. According to the `Reforma Fiscal 2022 `_, since January 1st, 2022, there are two requirements for this:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:437 -msgid "With all cancellation requests, you have to specify a *cancellation reason*." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:463 +msgid "With all cancellation requests, you **must** specify a *cancellation reason*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:438 -msgid "After 24 hours have passed, the client must be asked to accept the cancellation." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:464 +msgid "After 24 hours have passed since the creation of the invoice, the client **must** be asked to accept the cancellation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:440 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:467 msgid "There are four different cancellation reasons. In Odoo, you can cancel invoices with the reasons *01 Invoices sent with errors with a relation*, and *02 Invoices sent with errors without a relation*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:444 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:470 +msgid "The following sections break down the process of canceling invoices for each cancellation reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:474 +msgid "Odoo has certain limitations to canceling invoices in the |SAT|: The reasons 03 and 04 (*Operation did not take place* and *Nominative transactions related to a global invoice*, respectively) are not currently supported by Odoo. For this, you need to cancel the invoice directly in the |SAT|, and press :guilabel:`Retry` in the :guilabel:`SAT Status field`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:480 msgid "01 - invoices sent with errors with a relation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:446 -msgid "This cancellation motive has to be used when a new invoice needs to substitute the original one, due to an error in any field." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 +msgid "This cancellation reason must be used when a new invoice needs to substitute the original one, due to an error in any field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:449 -msgid "Copy the :guilabel:`Fiscal Folio` of the *old invoice*" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:485 +msgid "Begin by navigating to :menuselection:`Accounting --> Customers --> Invoices`, and select the old invoice. Copy the :guilabel:`Fiscal Folio` from the old invoice. Then, navigate to the new invoice, and in the :guilabel:`CFDI Origin` field, add the value `04|` and paste the :guilabel:`Fiscal Folio` of the old invoice after the value. Finally, sign the new document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:450 -msgid "Paste it into the field :guilabel:`CFDI Origin` of the *new invoice*, followed by a `04|`" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:490 +msgid "Next, navigate back to the old invoice, and notice the :guilabel:`Substituted By` field is now available. Click the :guilabel:`Request EDI Cancellation` button on the old invoice, and then click :guilabel:`Process Now` in the blue section that appears. The invoice status changes to :guilabel:`Canceled`, and a confirmation is logged in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:451 -msgid "Sign the new document." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:495 +msgid "Now, the invoice should be canceled in the |SAT| as well. You can confirm this was done correctly, by pressing :guilabel:`Retry` in the |SAT| status field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 +msgid "If the document was canceled more than 24 hours after its creation, you may need to ask the client to accept the cancellation in their ā€œBuzĆ³n Tributarioā€ directly from the `SAT website `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:503 +msgid "The `04|` is only a code that helps Odoo to perform this process. It has no relation to the method 04 reason for cancellation." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Old invoice with CFDI Origin." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:456 -msgid "Go back to the *old invoice*, the field :guilabel:`Substituted By` should appear." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:457 -msgid "Click the :guilabel:`Request EDI Cancellation` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:458 -msgid "As if it were a regular invoice, a blue field then appears on the invoice. Click :guilabel:`Process Now`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:460 -msgid "The invoice status is moved to :guilabel:`Cancelled` and you receive a confirmation in the chatter." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Invoice 01 properly canceled." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:466 -msgid "Now, the invoice should be canceled in the SAT too. You can confirm that this was done correctly by pressing :guilabel:`Retry` in the SAT status field." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:469 -msgid "If the document was canceled after 24 hours, it is possible that the client must be asked to accept the cancellation in their \"BuzĆ³n Tributario\"." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:473 -msgid "The `04|` is only a code that helps Odoo to perform this process. It has no relation to the method 04 reason for cancellation." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:477 -msgid "02 - invoices sent with errors without a relation" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 -msgid "This cancellation motive has to be used when an invoice was sent with an error in any field and does not need to be replaced by another one." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 -msgid "For this case, all that is required is to click on :guilabel:`Request EDI Cancellation`, and then press click the :guilabel:`Process Now` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Invoice 02 properly canceled." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:488 -msgid "As the field :guilabel:`Substituted By` does not exist, the SAT should detect automatically that the cancellation reason is 02." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:492 -msgid "Odoo has certain limitations to canceling invoices in the SAT: The reasons 03 and 04 (*Operation did not take place* and *Nominative transactions related to a global invoice*) are not currently supported by Odoo. For this, you need to cancel the invoice directly in the SAT and use a *Server Action*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 -msgid "Payment cancellations" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:500 -msgid "It is also possible to cancel *Payment Complements*. For this, go to the payment and select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button will appear. Select :guilabel:`Process now`, and the document will be sent to the SAT. After a few seconds, you can press :guilabel:`Retry` to confirm the current SAT status." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:505 -msgid "The payment moves their status to :guilabel:`Cancelled`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:508 -msgid "Just like invoices, when you create a new *Payment Complement*, you can add the relation of the original document by adding a `04|` plus the fiscal folio." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:512 -msgid "Invoicing special use cases" +msgid "Invoice with the Substituted By field referencing the CFDI Origin invoice." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 -msgid "CFDI to public" +msgid "02 - invoices sent with errors without a relation" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:517 -msgid "If the customer you are selling goods or services to does not require an invoice, a *CFDI to Public* has to be created." +msgid "This cancellation reason has to be used when an invoice was sent with an error in any field, and does not need to be replaced by another one." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:520 -msgid "However, if you use the name `PUBLICO EN GENERAL`, an error will be triggered. This is a main change in the CFDI 4.0 that states that invoices with that specific name needs additional fields." +msgid "For this case, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select the old invoice. From here, the only requirement is to click the :guilabel:`Request EDI Cancellation` button, and then click the :guilabel:`Process Now` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:523 -msgid "Odoo currently does not support this. So for a *CFDI to Public* to be created, you need to add any name to your customer that is not `PUBLICO EN GENERAL`. (For example `CLIENTE FINAL`)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:524 +msgid "Because the field :guilabel:`Substituted By` does not appear when using this cancellation reason, the |SAT| should automatically detect that the cancellation reason is 02." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:526 -msgid "In addition to this, the zip code of your company, and the generic :guilabel:`RFC` ``XAXX010101000`` are needed. The :guilabel:`Fiscal Regime` of your customer must be `Sin obligaciones fiscales`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:528 +msgid "Payment cancellations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "CFDI to Public Error." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:530 +msgid "It is also possible to cancel *Payment Complements*. For this, go to the payment, via :menuselection:`Accounting --> Customers --> Payments`, and select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button will appear. Click :guilabel:`Process now`, and the document will be sent to the |SAT|. After a few seconds, you can click :guilabel:`Retry` to confirm the current |SAT| status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:535 -msgid "The main currency in Mexico is MXN. While this is mandatory for all Mexican companies, it is possible to send and receive invoices and payments in different currencies. To do this, you can enable the use of :doc:`multicurrency `. And select :guilabel:`Mexican Bank` as the service in :menuselection:`Accounting --> Settings --> Currency`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:536 +msgid "Finally, the payment status is moved to :guilabel:`Cancelled`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:541 -msgid "This way, in the XML file of the document you get the correct exchange rate and the total amount both in the foreign currency and in MXN." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:539 +msgid "Just like invoices, when you create a new *Payment Complement*, you can add the relation of the original document, by adding a `04|` plus the fiscal folio in the :guilabel:`CFDI Origin` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:544 -msgid "It is highly recommended to use :doc:`a bank account for each currency `." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:543 +msgid "Invoicing special use cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Multi-currency configuration." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:546 +msgid "CFDI to public" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 +msgid "If the customer you are selling goods or services to does not require an invoice, a *CFDI to Public* has to be created." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:551 -msgid "The only currencies that automatically update their exchange rate daily are USD, EUR, GBP, and JPY." +msgid "If you use the :guilabel:`Customer` name `PUBLICO EN GENERAL`, an error will be triggered. This is a main change in the CFDI 4.0 that requires invoices with that specific name to need additional fields, which Odoo does not currently support. So, for a *CFDI to Public* to be created, you need to add any name to your customer that is **not** `PUBLICO EN GENERAL`. (For example: `CLIENTE FINAL`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:555 -msgid "Down payments" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:556 +msgid "In addition to this, it is required that the :guilabel:`ZIP` code of your company is added, the generic |RFC| is set as `XAXX010101000`, and the :guilabel:`Fiscal Regime` of your customer must be set as: `Sin obligaciones fiscales`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:557 -msgid "There can be cases where you receive a payment in advance from a customer, that needs to be applied to an invoice later. In order to do this in Odoo, it is required to properly link invoices to each other with the :guilabel:`CFDI Origin` field." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:561 -msgid "It is necessary to have the :doc:`Sales ` app installed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:564 -msgid "`The official documentation for registration of down payments in Mexico `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "CFDI to Public Customer field configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:567 -msgid "First, navigate to the :menuselection:`Sales` app to create a product `Anticipo` and configure it: the :guilabel:`Product Type` must be :guilabel:`Service`, and use the :guilabel:`UNSPSC Category` `84111506 Servicios de facturaciĆ³n`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:571 -msgid "Then, go to :menuselection:`Sales --> Settings --> Invoicing --> Down Payments` and add the product as the default." +msgid "The main currency in Mexico is MXN. While this is mandatory for all Mexican companies, it is possible to send and receive invoices (and payments) in different currencies. To enable the use of :doc:`multicurrency <../accounting/get_started/multi_currency>`, navigate to the :menuselection:`Accounting --> Settings --> Currencies`, and set :guilabel:`Mexican Bank` as the :guilabel:`Service` in the :guilabel:`Automatic Currency Rates` section. Then, set the :guilabel:`Interval` field to the frequency you wish to update the exchange rates." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:574 -msgid "Create a sales order with the total amount, and create a down payment (either using a percentage or fixed amount). Then, sign the document, and :guilabel:`Register the Payment`." +msgid "This way, the XML file of the document will have the correct exchange rate, and the total amount, in both the foreign currency and in MXN." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:577 -msgid "When the time comes for the customer to get the final invoice, create it again from the same sales order. In the :guilabel:`Create Invoices` wizard select :guilabel:`Regular Invoice` and uncheck :guilabel:`Deduct down payments`." +msgid "It is highly recommended to use :doc:`a bank account for each currency <../accounting/bank/foreign_currency>`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:581 -msgid "Then, copy the :guilabel:`Fiscal Folio` from the first invoice and paste it into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix `07|`. Sign the document." +msgid "The only currencies that automatically update their exchange rate daily are: USD, EUR, GBP, and JPY." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:584 -msgid "After this, create a credit note for the first invoice. Copy the :guilabel:`Fiscal Folio` from the second invoice and paste it in the :guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Sign the document." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Multi-currency configuration in the Accounting settings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:588 -msgid "With this, all electronic documents are linked to each other. The final step is to fully pay the new invoice. At the bottom of the new invoice, you can find :guilabel:`Outstanding credits` in the credit note, add it as payment. Finally, register the remaining amount with the :guilabel:`Register Payment` wizard." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:589 +msgid "Down payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:594 -msgid "External trade" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:591 +msgid "There can be cases where you receive a payment in advance from a customer that needs to be applied to an invoice later. In order to do this in Odoo, it is required to properly link invoices to each other with the :guilabel:`CFDI Origin` field. To do so, it is necessary to have the :doc:`Sales <../../sales>` app installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:596 -msgid "The external trade is a complement to a regular invoice that adds certain values in both the XML and PDF, according to `SAT regulations `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:597 +msgid "`The official documentation for registration of down payments in Mexico `_." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:600 -msgid "This adds certain mandatory fields to invoices with a foreign customer, such as:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:602 -msgid "The specific address of the receiver and the sender" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:603 -msgid "The addition of a :guilabel:`Tariff Fraction` that identifies the type of product" +msgid "First, navigate to the :menuselection:`Sales` app to create a product `Anticipo` and configure it. The :guilabel:`Product Type` must be :guilabel:`Service`, and use the :guilabel:`UNSPSC Category` must be: `84111506 Servicios de facturaciĆ³n`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 -msgid "The correct :guilabel:`Incoterm` (International Commercial Terms), among others." +msgid "Then, go to :menuselection:`Sales --> Settings --> Invoicing --> Down Payments`, and add the *Anticipo* product as the default." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:606 -msgid "This allows the correct identification of exporters and importers, in addition to expanding the description of the merchandise sold." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:607 +msgid "Create a sales order with the total amount, and create a down payment (either using a percentage or fixed amount). Then, sign the document, and :guilabel:`Register the Payment`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:609 -msgid "Since January 1st, 2018, it is a requirement for taxpayers who carry export operations of A1 type. While the current CFDI is 4.0, the external trade is currently on version 1.1" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:610 +msgid "When the time comes for the customer to get the final invoice, create it again from the same sales order. In the :guilabel:`Create Invoices` wizard, select :guilabel:`Regular Invoice`, and uncheck :guilabel:`Deduct down payments`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:612 -msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended` and :guilabel:`l10n_mx_edi_extended_40` have to be installed." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:614 +msgid "Then, copy the :guilabel:`Fiscal Folio` from the first invoice, and paste it into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix `07|` before the value. Then, sign the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:616 -msgid "Before installing, make sure first that your business needs to use this feature. Consult your accountant first if needed before doing any modification." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:618 +msgid "After this, create a credit note for the first invoice. Copy the :guilabel:`Fiscal Folio` from the second invoice, and paste it in the :guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Then, sign the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:625 -msgid "While the CFDI 4.0 requirements ask you to add a valid zip code in your contact, the external trade complement adds as a mandatory field the :guilabel:`City` and the :guilabel:`State`. All three fields must coincide with the `Official SAT Catalog `_ or you will receive an error." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:622 +msgid "With this, all electronic documents are linked to each other. The final step is to fully pay the new invoice. At the bottom of the new invoice, you can find the credit note in the :guilabel:`Outstanding credits` - add it as payment. Finally, register the remaining amount with the :guilabel:`Register Payment` wizard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:628 +msgid "External trade" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:630 -msgid "Add the :guilabel:`City` and :guilabel:`State` in the company's contract, not in the company itself. You can find your company's contact in :menuselection:`Accounting --> Customers --> Customers`" +msgid "The external trade is a complement to a regular invoice that adds certain values in both the XML and PDF, to invoices with a foreign customer according to `SAT regulations `_, such as:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:634 -msgid "The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and can be added in the company directly in :menuselection:`Settings --> General Settings --> Companies`. These two have to coincide with the data in the SAT." +msgid "The specific address of the receiver and the sender" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Optional External Trade Company fields." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 +msgid "The addition of a :guilabel:`Tariff Fraction` that identifies the type of product" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:641 -msgid "The contact data for the foreign receiving client must have the following fields completed to avoid errors:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:636 +msgid "The correct :guilabel:`Incoterm` (International Commercial Terms), among others (*certificate of origin* and *special units of measure*)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:644 -msgid "The entire company :guilabel:`Address`, including a valid :guilabel:`ZIP` code and the foreign :guilabel:`Country`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:639 +msgid "This allows the correct identification of exporters and importers, in addition to expanding the description of the merchandise sold." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:646 -msgid "The format of the foreign :guilabel:`VAT` (tax identification number, for example: Colombia `123456789-1`)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:642 +msgid "Since January 1, 2018, external trade is a requirement for taxpayers, who carry export operations of type A1. While the current CFDI is 4.0, the external trade is currently on version 1.1" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:648 -msgid "In the :guilabel:`MX EDI` tab, you need to address if the customer receives goods for a period of time temporarily (:guilabel:`Temporary`) or permanently (:guilabel:`Definitive`)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:645 +msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended` and :guilabel:`l10n_mx_edi_extended_40` have to be installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:650 -msgid "If you create this contact based in another from Mexico, make sure that you delete any information in the field :guilabel:`Fiscal Regime`. Do not use :guilabel:`No Tax Breakdown` either." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Required External Trade Customer fields." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:649 +msgid "Before installing, make sure your business needs to use this feature. Consult your accountant first, if needed, before installing any modules." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:658 -msgid "In the resulting XML and PDF, the :guilabel:`VAT` is automatically replaced by the generic VAT for abroad transactions: `XEXX010101000`." +msgid "To configure your company contact for external trade, navigate to :menuselection:`Accounting --> Customers --> Customers`, and select your :guilabel:`Company`. While the CFDI 4.0 requirements ask you to add a valid :guilabel:`ZIP` code in your contact, the external trade complement adds the requirement that your :guilabel:`City` and the :guilabel:`State` must also be valid. All three fields must coincide with the `Official SAT Catalog `_, or you will receive an error." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:664 -msgid "All products involved with external trade must fill four fields, two of them exclusive to this feature." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:667 -msgid "The :guilabel:`Internal Reference` of the product is in the :guilabel:`General Information` tab." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:668 -msgid "The :guilabel:`Weight` of the product must be more than `0`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:665 +msgid "Add the :guilabel:`City` and :guilabel:`State` in the company's *contact*, not in the company itself. You can find your company's contact in :menuselection:`Accounting --> Customers --> Customers`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:669 +msgid "The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and can be added in the company directly in :menuselection:`Settings --> General Settings --> Companies`. These two fields have to coincide with the data in the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Optional external trade company fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 +msgid "To configure the contact data for a foreign receiving client, navigate to :menuselection:`Accounting --> Customers --> Customers`, and select the foreign client's contact. The contact must have the following fields completed to avoid errors:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:681 +msgid "The entire company :guilabel:`Address`, including a valid :guilabel:`ZIP` code and the foreign :guilabel:`Country`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:683 +msgid "The format of the foreign :guilabel:`VAT` (tax identification number, for example: Colombia `123456789-1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 +msgid "In the :guilabel:`MX EDI` tab, you need to address if the customer receives goods for a period of time temporarily (:guilabel:`Temporary`) or permanently (:guilabel:`Definitive`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:689 +msgid "If the new contact was created by duplicating another existing contact from Mexico, make sure to delete any carried over information from the :guilabel:`Fiscal Regime` field. In addition, do not enable the :guilabel:`No Tax Breakdown` option. Selecting this option hides mandatory fields that are required for external trade contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Required external trade customer fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:699 +msgid "In the resulting XML and PDF files, the :guilabel:`VAT` is automatically replaced by the generic VAT for abroad transactions: `XEXX010101000`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:705 +msgid "All products involved with external trade have four fields that are required, two of them exclusive to external trade." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:708 +msgid "The :guilabel:`Internal Reference` of the product is in the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 +msgid "The :guilabel:`Weight` of the product must be more than `0`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:710 msgid "The `correct `_ :guilabel:`Tariff Fraction` of the product in the :guilabel:`Accounting` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:671 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:712 msgid "The :guilabel:`UMT Aduana` corresponds to the :guilabel:`Tariff Fraction`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Required External Trade Product fields." +msgid "Required external trade product fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:719 msgid "If the UoM code of the :guilabel:`Tariff Fraction` is `01`, the correct :guilabel:`UMT Aduana` is `kg`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:679 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:721 msgid "If the UoM code of the :guilabel:`Tariff Fraction` is `06`, the correct :guilabel:`UMT Aduana` is `Units`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:683 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:725 msgid "Invoicing flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 -msgid "Before creating an invoice, it is important to take into account that external trade invoices require to convert the amounts of your product into USD. Therefore, we need to have :doc:`multicurrency enabled ` and activate USD in the :guilabel:`Currencies` section. The correct :guilabel:`Service` to run is :guilabel:`Mexican Bank`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:727 +msgid "Before creating an invoice, it is important to take into account that external trade invoices require to convert the amounts of your product into USD. Therefore, :doc:`multicurrency <../accounting/get_started/multi_currency>` **must** be enabled and *USD* **must** be activated in the :guilabel:`Currencies` section. The correct :guilabel:`Service` to run is :guilabel:`Mexican Bank`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:691 -msgid "With the correct exchange rate set up in :menuselection:`Accounting --> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` and :guilabel:`Certificate Source` in the :guilabel:`Other Info` tab. The latter is optional." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:733 +msgid "Then, with the correct exchange rate set up in :menuselection:`Accounting --> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` and the optional :guilabel:`Certificate Source` in the :guilabel:`Other Info` tab." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "External Trade Other Info." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:698 -msgid "Sign the invoice with the same process as a regular one: Press the :guilabel:`Process Now` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:701 -msgid "Delivery guide" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 -msgid "A `Carta Porte `_ is a bill of lading: a document that states the type, quantity, and destination of goods being carried." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:706 -msgid "On December 1st, 2021, version 2.0 of this CFDI was implemented for all transportation providers, intermediaries, and owners of goods. Odoo is able to generate a document type \"T\" (Traslado) which, unlike other documents, is created in a delivery order instead of an invoice or payment." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:710 -msgid "Odoo can create XML and PDF files with or without ground transport and can process materials that are treated as *Dangerous Hazards*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:713 -msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, :guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and :guilabel:`l10n_mx_edi_stock_40` have to be installed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:717 -msgid "In addition to this, it is necessary to have the :doc:`Inventory ` and :doc:`Sales ` apps configured." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:722 -msgid "Odoo does not support Carta Porte type \"I\" (Ingreso), air, or marine transport. Consult your accountant first if this feature is needed before doing any modifications." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:728 -msgid "Odoo manages two different types of CFDI:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:730 -msgid "**No Federal Highways**: It is used when the *Distance to Destination* is `less than 30 KM `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:732 -msgid "**Federal Transport**: It is used when the *Distance to Destination* exceeds 30 KM." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:734 -msgid "Other than the standard requirements of regular invoicing (The RFC of the customer, the UNSPSC code...), if you are using *No Federal Highways*, no external configuration is needed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:737 -msgid "For *Federal Transport*, several configurations have to be added to contacts, vehicle setups, and products. Those configurations are added to the XML and PDF files." +msgid "External trade Other Info tab of a product." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:741 -msgid "Contacts and vehicles" +msgid "Finally, sign the invoice with the same process as a regular invoice, and click the :guilabel:`Process Now` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:743 -msgid "Like with the external trade feature, the address in both your company and your final customer has to be complete. The zip code, city, and state must coincide with the `Official SAT Catalog `_" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:747 +msgid "A `Carta Porte `_ is a bill of lading: a document that states the type, quantity, and destination of goods being carried." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:748 -msgid "The field :guilabel:`Locality` is optional for both addresses." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide Contacts." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:750 +msgid "On December 1st, 2021, version 2.0 of this CFDI was implemented for all transportation providers, intermediaries, and owners of goods. Odoo is able to generate a document type \"T\" (Traslado), which, unlike other documents, is created in a delivery order instead of an invoice or payment." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:754 -msgid "The origin address used for the delivery guide is set in :menuselection:`Inventory --> Configuration --> Warehouses Management --> Warehouses`. While this is set as the company address by default, you can change it according to your correct warehouse address." +msgid "Odoo can create XML and PDF files with (or without) ground transport, and can process materials that are treated as *Dangerous Hazards*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:758 -msgid "Another addition to this feature is the :guilabel:`Vehicle Setups` menu found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets you add all the information related to the vehicle used for the delivery order." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:757 +msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, :guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and :guilabel:`l10n_mx_edi_stock_40` have to be installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:762 -msgid "All fields are mandatory to create a correct delivery guide." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:761 +msgid "In addition to this, it is necessary to have the :doc:`Inventory <../../inventory_and_mrp/inventory>` and :doc:`Sales <../../sales/sales>` apps installed, as well." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide Vehicle Configurations required fields." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:765 +msgid "Odoo does not support Carta Porte type document type \"I\" (Ingreso), air, or marine transport. Consult your accountant first if this feature is needed before doing any modifications." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:767 -msgid "In the :guilabel:`Intermediaries` section, you need to add the operator of the vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` and :guilabel:`Operator Licence`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:771 +msgid "Odoo manages two different types of CFDI:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:773 -msgid "Like with regular invoicing, all products must have a :guilabel:`UNSPSC category`. In addition to this, there are two extra configurations for products involved in delivery guides:" +msgid "**No Federal Highways**: Is used when the *Distance to Destination* is `less than 30 KM `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:776 -msgid "The :guilabel:`Product Type` must be set as :guilabel:`Storable Product` for stock movements to be created." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:775 +msgid "**Federal Transport**: Is used when the *Distance to Destination* exceeds 30 KM." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:778 -msgid "In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have more than 0." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:777 +msgid "Other than the standard requirements of regular invoicing (The |RFC| of the customer, the UNSPSC code, etc.), if you are using *No Federal Highways*, no external configuration is needed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide Product Configurations." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:780 +msgid "For *Federal Transport*, several configurations have to be added to contacts, vehicle setups, and products. Those configurations are added to the XML and PDF files." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:784 -msgid "Sales and inventory flow" +msgid "Contacts and vehicles" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:786 -msgid "To create a delivery guide, first, you need to create and confirm a sales order. This generates a :guilabel:`Delivery` smart button. Press it and :guilabel:`Validate` the transfer." +msgid "Like the external trade feature, the :guilabel:`Address` in both the company and the final customer must be complete. The :guilabel:`ZIP` code, :guilabel:`City`, and :guilabel:`State` must coincide with the `Official SAT Catalog for Carta Porte _`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:789 -msgid "After the status is set to :guilabel:`Done`, you can edit the transfer and select the :guilabel:`Transport Type` (either :guilabel:`No Federal Highways` or :guilabel:`Federal Transport`)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:793 -msgid "If your delivery guide has the type :guilabel:`No Federal Highways`, you can save the transfer and then press :guilabel:`Generate Delivery Guide`. The resulting XML can be found in the chatter." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:797 -msgid "Other than the :guilabel:`UNSPSC` in all products, delivery guides that use :guilabel:`No Federal Highways` do not require any special configuration to be sent to the government." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:800 -msgid "If your delivery guide has the type :guilabel:`Federal Transport`, the tab :guilabel:`MX EDI` appears. In there, write a value in :guilabel:`Distance to Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` used for this delivery." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:791 +msgid "The field, :guilabel:`Locality`, is optional for both addresses." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide MX EDI tab configuration." +msgid "Delivery guide contact configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:808 -msgid "Dangerous hazards" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:798 +msgid "The origin address used for the delivery guide is set in :menuselection:`Inventory --> Configuration --> Warehouses Management --> Warehouses`. While this is set as the company address by default, you can change it according to your correct warehouse address." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:810 -msgid "Certain values in the :guilabel:`UNSPSC Category` are considered in the `official SAT catalog `_ as dangerous hazards. These categories need additional considerations when creating a delivery guide with :guilabel:`Federal Transport`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:802 +msgid "Another addition to this feature is the :guilabel:`Vehicle Setups` menu found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets you add all the information related to the vehicle used for the delivery order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:815 -msgid "In the product, the fields :guilabel:`Hazardous Material Designation Code (MX)` and :guilabel:`Hazardous Packaging (MX)` must be filled with the correct code from the |SAT| catalog." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:806 +msgid "All fields are mandatory to create a correct delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:818 -msgid "In the vehicle setup, the data from the :guilabel:`Environment Insurer` and :guilabel:`Environment Insurance Policy` has to be filed too." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:809 +msgid "The fields, :guilabel:`Vehicle Plate Number` and :guilabel:`Number Plate`, must contain between 5 to 7 characters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:812 +msgid "In the :guilabel:`Intermediaries` section, you must add the operator of the vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` and :guilabel:`Operator Licence`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide environment required fields." +msgid "Delivery guide vehicle configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:824 -msgid "After this, continue with the regular process to create a delivery guide." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 +msgid "Similar to regular invoicing, all products must have a :guilabel:`UNSPSC category`. In addition to this, there are two extra configurations for products involved in delivery guides:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:825 +msgid "The :guilabel:`Product Type` must be set as :guilabel:`Storable Product` for stock movements to be created." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:827 -msgid "Customs numbers" +msgid "In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have more than `0`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:829 -msgid "A *customs declaration* (Pedimento Aduanero) is a fiscal document that certifies that all contributions to the fiscal entity (the |SAT|) has been paid, for the import/export of goods." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:830 +msgid "Creating a delivery guide of a product with the value `0` will trigger an error. As the :guilabel:`Weight` has been already stored in the delivery order, it is needed to return the products, and create the delivery order (and delivery guide) again with the correct amounts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:832 -msgid "According to the `Annex 20 `_ of CFDI 4.0, in documents where the invoiced goods come from a first-hand import operation, the field :guilabel:`Customs Number` needs to be added to all lines of products involved with the operation." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery guide product configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:836 -msgid "For this, the module :guilabel:`l10n_mx_edi_landing` has to be installed, in addition to the :doc:`Inventory `, :doc:`Purchase ` and :doc:`Sales ` apps configured." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:839 +msgid "Sales and inventory flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:842 -msgid "Do not confuse this feature with external trade. The customs numbers are directly related to importing goods, while the external trade complement is related to exporting. Consult your accountant first if this feature is needed before doing any modifications." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:841 +msgid "To create a delivery guide, first, you need to create and confirm a sales order from :menuselection:`Sales --> Sales Order`. This generates a :guilabel:`Delivery` smart button. Click it, and :guilabel:`Validate` the transfer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:845 +msgid "After the status is set to :guilabel:`Done`, you can edit the transfer, and select the :guilabel:`Transport Type` (either :guilabel:`No Federal Highways` or :guilabel:`Federal Transport`)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 -msgid "In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs `. Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that :guilabel:`Landed Costs` is activated." +msgid "If your delivery guide has the type :guilabel:`No Federal Highways`, you can save the transfer, and then click :guilabel:`Generate Delivery Guide`. The resulting XML can be found in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:854 -msgid "First, a *service*-type product called `Pedimento` has to be created. In the :guilabel:`Purchase` tab, check :guilabel:`Is a Landed Cost` and select a :guilabel:`Default Split Method`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:853 +msgid "Other than the :guilabel:`UNSPSC` in all products, delivery guides that use :guilabel:`No Federal Highways` do not require any special configuration to be sent to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:857 -msgid "After this, we need to configure the *storable products* that holds the customs numbers. We need to make sure that the product category has the following configuration:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:856 +msgid "If your delivery guide has the type, :guilabel:`Federal Transport`, the tab :guilabel:`MX EDI` appears. There, enter a value in :guilabel:`Distance to Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` used for this delivery." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:860 -msgid ":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:861 -msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:862 -msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:863 -msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:864 -msgid ":guilabel:`Stock Input Account`: :guilabel:`115.05.01 MercancĆ­as en trĆ”nsito`" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery guide MX EDI tab configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 +msgid "Dangerous hazards" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:867 +msgid "Certain values in the :guilabel:`UNSPSC Category` are considered in the `official SAT catalog `_ as *dangerous hazards*. These categories need additional considerations when creating a delivery guide with :guilabel:`Federal Transport`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:872 +msgid "First, select your product from :menuselection:`Inventory --> Products --> Products`. Then, in the :guilabel:`Accounting` tab, the fields :guilabel:`Hazardous Material Designation Code (MX)` and :guilabel:`Hazardous Packaging (MX)` must be filled with the correct code from the |SAT| catalog." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery guide hazardous material product required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:880 +msgid "In :menuselection:`Inventory --> Settings --> Mexico --> Vehicle Setup`, the data from the :guilabel:`Environment Insurer` and :guilabel:`Environment Insurance Policy` has to be filed, as well. After this, continue with the regular process to create a delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery Guide environment insurer required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:889 +msgid "Customs numbers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:891 +msgid "A *customs declaration* (Pedimento Aduanero) is a fiscal document that certifies that all contributions to the fiscal entity (the |SAT|) has been paid for, including the import/export of goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:895 +msgid "According to the `Annex 20 `_ of CFDI 4.0, in documents where the invoiced goods come from a first-hand import operation, the field, :guilabel:`Customs Number`, needs to be added to all lines of products involved with the operation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:899 +msgid "To do so, the module :guilabel:`l10n_mx_edi_landing` must be installed, in addition to the :doc:`Inventory <../../inventory_and_mrp/inventory>`, :doc:`Purchase <../../inventory_and_mrp/purchase>` and :doc:`Sales <../../sales/sales>` apps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:904 +msgid "Do not confuse this feature with external trade. The customs numbers are directly related to importing goods, while the external trade complement is related to exporting. Consult your accountant first if this feature is needed before doing any modifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:911 +msgid "In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs <../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs>`. Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that :guilabel:`Landed Costs` is activated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +msgid "Begin by creating a *service*-type product called, `Pedimento`. In the :guilabel:`Purchase` tab, activate :guilabel:`Is a Landed Cost`, and select a :guilabel:`Default Split Method`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 +msgid "Then, configure the *storable products* that hold the customs numbers. To do so, create the storable products, and make sure the :guilabel:`Product Category` has the following configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:922 +msgid ":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:923 +msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 +msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:925 +msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:926 +msgid ":guilabel:`Stock Input Account`: :guilabel:`115.05.01 MercancĆ­as en trĆ”nsito`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:927 msgid ":guilabel:`Stock Output Account`: :guilabel:`115.05.01 MercancĆ­as en trĆ”nsito`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Storable products configurations." +msgid "Storable products general configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:871 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Storable product category configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:938 msgid "Purchase and sales flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:873 -msgid "Create a :guilabel:`Purchase Order`, and confirm the order. This should trigger a :guilabel:`Receipt` smart button. Validate the receipt too." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:940 +msgid "After you configure your product, follow the standard :doc:`purchase flow <../../inventory_and_mrp/purchase>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Customs Number Purchase." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:943 +msgid "Create a purchase order from :menuselection:`Purchase --> Orders --> Purchase Order`. Then, confirm the order to display a :guilabel:`Receipt` smart button. Click on the :guilabel:`Receipt` smart button to :guilabel:`Validate` the receipt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:879 -msgid "Go to :menuselection:`Inventory --> Operations --> Landed Costs` and create a new record. Add the transfer that you just created, and both the product `Pedimento` and :guilabel:`Customs number`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 +msgid "Go to :menuselection:`Inventory --> Operations --> Landed Costs`, and create a new record. Add the transfer that you just created, and both: the product `Pedimento` and :guilabel:`Customs number`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:882 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:950 msgid "Optionally, you can add a cost amount. After this, validate the landed cost. Once :guilabel:`Posted`, all products related to that receipt have the customs number assigned." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:886 -msgid "You can only add the Pedimentos number once, so be careful when associating the correct number with the transfer(s)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:954 +msgid "You can only add the *Pedimentos* number **once**, so be careful when associating the correct number with the transfer(s)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Customs number Inventory." +msgid "Customs number on a landed costs Inventory record." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:892 -msgid "Now, create a sales order and confirm it. This should trigger a :guilabel:`Delivery` smart button. Validate it." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:961 +msgid "Now, create a sales order, and confirm it. This should trigger a :guilabel:`Delivery` smart button. Validate it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:895 -msgid "Finally, create an invoice from the sales order and confirm it. The invoice line related to your product has a customs number in it." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:964 +msgid "Finally, create an invoice from the sales order, and confirm it. The invoice line related to your product has a customs number in it. This number should match the customs number added in the *Landed Costs* record you created earlier." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Customs number on confirmed sales order product." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:902 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:973 msgid "Electronic accounting" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:904 -msgid "For Mexico, `Electronic Accounting `_ refers to the obligation to keep accounting records and entries through electronic means and to enter accounting information on a monthly basis through the SAT's website." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:975 +msgid "For Mexico, `Electronic Accounting `_ refers to the obligation to keep accounting records and entries through electronic means, and to enter accounting information on a monthly basis, through the |SAT| website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:909 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:980 msgid "It consists of three main XML files:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:911 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:982 msgid "The updated list of the chart of accounts that you are currently using." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:912 -msgid "A monthly trial balance, plus a closing entry report also known as *Trial Balance Month 13*." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:983 +msgid "A monthly trial balance, plus a closing entry report, also known as: *Trial Balance Month 13*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:913 -msgid "Either optional or for a compulsory audit, an export of the journal entries in your general ledger." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:984 +msgid "Either optional, or for a compulsory audit, an export of the journal entries in your general ledger." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:987 msgid "The resulting XML files follow the requirements of the `Anexo TĆ©cnico de Contabilidad ElectrĆ³nica 1.3 `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 -msgid "In addition to this, you can generate the `DIOT `_: A report of vendor's journal entries that involves IVA taxes that can be exported in :file:`.txt` file." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 -msgid "In order to use these reports, the modules :guilabel:`l10n_mx_reports`, :guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and :guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the :doc:`Accounting `." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:929 -msgid "You can find all of those reports in :menuselection:`Accounting --> Reporting --> Mexico`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:932 -msgid "The specific characteristics and obligations of the reports that you send might change according to your fiscal regime. Always contact your accountant before sending any documents to the government." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:937 -msgid "CatĆ”logo de cuentas (chart of accounts)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:939 -msgid "The :doc:`chart of accounts ` in MĆ©xico follows a specific pattern based in SAT's `CĆ³digo agrupador de cuentas `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:943 -msgid "You can create any account as long as it respects |SAT|'s encoding group, This pattern is `NNN.YY.ZZ` or `NNN.YY.ZZZ`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 -msgid "Some examples are `102.01.99` or `401.01.001`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:949 -msgid "When you create a new account in :menuselection:`Accounting --> Configuration --> Chart of Accounts`, if you follow this pattern, you get the correct grouping code in :guilabel:`Tags`, and your account appears in the COA report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:953 -msgid "Once you created all your accounts, and made sure that you put the correct :guilabel:`Tags` in them." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:956 -msgid "You cannot use any pattern that ends a section with a 0 (such as `100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:959 -msgid "Once all is set up, you can go to :menuselection:`Accounting --> Reporting --> Mexico --> COA` and press the button :guilabel:`SAT (XML)`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:963 -msgid "Balanza de comprobaciĆ³n (trial balance)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:965 -msgid "The trial balance reports the initial balance, credit, and total balance of your accounts, provided that you added their correct encoding group." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:968 -msgid "This report can be generated monthly, and an XML file version is created if you go to :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance` and press the button :guilabel:`SAT (XML)`. Select the month you want to download beforehand." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Trial Balance Report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:976 -msgid "Odoo does not generate the *Balanza de ComprobaciĆ³n Complementaria*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:978 -msgid "An additional report is the *Month 13*: a closing balance sheet that shows any adjustments or movements made in the accounting to close the year." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:981 -msgid "In order to be able to generate this XML document, you have to go to :menuselection:`Accounting --> Accounting --> Miscellaneous --> Journal Entries` and create a new document. Here, you can add all amounts that you want to modify, and you can balance the debit and/or credit of each one." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:985 -msgid "After this is done, press :guilabel:`Mark as Closing Entry`, and the report found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance Month 13` contains the total amount of the year, plus all the additions of the journal entry." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:989 -msgid "You can generate the XML file by pressing the button :guilabel:`SAT (XML)`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Trial Balance Month 13 Setup." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:990 +msgid "In addition to this, you can generate the `DIOT `_: A report of vendor's journal entries that involve IVA taxes that can be exported in a :file:`.txt` file." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:995 -msgid "PĆ³lizas (general ledger)" +msgid "In order to use these reports, the modules :guilabel:`l10n_mx_reports`, :guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and :guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the :doc:`Accounting <../accounting/get_started>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:997 -msgid "By law, all transactions in Mexico must be recorded digitally. Because Odoo automatically creates all the underlying journal entries of your invoicing and payments, you can export your journal entries to comply with SAT's audits or tax refunds." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1000 +msgid "You can find the *Chart of accounts*, *Trial Balance Month 13*, and *DIOT* reports in :menuselection:`Accounting --> Reporting --> Mexico`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1001 -msgid "This XML file is created in :menuselection:`Accounting --> Reporting --> Audit Reports --> General Ledger`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1004 +msgid "The specific characteristics and obligations of the reports that you send might change according to your fiscal regime. Always contact your accountant before sending any documents to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1005 -msgid "You can filter by period or by journal, according to your current needs." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1013 +msgid "The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` in MĆ©xico follows a specific pattern based on |SAT|'s' `CĆ³digo agrupador de cuentas `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1007 -msgid "After you press :guilabel:`XML (Polizas)`, a wizard appears. In here, you can select between four types of :guilabel:`Export type`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1017 +msgid "You can create any account, as long as it respects |SAT|'s encoding group: the pattern is `NNN.YY.ZZ` or `NNN.YY.ZZZ`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1010 -msgid "For :guilabel:`Tax audit` or :guilabel:`Audit certification`, you need to write the :guilabel:`Order Number` provided by the |SAT| for :guilabel:`Return of goods` or :guilabel:`Compensation`, you need to write your :guilabel:`Process Number`, also provided by the |SAT|." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1021 +msgid "Some examples are `102.01.99` or `401.01.001`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Types of Polizas." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1023 +msgid "When a new account is created in :menuselection:`Accounting --> Configuration --> Chart of Accounts`, with the |SAT| encoding group pattern, the correct grouping code appears in :guilabel:`Tags`, and your account appears in the *COA* report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1018 -msgid "If you want to see this report without sending it, use `ABC6987654/99` for :guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process Number`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1027 +msgid "Once you create all your accounts, make sure the correct :guilabel:`Tags` are added." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1022 -msgid "DIOT report" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1024 -msgid "The DIOT (DeclaraciĆ³n Informativa de Operaciones con Terceros / *Informative Declaration of Operations with Third Parties*) is an additional obligation with the |SAT|, where we give the current status of our creditable and non-creditable payments, withholdings and refunds of VAT from your vendor bills." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1029 -msgid "Unlike other reports, this is uploaded to a software provided by the |SAT| that contains the A-29 form. In Odoo, you can download the records of your transactions in a :file:`.txt` file that you can upload to the form, avoiding direct capture of this data." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1030 +msgid "You cannot use any pattern that ends a section with a 0 (such as `100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the report." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 -msgid "This file contains the total amount of your payments registered in vendor bills, broken down into the corresponding types of IVA. The :guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors." +msgid "Once everything is set up, you can go to :menuselection:`Accounting --> Reporting --> Mexico --> COA`, and click the :guilabel:`SAT (XML)` button to generate an XML file containing all of your accounts, which will be ready to upload to the |SAT| website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 -msgid "To get the report, go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third parties [DIOT]`. Select the month that suits you, and press :guilabel:`DIOT (TXT)` to download the :file:`.txt` file." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1040 +msgid "The trial balance reports the initial balance, credit, and total balance of your accounts, provided that you added their correct :ref:`encoding group `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1043 +msgid "This report can be generated monthly, and a corresponding XML file is created, if you go to :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance`, and click the :guilabel:`SAT (XML)` button. Select the month you want to download beforehand." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "DIOT Example." +msgid "Trial balance report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1045 -msgid "You need to fill the field :guilabel:`L10N Mx Type of Operation` in the :guilabel:`Accounting` tab of each one of your vendors to prevent validation errors. Make sure that your foreign customers have their country set up for :guilabel:`L10N Mx Nationality` to appear automatically." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1052 +msgid "Odoo does not generate the *Balanza de ComprobaciĆ³n Complementaria*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1054 +msgid "An additional report is the *Month 13*: a closing balance sheet that shows any adjustments or movements made in the accounting to close the year." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1057 +msgid "To generate this XML document, navigate to :menuselection:`Accounting --> Accounting --> Miscellaneous --> Journal Entries`, and create a new document. Here, add all amounts to modify, and balance the debit and/or credit of each one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1061 +msgid "After this is done, click :guilabel:`Mark as Closing Entry`, and the report found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance Month 13`, contains the total amount of the year, plus all the additions of the journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1065 +msgid "The XML file is generated by pressing the :guilabel:`SAT (XML)` button." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "DIOT Example contact." +msgid "Trial Balance Month 13 setup." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Trial Balance Month 13 report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1078 +msgid "By law, all transactions in Mexico must be recorded digitally. Since Odoo automatically creates all the underlying journal entries of your invoicing and payments, you can export your journal entries to comply with |SAT|'s audits and/or tax refunds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1083 +msgid "You can filter by period, or by journal, according to your current needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1085 +msgid "To create the XML, go to :menuselection:`Accounting --> Reporting --> Audit Reports --> General Ledger`, and click :guilabel:`XML (Polizas)`. Here, you can select between four types of :guilabel:`Export` types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1089 +msgid ":guilabel:`Tax audit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1090 +msgid ":guilabel:`Audit certification`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1091 +msgid ":guilabel:`Return of goods`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1092 +msgid ":guilabel:`Compensation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1094 +msgid "For :guilabel:`Tax audit`, or :guilabel:`Audit certification`, you need to write the :guilabel:`Order Number` provided by the |SAT|. For :guilabel:`Return of goods`, or :guilabel:`Compensation`, you need to write your :guilabel:`Process Number`, also provided by the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1100 +msgid "If you want to see this report without sending it, use `ABC6987654/99` for :guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1104 +msgid "DIOT report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1106 +msgid "The DIOT (DeclaraciĆ³n Informativa de Operaciones con Terceros / *Informative Declaration of Operations with Third Parties*) is an additional obligation with the |SAT|, where the current status of creditable and non-creditable payments, withholdings, and refunds of VAT from your vendor bills, are provided to the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1111 +msgid "Unlike other reports, the |DIOT| is uploaded to a software provided by the |SAT| that contains the A-29 form. In Odoo, you can download the records of your transactions as a :file:`.txt` file that can be uploaded to the form, avoiding direct capture of this data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1115 +msgid "The transactions file contains the total amount of your payments registered in vendor bills, broken down into the corresponding types of IVA. The :guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1119 +msgid "To get the |DIOT| report, go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third parties [DIOT]`. Select the month that suits you, and click :guilabel:`DIOT (TXT)` to download the :file:`.txt` file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "A Vendor Bill that is In Payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "DIOT (TXT) download button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1132 +msgid "You need to fill the field, :guilabel:`L10N Mx Type of Operation`, in the :guilabel:`Accounting` tab of each one of your vendors to prevent validation errors. Make sure that your foreign customers have their country set up for :guilabel:`L10N Mx Nationality` to appear automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "DIOT information on a vendor contact." msgstr "" #: ../../content/applications/finance/fiscal_localizations/netherlands.rst:3 @@ -20774,8 +21526,8 @@ msgstr "" msgid "The chart of accounts is installed by default as part of the set of data included in the localization module, the accounts are mapped automatically in:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:75 -msgid "Default Account Receivable" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:74 +msgid "Default Account Payable." msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst:77 @@ -21031,6 +21783,10 @@ msgstr "" msgid "Taxes EDI data for Peru" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:268 +msgid "Fiscal Positions" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/peru.rst:270 msgid "There are two main fiscal positions included by default when you install the Peruvian localization." msgstr "" @@ -21043,6 +21799,10 @@ msgstr "" msgid "**Local Peru**: Set this fiscal position on local customers." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:277 +msgid "Document Types" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/peru.rst:279 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 "" @@ -21091,6 +21851,10 @@ msgstr "" msgid "By default, the value Factur-X (FR) is always displayed, make sure you can uncheck it manually." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:328 +msgid "Identification Type and VAT" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/peru.rst:330 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 "" @@ -21189,6 +21953,10 @@ msgstr "" 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/fiscal_localizations/peru.rst:429 +msgid "Common Errors" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/peru.rst:431 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 "" @@ -21213,6 +21981,10 @@ msgstr "" msgid "For more detail please refert to `Common errors in SUNAT `_." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:453 +msgid "Invoice PDF Report" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/peru.rst:455 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 "" @@ -21346,6 +22118,10 @@ msgstr "" msgid "Detraction code on invoices." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:558 +msgid "Credit Notes" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/peru.rst:560 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 "" @@ -21374,6 +22150,10 @@ msgstr "" msgid "The EDI workflow for the Credit notes works in the same way as the invoices." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/peru.rst:585 +msgid "Debit Notes" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/peru.rst:587 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 "" @@ -22085,6 +22865,17 @@ msgstr "" msgid "TVA 7.7%" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Purchases" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 @@ -23337,7 +24128,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/demo.rst:12 #: ../../content/applications/finance/payment_providers/mollie.rst:11 #: ../../content/applications/finance/payment_providers/ogone.rst:9 -#: ../../content/applications/finance/payment_providers/paypal.rst:92 +#: ../../content/applications/finance/payment_providers/paypal.rst:97 #: ../../content/applications/finance/payment_providers/sips.rst:12 #: ../../content/applications/finance/payment_providers/stripe.rst:12 msgid ":ref:`payment_providers/add_new`" @@ -23352,7 +24143,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/flutterwave.rst:44 #: ../../content/applications/finance/payment_providers/mercado_pago.rst:36 #: ../../content/applications/finance/payment_providers/mollie.rst:31 -#: ../../content/applications/finance/payment_providers/paypal.rst:156 +#: ../../content/applications/finance/payment_providers/paypal.rst:161 #: ../../content/applications/finance/payment_providers/razorpay.rst:46 #: ../../content/applications/finance/payment_providers/sips.rst:32 #: ../../content/applications/finance/payment_providers/stripe.rst:133 @@ -24237,7 +25028,7 @@ msgid "To allow your customers to save their credit card credentials for future msgstr "" #: ../../content/applications/finance/payment_providers/ogone.rst:103 -#: ../../content/applications/finance/payment_providers/paypal.rst:89 +#: ../../content/applications/finance/payment_providers/paypal.rst:94 msgid "Settings in Odoo" msgstr "" @@ -24254,10 +25045,14 @@ msgid "`Paypal `_ is an American online payment provide msgstr "" #: ../../content/applications/finance/payment_providers/paypal.rst:9 +msgid "While PayPal is available in `over 200 countries/regions `_, only `a selection of currencies are supported `_." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:14 msgid "Settings in PayPal" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:11 +#: ../../content/applications/finance/payment_providers/paypal.rst:16 msgid "To access your PayPal account settings, log into PayPal, open the :guilabel:`Account Settings`, and open the :guilabel:`Website payments` menu." msgstr "" @@ -24265,151 +25060,151 @@ msgstr "" msgid "PayPal account menu" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:19 +#: ../../content/applications/finance/payment_providers/paypal.rst:24 msgid "Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return `, :ref:`PDT `, and :ref:`IPN ` **must** all be enabled." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:25 +#: ../../content/applications/finance/payment_providers/paypal.rst:30 msgid "Auto Return" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:27 +#: ../../content/applications/finance/payment_providers/paypal.rst:32 msgid "The **Auto Return** feature automatically redirects customers to Odoo once the payment is processed." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:29 +#: ../../content/applications/finance/payment_providers/paypal.rst:34 msgid "From :guilabel:`Website payments`, go to :menuselection:`Website preferences --> Update --> Auto return for website payments --> Auto return` and select :guilabel:`On`. Enter the address of your Odoo database (e.g., `https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:35 +#: ../../content/applications/finance/payment_providers/paypal.rst:40 msgid "Any URL does the job. Odoo only needs the setting to be enabled since it uses another URL." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:40 +#: ../../content/applications/finance/payment_providers/paypal.rst:45 msgid "Payment Data Transfer (PDT)" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:42 +#: ../../content/applications/finance/payment_providers/paypal.rst:47 msgid ":abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations, displays the payment status to the customers, and verifies the authenticity of the payments. From :menuselection:`Website preferences --> Update`, scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:47 +#: ../../content/applications/finance/payment_providers/paypal.rst:52 msgid "PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return ` and :ref:`Payment Data Transfer (PDT) ` are enabled. If you need the **PDT Identity Token**, disable and re-enable :guilabel:`Payment data transfer` to display the token again." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:54 +#: ../../content/applications/finance/payment_providers/paypal.rst:59 msgid "Instant Payment Notification (IPN)" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:56 +#: ../../content/applications/finance/payment_providers/paypal.rst:61 msgid ":abbr:`IPN (Instant Payment Notifications)` is similar to **PDT**, but allows for more notifications, such as chargeback notifications. To enable **IPN**, go to :menuselection:`Website payments --> Instant payment notifications --> Update` and click :guilabel:`Choose IPN settings`. Enter a :guilabel:`Notification URL`, select :guilabel:`Receive IPN messages (Enabled)`, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:63 +#: ../../content/applications/finance/payment_providers/paypal.rst:68 msgid "PayPal Account Optional" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:65 +#: ../../content/applications/finance/payment_providers/paypal.rst:70 msgid "We advise not to prompt customers to log in with a PayPal account upon payment. It is better and more accessible for customers to pay with a debit/credit card. To disable that prompt, go to :menuselection:`Account Settings --> Website payments --> Update` and select :guilabel:`On` for :guilabel:`PayPal account optional`." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:71 +#: ../../content/applications/finance/payment_providers/paypal.rst:76 msgid "Payment Messages Format" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:73 +#: ../../content/applications/finance/payment_providers/paypal.rst:78 msgid "If you use accented characters (or anything other than primary Latin characters) for customer names or addresses, then you **must** configure the encoding format of the payment request sent by Odoo to PayPal. If you do not, some transactions fail without notice." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:77 +#: ../../content/applications/finance/payment_providers/paypal.rst:82 msgid "To do so, go to `your production account `_. Then, click :guilabel:`More Options` and set the two default encoding formats as :guilabel:`UTF-8`." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:82 +#: ../../content/applications/finance/payment_providers/paypal.rst:87 msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `Paypal documentation `_." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:84 +#: ../../content/applications/finance/payment_providers/paypal.rst:89 msgid "Configure your :ref:`Paypal Sandbox account `, then follow this `link `_ to configure the encoding format in a test environment." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:95 +#: ../../content/applications/finance/payment_providers/paypal.rst:100 msgid "Credentials" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:97 +#: ../../content/applications/finance/payment_providers/paypal.rst:102 msgid "Odoo needs your **API Credentials** to connect with your PayPal account. To do so, go to :menuselection:`Accounting --> Configuration --> Payment Providers` and :guilabel:`Activate` PayPal. Then, enter your PayPal account credentials in the :guilabel:`Credentials` tab:" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:101 +#: ../../content/applications/finance/payment_providers/paypal.rst:106 msgid ":guilabel:`Email`: the login email address in Paypal;" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:102 +#: ../../content/applications/finance/payment_providers/paypal.rst:107 msgid ":guilabel:`PDT Identity Token`: the key used to verify the authenticity of transactions;" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:103 +#: ../../content/applications/finance/payment_providers/paypal.rst:108 msgid ":guilabel:`Use IPN`: enable for PayPal to work properly in Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:106 +#: ../../content/applications/finance/payment_providers/paypal.rst:111 msgid "Save the :guilabel:`PDT Identity Token` for later use." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:108 +#: ../../content/applications/finance/payment_providers/paypal.rst:113 msgid "To set the :guilabel:`PDT Identity Token`, switch to :ref:`developer mode ` and retrieve the token by following the configuration steps at :ref:`paypal/pdt`." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:112 +#: ../../content/applications/finance/payment_providers/paypal.rst:117 msgid "The PayPal **Merchant ID** is not required in Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:114 +#: ../../content/applications/finance/payment_providers/paypal.rst:119 msgid "If you are trying PayPal as a test, using a :ref:`PayPal Sandbox account `, change the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than on your main database." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:119 +#: ../../content/applications/finance/payment_providers/paypal.rst:124 msgid "Extra fees" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:121 +#: ../../content/applications/finance/payment_providers/paypal.rst:126 msgid "You can charge :ref:`extra fees ` to customers choosing to pay with PayPal in order to cover the transaction fees PayPal charges you." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:125 +#: ../../content/applications/finance/payment_providers/paypal.rst:130 msgid "You can refer to `Paypal Fees `_ to set up fees." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:127 +#: ../../content/applications/finance/payment_providers/paypal.rst:132 msgid "`Traders in the EU `_ are not allowed to charge extra fees for paying with credit cards." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:132 +#: ../../content/applications/finance/payment_providers/paypal.rst:137 msgid "Test environment" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:137 +#: ../../content/applications/finance/payment_providers/paypal.rst:142 msgid "Thanks to PayPal sandbox accounts, you can test the entire payment flow in Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:139 +#: ../../content/applications/finance/payment_providers/paypal.rst:144 msgid "Log into the `Paypal Developer Site `_ using your PayPal credentials, which creates two sandbox accounts:" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:142 +#: ../../content/applications/finance/payment_providers/paypal.rst:147 msgid "A business account (to use as merchants, e.g., `pp.merch01-facilitator@example.com `_);" msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:144 +#: ../../content/applications/finance/payment_providers/paypal.rst:149 msgid "A default personal account (to use as shoppers, e.g., `pp.merch01-buyer@example.com `_)." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:147 +#: ../../content/applications/finance/payment_providers/paypal.rst:152 msgid "Log into PayPal sandbox using the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo (:menuselection:`Accounting --> Configuration --> Payment Providers --> PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set on :guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than your main database." msgstr "" -#: ../../content/applications/finance/payment_providers/paypal.rst:153 +#: ../../content/applications/finance/payment_providers/paypal.rst:158 msgid "Run a test transaction from Odoo using the sandbox personal account." msgstr "" @@ -24777,7 +25572,7 @@ msgid "Sign" msgstr "" #: ../../content/applications/finance/sign.rst:5 -msgid "**Odoo Sign** allows you to send, sign and approve documents online, using electronic signatures." +msgid "**Odoo Sign** allows you to send, sign, and approve documents online, using electronic signatures." msgstr "" #: ../../content/applications/finance/sign.rst:7 @@ -24785,7 +25580,7 @@ msgid "An **electronic signature** shows a person's agreement to the content of msgstr "" #: ../../content/applications/finance/sign.rst:11 -msgid "With Sign, you can upload any PDF file and add fields to it. These fields are automatically filled in with the user's details present in your database." +msgid "With Sign, you can upload any PDF file and add fields to it. These fields can be automatically filled in with the user's details present in your database." msgstr "" #: ../../content/applications/finance/sign.rst:15 @@ -24793,7 +25588,7 @@ msgid "`Odoo Sign: product page `_" msgstr "" #: ../../content/applications/finance/sign.rst:16 -msgid "`Odoo Tutorials: Sign `_" +msgid "`Odoo Tutorials: Sign [video] `_" msgstr "" #: ../../content/applications/finance/sign.rst:19 @@ -24885,154 +25680,247 @@ msgid "The above information has no legal value; it is only provided for general msgstr "" #: ../../content/applications/finance/sign.rst:86 -msgid "Roles" +msgid "Send a document to sign" msgstr "" -#: ../../content/applications/finance/sign.rst:88 -msgid "Each field in a Sign document is related to a role that corresponds to a specific person. When a document is being signed, the person assigned to the role needs to fill in their assigned fields and sign it." +#: ../../content/applications/finance/sign.rst:89 +msgid "One-time signature" msgstr "" -#: ../../content/applications/finance/sign.rst:92 -msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." +#: ../../content/applications/finance/sign.rst:91 +msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields ` in your document. You can modify the :ref:`role ` assigned to a field by clicking on it and selecting the one you want." msgstr "" -#: ../../content/applications/finance/sign.rst:94 -msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`Create`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template." +#: ../../content/applications/finance/sign.rst:96 +msgid "When ready, click :guilabel:`Send`, and fill in the required fields. Once sent, your document remains available. Go to :menuselection:`Documents --> All Documents` to see your document and the status of the signatures." msgstr "" -#: ../../content/applications/finance/sign.rst:102 -msgid "Secured identification" +#: ../../content/applications/finance/sign.rst:-1 +msgid "Signature status" msgstr "" #: ../../content/applications/finance/sign.rst:104 -msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through an SMS verification or via ItsmeĀ® (available in Belgium and the Netherlands). Both authentication options require :ref:`credits `. If you do not have any credits left, the authentication steps will be skipped." +#: ../../content/applications/finance/spreadsheet/templates.rst:3 +msgid "Templates" msgstr "" -#: ../../content/applications/finance/sign.rst:110 -msgid ":doc:`In-App Purchase (IAP) <../general/in_app_purchase>`" +#: ../../content/applications/finance/sign.rst:106 +msgid "You can create document templates when you have to send the same document several times. From your dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required :ref:`fields `. You can modify the :ref:`role ` of a field by clicking on it and selecting the one you want." msgstr "" #: ../../content/applications/finance/sign.rst:111 +msgid "Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a :guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will be available in the signature confirmation message received after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your template to specific authorized users or groups." +msgstr "" + +#: ../../content/applications/finance/sign.rst:117 +msgid "Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document immediately." +msgstr "" + +#: ../../content/applications/finance/sign.rst:122 +msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on ā‹®, then :guilabel:`Template`. Click on ā‹® again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." +msgstr "" + +#: ../../content/applications/finance/sign.rst:130 +msgid "Roles" +msgstr "" + +#: ../../content/applications/finance/sign.rst:132 +msgid "Each field in a Sign document is related to a role corresponding to a specific person. When a document is being signed, the person assigned to the role must fill in their assigned fields and sign it." +msgstr "" + +#: ../../content/applications/finance/sign.rst:136 +msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:138 +msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template." +msgstr "" + +#: ../../content/applications/finance/sign.rst:146 +msgid "Secured identification" +msgstr "" + +#: ../../content/applications/finance/sign.rst:148 +msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification ` or via :ref:`ItsmeĀ® ` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits `. If you do not have any credits left, the authentication steps will be skipped." +msgstr "" + +#: ../../content/applications/finance/sign.rst:154 +msgid ":doc:`In-App Purchase (IAP) <../general/in_app_purchase>`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:155 msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>`" msgstr "" -#: ../../content/applications/finance/sign.rst:114 +#: ../../content/applications/finance/sign.rst:160 msgid "SMS verification" msgstr "" -#: ../../content/applications/finance/sign.rst:116 +#: ../../content/applications/finance/sign.rst:162 msgid "Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`." msgstr "" +#: ../../content/applications/finance/sign.rst:166 +msgid "Before being able to send SMS Text Messages, you need to register your phone number. To do so, go to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by SMS`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:170 +msgid "Go to the document to sign, add the field for which the SMS verification is required, for example, the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the :guilabel:`customer` and click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:174 +msgid "The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS." +msgstr "" + #: ../../content/applications/finance/sign.rst:-1 msgid "Add a hash to your document" msgstr "" -#: ../../content/applications/finance/sign.rst:123 -msgid "Go to the document to sign, add the field for which the SMS verification is required, for example the :guilabel:`Signature` field, and click :guilabel:`Send`. A page pops up, select the customer, and click :guilabel:`Send`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:127 -msgid "The person signing the document fills in the :guilabel:`Signature` field and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS." -msgstr "" - -#: ../../content/applications/finance/sign.rst:-1 -msgid "fill in your phone number for final validation" -msgstr "" - -#: ../../content/applications/finance/sign.rst:136 +#: ../../content/applications/finance/sign.rst:182 msgid "This feature is enabled by default." msgstr "" -#: ../../content/applications/finance/sign.rst:137 +#: ../../content/applications/finance/sign.rst:183 msgid "As soon as the :guilabel:`Extra Authentication Step` applies to a role, this validation step is requested for any field assigned to this role." msgstr "" -#: ../../content/applications/finance/sign.rst:141 +#: ../../content/applications/finance/sign.rst:189 msgid "ItsmeĀ®" msgstr "" -#: ../../content/applications/finance/sign.rst:143 -msgid "Go to :menuselection:`Sign --> Configuration --> Settings` and enable :guilabel:`Identify with itsmeĀ®`." +#: ../../content/applications/finance/sign.rst:191 +msgid "ItsmeĀ® authentication can be used to allow signatories to provide their identity using itsmeĀ®. This feature is only available in **Belgium** and the **Netherlands**." msgstr "" -#: ../../content/applications/finance/sign.rst:146 -msgid "Then, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsmeĀ®`." +#: ../../content/applications/finance/sign.rst:194 +msgid "The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the :guilabel:`Customer (identified with itsmeĀ®)` role. To enable it for other roles, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsmeĀ®`." msgstr "" -#: ../../content/applications/finance/sign.rst:149 -msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch the role to :guilabel:`customer (identified with itsmeĀ®)`, and click :guilabel:`Validate`, and :guilabel:`Send`." +#: ../../content/applications/finance/sign.rst:199 +msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`." msgstr "" #: ../../content/applications/finance/sign.rst:-1 msgid "select customer identified with itsmeĀ®" msgstr "" -#: ../../content/applications/finance/sign.rst:157 -msgid "The person signing the document fills in the :guilabel:`Signature` field and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up, and the person must authenticate with itsmeĀ®." +#: ../../content/applications/finance/sign.rst:205 +msgid "Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by clicking on :guilabel:`Validate & Send Completed Document`, triggering a :guilabel:`Final verification` page where authentication via itsmeĀ® is required." msgstr "" -#: ../../content/applications/finance/sign.rst:162 -msgid "This feature is only available in Belgium and the Netherlands." +#: ../../content/applications/finance/sign.rst:210 +msgid "Signatory hash" msgstr "" -#: ../../content/applications/finance/sign.rst:167 -msgid "Field Types" +#: ../../content/applications/finance/sign.rst:212 +msgid "Each time someone signs a document, a **hash** - a unique digital signature of the operation - is generated to ensure traceability, integrity, and inalterability. This process guarantees that any changes made after a signature is affixed can be easily detected, maintaining the document's authenticity and security throughout its lifecycle." msgstr "" -#: ../../content/applications/finance/sign.rst:169 -msgid "Various field types can be used to sign documents (placeholder, autocompletion, ...). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees." +#: ../../content/applications/finance/sign.rst:217 +msgid "A visual security frame displaying the beginning of the hash is added to the signatures. Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the document." msgstr "" -#: ../../content/applications/finance/sign.rst:173 +#: ../../content/applications/finance/sign.rst:-1 +msgid "Adding the visual security frame to a signature." +msgstr "" + +#: ../../content/applications/finance/sign.rst:229 +msgid "Tags can be used to categorize and organize documents, allowing users to search for and filter documents based on specific criteria quickly." +msgstr "" + +#: ../../content/applications/finance/sign.rst:232 +msgid "You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index` for your tag." +msgstr "" + +#: ../../content/applications/finance/sign.rst:236 +msgid "To apply a tag to a document, use the dropdown list available in your document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:239 +msgid "Sign order" +msgstr "" + +#: ../../content/applications/finance/sign.rst:241 +msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature." +msgstr "" + +#: ../../content/applications/finance/sign.rst:244 +msgid "By going to :menuselection:`Configuration --> Settings`, you can :guilabel:`Enable Signing Order`. Each recipient receives the signature request notification only once the previous recipient has completed their action." +msgstr "" + +#: ../../content/applications/finance/sign.rst:248 +msgid "Add at least two :guilabel:`Signature` fields with different roles to your document. Click :guilabel:`Send`, go to the :guilabel:`Options` tab, and tick the :guilabel:`Specify signing order` box." +msgstr "" + +#: ../../content/applications/finance/sign.rst:252 +msgid "Add the signer's :guilabel:`Name or email` information. You can decide on the :guilabel:`Sign Order` by typing :guilabel:`1` or :guilabel:`2` in the :guilabel:`Sign Order` column." +msgstr "" + +#: ../../content/applications/finance/sign.rst:256 +msgid "`Odoo Quick Tips: Sign order [video] `_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:261 +msgid "Field types" +msgstr "" + +#: ../../content/applications/finance/sign.rst:263 +msgid "Fields are used in a document to indicate what information must be completed by the signers. You can add fields to your document simply by dragging and dropping them for the left column into your document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:267 +msgid "Various field types can be used to sign documents (placeholder, autocompletion, etc.). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees." +msgstr "" + +#: ../../content/applications/finance/sign.rst:271 msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`." msgstr "" -#: ../../content/applications/finance/sign.rst:176 -msgid "You can select an existing field by clicking on it or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:" +#: ../../content/applications/finance/sign.rst:274 +msgid "You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:" msgstr "" -#: ../../content/applications/finance/sign.rst:179 +#: ../../content/applications/finance/sign.rst:277 msgid ":guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating an automatic one based on their name, or uploading a local file (usually an image). Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field." msgstr "" -#: ../../content/applications/finance/sign.rst:182 +#: ../../content/applications/finance/sign.rst:280 msgid ":guilabel:`Initial`: users are asked to enter their initials, in a similar way to the :guilabel:`Signature` field." msgstr "" -#: ../../content/applications/finance/sign.rst:184 +#: ../../content/applications/finance/sign.rst:282 msgid ":guilabel:`Text`: users enter text on a single line." msgstr "" -#: ../../content/applications/finance/sign.rst:185 +#: ../../content/applications/finance/sign.rst:283 msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." msgstr "" -#: ../../content/applications/finance/sign.rst:186 +#: ../../content/applications/finance/sign.rst:284 msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)." msgstr "" -#: ../../content/applications/finance/sign.rst:187 +#: ../../content/applications/finance/sign.rst:285 msgid ":guilabel:`Selection`: users choose a single option from a variety of options." msgstr "" -#: ../../content/applications/finance/sign.rst:189 +#: ../../content/applications/finance/sign.rst:287 msgid "The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the signature process. It uses the value of one of the fields on the contact (`res.partner`) model of the person signing the document. To do so, enter the contact model field's technical name." msgstr "" -#: ../../content/applications/finance/sign.rst:194 +#: ../../content/applications/finance/sign.rst:292 msgid "To know the technical name of a field, enable developer mode and hover your mouse on the question mark next to the field." msgstr "" -#: ../../content/applications/finance/sign.rst:198 +#: ../../content/applications/finance/sign.rst:296 msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document." msgstr "" -#: ../../content/applications/finance/sign.rst:201 -msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`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." +#: ../../content/applications/finance/sign.rst:299 +msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`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 "" -#: ../../content/applications/finance/sign.rst:207 +#: ../../content/applications/finance/sign.rst:305 msgid "Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process to help them understand what the step entails (e.g., \"Sign here\" or ā€œFill in your birthdateā€). You can also use a :guilabel:`Placeholder` text to be displayed inside the field before it is completed." msgstr "" @@ -25040,22 +25928,6 @@ msgstr "" msgid "Tip and placeholder example in Odoo Sign" msgstr "" -#: ../../content/applications/finance/sign.rst:217 -msgid "Signatory hash" -msgstr "" - -#: ../../content/applications/finance/sign.rst:219 -msgid "A :guilabel:`hash` can be added to a document that is shared (attached to an email or printed, for example) to indicate that the signature is electronic and that there is some traceability behind it. The :guilabel:`hash` corresponds to a unique ID number related to the signed document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:223 -msgid "If you are an :doc:`internal user <../general/users/manage_users>`, you can choose to tick or untick the frame option when signing the document. Tick the box to have the frame and hash visible." -msgstr "" - -#: ../../content/applications/finance/sign.rst:232 -msgid "The :guilabel:`hash` is only applicable to the signature field." -msgstr "" - #: ../../content/applications/finance/spreadsheet.rst:6 msgid "Spreadsheet" msgstr "" @@ -25204,10 +26076,6 @@ msgstr "" msgid "To change which records are :ref:`used by the pivot `, right-click on a pivot cell, select :guilabel:`See pivot properties`, and click :guilabel:`Edit domain`." msgstr "" -#: ../../content/applications/finance/spreadsheet/templates.rst:3 -msgid "Templates" -msgstr "" - #: ../../content/applications/finance/spreadsheet/templates.rst:5 msgid "Spreadsheet templates allow you to quickly create spreadsheets without starting from scratch." msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 6690b58ea..6a00adacb 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2705,7 +2705,7 @@ msgid "In-App Purchase (IAP)" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:5 -msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from my database." +msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from your database." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:11 @@ -2713,11 +2713,11 @@ msgid "Buying Credits" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:13 -msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`." +msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult your current balance or to recharge your account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:21 -msgid "If I am on Odoo Online and have the Enterprise version, I benefit from free credits to test our IAP features." +msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free credits to test our IAP features." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:25 @@ -2737,7 +2737,7 @@ msgid "IAP Portal" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:42 -msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low." +msgid "The IAP Portal is a platform regrouping your IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, you can view your current balance, recharge your credits and set a reminder when your balance falls below a threshold." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:50 @@ -2745,31 +2745,7 @@ msgid "Get notified when credits are low" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:52 -msgid "To be notified when itā€™s time to recharge my credits, Iā€™ll go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, Iā€™ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:62 -msgid "IAP services available" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:64 -msgid "Different services are available depending on the hosting type of your Database:" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:66 -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:68 -msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used." -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:72 -msgid "Offering my own services" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:74 -msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than ā€” and possibly instead of ā€” a sole initial purchase. Please, find more information at: :doc:`/developer/howtos/provide_iap_services`." +msgid "To be notified when itā€™s time to recharge your credits, you can go to your IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and check the Receive threshold warning option. Then, you can provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent by email!" msgstr "" #: ../../content/applications/general/reporting.rst:3 @@ -2777,7 +2753,7 @@ msgid "Reporting" msgstr "" #: ../../content/applications/general/reporting.rst:5 -msgid "You can find under the :guilabel:`Reporting` menu of most apps several reports that let you analyze and visualize your records' data." +msgid "You can find several reports under the :guilabel:`Reporting` menu of most apps that let you analyze and visualize the data of your records." msgstr "" #: ../../content/applications/general/reporting.rst:11 @@ -2800,11 +2776,11 @@ msgstr "" msgid "Selecting the graph view" msgstr "" -#: ../../content/applications/general/reporting.rst:34 +#: ../../content/applications/general/reporting.rst:33 msgid "Pivot view" msgstr "" -#: ../../content/applications/general/reporting.rst:36 +#: ../../content/applications/general/reporting.rst:35 msgid "The :ref:`pivot view ` is used to aggregate your records' data and break it down for analysis. The view is often found under the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the **pivot view button** located at the top right to access it." msgstr "" @@ -2812,23 +2788,23 @@ msgstr "" msgid "Selecting the pivot view" msgstr "" -#: ../../content/applications/general/reporting.rst:47 +#: ../../content/applications/general/reporting.rst:45 msgid "Choosing measures" msgstr "" -#: ../../content/applications/general/reporting.rst:49 +#: ../../content/applications/general/reporting.rst:47 msgid "After selecting a view, you should ensure only the relevant records are :doc:`filtered `. Next, you should choose what is measured. By default, a measure is always selected. If you wish to edit it, click :guilabel:`Measures` and choose one or, only for pivots, multiple measures." msgstr "" -#: ../../content/applications/general/reporting.rst:54 +#: ../../content/applications/general/reporting.rst:52 msgid "When you select a measure, Odoo aggregates the values recorded on that field for the filtered records. Only numerical fields (:ref:`integer `, :ref:`decimal `, :ref:`monetary `) can be measured. In addition, the :guilabel:`Count` option is used to count the total number of filtered records." msgstr "" -#: ../../content/applications/general/reporting.rst:60 +#: ../../content/applications/general/reporting.rst:58 msgid "After choosing what you want to measure, you can define how the data should be :ref:`grouped ` depending on the dimension you want to analyze. By default, the data is often grouped by *Date > Month*, which is used to analyze the evolution of a measure over the months." msgstr "" -#: ../../content/applications/general/reporting.rst:65 +#: ../../content/applications/general/reporting.rst:63 msgid "When you filter a single time period, the option to compare it against another one appears." msgstr "" @@ -2836,11 +2812,11 @@ msgstr "" msgid "Using the comparison option" msgstr "" -#: ../../content/applications/general/reporting.rst:75 +#: ../../content/applications/general/reporting.rst:72 msgid "Select measures" msgstr "" -#: ../../content/applications/general/reporting.rst:77 +#: ../../content/applications/general/reporting.rst:74 msgid "Among other measures, you could add the :guilabel:`Margin` and :guilabel:`Count` measures to the Sales Analysis report. By default, the :guilabel:`Untaxed Amount` measure is selected." msgstr "" @@ -2848,11 +2824,11 @@ msgstr "" msgid "Selecting different measures on the Sales Analysis report" msgstr "" -#: ../../content/applications/general/reporting.rst:85 +#: ../../content/applications/general/reporting.rst:81 msgid "Group measures" msgstr "" -#: ../../content/applications/general/reporting.rst:87 +#: ../../content/applications/general/reporting.rst:83 msgid "You could group the measures by :guilabel:`Product Category` at the level of rows on the previous Sales Analysis report example." msgstr "" @@ -2860,19 +2836,19 @@ msgstr "" msgid "Adding a group on the Sales Analysis report" msgstr "" -#: ../../content/applications/general/reporting.rst:97 +#: ../../content/applications/general/reporting.rst:92 msgid "Using the pivot view" msgstr "" -#: ../../content/applications/general/reporting.rst:99 +#: ../../content/applications/general/reporting.rst:94 msgid "Grouping data is quintessential to the pivot view. It enables drilling down the data to gain deeper insights. While you can use the :guilabel:`Group By` option to quickly add a group at the level of rows, as shown in the example above, you can also click the plus button (:guilabel:`āž•`) next to the :guilabel:`Total` header at the level of rows *and* columns, and then select one of the **preconfigured groups**. To remove one, click the minus button (:guilabel:`āž–`)." msgstr "" -#: ../../content/applications/general/reporting.rst:105 +#: ../../content/applications/general/reporting.rst:100 msgid "Once you have added a group, you can add new ones on the opposite axis or the newly created subgroups." msgstr "" -#: ../../content/applications/general/reporting.rst:109 +#: ../../content/applications/general/reporting.rst:104 msgid "You could further divide the measures on the previous Sales Analysis report example by the :guilabel:`Salesperson` group at the level of columns and by the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / Office Furniture` product category." msgstr "" @@ -2880,39 +2856,39 @@ msgstr "" msgid "Adding multiple groups on the Sales Analysis report" msgstr "" -#: ../../content/applications/general/reporting.rst:118 +#: ../../content/applications/general/reporting.rst:112 msgid "Switch the rows and columns' groups by clicking the flip axis button (:guilabel:`ā‡„`)." msgstr "" -#: ../../content/applications/general/reporting.rst:119 +#: ../../content/applications/general/reporting.rst:113 msgid "Click on a measure's label to sort the values by ascending (ā¶) or descending (ā·) order." msgstr "" -#: ../../content/applications/general/reporting.rst:120 +#: ../../content/applications/general/reporting.rst:114 msgid "Download a `.xlsx` version of the pivot by clicking the download button (:guilabel:`ā­³`)." msgstr "" -#: ../../content/applications/general/reporting.rst:125 +#: ../../content/applications/general/reporting.rst:119 msgid "Using the graph view" msgstr "" -#: ../../content/applications/general/reporting.rst:127 -msgid "Three graphs are available, the bar, line, and pie charts." +#: ../../content/applications/general/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." msgstr "" -#: ../../content/applications/general/reporting.rst:129 +#: ../../content/applications/general/reporting.rst:123 msgid "**Bar charts** are used to show the distribution or a comparison of several categories. They are especially useful as they can deal with larger data sets." msgstr "" -#: ../../content/applications/general/reporting.rst:132 +#: ../../content/applications/general/reporting.rst:126 msgid "**Line charts** are useful to show changing time series and trends over time." msgstr "" -#: ../../content/applications/general/reporting.rst:134 +#: ../../content/applications/general/reporting.rst:128 msgid "**Pie charts** are used to show the distribution or a comparison of a small number of categories when they form a meaningful whole." msgstr "" -#: ../../content/applications/general/reporting.rst:139 +#: ../../content/applications/general/reporting.rst:133 msgid "Bar chart" msgstr "" @@ -2920,7 +2896,7 @@ msgstr "" msgid "Viewing the Sales Analysis report as a bar chart" msgstr "" -#: ../../content/applications/general/reporting.rst:145 +#: ../../content/applications/general/reporting.rst:138 msgid "Line chart" msgstr "" @@ -2928,7 +2904,7 @@ msgstr "" msgid "Viewing the Sales Analysis report as a line chart" msgstr "" -#: ../../content/applications/general/reporting.rst:151 +#: ../../content/applications/general/reporting.rst:143 msgid "Pie chart" msgstr "" @@ -2936,11 +2912,11 @@ msgstr "" msgid "Viewing the Sales Analysis report as a pie chart" msgstr "" -#: ../../content/applications/general/reporting.rst:158 +#: ../../content/applications/general/reporting.rst:149 msgid "For **bar** and **line** charts, you can use the stacked option when you have at least two groups, which then appear on top of each other instead of next to each other." msgstr "" -#: ../../content/applications/general/reporting.rst:163 +#: ../../content/applications/general/reporting.rst:154 msgid "Stacked bar chart" msgstr "" @@ -2948,7 +2924,7 @@ msgstr "" msgid "Stacked bar chart example" msgstr "" -#: ../../content/applications/general/reporting.rst:169 +#: ../../content/applications/general/reporting.rst:159 msgid "Regular bar chart" msgstr "" @@ -2956,7 +2932,7 @@ msgstr "" msgid "Non-stacked bar chart example" msgstr "" -#: ../../content/applications/general/reporting.rst:175 +#: ../../content/applications/general/reporting.rst:164 msgid "Stacked line chart" msgstr "" @@ -2964,8 +2940,8 @@ msgstr "" msgid "Stacked line chart example" msgstr "" -#: ../../content/applications/general/reporting.rst:181 -#: ../../content/applications/general/reporting.rst:198 +#: ../../content/applications/general/reporting.rst:169 +#: ../../content/applications/general/reporting.rst:184 msgid "Regular line chart" msgstr "" @@ -2973,11 +2949,11 @@ msgstr "" msgid "Non-stacked line chart example" msgstr "" -#: ../../content/applications/general/reporting.rst:187 +#: ../../content/applications/general/reporting.rst:174 msgid "For **line** charts, you can use the cumulative option to sum values, which is especially useful to show the change in growth over a time period." msgstr "" -#: ../../content/applications/general/reporting.rst:192 +#: ../../content/applications/general/reporting.rst:179 msgid "Cumulative line chart" msgstr "" diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index 1c43162e7..7b1fbb27f 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -131,6 +131,7 @@ msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:22 #: ../../content/applications/hr/payroll/contracts.rst:39 +#: ../../content/applications/hr/payroll/payslips.rst:51 msgid "Required fields" msgstr "" @@ -144,6 +145,7 @@ msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:33 #: ../../content/applications/hr/payroll/contracts.rst:66 +#: ../../content/applications/hr/payroll/payslips.rst:91 msgid "Optional fields" msgstr "" @@ -471,27 +473,27 @@ msgstr "" msgid "All uploaded documents associated with the employee appear in the documents smart-button." msgstr "" -#: ../../content/applications/hr/payroll.rst:3 +#: ../../content/applications/hr/payroll.rst:5 msgid "Payroll" msgstr "" -#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:7 msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*." msgstr "" -#: ../../content/applications/hr/payroll.rst:9 +#: ../../content/applications/hr/payroll.rst:11 msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips." msgstr "" -#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/payroll.rst:17 msgid "Settings" msgstr "" -#: ../../content/applications/hr/payroll.rst:17 +#: ../../content/applications/hr/payroll.rst:19 msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here." msgstr "" -#: ../../content/applications/hr/payroll.rst:20 +#: ../../content/applications/hr/payroll.rst:22 msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees." msgstr "" @@ -499,36 +501,36 @@ msgstr "" msgid "Settings available for Payroll." msgstr "" -#: ../../content/applications/hr/payroll.rst:29 +#: ../../content/applications/hr/payroll.rst:31 msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required." msgstr "" -#: ../../content/applications/hr/payroll.rst:37 +#: ../../content/applications/hr/payroll.rst:39 #: ../../content/applications/hr/payroll/work_entries.rst:3 msgid "Work entries" msgstr "" -#: ../../content/applications/hr/payroll.rst:39 +#: ../../content/applications/hr/payroll.rst:41 msgid "A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`." msgstr "" -#: ../../content/applications/hr/payroll.rst:44 +#: ../../content/applications/hr/payroll.rst:46 msgid ":doc:`Manage work entries `" msgstr "" -#: ../../content/applications/hr/payroll.rst:47 +#: ../../content/applications/hr/payroll.rst:49 msgid "Work entry types" msgstr "" -#: ../../content/applications/hr/payroll.rst:49 +#: ../../content/applications/hr/payroll.rst:51 msgid "When creating a work entry in the *Payroll* application, or when an employee enters information in the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of :guilabel:`Work Entry Types` is automatically created based on localization settings set in the database." msgstr "" -#: ../../content/applications/hr/payroll.rst:54 +#: ../../content/applications/hr/payroll.rst:56 msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entry Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:57 +#: ../../content/applications/hr/payroll.rst:59 msgid "Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees are correctly entered." msgstr "" @@ -536,27 +538,27 @@ msgstr "" msgid "List of all work entry types currently available." msgstr "" -#: ../../content/applications/hr/payroll.rst:65 +#: ../../content/applications/hr/payroll.rst:67 msgid "New work entry type" msgstr "" -#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll.rst:69 msgid "To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the form:" msgstr "" -#: ../../content/applications/hr/payroll.rst:70 +#: ../../content/applications/hr/payroll.rst:72 msgid ":guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or `Public Holiday`." msgstr "" -#: ../../content/applications/hr/payroll.rst:72 +#: ../../content/applications/hr/payroll.rst:74 msgid ":guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use." msgstr "" -#: ../../content/applications/hr/payroll.rst:75 +#: ../../content/applications/hr/payroll.rst:77 msgid ":guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the payslip list." msgstr "" -#: ../../content/applications/hr/payroll.rst:77 +#: ../../content/applications/hr/payroll.rst:79 msgid "Check boxes: If any of the items in the list applies to the work entry, check off the box by clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, or a new type of time off can be entered." msgstr "" @@ -564,35 +566,35 @@ msgstr "" msgid "New work entry type form." msgstr "" -#: ../../content/applications/hr/payroll.rst:86 +#: ../../content/applications/hr/payroll.rst:88 msgid ":guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:89 +#: ../../content/applications/hr/payroll.rst:91 msgid ":guilabel:`No Rounding`: A timesheet entry is not modified." msgstr "" -#: ../../content/applications/hr/payroll.rst:90 +#: ../../content/applications/hr/payroll.rst:92 msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:91 +#: ../../content/applications/hr/payroll.rst:93 msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:94 +#: ../../content/applications/hr/payroll.rst:96 msgid "If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours." msgstr "" -#: ../../content/applications/hr/payroll.rst:100 +#: ../../content/applications/hr/payroll.rst:102 msgid "Working times" msgstr "" -#: ../../content/applications/hr/payroll.rst:102 +#: ../../content/applications/hr/payroll.rst:104 msgid "To view the currently configured working times, go to :menuselection:`Payroll --> Configuration --> Working Times`. The working times that are available for an employee's contracts and work entries are found in this list." msgstr "" -#: ../../content/applications/hr/payroll.rst:106 +#: ../../content/applications/hr/payroll.rst:108 msgid "Working times are company-specific. Each company must identify each type of working time they use. For example, an Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working time entry for each company that uses the 40-hour standard work week." msgstr "" @@ -600,11 +602,11 @@ msgstr "" msgid "All working times currently set up in the database." msgstr "" -#: ../../content/applications/hr/payroll.rst:116 +#: ../../content/applications/hr/payroll.rst:118 msgid "New working time" msgstr "" -#: ../../content/applications/hr/payroll.rst:118 +#: ../../content/applications/hr/payroll.rst:120 msgid "To create a new working time, click the :guilabel:`Create` button. Enter the information on the form." msgstr "" @@ -612,43 +614,43 @@ msgstr "" msgid "New working type form." msgstr "" -#: ../../content/applications/hr/payroll.rst:125 +#: ../../content/applications/hr/payroll.rst:127 msgid "The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any adjustments to the days and times that apply to the new working time." msgstr "" -#: ../../content/applications/hr/payroll.rst:129 +#: ../../content/applications/hr/payroll.rst:131 msgid "In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified by typing in the time." msgstr "" -#: ../../content/applications/hr/payroll.rst:135 +#: ../../content/applications/hr/payroll.rst:137 msgid "The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example, `2:00 PM` would be entered as `14:00`." msgstr "" -#: ../../content/applications/hr/payroll.rst:138 +#: ../../content/applications/hr/payroll.rst:140 msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." msgstr "" -#: ../../content/applications/hr/payroll.rst:142 +#: ../../content/applications/hr/payroll.rst:144 msgid "Salary" msgstr "" -#: ../../content/applications/hr/payroll.rst:147 +#: ../../content/applications/hr/payroll.rst:149 msgid "Structure types" msgstr "" -#: ../../content/applications/hr/payroll.rst:149 +#: ../../content/applications/hr/payroll.rst:151 msgid "In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how an employee enters timesheets. Each structure type is an individual set of rules for processing a timesheet entry, which consists of different structures nested within it. Structure types define how often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how many hours the employee worked (varied)." msgstr "" -#: ../../content/applications/hr/payroll.rst:155 +#: ../../content/applications/hr/payroll.rst:157 msgid "For example, a structure type could be `Employee`, and that structure type could have two different structures in it: a `Regular Pay` structure which includes all the separate rules for processing regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures within the `Employee` structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:161 +#: ../../content/applications/hr/payroll.rst:163 msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Structure Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:164 +#: ../../content/applications/hr/payroll.rst:166 msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*." msgstr "" @@ -656,7 +658,7 @@ msgstr "" msgid "List of all structure types." msgstr "" -#: ../../content/applications/hr/payroll.rst:172 +#: ../../content/applications/hr/payroll.rst:174 msgid "Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." msgstr "" @@ -664,19 +666,19 @@ msgstr "" msgid "New structure type box." msgstr "" -#: ../../content/applications/hr/payroll.rst:181 +#: ../../content/applications/hr/payroll.rst:183 msgid "Structures" msgstr "" -#: ../../content/applications/hr/payroll.rst:183 +#: ../../content/applications/hr/payroll.rst:185 msgid "*Salary structures* are the different ways an employee gets paid within a specific *structure*, and are specifically defined by various rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:186 +#: ../../content/applications/hr/payroll.rst:188 msgid "The amount of structures a company needs for each structure type depends on how many different ways employees are paid, and how their pay is calculated. For example, a common structure that could be useful to add may be a `Bonus`." msgstr "" -#: ../../content/applications/hr/payroll.rst:190 +#: ../../content/applications/hr/payroll.rst:192 msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Structures`." msgstr "" @@ -684,11 +686,11 @@ msgstr "" msgid "All available salary structures." msgstr "" -#: ../../content/applications/hr/payroll.rst:197 +#: ../../content/applications/hr/payroll.rst:199 msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." msgstr "" -#: ../../content/applications/hr/payroll.rst:200 +#: ../../content/applications/hr/payroll.rst:202 msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." msgstr "" @@ -696,15 +698,15 @@ msgstr "" msgid "Salary structure details for Regular Pay." msgstr "" -#: ../../content/applications/hr/payroll.rst:208 +#: ../../content/applications/hr/payroll.rst:210 msgid "Rules" msgstr "" -#: ../../content/applications/hr/payroll.rst:210 +#: ../../content/applications/hr/payroll.rst:212 msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary." msgstr "" -#: ../../content/applications/hr/payroll.rst:214 +#: ../../content/applications/hr/payroll.rst:216 msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." msgstr "" @@ -712,7 +714,7 @@ msgstr "" msgid "Rules for each salary structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:221 +#: ../../content/applications/hr/payroll.rst:223 msgid "To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the fields, then click :guilabel:`Save`." msgstr "" @@ -720,47 +722,47 @@ msgstr "" msgid "Enter the information for the new rule." msgstr "" -#: ../../content/applications/hr/payroll.rst:228 +#: ../../content/applications/hr/payroll.rst:230 msgid "The required fields for a rule are:" msgstr "" -#: ../../content/applications/hr/payroll.rst:230 +#: ../../content/applications/hr/payroll.rst:232 msgid ":guilabel:`Name`: Enter a name for the rule." msgstr "" -#: ../../content/applications/hr/payroll.rst:231 +#: ../../content/applications/hr/payroll.rst:233 msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one." msgstr "" -#: ../../content/applications/hr/payroll.rst:233 +#: ../../content/applications/hr/payroll.rst:235 msgid ":guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code as this will affect them." msgstr "" -#: ../../content/applications/hr/payroll.rst:235 +#: ../../content/applications/hr/payroll.rst:237 msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one." msgstr "" -#: ../../content/applications/hr/payroll.rst:237 +#: ../../content/applications/hr/payroll.rst:239 msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection)." msgstr "" -#: ../../content/applications/hr/payroll.rst:241 +#: ../../content/applications/hr/payroll.rst:243 msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next." msgstr "" -#: ../../content/applications/hr/payroll.rst:247 +#: ../../content/applications/hr/payroll.rst:249 msgid "Rule parameters" msgstr "" -#: ../../content/applications/hr/payroll.rst:250 +#: ../../content/applications/hr/payroll.rst:252 msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." msgstr "" -#: ../../content/applications/hr/payroll.rst:255 +#: ../../content/applications/hr/payroll.rst:257 msgid "Other input types" msgstr "" -#: ../../content/applications/hr/payroll.rst:257 +#: ../../content/applications/hr/payroll.rst:259 msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Other Input Types`." msgstr "" @@ -768,7 +770,7 @@ msgstr "" msgid "Other input types for payroll." msgstr "" -#: ../../content/applications/hr/payroll.rst:265 +#: ../../content/applications/hr/payroll.rst:267 msgid "To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." msgstr "" @@ -776,27 +778,27 @@ msgstr "" msgid "Create a new Input Type." msgstr "" -#: ../../content/applications/hr/payroll.rst:275 +#: ../../content/applications/hr/payroll.rst:277 msgid "Salary package configurator" msgstr "" -#: ../../content/applications/hr/payroll.rst:277 +#: ../../content/applications/hr/payroll.rst:279 msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package." msgstr "" -#: ../../content/applications/hr/payroll.rst:282 +#: ../../content/applications/hr/payroll.rst:284 msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated as the applicant enters information." msgstr "" -#: ../../content/applications/hr/payroll.rst:288 +#: ../../content/applications/hr/payroll.rst:290 msgid "Advantages" msgstr "" -#: ../../content/applications/hr/payroll.rst:290 +#: ../../content/applications/hr/payroll.rst:292 msgid "When offering potential employees a position, there can be certain *advantages* set in Odoo in addition to the salary to make the offer more appealing (such as extra time off, access to a company car, reimbursement for a phone or internet, etc.)." msgstr "" -#: ../../content/applications/hr/payroll.rst:294 +#: ../../content/applications/hr/payroll.rst:296 msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages are grouped by :guilabel:`Structure type`." msgstr "" @@ -804,7 +806,7 @@ msgstr "" msgid "Settings available for payroll." msgstr "" -#: ../../content/applications/hr/payroll.rst:301 +#: ../../content/applications/hr/payroll.rst:303 msgid "To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields, then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." msgstr "" @@ -812,39 +814,39 @@ msgstr "" msgid "List of advantages employee's can have." msgstr "" -#: ../../content/applications/hr/payroll.rst:309 +#: ../../content/applications/hr/payroll.rst:311 msgid "The required fields for an advantage are:" msgstr "" -#: ../../content/applications/hr/payroll.rst:311 +#: ../../content/applications/hr/payroll.rst:313 msgid ":guilabel:`Name`: Enter the name for the advantage." msgstr "" -#: ../../content/applications/hr/payroll.rst:312 +#: ../../content/applications/hr/payroll.rst:314 msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under." msgstr "" -#: ../../content/applications/hr/payroll.rst:314 +#: ../../content/applications/hr/payroll.rst:316 msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`." msgstr "" -#: ../../content/applications/hr/payroll.rst:317 +#: ../../content/applications/hr/payroll.rst:319 msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to." msgstr "" -#: ../../content/applications/hr/payroll.rst:321 +#: ../../content/applications/hr/payroll.rst:323 msgid "Personal info" msgstr "" -#: ../../content/applications/hr/payroll.rst:323 +#: ../../content/applications/hr/payroll.rst:325 msgid "Every employee in Odoo has an *employee card* that includes all of their personal information, resume, work information, and documents. To view an employee's card, go to the main :menuselection:`Payroll` app dashboard, and click on the employee's card, or go to :menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee cards can also be viewed by going to the :menuselection:`Employees` app." msgstr "" -#: ../../content/applications/hr/payroll.rst:330 +#: ../../content/applications/hr/payroll.rst:332 msgid "An employee card can be thought of as an employee personnel file." msgstr "" -#: ../../content/applications/hr/payroll.rst:332 +#: ../../content/applications/hr/payroll.rst:334 msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Personal Info`." msgstr "" @@ -852,7 +854,7 @@ msgstr "" msgid "Personal information that appear on employee cards to enter." msgstr "" -#: ../../content/applications/hr/payroll.rst:340 +#: ../../content/applications/hr/payroll.rst:342 msgid "To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel the edits." msgstr "" @@ -860,23 +862,23 @@ msgstr "" msgid "New personal information entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:348 +#: ../../content/applications/hr/payroll.rst:350 msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card." msgstr "" -#: ../../content/applications/hr/payroll.rst:352 +#: ../../content/applications/hr/payroll.rst:354 msgid "The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." msgstr "" -#: ../../content/applications/hr/payroll.rst:356 +#: ../../content/applications/hr/payroll.rst:358 msgid "Once the information is entered, click the :guilabel:`Save` button to save the entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:359 +#: ../../content/applications/hr/payroll.rst:361 msgid "Resume" msgstr "" -#: ../../content/applications/hr/payroll.rst:362 +#: ../../content/applications/hr/payroll.rst:364 msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." msgstr "" @@ -1168,6 +1170,422 @@ msgstr "" msgid ":guilabel:`Credit Time`: This option is for Belgian companies only. When clicked, a pop-up window appears that allows for the changing of working times, and can compute time off." msgstr "" +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "Payslips are created either by the employees themselves or their managers, and are approved by authorized employees (typically managers). Then, once payslips are approved, employees are issued payslips and are paid either by check or direct deposit, depending on how their employee profile is configured." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:10 +msgid "The :guilabel:`Payslips` drop-down header of the :menuselection:`Payroll` application consists of three sections: :guilabel:`To Pay`, :guilabel:`All Payslips`, and :guilabel:`Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:13 +msgid "These three sections provide all the tools needed to create payslips for employees, including individual payslips, a batch of payslips, or commission payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Payslips menu selection in Payroll." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:21 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:23 +msgid "Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the payslips that need to be paid. On this page, Odoo displays the payslips that have not been generated yet, and can be created from this dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "View all payslips that need to be paid on the Payslips To Pay page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:31 +msgid "Each payslip will list the :guilabel:`Reference` number for the individual payslip, the :guilabel:`Employee` name, :guilabel:`Batch Name`, the :guilabel:`From` and :guilabel:`To` date range, the :guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:36 +msgid "Clicking on an individual payslip entry will show the details for the individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:41 +msgid "Create new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "A new payslip can be created from the :guilabel:`Payslips To Pay` page (:menuselection:`Payroll app --> Payslips --> To Pay`) or the :guilabel:`Employee Payslips` page (:menuselection:`Payroll app --> Payslips --> All Payslips`), by clicking the :guilabel:`Create` button in the top-left corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:47 +msgid "Clicking :guilabel:`Create` reveals a blank payslip form, wherein the necessary payslip information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "On the blank payslip form, a number of fields are required to be filled in with the necessary information. These required fields are represented by **bold** lines." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The necessary fields for a new payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:60 +msgid ":guilabel:`Employee`: Type in the name of an employee, or select the desired employee from the drop-down list. Upon selecting an employee, several other fields on the payslip form may auto-populate. Typically, after making a selection in the :guilabel:`Employee` field, Odoo auto-populates the :guilabel:`Contract`, :guilabel:`Structure`, and :guilabel:`Payslip Name` fields, but **only** if that information is already on that employee's form in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:66 +msgid ":guilabel:`Period`: Click the default date to reveal a pop-up calendar. On this calendar, use the :guilabel:`< (less-than)` and :guilabel:`> (greater than)` icons to select the desired month, and click on the desired day to select that specific date as the start date for the payslip. Repeat this process to add an end date for the payslip in the field below." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:70 +msgid ":guilabel:`Contract`: Using the drop-down menu, select the desired contract for the employee. Only the available corresponding contracts for the selected employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:72 +msgid ":guilabel:`Structure`: Using the drop-down menu, select the salary structure type. Only the available corresponding structures for the selected contract for that specific employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:75 +msgid ":guilabel:`Payslip Name`: In the blank field, type in the name for the payslip. The name should be short and descriptive, such as `April 2023`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid ":guilabel:`Company`: In the :guilabel:`Accounting Information` tab, select the company the payslip applies to from the :guilabel:`Company` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid ":guilabel:`Salary Journal`: In the :guilabel:`Accounting Information` tab, enter the salary journal in which the payment will be reflected, and found in the *Accounting* application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The necessary fields for a new payslip in the Accounting Information tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:87 +msgid "It is recommended to check with the accounting department to ensure every entry that affects the *Accounting* application is correct." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:93 +msgid ":guilabel:`Reference`: Any note or reference message for the new entry can be entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:94 +msgid ":guilabel:`Company Car`: If applicable, select the company car from the drop-down." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:95 +msgid ":guilabel:`Worked Days`: In the :guilabel:`Worked Days \\& Inputs` tab, the entries under :guilabel:`Worked Days` (including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are automatically filled in, based on what was entered for the :guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields of the payslip form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:100 +msgid ":guilabel:`Salary Computation`: The :guilabel:`Salary Computation` tab is automatically filled in after the :guilabel:`Compute Sheet` button is clicked. Doing so displays all the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:103 +msgid ":guilabel:`Batch Name`: Located in the :guilabel:`Accounting Information` tab, select the payslip batch this new payslip should be added to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:105 +msgid ":guilabel:`Date Account`: Located in the :guilabel:`Accounting Information` tab, enter the date on which the payslip should be posted, by clicking on the drop-down menu, and navigating to the correct month and year using the :guilabel:`< > (less-than/greater-than)` icons in the calendar pop-up window. Then, click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:109 +msgid ":guilabel:`Salary Journal`: This field, located in the :guilabel:`Accounting Information` tab, represents the journal that the payslip will be logged in, and is automatically selected when the :guilabel:`Contract` and :guilabel:`Structure` are entered in the payslip form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:112 +msgid ":guilabel:`Accounting Entry`: This field, located in the :guilabel:`Accounting Information` tab, is automatically filled in once the payslip is confirmed." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:116 +msgid "Save and process new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:118 +msgid "When all the necessary information on the payslip is entered, click :guilabel:`Save` to save the data, or click :guilabel:`Discard` to delete the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Saving the entry is not required in order to compute the sheet, although it is considered best practice to do so. The :guilabel:`Compute Sheet` button can be clicked without first saving the payslip. Doing so will save the entry *and* compute the sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:126 +msgid "Click the :guilabel:`Compute Sheet` button to register all the information, and have the :guilabel:`Salary Computation` tab populated. If any modifications need to be made, click the :guilabel:`Edit` button, make the desired changes, then click the :guilabel:`Recompute Worked Days` button to have the changes reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:132 +msgid "To print the payslip, click the :guilabel:`Print` button. To cancel the payslip, click the :guilabel:`Cancel Payslip` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip. The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The new payslip is emailed to the employee and the email appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:143 +msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Make Payment` button. Doing so reveals a pop-up form, in which the desired :guilabel:`Bank Journal` that the payment should be made against must be selected from a drop-down menu. Then, click the :guilabel:`Confirm` button to confirm the journal, and return to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click Make Payment to send the payment to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:152 +msgid "If a payment needs to be cancelled or refunded, click the corresponding :guilabel:`Refund` or :guilabel:`Cancel Payslip` button, located at the top of the payslip form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:156 +msgid "In order for a payslip to be paid, the employee *must* have a bank account entered in their contact information. If there is no bank information, a payslip cannot be paid, and an error will appear when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :guilabel:`Private Information` tab on the employee's card. Edit the employee card, and add banking information, if it is missing." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "Banking information can be entered in an employee's card." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:167 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:169 +msgid "To view all payslips regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. Here, all payslips are organized by batch (in a default list view)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:172 +msgid "Click on the :guilabel:`ā–¶ (arrow)` next to the individual batch name to view all the payslips in that particular batch, along with all the payslip details. The number of payslips in the batch is written in parenthesis after the batch name. The :guilabel:`Status` for each individual payslip appears on the far-right side, indicating if it is in :guilabel:`Draft Mode`, :guilabel:`Waiting`, or if it is :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:179 +msgid ":guilabel:`Draft` indicates the payslip is created, and there is still time to make edits, since the amounts are not calculated." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:181 +msgid "`Waiting` indicates the payslip has been calculated and the salary details can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:183 +msgid "`Done` indicates the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "View all payslips organized by batches. Click on the arrow to expand each batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:189 +msgid "Click on an individual payslip to view the details for that payslip on a separate page. Using the breadcrumb menu, click :guilabel:`Employee Payslips` to go back to the list view of all payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:192 +msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`Create` button in the upper-left corner. Doing so reveals a separate blank payslip form page. On that blank payslip form page, enter all the necessary information, as described in the :ref:`Create a new payslip ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:197 +msgid "To print PDF versions of payslips from the :guilabel:`Payslips to Pay` or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox next to each payslip to be printed. Or, click the box next to :guilabel:`Reference`, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click on the Print smart button to print payslips to a PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:206 +msgid "Payslips can also be exported to an Excel spreadsheet. When exporting, all payslips are exported regardless of whether some are selected or not. Click on the :guilabel:`Export All` button (download icon) to export all payslips to an Excel spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click on the Export All smart button to export all payslips to an Excel payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "Both *To Pay* and *All Payslips* display all the detailed information for each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:218 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:220 +msgid "To view payslips in batches, navigate to :menuselection:`Payroll app --> Payslips --> Batches` to display all the payslip batches that have been created. These payslip batches are displayed in a list view, by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:224 +msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, whether it was a :guilabel:`Credit note`, its :guilabel:`Status`, and the :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "View displaying all batches created." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:231 +msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, modifications can be made. To make any modifications to a batch, click the :guilabel:`Edit` button. Then, proceed to make any necessary changes." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:235 +msgid "When all desired changes have been made, click either :guilabel:`Save` to save the changes, or :guilabel:`Discard` to revert back to the original data." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "After modifications have been saved, click the :guilabel:`Generate Payslips` button to reveal a :guilabel:`Generate Payslips` pop-up form, in which payslips affected by the changes can be created or modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:242 +msgid "All payslips associated with the batch are displayed in the employees section of the :guilabel:`Generate Payslips` pop-up. To filter the results by either the :guilabel:`Salary Structure` and/or the :guilabel:`Department`, select a salary structure and/or department from the respective drop-down menus." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:247 +msgid "Only employees that match the selected :guilabel:`Salary Structure` and/or :guilabel:`Department` appear in the employees list. Click the :guilabel:`Generate` button at the bottom of the :guilabel:`Generate Payslips` pop-up window to generate the modified payslips, and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Generate payslips from the edited batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:256 +msgid "Back on the batch details page, click the :guilabel:`Create Draft Entry` smart button to create a draft of the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:263 +msgid "Once the draft payslips are created, the button changes to say :guilabel:`Make Payment`. Click the :guilabel:`Make Payment` button. A pop-up window appears, in which the bank journal information must be entered. Select the :guilabel:`Bank Journal` from the drop-down list, and click :guilabel:`Confirm` to process the payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:268 +msgid "On the batch detail page, the number of payslips in the batch is accessible via the :guilabel:`Payslips` smart button, located in the top-right corner. Individual payslips for the batch can be viewed by clicking the :guilabel:`Payslips` smart button in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:272 +msgid "Use the breadcrumb menu to navigate back to the individual batch detail page, or back to the list of all batches." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Click the Payslips smart button to view the individual payslips in the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:280 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:282 +msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`Create` button in the upper-left corner. Doing so reveals a blank payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:286 +msgid "On the new payslip batch form, enter the :guilabel:`Name` for the batch, and select the date range to which the batch applies, by clicking the :guilabel:`ā–¼ (drop-down arrow)` icon in the :guilabel:`Period` fields, which reveals a calendar pop-up window. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +msgid "If the batch is a credit note, check the box next to :guilabel:`Credit Note`. Then, in the :guilabel:`Generation Date` field, select the date the payslips should be generated from a calendar pop-up window. This generated date is reflected in the accounting journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:299 +msgid "Lastly, in the :guilabel:`Company` field, select the company these payslips are written against." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:301 +msgid "When all the information on the payslip batch form is correct, click the :guilabel:`Save` button to save the information. To delete the entry, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:304 +msgid "To create the payslips for the newly-created batch, click the :guilabel:`Generate Payslips` button at the top of the form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:307 +msgid "When clicked, a pop-up window appears showing all the payslips that will be created. To remove any individual payslips, click the black :guilabel:`āœ– (x mark)` icon at the far right of the payslip line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:311 +msgid "If a specific :guilabel:`Salary Structure` or :guilabel:`Department` needs to be specified for the batch, select them from the corresponding drop-down menus." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "Click the :guilabel:`Generate` button at the bottom of the pop-up window to create the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Generate payslips for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:322 +msgid "On the :guilabel:`Generate Payslips` pop-up window, selecting a :guilabel:`Department` and/or :guilabel:`Salary Structure` only displays payslips that apply to those specifically-selected parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:326 +msgid "If there are any errors or issues preventing the payslips from being generated, an error message appears in the top-right section. This error box disappears on its own after several seconds, or the :guilabel:`āœ– (x mark)` icon can be clicked to close the alert." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:330 +msgid "To remedy the issue, make any necessary modifications (e.g. removing any payslip lines that cannot be processed), then click the :guilabel:`Generate` button again." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "Once the payslips have been successfully generated, the screen returns to the payslip batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:335 +msgid "From here, click the :guilabel:`Generate Draft Entry` button to change the payslips' status from :guilabel:`Draft` to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:338 +msgid "Once payslips have been generated, click the :guilabel:`Make Payment` button to process the payments. Doing so reveals a pop-up window, in which the proper banking information must be entered. In this pop-up window, select the appropriate :guilabel:`Bank Journal` from the drop-down menu, and enter the appropriate file name." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "When done, click the :guilabel:`Confirm` button to confirm the information, or click :guilabel:`Cancel` to discard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "Generate commission payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:349 +msgid "Commission payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`). To generate commission payslips from this page, click on the desired batch (or batches) to create commissions payslips for, then click the :guilabel:`Generate Commission Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:354 +msgid "Doing so reveals a :guilabel:`Generate Commission Payslip` pop-up window, in which the necessary information **must** be filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the commission details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:361 +msgid "On this pop-up window, click on the drop-down menus, located beside the :guilabel:`Period` field, to reveal calendar pop-up windows. On these calendar pop-up windows, select the desired period for which the payslips are being generated. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrows, navigate to the correct month, and click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:366 +msgid "In the :guilabel:`Department` field, select the desired department from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:368 +msgid "When a department is selected, the employees listed for that department appear in the :guilabel:`Employee` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:371 +msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the appropriate column. To remove an employee, click the :guilabel:`šŸ—‘ļø (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +msgid "Add a new entry by clicking :guilabel:`Add a Line`, and entering the :guilabel:`Employee` and the appropriate :guilabel:`Commission Amount`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:378 +msgid "Click the :guilabel:`Upload Your File` button to add a file, if necessary. Any file type is accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:381 +msgid "Using the drop-down menu beside the :guilabel:`Commission Type` field, select either :guilabel:`Classic Commission` or :guilabel:`Warrant`. :guilabel:`Classic` is the most typical of commission, while :guilabel:`Warrant` is primarily used for Belgium companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:385 +msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the commission payslips." +msgstr "" + #: ../../content/applications/hr/payroll/work_entries.rst:5 msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift." msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 1da8998a9..35727e748 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 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,6 +33,7 @@ msgid "`Odoo Tutorials: Barcode Basics `_ consolidates multiple pieces of information in a single barcode. Each piece needs to follow a specific barcode patternā€”which is a defined format of numbers, letters, special characters, and character lengthā€”to ensure proper interpretation of the barcode. By scanning the barcode on an unopened box, GS1 nomenclature can identify the product, lot number, number of units contained, and more." -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:12 -msgid "`All GS1 barcodes `_" +msgid "`GS1 nomenclature `_ consolidates various product and supply chain data into a single barcode. Odoo takes in `unique Global Trade Item Numbers `_ (GTIN), purchased by businesses, to enable global shipping, sales, and eCommerce product listing." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:13 -msgid ":ref:`Odoo's default GS1 rules `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:14 -msgid ":ref:`Why's my barcode not working? `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:19 -msgid "Set up barcode nomenclature" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:17 +msgid "Configure GS1 nomenclature to scan barcodes of sealed boxes and identify essential product information, such as |GTIN|, lot number, quantity information, and more." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:21 +msgid "|GTINs| are unique product identification that **must** be `purchased from GS1 `_ to use GS1 barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:25 +msgid "`All GS1 barcodes `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:26 +msgid ":ref:`Odoo's default GS1 rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:27 +msgid ":ref:`Why's my barcode not working? `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:32 +msgid "Set up barcode nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:34 msgid "To use GS1 nomenclature, navigate to the :menuselection:`Inventory app --> Configuration --> Settings`. Then under the :guilabel:`Barcode` section, check the :guilabel:`Barcode Scanner` box. Next, select :menuselection:`Barcode Nomenclature --> Default GS1 Nomenclature` from the default barcode nomenclature options." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:-1 -msgid "Choose GS1 from dropdown and click the internal link to see the list of GS1 rules." +msgid "Choose GS1 from dropdown and click the external link to see the list of GS1 rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:30 -msgid "To view and edit a list of GS1 *rules* and *barcode patterns* Odoo supports by default, click the :guilabel:`āž”ļø (External link)` icon to the right of the :guilabel:`Barcode Nomenclature` selection." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:33 -msgid "Opening the pop-up table provides an editable view of GS1 :guilabel:`Rule Names` available in Odoo. The table contains all the information that can be condensed with a GS1 barcode, along with the corresponding :guilabel:`Barcode Pattern`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:38 -msgid "After setting GS1 as the barcode nomenclature, :menuselection:`Barcode Nomenclatures` can also be accessed by first enabling :ref:`developer mode `. Navigate to :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures` and finally, select :guilabel:`Default GS1 Nomenclature`." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:43 +msgid "The list of GS1 *rules* and *barcode patterns* Odoo supports by default is accessible by clicking the :guilabel:`āž”ļø (arrow)` icon to the right of the :guilabel:`Barcode Nomenclature` selection." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:46 -msgid "Use GS1 barcode" +msgid "In the :guilabel:`Open: Nomenclature` pop-up table, view and edit the GS1 :guilabel:`Rule Names` available in Odoo. The table contains all the information that can be condensed with a GS1 barcode, along with the corresponding :guilabel:`Barcode Pattern`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:48 -msgid "To build GS1 barcodes in Odoo, combine multiple pieces of information using the specified barcode pattern. The `application identifier `_ (A.I.) serves as the universal prefix for GS1 for barcode identification. Odoo uses regular expressions to describe barcode patterns concisely. Each barcode pattern begins with a required 2-4 digit :abbr:`A.I. (application identifier)`, which corresponds to the rule defined in the system's :ref:`barcode nomenclature list `. By including the appropriate :abbr:`A.I. (application identifier)` from the list, Odoo can accurately interpret GS1 barcodes. While most barcode patterns have a flexible length, some specific patterns, such as barcodes for dates, have defined length requirements." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:51 +msgid "After setting GS1 as the barcode nomenclature, the :menuselection:`Barcode Nomenclatures` settings can also be accessed by a hidden menu that's discoverable after enabling :ref:`developer mode `. Once enabled, navigate to the :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures` menu and finally, select :guilabel:`Default GS1 Nomenclature`." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:60 -msgid "Use the FNC1 separator (`\\x1D`) to end the barcode without needing to reach the maximum character length." +msgid "Use GS1 barcodes in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:63 -msgid "Refer to the :ref:`GS1 nomenclature list ` to see a comprehensive list of all barcode patterns and rules to follow. Otherwise, the following section contains examples of how to generate a barcode for common items in a warehouse." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:62 +msgid "For product identification using GS1 barcodes in Odoo, businesses obtain a `unique GTIN `_ as an internationally distinct product identifier purchased from GS1. This |GTIN| is combined with specific product details following GS1's designated *barcode pattern*. The barcode pattern's arrangement of numbers and letters must adhere to GS1 conventions for accurate interpretation by global systems along the supply chain." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:68 -msgid "Product + quantity + lot" +msgid "Every barcode starts with a 2-4 digit `application identifier `_ (A.I.). This required prefix universally indicates what kind of information the barcode contains. Odoo follows GS1 rules for identifying information, as detailed in the :ref:`default GS1 rules list `. Including the relevant |AI| from the list enables Odoo to correctly interpret GS1 barcodes. While most barcode patterns have a fixed length requirement, certain ones, such as lots and serial numbers, have flexible length." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:70 -msgid "To build a GS1 barcode for a box that contains a product, number of units in it, and the lot number, the following barcode patterns are used:" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:77 +msgid "For flexible-length barcode patterns not placed at the end of the GS1 barcode, use the FNC1 separator (`\\\\x1D`) to end the barcode." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:188 -msgid "Name" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:80 +msgid "Example: The barcode pattern for lot numbers is 20 characters long. Instead of creating a 20-character lot number barcode, like `LOT00000000000000001`, use the FNC1 separator to make it shorter: `LOT001\\x1D`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:188 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:302 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:84 +msgid "Refer to the :ref:`GS1 nomenclature list ` to see a comprehensive list of all barcode patterns and rules to follow. Otherwise, refer to :ref:`this GS1 usage doc ` for specific examples of combining |GTIN| to product information and configuring the workflow." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:90 +msgid ":ref:`Lots workflow `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:91 +msgid ":ref:`Non-unit quantities workflow `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 +msgid "Create rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:98 +msgid "GS1 rules are a specific format of information contained in the barcode, beginning with an |AI| and containing a defined length of characters. Scanning GS1 barcodes from the :ref:`default GS1 list ` auto-fills corresponding data in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:103 +msgid "Adding GS1 barcode rules in Odoo ensures accurate interpretation of unique, non-standard GS1 formats." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:106 +msgid "To do so, begin by turning on :ref:`developer mode ` and navigating to the :guilabel:`Barcode Nomenclatures` list in :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. Then, select the :guilabel:`Default GS1 Nomenclature` list item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:110 +msgid "On the :guilabel:`Default GS1 Nomenclature` page, select :guilabel:`Add a line` at the bottom of the table, which opens a window to create a new rule. The :guilabel:`Rule Name` field is used internally to identify what the barcode represents. The barcode :guilabel:`Types` are different classifications of information that can be understood by the system (e.g. product, quantity, best before date, package, coupon). The :guilabel:`Sequence` represents the priority of the rule; this means the smaller the value, the higher the rule appears on the table. Odoo follows the sequential order of this table and will use the first rule it matches based on the sequence. The :guilabel:`Barcode Pattern` is how the sequence of letters or numbers is recognized by the system to contain information about the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:120 +msgid "After filling in the information, click the :guilabel:`Save & New` button to make another rule or click :guilabel:`Save & Close` to save and return to the table of rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:126 +msgid "Barcode troubleshooting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:128 +msgid "Since GS1 barcodes are challenging to work with, here are some checks to try when the barcodes are not working as expected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:131 +msgid "Ensure that the :guilabel:`Barcode Nomenclature` setting is set as :menuselection:`Default GS1 Nomenclature`. Jump to the :ref:`nomenclature setup section ` for more details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:134 +msgid "Ensure that the fields scanned in the barcode are enabled in Odoo. For example, to scan a barcode containing lots and serial numbers, make sure the :guilabel:`Lots & Serial Numbers` feature is enabled in :ref:`Odoo's settings ` and :ref:`on the product `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:138 +msgid "Omit punctuation such as parentheses `()` or brackets `[]` between the :abbr:`A.I. (Application Identifier)` and the barcode sequence. These are typically used in examples for ease of reading and should **not** be included in the final barcode. For more details on building GS1 barcodes, go to :ref:`this section `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:142 +msgid "When a single barcode contains multiple encoded fields, Odoo requires all rules to be listed in the barcode nomenclature for Odoo to read the barcode. :ref:`This section ` details how to add new rules in the barcode nomenclature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:146 +msgid "Test barcodes containing multiple encoded fields, piece by piece, to figure out which field is causing the issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:150 +msgid "When testing a barcode containing the |GTIN|, lot number, and quantity, start by scanning the |GTIN| alone. Then, test the |GTIN| with the lot number, and finally, try scanning the whole barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:154 +msgid "After diagnosing the encoded field is unknown, :ref:`add new rules ` to Odoo's default list to recognize GS1 barcodes with unique specifications." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:159 +msgid "While the new field will be read, the information won't link to an existing field in Odoo without developer customizations. However, adding new rules is necessary to ensure the rest of the fields in the barcode are interpreted correctly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:166 +msgid "GS1 nomenclature list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:168 +msgid "The table below contains Odoo's default list of GS1 rules. Barcode patterns are written in regular expressions. Only the first three rules require a `check digit `_ as the final character." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 msgid "Rule Name" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:188 -msgid "A.I." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Type" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:188 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:302 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 msgid "Barcode Pattern" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:188 -msgid "Field in Odoo" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "GS1 Content Type" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:190 -msgid "Product" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Odoo field" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:190 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:306 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Serial Shipping Container Code" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "(00)(\\\\d{18})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "Numeric identifier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 msgid "Global Trade Item Number (GTIN)" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:190 -msgid "01" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "Unit Product" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:190 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:306 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 msgid "(01)(\\\\d{14})" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:190 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:306 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 msgid ":guilabel:`Barcode` field on product form" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:335 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:337 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:340 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:342 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:344 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:346 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:348 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:350 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:352 -msgid "Quantity" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "GTIN of contained trade items" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:193 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:335 -msgid "Variable count of items" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "(02)(\\\\d{14})" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:79 -msgid "30" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "Packaging" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:335 -msgid "(30)(\\\\d{0,8})" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +msgid "Ship to / Deliver to global location" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:193 -msgid ":guilabel:`Units` field on transfer form" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Destination location" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:81 -msgid "Lot Number" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +msgid "(410)(\\\\d{13})" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:81 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:320 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Ship / Deliver for forward" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "(413)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Source location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "I.D. of a physical location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:17 +msgid "Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "(414)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 msgid "Batch or lot number" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:81 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "Lot" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Alpha-numeric name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "Serial number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "(21) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "(13)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Pack date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "(15)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "(17)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiry date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "Variable count of items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +msgid "Quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +msgid "(30)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +msgid "UoM: Units" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "Count of trade items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "(37)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "Qty in units for containers (AI 02)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +msgid "Net weight: kilograms (kg)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "(310[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +msgid "Qty in kg" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "Length in meters (m)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "(311[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "Qty in m" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "Net volume: liters (L)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "(315[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "Qty in L" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "Net volume: cubic meters (m\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "(316[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "Qty in m\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "Length in inches (in)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "(321[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "Qty in inches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "Net weight/volume: ounces (oz)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "(357[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "Qty in oz" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Net volume: cubic feet (ft\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "(365[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Qty in ft\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging Type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Package type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:3 +msgid "GS1 barcode usage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:10 +msgid "GS1 barcodes provide a standardized format that barcode scanners can interpret. They encode information in a :ref:`specific structure recognized globally `, allowing scanners to understand and process supply chain data consistently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:14 +msgid "Odoo *Barcode* interprets and prints GS1 barcodes, automating product identification and tracking in warehouse operations such as receiving, picking, and shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:17 +msgid "The following sections contain examples of how Odoo uses GS1 barcodes provided by the business to identify common warehouse items and automate certain warehouse workflows." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:21 +msgid "Odoo **does not** create GS1 barcodes. Businesses must purchase a unique Global Trade Item Number (GTIN) from GS1. Then, they can combine their existing GS1 barcodes with product and supply chain information (also provided by GS1) to create barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:26 +msgid "`Purchase GTINs `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:27 +msgid ":ref:`GS1 nomenclature `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:32 +msgid "Configure barcodes for product, quantity, and lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:34 +msgid "To build a GS1 barcode that contains information about a product, its quantities, and the lot number, the following barcode patterns and Application Identifiers (A.I.) are used:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "A.I." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Field in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid "Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:135 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:203 +msgid "01" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:139 +msgid "30" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid ":guilabel:`Units` field on transfer form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid "Lot Number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 msgid "10" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:81 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 msgid "(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:81 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 msgid ":guilabel:`Lot` on Detailed Operations pop-up" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:88 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:52 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:39 #: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:14 -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:20 -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:51 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:9 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/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:18 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:84 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:15 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:17 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:11 #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:9 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:13 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10 msgid "Configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:90 -msgid "To track products using lots, first enable the :ref:`Lots and Serial Numbers ` feature. To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Next, under the :guilabel:`Traceability` heading, check the box for :guilabel:`Lots & Serial Numbers`." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:54 +msgid "First, :ref:`enable product tracking using lots ` by navigating to :menuselection:`Inventory app --> Configuration --> Settings`, and checking the box for :guilabel:`Lots & Serial Numbers` under the :guilabel:`Traceability` heading." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:95 -msgid "Then, set up the product barcode by navigating to the intended product form in :menuselection:`Inventory app --> Products --> Products` and selecting the product. On the product form, click :guilabel:`Edit`. Then, in the :guilabel:`General Information` tab, fill in the :guilabel:`Barcode` field with the 14-digit `Global Trade Item Number (GTIN) `_, which is a universal and unique identifying number from GS1." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:58 +msgid "Then, set up the product barcode by navigating to the intended product form in :menuselection:`Inventory app --> Products --> Products` and selecting the product. On the product form, click :guilabel:`Edit`. Then, in the :guilabel:`General Information` tab, fill in the :guilabel:`Barcode` field with the unique 14-digit `Global Trade Item Number (GTIN) `_, which is a universally recognized identifying number that is provided by GS1." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:103 -msgid "On the product form, omit the :abbr:`A.I. (application identifier)` `01` for GTIN product barcode pattern, as it is only used to encode multiple barcodes into a single barcode that contains detailed information about the package contents." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:66 +msgid "On the product form, omit the |AI| `01` for |GTIN| product barcode pattern, as it is only used to encode multiple barcodes into a single barcode that contains detailed information about the package contents." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:108 -msgid "To create a barcode for the product, `Fuji Apple`, enter the 14-digit GTIN `12345678901231` in the :guilabel:`Barcode` field on the product form." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:72 +msgid "To record the GS1 barcode for the product, `Fuji Apple`, enter the 14-digit |GTIN| `20611628936004` in the :guilabel:`Barcode` field on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 msgid "Enter 14-digit GTIN into the Barcode field on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:116 -msgid "It is also possible to view a list of all products and barcodes. To access this list, go to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Barcode` heading, click on the :guilabel:`Configure Product Barcodes` button under the :guilabel:`Barcode Scanner` section. Enter the 14-digit GTIN into the :guilabel:`Barcode` column, then click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:80 +msgid "To view a list of *all* products and their corresponding barcodes in the Odoo database, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Barcode` heading, click on the :guilabel:`Configure Product Barcodes` button under the :guilabel:`Barcode Scanner` section. Enter the 14-digit |GTIN| into the :guilabel:`Barcode` column, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 msgid "View the Product Barcodes page from inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:128 -msgid "Next, enable lots and serial number tracking on the product. Select the :guilabel:`Inventory` tab on the product form. Under :guilabel:`Tracking`, choose the :guilabel:`By Lots` radio button." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:92 +msgid "After activating tracking by lots and serial numbers from the settings page, specify that this feature is to be applied on each product by navigating to the :guilabel:`Inventory` tab on the product form. Under :guilabel:`Tracking`, choose the :guilabel:`By Lots` radio button." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:-1 msgid "Enable product tracking by lots in the \"Inventory\" tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:136 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:198 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:101 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:176 msgid "Scan barcode on receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:138 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:103 msgid "To ensure accurate lot interpretation in Odoo on product barcodes scanned during a receipt operation, navigate to the :menuselection:`Barcode` app to manage the :ref:`receipt picking process `." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:142 -msgid "From the :guilabel:`Barcode Scanning` dashboard, click the :guilabel:`Operations` button, then the :guilabel:`Receipts` button to view the list of vendor receptions to process. Receipts generated from :abbr:`POs (Purchase Orders)` are listed, but new receipt operations can also be created directly through the :menuselection:`Barcode` app using the :guilabel:`Create` button." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:107 +msgid "From the :guilabel:`Barcode Scanning` dashboard, click the :guilabel:`Operations` button, then the :guilabel:`Receipts` button to view the list of vendor receipts to process. Receipts generated from :abbr:`POs (Purchase Orders)` are listed, but new receipt operations can also be created directly through the :menuselection:`Barcode` app using the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:147 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:112 msgid "On the list of receipts, click on the warehouse operation (`WH/IN`) and scan product barcodes and lot numbers with a barcode scanner. The scanned product then appears on the list. Use the :guilabel:`āœļø (pencil)` button to open a window and manually enter quantities for specific lot numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:153 -msgid "After placing a :abbr:`PO (Purchase Order)` for 50 apples, navigate to the associated receipt. Scan the product barcode, and Odoo will prompt for the lot number." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:118 +msgid "After placing a :abbr:`PO (Purchase Order)` for fifty apples, navigate to the associated receipt in the *Barcode* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:121 +msgid "Scan the barcode containing the |GTIN|, quantity, and lot number. For testing with a barcode scanner, below is an example barcode for the fifty Fuji apples in Lot 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:129 +msgid "50 Fuji apples in Lot0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:131 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:199 +msgid "2D Matrix" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "2D matrix of GS1 barcode of 50 fuji apples with an assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:134 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:202 +msgid "|AI| (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:136 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:204 +msgid "GS1 Barcode (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:137 +msgid "20611628936004" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:138 +msgid "|AI| (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:140 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:208 +msgid "GS1 Barcode (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:141 +msgid "00000050" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:142 +msgid "|AI| (lot)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:144 +msgid "GS1 Barcode (lot #)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:145 +msgid "LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:146 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:210 +msgid "Full GS1 barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:147 +msgid "01206116289360043 000000050 10LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:149 +msgid ":ref:`If the configuration is correct `, `50/50` :guilabel:`Units` processed will be displayed and the :guilabel:`Validate` button turns green. Click the :guilabel:`Validate` button to complete the reception." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 msgid "Scan the barcode for a product on the reception picking page in the *Barcode* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:160 -msgid "Scan the lot number to process 1 of 50 apples. To avoid scanning 49 remaining barcodes, click the :guilabel:`āœļø (pencil)` button next to the desired lot number." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:160 +msgid "Configure barcode for product and non-unit quantity" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:0 -msgid "Scan lot number and click the pencil to edit quantities." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:167 -msgid "Doing so opens a mobile-friendly keypad page to specify received quantities. Use the keypad to specify the :guilabel:`Units` for the lot number. When finished, click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:0 -msgid "Change scanned quantities using pencil button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:174 -msgid "Repeat this process to specify additional lot numbers and quantities in this receipt. Once the :guilabel:`Units` are all accounted for, finish the reception by clicking the :guilabel:`Validate` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:178 -msgid "Alternatively, scan the barcode containing the product, lot number, and quantity to complete the receipt operation in fewer steps." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:182 -msgid "Product + non-unit quantity" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:184 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:162 msgid "To build a GS1 barcode that contains products measured in a non-unit quantity, like kilograms, for example, the following barcode patterns are used:" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:193 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 msgid "Quantity in kilograms" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:193 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 msgid "310[0-5]" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:193 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:340 -msgid "(310[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:178 msgid "To confirm that quantities are correctly interpreted in Odoo, place an order in the *Purchase* app using the appropriate unit of measure (:guilabel:`UoM`) for the quantity of products to be purchased." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:205 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:183 msgid ":ref:`Simplify vendor unit conversions with UoMs `" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:207 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:185 msgid "After the order is placed, navigate to the :menuselection:`Barcode` app to :ref:`receive the vendor shipment `." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 -msgid "On the receipt in the *Barcode* app, receive an order for `52.1 kg` of peaches by scanning the barcode. If `52.1 / 52.1` :guilabel:`kg` appears on the page, this means the reception was processed without issue. Finally, press :guilabel:`Validate`." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:189 +msgid "On the receipt in the *Barcode* app, receive an order for `52.1 kg` of peaches by scanning the barcode containing the |GTIN| and quantity of peaches in kilograms." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 -msgid "Note: the :abbr:`A.I. (application identifier)` for kilograms, `310` + `1`, was used to represent `52.1` kg as a barcode: `000521`. This is because the `1` represents how many digits from the right to place the decimal point." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:197 +msgid "52.1 kg of Peaches" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "2D matrix of GS1 barcode of 52.1 kg of peaches." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:205 +msgid "00614141000012" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:206 +msgid "|AI| (kg, 1 decimal point)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:207 +msgid "3101" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:209 +msgid "000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:211 +msgid "0100614141000012 3101000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:213 +msgid ":ref:`If the configuration is correct `, `52.1 / 52.1` :guilabel:`kg` will be displayed and the :guilabel:`Validate` button turns green. Finally, press :guilabel:`Validate` to complete the validation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 msgid "Scan barcode screen for a reception operation in the Barcode app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 -msgid "For additional verification purposes, the quantities of received products are also recorded on the :guilabel:`Product Moves` report, accessible by navigating to :menuselection:`Inventory app --> Reporting --> Product Moves`." +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:222 +msgid "Verify product moves" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:227 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:224 +msgid "For additional verification, the quantities of received products are also recorded on the :guilabel:`Product Moves` report, accessible by navigating to :menuselection:`Inventory app --> Reporting --> Product Moves`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:228 msgid "The items on the :guilabel:`Product Moves` report are grouped by product by default. To confirm the received quantities, click on a product line to open its collapsible drop-down menu, which displays a list of *stock move lines* for the product. The latest stock move matches the warehouse reception reference number (e.g. `WH/IN/00013`) and quantity processed in the barcode scan, demonstrating that the records processed in the *Barcode* app were properly stored in *Inventory*." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:-1 msgid "Reception stock move record for 52.1 kg of peaches." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:240 -msgid "Create rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:242 -msgid "If a supplier uses a GS1 barcode with a field not supported by Odoo's :ref:`default GS1 list `, Odoo will fail to interpret the entire barcode. To ensure the complete reading of the barcode, it is necessary to add the missing barcode to Odoo's list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:248 -msgid "While the new field will be read, the information won't link to an existing field in Odoo without developer customizations. However, adding new rules is still useful to ensure the rest of the fields in the barcode are interpreted correctly." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:252 -msgid "Begin by turning on :ref:`developer mode ` and navigating to the :guilabel:`Barcode Nomenclatures` list in :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. Then, select the :guilabel:`Default GS1 Nomenclature` list item." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:256 -msgid "On the :guilabel:`Default GS1 Nomenclature` page, select :guilabel:`Add a line` at the bottom of the table, which opens a window to create a new rule. The :guilabel:`Rule Name` field is used internally to identify what the barcode represents. The barcode :guilabel:`Types` are different classifications of information that can be understood by the system (e.g. product, quantity, best before date, package, coupon). The :guilabel:`Sequence` represents the priority of the rule; this means the smaller the value, the higher the rule appears on the table. Odoo follows the sequential order of this table and will use the first rule it matches based on the sequence. The :guilabel:`Barcode Pattern` is how the sequence of letters or numbers is recognized by the system to contain information about the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:266 -msgid "After filling in the information, click the :guilabel:`Save & New` button to make another rule or click :guilabel:`Save & Close` to save and return to the table of rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:272 -msgid "Barcode troubleshooting" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:274 -msgid "Since GS1 barcodes are challenging to work with, here are some checks to try when the barcodes are not working as expected:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:277 -msgid "Ensure that the :guilabel:`Barcode Nomenclature` setting is set as :menuselection:`Default GS1 Nomenclature`. Jump to the :ref:`nomenclature setup section ` for more details." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:280 -msgid "Ensure that the fields scanned in the barcode are enabled in Odoo. For example, to scan a barcode containing lots and serial numbers, make sure the :guilabel:`Lots & Serial Numbers` feature is enabled in :ref:`Odoo's settings ` and :ref:`on the product `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:284 -msgid "Omit punctuation such as parentheses `()` or brackets `[]` between the :abbr:`A.I. (Application Identifier)` and the barcode sequence. These are typically used in examples for ease of reading and should **not** be included in the final barcode. For more details on building GS1 barcodes, go to :ref:`this section `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:288 -msgid "When a single barcode contains multiple encoded fields, Odoo requires all rules to be listed in the barcode nomenclature for Odoo to read the barcode. :ref:`This section ` details how to add new rules in the barcode nomenclature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:295 -msgid "GS1 nomenclature list" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:297 -msgid "The table below contains Odoo's default list of GS1 rules. Barcode patterns are written in regular expressions. Only the first three rules require a `check digit `_ as the final character." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:302 -msgid "Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:302 -msgid "GS1 Content Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:302 -msgid "Odoo field" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:304 -msgid "Serial Shipping Container Code" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:304 -msgid "Package" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:304 -msgid "(00)(\\\\d{18})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:304 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:306 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:309 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:312 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:315 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:318 -msgid "Numeric identifier" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:304 -msgid "Package name" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:306 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:309 -msgid "Unit Product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:309 -msgid "GTIN of contained trade items" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:309 -msgid "(02)(\\\\d{14})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:309 -msgid "Packaging" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:312 -msgid "Ship to / Deliver to global location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:312 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:315 -msgid "Destination location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:312 -msgid "(410)(\\\\d{13})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:315 -msgid "Ship / Deliver for forward" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:315 -msgid "(413)(\\\\d{13})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:315 -msgid "Source location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:318 -msgid "I.D. of a physical location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:318 -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:15 -msgid "Location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:318 -msgid "(414)(\\\\d{13})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:320 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:323 -msgid "Lot" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:320 -msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:320 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:323 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:354 -msgid "Alpha-numeric name" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:323 -msgid "Serial number" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:323 -msgid "(21) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:326 -msgid "Packaging date (YYMMDD)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:326 -msgid "Packaging Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:326 -msgid "(13)(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:326 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:329 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:332 -msgid "Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:326 -msgid "Pack date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:329 -msgid "Best before date (YYMMDD)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:329 -msgid "Best before Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:329 -msgid "(15)(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:329 -msgid "Best before date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:332 -msgid "Expiration date (YYMMDD)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:332 -msgid "Expiration Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:332 -msgid "(17)(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:332 -msgid "Expiry date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:335 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:337 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:340 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:342 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:344 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:346 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:348 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:350 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:352 -msgid "Measure" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:335 -msgid "UoM: Units" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:337 -msgid "Count of trade items" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:337 -msgid "(37)(\\\\d{0,8})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:337 -msgid "Qty in units for containers (AI 02)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:340 -msgid "Net weight: kilograms (kg)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:340 -msgid "Qty in kg" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:342 -msgid "Length in meters (m)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:342 -msgid "(311[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:342 -msgid "Qty in m" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:344 -msgid "Net volume: liters (L)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:344 -msgid "(315[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:344 -msgid "Qty in L" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:346 -msgid "Net volume: cubic meters (m\\ :sup:`3`)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:346 -msgid "(316[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:346 -msgid "Qty in m\\ :sup:`3`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:348 -msgid "Length in inches (in)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:348 -msgid "(321[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:348 -msgid "Qty in inches" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:350 -msgid "Net weight/volume: ounces (oz)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:350 -msgid "(357[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:350 -msgid "Qty in oz" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:352 -msgid "Net volume: cubic feet (ft\\ :sup:`3`)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:352 -msgid "(365[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:352 -msgid "Qty in ft\\ :sup:`3`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:354 -msgid "Packaging type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:354 -msgid "Packaging Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:354 -msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:354 -msgid "Package type" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:3 msgid "Process to Transfers" msgstr "" @@ -974,47 +1126,95 @@ msgid "Set up your barcode scanner" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:7 -msgid "Getting started with barcode scanning in Odoo is fairly easy. Yet, a good user experience relies on an appropriate hardware setup. This guide will help you through the task of choosing and configuring the barcode scanner." +msgid "Follow this guide to choose and set up a barcode scanner compatible with Odoo's *Inventory* and *Barcode* apps." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:13 -msgid "Find the barcode scanner that suits your needs" +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:14 +msgid "An image of an example barcode scanner." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:15 -msgid "The 3 recommended type of barcode scanners to work with the Odoo **Inventory** and **Barcode Scanning** apps are the **USB scanner**, **the bluetooth scanner** and the **mobile computer scanner**." +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:17 +msgid "Scanner types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:19 +msgid "Before setting up a barcode scanner, it is important to determine which scanner type best meets the needs of the business. There are three main types, each with their own benefits and use cases:" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:22 -msgid "If you scan products at a computer location, the **USB scanner** is the way to go. Simply plug it in the computer to start scanning. Just make sure when you buy it that the scanner is compatible with your keyboard layout or can be configured to be so." +msgid "**USB scanners** are connected to a computer, and are suitable for businesses that scan products at a fixed location, like at the checkout in a grocery store. Ensure the chosen USB scanner is compatible with the keyboard layout of the computer." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:27 -msgid "The **bluetooth scanner** can be paired with a smartphone or a tablet and is a good choice if you want to be mobile but don't need a big investment. An approach is to log in Odoo on you smartphone, pair the bluetooth scanner with the smartphone and work in the warehouse with the possibility to check your smartphone from time to time and use the software 'manually'." +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:26 +msgid "**Bluetooth scanners** pair with a smartphone or tablet, making them an ideal cost-effective and portable barcode scanner option. In this scenario, Odoo is installed on the smartphone, allowing warehouse operators to handle operations, and check stock directly through their mobile devices." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:34 -msgid "For heavy use, the **mobile computer scanner** is the handiest solution. It consists of a small computer with a built-in barcode scanner. This one can turn out to be a very productive solution, however you need to make sure that is is capable of running Odoo smoothly. The most recent models using Android + Google Chrome or Windows + Internet Explorer Mobile should do the job. However, due to the variety of models and configurations on the market, it is essential to test it first." +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:30 +msgid "**Mobile computer scanners** are mobile devices with a built-in barcode scanner. First, ensure the device can run the Odoo mobile app properly. Recent models that use Android OS with the Google Chrome browser, or Windows OS with Microsoft Edge, should work. However, testing is crucial due to the variety of available models and configurations." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:44 -msgid "Configure your barcode scanner" +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:36 +msgid "`Compatible hardware with Odoo Inventory `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:47 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:41 +msgid "When setting up the barcode scanner, make sure the following configurations are correct so the scanner can properly interpret barcodes with Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:45 msgid "Keyboard layout" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:52 -msgid "An USB barcode scanner needs to be configured to use the same keyboard layout as your operating system. Otherwise, your scanner won't translate characters correctly (replacing a 'A' with a 'Q' for example). Most scanners are configured by scanning the appropriate barcode in the user manual." +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:47 +msgid "When using a USB barcode scanner, match its keyboard layout with the operating system's layout for proper interpretation of characters. Generally, the scanning mode should be set to accept a USB keyboard (HID), with the language set based on the keyboard that is in use." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:59 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:51 +msgid "To configure the keyboard layout for a **Zebra** scanner, scan the keyboard wedge barcode for the desired language in the scanner's user manual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:57 +msgid "Example of a user manual for keyboard layout." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:57 +msgid "Examples of keyboard language settings in the Zebra scanner user manual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:60 msgid "Automatic carriage return" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:61 -msgid "By default, Odoo has a 50 milliseconds delay between each successive scan (it helps avoid accidental double scanning). If you want to suppress this delay, you can configure your scanner to insert a carriage return at the end of each barcode. This is usually the default configuration and can be explicitly configured by scanning a specific barcode in the user manual ('CR suffix ON', 'Apply Enter for suffix', etc.)." +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:62 +msgid "Odoo has a default 100-millisecond delay between scans to prevent accidental double scanning. To synchronize with the barcode scanner, set it to include a *carriage return* (:dfn:`character like the \"Enter\" key on a keyboard`) after each scan. Odoo interprets the carriage return as the end of the barcode input; so Odoo accepts the scan, and waits for the next one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:67 +msgid "Typically, on the scanner, a carriage return is included by default. Ensure it is set by scanning a specific barcode in the user manual, like `CR suffix ON` or `Apply Enter for suffix`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:71 +msgid "Zebra scanner" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:73 +msgid "When using Zebra scanners, ensure the following keystroke configurations are set to prevent errors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:75 +msgid "Begin on the Zebra scanner's home screen, and select the :guilabel:`DataWedge` app (the icon for the app is a light blue barcode). On the :guilabel:`DataWedge Profiles` page, select the profile option to access the Zebra scanner's settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:79 +msgid "Scroll down to the :guilabel:`Keyboard Output` option, and ensure the :guilabel:`Enable/disable keystroke output` option is :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:-1 +msgid "Show keystroke option in the Zebra scanner's DataWedge app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:86 +msgid "Now, go back to the :guilabel:`Profile` options page, and select :guilabel:`Key event options`. Here, ensure the :guilabel:`Send Characters as Events` option is checked." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:3 @@ -1045,31 +1245,31 @@ msgstr "" msgid "Be careful to add barcodes directly on the product variants and not on the template product. Otherwise, you wonā€™t be able to differentiate them." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:47 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:49 msgid "Set Locations Barcodes" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:49 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:51 msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in :menuselection:`Inventory --> Configuration --> Locations`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:60 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:62 msgid "You can easily print the barcode you allocate to the locations via the *Print* menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:64 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:66 msgid "Barcode Formats" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:66 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:68 msgid "Most retail products use EAN-13 barcodes, also known as GTIN (Global Trade Identification Numbers). GTIN are used by companies to uniquely identify their products and services. While GTIN and UPC are often used synonymously, GTIN refers to the number a barcode represents, while UPC refers to the barcode itself. More information about GTIN can be found on the GS1 website." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:71 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:73 msgid "In order to create GTIN for items, a company must have a GS1 Company Prefix. This prefix is the number that will appear at the beginning of each GTIN, and will identify the company as the owner of the barcode any the products it appears on. To learn more about GS1 Company Prefixes, or purchase a license for a prefix, visit the GS1 Company Prefix page." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:76 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:78 msgid "Odoo users are able to use GTIN barcodes to identify their products. However, since Odoo supports any numeric string as a barcode, it is also possible to define a custom barcode for internal use." msgstr "" @@ -1085,6840 +1285,7642 @@ msgstr "" msgid "`Odoo Tutorials: Inventory `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management.rst:5 -msgid "Warehouse management" +#: ../../content/applications/inventory_and_mrp/inventory/product_management.rst:5 +msgid "Product management" 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" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment.rst:5 +msgid "Product replenishment" 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 damages, human errors, theft, 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:12 -msgid "Inventory Adjustments page" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:14 -msgid "To view the *Inventory Adjustments* page, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:-1 -msgid "In stock products listed on the Inventory adjustments page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:21 -msgid "On the :guilabel:`Inventory Adjustments` page, all products that are currently in stock are listed, with each product line containing the following information:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:24 -msgid ":guilabel:`Location`: the specific location in the warehouse where a product is stored." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:25 -msgid ":guilabel:`Product`: the product whose quantity is listed on the inventory adjustment line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:26 -msgid ":guilabel:`Lot/Serial Number`: the tracking identifier assigned to the specific product listed. It can contain letters, numbers, or a combination of both." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:30 -msgid "If a specific product has a quantity of more than `1.00` in stock, and more than one serial number (or lot number) assigned to it, each uniquely-identified product is displayed on its own product line with its own lot/serial number, displayed under the :guilabel:`Lot/Serial Number` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:35 -msgid ":guilabel:`On Hand Quantity`: the quantity of the product currently recorded in the database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:36 -msgid ":guilabel:`UoM`: the *unit of measure* in which the product is measured. Unless otherwise specified (i.e., in :guilabel:`Pounds` or :guilabel:`Ounces`), the default :abbr:`UoM (Unit of Measure)` is :guilabel:`Units`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:39 -msgid ":guilabel:`Counted Quantity`: the real quantity counted during an inventory count. This field is left blank by default, but can be changed, depending on if it matches the :guilabel:`On Hand Quantity` or not." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:42 -msgid ":guilabel:`Difference`: the difference between the :guilabel:`On Hand Quantity` and :guilabel:`Counted Quantity`, once an inventory adjustment is made. The difference is automatically calculated after every inventory adjustment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:45 -msgid ":guilabel:`Scheduled Date`: the date at which a count should be made. If not otherwise specified, this date will default to the 31st of December of the current year." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:47 -msgid ":guilabel:`User`: the person assigned to the count in the database. This can either be the person physically counting the inventory, or applying the count in the database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:49 -msgid ":guilabel:`Product Category`: the category assigned internally to a specific product. Unless otherwise specified (i.e., as :guilabel:`Consumable` or :guilabel:`Rental`), the default *Product Category* is set to :guilabel:`All`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:52 -msgid ":guilabel:`Available Quantity`: the quantity of a specific product that is currently available, based on any outstanding/uncompleted sales orders, purchase orders, or manufacturing orders that might change the available quantity once fulfilled." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:55 -msgid ":guilabel:`Accounting Date`: the date on which the adjustments will be accounted in the Odoo *Accounting* app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:57 -msgid ":guilabel:`Company`: the company whose database these inventory adjustments are being made on. The company is listed in the top right corner of the database, next to the user currently logged in." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:61 -msgid "Some columns are hidden by default. To reveal these columns, click the :guilabel:`additional options` button (three dots icon) to the far right of the form's top row, and select any desired column to reveal by clicking the checkbox next to that option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:66 -msgid "Create an inventory adjustment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:68 -msgid "To create a new inventory adjustment from the :menuselection:`Inventory Adjustments` page, click :guilabel:`Create`. Doing so creates a new, blank inventory adjustment line at the bottom of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:72 -msgid "On this blank inventory adjustment line, click the drop-down menu under the :guilabel:`Product` column, and select a product. If the selected product is tracked using either lots or serial numbers, the desired lot or serial number can also be chosen from the drop-down menu under the :guilabel:`Lot/Serial Number` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:77 -msgid "Next, set the value in the :guilabel:`Counted Quantity` column to the quantity counted for that product during the inventory adjustment process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:81 -msgid "The :guilabel:`Counted Quantity` for new inventory adjustments is set to `0.00` by default. An inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the product's inventory adjustment history, so it should be set to reflect the actual quantity counted." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:85 -msgid "To the right of the :guilabel:`Counted Quantity` column, the :guilabel:`Scheduled Date` and :guilabel:`User` can also be changed via their respective drop-down menus. Changing the :guilabel:`Scheduled Date` changes the date that the inventory adjustment should be processed on, and selecting a responsible :guilabel:`User` assigns a user to the specific inventory adjustment (for traceability purposes)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:91 -msgid "Once all changes have been made to the new inventory adjustment line, click away from the line. Doing so saves the adjustment, and moves the line to the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:94 -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:156 -msgid "If the :guilabel:`Counted Quantity` is greater than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **green**. If the :guilabel:`Counted Quantity` is less than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **red**. If the quantities match, and haven't been changed at all, no value appears in the :guilabel:`Difference` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:-1 -msgid "Difference column on inventory adjustments page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:104 -msgid "At this stage, the count (:dfn:`inventory adjustment`) is recorded, but not yet applied. This means that the quantity on hand before the adjustment has not yet been updated to match the new, real counted quantity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:108 -msgid "There are two ways to apply the new inventory adjustment. The first way is to click the :guilabel:`Apply` button on the line at the far right of the page. The second way is to click the checkbox on the far left of the line. Doing so reveals new button options at the top of the page, one of which is an :guilabel:`Apply` button. Clicking this button instead causes an :guilabel:`Inventory Adjustment Reference / Reason` pop-up window to appear." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:114 -msgid "From this pop-up menu, a reference or reason can be assigned to the inventory adjustment. By default, the :guilabel:`Inventory Reference / Reason` field is pre-populated with the date the adjustment is being made on, but can be changed to reflect whatever reference or reason is desired." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:118 -msgid "Once ready, click :guilabel:`Apply` to apply the inventory adjustment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:-1 -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:125 -msgid "Count products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:127 -msgid "Counting products is a recurring activity in a warehouse. Once a count is complete, go to :menuselection:`Inventory app --> 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:131 -msgid "On each product line, identify whether the value in the :guilabel:`On Hand Quantity` column recorded in the database matches the newly-counted value. If the recorded value and the counted value do match, click the :guilabel:`Set` button (target icon) at the far right of the product line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:135 -msgid "Doing so copies the value from the :guilabel:`On Hand Quantity` column over to the :guilabel:`Counted Quantity` column, and sets the value of the :guilabel:`Difference` column to `0.00`. Subsequently, once applied, an inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the product's inventory adjustment history." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:-1 -msgid "Zero count inventory adjustment move." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:144 -msgid "If the newly-counted value for a given product does **not** match the value in the :guilabel:`On Hand Quantity` recorded in the database, instead of clicking the :guilabel:`Set` button, record the real value in the field in the :guilabel:`Counted Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:148 -msgid "To do so, click the field in the :guilabel:`Counted Quantity` column on the specific inventory adjustment line for the product whose count is being changed. This automatically assigns a :guilabel:`Counted Quantity` of `0.00`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:152 -msgid "To change this value, type in a new value that matches the real, newly-counted value. Then, click away from the line. Doing so saves the adjustment, and automatically adjusts the value in the :guilabel:`Difference` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:162 -msgid "Subsequently, once applied, a move with the difference between the :guilabel:`On Hand Quantity` and the :guilabel:`Counted Quantity` is recorded in the product's inventory adjustment history." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:-1 -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:170 -msgid "Sometimes a count occurs, but cannot 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 on-hand quantity in the database can change and no longer be consistent with the counted quantity. As an extra precaution, Odoo asks for confirmation before applying the inventory adjustment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:177 -msgid "Change inventory count frequency" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:179 -msgid "By default, the *scheduled date* for inventory adjustments are always scheduled for the 31st of December of the current year. However, for some companies, it is crucial that they have an accurate inventory count at all times. In such cases, the default scheduled date can be modified." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:183 -msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting, which includes a drop-down menu that is set to `31 December` by default." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:-1 -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/count_products.rst:191 -msgid "To change the day, click the :guilabel:`31`, and change it to a day within the range `1-31`, depending on the desired month of the year." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:194 -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:115 -msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:197 -msgid "Once all desired changes have been made, click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:200 -msgid "Plan big inventory counts" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:202 -msgid "To plan big inventory counts, such as a full count of everything currently in stock, first navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:205 -msgid "Then, select the desired products to be counted by clicking the checkbox on the far left of each product line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:209 -msgid "To request a count of **all** products currently in stock, click the checkbox at the very top of the table, in the header row next to the :guilabel:`Location` label. This selects **all** product lines." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:-1 -msgid "Request a count popup on inventory adjustments page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:217 -msgid "Once all desired products have been selected, click the :guilabel:`Request a Count` button at the top of the page. This causes a :guilabel:`Request a Count` pop-up window to appear. From this pop-up, fill in the following information:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:221 -msgid ":guilabel:`Inventory Date`: the planned date of the count." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:222 -msgid ":guilabel:`User`: the user responsible for the count." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:223 -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:224 -msgid ":guilabel:`Count`: to leave the on-hand quantity of each product line blank, select :guilabel:`Leave Empty`. To prefill the 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:228 -msgid "Finally, once ready, click :guilabel:`Confirm` to request the count." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:231 -msgid "In the Odoo *Barcode* app, users can only view inventory counts that are assigned to **them**, and are scheduled for **today** or **earlier**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:235 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts`" -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 "For most companies, warehouse stock only needs to be counted once a year. This is why, by default, after making an *inventory adjustment* in Odoo, the scheduled date for the next inventory count is set for the 31st of December of the current year." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:9 -msgid "However, for some businesses, it's crucial to have an accurate inventory count at all times. These companies use *cycle counts* to keep critical stock levels accurate. Cycle counting is a method by which companies count their inventory more often in certain *locations*, to ensure that their physical inventory counts match their inventory records." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:15 -msgid "Activate storage locations" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:17 -msgid "In Odoo, cycle counts are location-based. Therefore, the *storage locations* feature needs to be enabled before performing a cycle count." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:20 -msgid "To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Then, click the checkbox next to :guilabel:`Storage Locations`. Click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 -msgid "Enabled storage locations setting in inventory settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:29 -msgid "Change inventory count frequency by location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:31 -msgid "Now that the storage locations setting is enabled, the inventory count frequency can be changed for specific locations created in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:34 -msgid "To view and edit locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. This reveals a :guilabel:`Locations` page containing every location currently created and listed in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:38 -msgid "From this page, click into a location to reveal the settings and configuration page for that location. Click :guilabel:`Edit` to edit the location settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:41 -msgid "Under the :guilabel:`Cyclic Inventory` section, locate the :guilabel:`Inventory Frequency (Days)` field, which should be set to `0` (if this location has not been edited previously). In this field, change the value to whichever number of days is desired." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 -msgid "Location frequency setting on location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:50 -msgid "A location that needs an inventory count every 30 days should have the :guilabel:`Inventory Frequency (Days)` value set to `30`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:53 -msgid "Once the frequency has been changed to the desired number of days, click :guilabel:`Save` to save changes. Now, once an inventory adjustment is applied to this location, the next scheduled count date is automatically set, based on the value entered into the :guilabel:`Inventory Frequency (Days)` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:59 -msgid "Count inventory by location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:61 -msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in stock, with each product listed on its own line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:66 -msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at the top of the page, under the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 -msgid "Inventory adjustments page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:74 -msgid "To select a specific location and view all products within that location, click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to reveal a new drop-down menu to the right." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:77 -msgid "Click :guilabel:`Location` from the drop-down menu, then click :guilabel:`Apply`. The page now displays condensed drop-down menus of each location in the warehouse that has products in stock, and a cycle count can be performed for all products in that location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:82 -msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right. Click this menu to reveal three drop-downs." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:87 -msgid "For the first field, click and select :guilabel:`Location` from the drop-down. For the second field, leave the :guilabel:`contains` value as is. For the third field, type in the name of the location that is being searched for. Click :guilabel:`Apply` for that location to appear on the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 -msgid "Applied filters and group by on inventory adjustments page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:97 -msgid "Change full inventory count frequency" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:99 -msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of everything in-stock in the warehouse can also be manually changed to push the date up sooner than the date listed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:103 -msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down that is set to `31` :guilabel:`December` by default." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1 -msgid "Frequency field in inventory app settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:112 -msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:118 -msgid "Once all changes have been made, click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:121 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers.rst:5 -msgid "Lots and Serial Numbers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:3 -msgid "What's the difference between lots and serial numbers?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:6 -msgid "Introduction" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:8 -msgid "In Odoo, lots and serial numbers have similarities in their functional system but are different in their behavior. They are both managed within the **Inventory**, **Purchases** and **Sales** app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:12 -msgid "**Lots** correspond to a certain number of products you received and store altogether in one single pack." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:15 -msgid "**Serial numbers** are identification numbers given to one product in particular, to allow to track the history of the item from reception to delivery and after-sales." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:20 -msgid "When to use" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:22 -msgid "**Lots** are interesting for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:28 -msgid "**Serial numbers** are interesting for items that could require after-sales service, such as smartphones, laptops, fridges, and any electronic devices. You could use the manufacturer's serial number or your own, depending on the way you manage these products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:34 -msgid "When not to use" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:36 -msgid "Storing consumable products such as kitchen roll, toilet paper, pens and paper blocks in lots would make no sense at all, as there are very few chances that you can return them for production fault." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:40 -msgid "On the other hand, giving a serial number to every product is a time-consuming task that will have a purpose only in the case of items that have a warranty and/or after-sales services. Putting a serial number on bread, for instance, makes no sense at all." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:46 -msgid ":doc:`serial_numbers`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:47 -msgid ":doc:`lots`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:3 -msgid "Expiration dates" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:5 -msgid "In Odoo, *expiration dates* can be used to manage and track the lifecycles of perishable products, from purchase to sale. Using expiration dates reduces product loss due to unexpected expiry, and helps to avoid sending expired products to customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:9 -msgid "In Odoo, only products that are tracked using *lots* and *serial numbers* can be assigned expiration information. Once a lot or serial number has been assigned, an expiration date can be set. This is especially helpful for companies (such as food manufacturers) that consistently, or exclusively, buy and sell perishable products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:15 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:17 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:19 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:19 -msgid "Enable expiration dates" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:21 -msgid "To enable the use of *expiration dates*, go to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Traceability` section. Then, click the checkbox to enable the :guilabel:`Lots & Serial Numbers` feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:25 -msgid "Once that feature is activated, a new option will appear to enable :guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and be sure to :guilabel:`Save` changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 -msgid "Enabled lots and serial numbers and expiration dates settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:33 -msgid "Once the :guilabel:`Lots & Serial Numbers` feature is activated, additional features appear to :guilabel:`Display Lots & Serial Numbers on Delivery Slips`; to :guilabel:`Display Lots & Serial Numbers on Invoices`; and to :guilabel:`Display Expiration Dates on Delivery Slips`. Activating these features helps with end-to-end traceability, making it easier to manage product recalls, identify \"bad\" batches of products, and more." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:40 -msgid "Configure expiration dates on products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:42 -msgid "Once the :guilabel:`Lots & Serial Numbers` and :guilabel:`Expiration Dates` features have been enabled in the settings of the *Inventory* app, expiration information can be configured on individual products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:46 -msgid "To do so, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to edit. Selecting a product reveals the product form for that particular item. Once on the product form, click :guilabel:`Edit` in the upper-left corner to make changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:51 -msgid "To be tracked using lots or serial numbers, or to configure expiration information, products *must* have their :guilabel:`Product Type` set as :guilabel:`Storable Product` under the :guilabel:`General Information` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:55 -msgid "Then, click the :guilabel:`Inventory` tab, and scroll down to the :guilabel:`Traceability` section. From here, make sure that either :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:59 -msgid "Once it is, a new :guilabel:`Expiration Date` checkbox appears that must also be clicked. When both are enabled, a new :guilabel:`Dates` field appears to the right." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:63 -msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed in order to assign lot numbers to the existing stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:68 -msgid "For processing large quantities of products on receipts or deliveries, it is recommended to track using lots, so multiple products can be traced back to the same lot, if any issues arise." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 -msgid "Expiration dates configuration on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:75 -msgid "Under the :guilabel:`Dates` field, there are four categories of expiration information to configure for the product:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:78 -msgid ":guilabel:`Expiration Time`: the number of days after receiving products (either from a vendor or in stock after production) in which goods may become dangerous and should not be used or consumed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:80 -msgid ":guilabel:`Best Before Time`: the number of days before the expiration date in which the goods start deteriorating, **without** necessarily being dangerous yet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:82 -msgid ":guilabel:`Removal Time`: the number of days before the expiration date in which the goods should be removed from stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:84 -msgid ":guilabel:`Alert Time`: the number of days before the expiration date in which an alert should be raised on goods in a particular lot or containing a particular serial number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:88 -msgid "The values entered into these fields automatically compute the expiration date for goods entered into stock, whether purchased from a vendor or manufactured in-house." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:91 -msgid "Once all the expiration information has been configured, click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:94 -msgid "If the :guilabel:`Dates` field is not populated with any values for expiration information, dates (and lots) can be manually assigned upon receipts and deliveries in and out of the warehouse. Even when assigned, they can still be overwritten and changed manually if needed, as well." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:99 -msgid "Set expiration dates on receipts with lots & serial numbers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:101 -msgid "Generating expiration dates for **incoming** goods can be done directly from the purchase order. To create a purchase order, go to the :menuselection:`Purchase` app and click :guilabel:`Create` to create a new request for quotation (RFQ)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:105 -msgid "Then, fill out the information by adding a :guilabel:`Vendor`, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a product`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:108 -msgid "Choose the desired quantity to order by changing the number in the :guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This converts the :abbr:`RFQ (request for quotation)` into a purchase order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:112 -msgid "Click the :guilabel:`Receipt` smart button at the top of the purchase order to be taken to the warehouse receipt form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:116 -msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities causes a :guilabel:`User Error` popup to appear. The popup requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` cannot be validated without an assigned lot or serial number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:0 -msgid "User error popup when validating an order with no lot number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:125 -msgid "From here, click the :guilabel:`Additional Options` menu (hamburger) icon located on the far-right of the product line. When clicked, a :guilabel:`Detailed Operations` pop-up will appear." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:128 -msgid "In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial number under the :guilabel:`Lot/Serial Number Name` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:131 -msgid "An expiration date automatically populates, based on the configuration on the product form (if previously configured)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:135 -msgid "If the :guilabel:`Dates` field on the product form has not been configured, this date can be manually entered." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:138 -msgid "After the expiration date has been established, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, click :guilabel:`Validate`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 -msgid "Detailed operations popup showing expiration dates for ordered products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:145 -msgid "A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial #`; and more." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:151 -msgid "Set expiration dates on manufactured products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:153 -msgid "Expiration dates can also be generated for products manufactured in-house. To assign expiration dates to manufactured products, a manufacturing order (MO) needs to be completed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:156 -msgid "To create a :abbr:`MO (manufacturing order)`, go to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, and click :guilabel:`Create`. Choose a product to manufacture from the :guilabel:`Product` field drop-down menu, then select the :guilabel:`Quantity` to produce." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 -msgid "Manufacturing order for product with expiration date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:165 -msgid "To manufacture a product, there must be materials to consume in the lines in the :guilabel:`Product` column. This can be achieved either by creating a :guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding materials to consume by clicking :guilabel:`Add a line`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:170 -msgid "Once ready, click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:172 -msgid "Next to :guilabel:`Lot/Serial Number`, either select an existing lot number from the drop-down menu, or click the green :guilabel:`+` sign to automatically assign a new lot number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:175 -msgid "Then, select a number of units for the :guilabel:`Quantity` field, and click :guilabel:`Mark as Done`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:178 -msgid "Click on the :guilabel:`External Link` icon in the assigned :guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail form for that specific number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:181 -msgid "On that pop-up, under the :guilabel:`Dates` tab, all expiration information that was previously configured for the product is displayed. That same information is also available on the detail form for that specific product, or by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 -msgid "Dates tab with expiration information for specific lot number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:191 -msgid "Sell products with expiration dates" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:193 -msgid "Selling perishable products with expiration dates is done the same as any other type of product. The first step in selling perishable products is to create a sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:196 -msgid "To do that, go to :menuselection:`Sales app --> Create` to create a new quotation, and fill out the information on the sales order form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:199 -msgid "Add a :guilabel:`Customer`, click :guilabel:`Add a product` to add the desired products to the :guilabel:`Product` lines, and set a :guilabel:`Quantity` for the products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:202 -msgid "Then, click the :guilabel:`Other Info` tab. Under the :guilabel:`Delivery` section, change the :guilabel:`Delivery Date` to a date after the expected date, and click the :guilabel:`green checkmark` icon to confirm the date. Finally, click :guilabel:`Confirm` to confirm the sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:206 -msgid "Next, click the :guilabel:`Delivery` smart button at the top of the sales order to see the warehouse receipt form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:209 -msgid "On the warehouse receipt form, click :guilabel:`Validate`, and then :guilabel:`Apply` in the accompanying pop-up window, to automatically process all :guilabel:`Done` quantities, and deliver the products to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:213 -msgid "If the products are delivered before the :guilabel:`Alert Date` set on the product form, then no alerts will be created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:217 -msgid "To sell perishable products with expiration dates, the :guilabel:`Removal Strategy` for the :guilabel:`Location` the products are stored in must be set to :abbr:`FEFO (First Expiry, First Out)`. If there is not enough stock of perishable products in one lot, Odoo will automatically take the remaining quantity required from a second lot with the next-soonest expiration date. Removal strategies can also be set on :guilabel:`Product Categories`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:224 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:211 -msgid ":doc:`/applications/inventory_and_mrp/inventory/routes/strategies/removal`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:227 -msgid "View expiration dates for lots & serial numbers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:229 -msgid "To view (and/or group) all products with expiration dates by lot number, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:232 -msgid "Once there, remove any default search filters from the :guilabel:`Search...` bar. Then, click :guilabel:`Group By`, choose :guilabel:`Add Custom Group`, and select the :guilabel:`Expiration Date` parameter from the drop-down menu. Finally, click :guilabel:`Apply` to apply the filter." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:236 -msgid "Doing so breaks down all perishable products, their expiration dates, and the assigned lot number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 -msgid "Group by expiration dates on lots and serial numbers page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:243 -msgid "Expiration alerts" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:245 -msgid "To see expiration alerts, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:247 -msgid "Then, click into a :guilabel:`Lot/Serial Number` with perishable products. Doing so reveals the serial number detail form. On the serial number detail form, click the :guilabel:`Dates` tab to see all expiration information related to the products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:251 -msgid "To edit the form, click :guilabel:`Edit` in the upper-left corner of the form, then change the :guilabel:`Expiration Date` to today's date (or earlier), and click :guilabel:`Save` to save changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:255 -msgid "After saving, the lot number form displays a red :guilabel:`Expiration Alert` at the top of the form to indicate that the products in this lot are either expired or expiring soon. From here, click back to the :guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:259 -msgid "To see the new expiration alert, or any expiration alerts for products that are expired (or will expire soon), remove all of the search filters from the :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:263 -msgid "Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 -msgid "Expiration alert for product past the expiration date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:3 -msgid "Use lots to manage groups of products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:5 -msgid "*Lots* are one of the two ways to identify and track products in Odoo. A lot usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse, but can also pertain to a batch of products manufactured in-house, as well." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:9 -msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps to identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their lifecycles." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:14 -msgid "Lots are useful for products that are manufactured or received in large quantities (such as clothes or food), and can be used to trace a product back to a group. This is especially useful when managing product recalls or expiration dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:22 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:20 -msgid "Enable lots & serial numbers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:24 -msgid "To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 -msgid "Enabled lots and serial numbers feature in inventory settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:36 -msgid "Track products by lots" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:38 -msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be configured to be tracked using lots. To do this, go to the :menuselection:`Inventory app --> Products --> Products`, and choose a product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:42 -msgid "Once on the product form, click :guilabel:`Edit` to make changes to the form. Then, click the :guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click :guilabel:`Save` to save changes. Existing or new lot numbers can now be assigned to newly-received or manufactured batches of this product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:48 -msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed to assign lot numbers to the existing stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 -msgid "Enabled tracking by lots feature on product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:56 -msgid "Create new lots for products already in stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:58 -msgid "New lots can be created for products already in stock with no assigned lot number. To do this, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a separate page where a new :guilabel:`Lot/Serial Number` is generated automatically." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:64 -msgid "While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:68 -msgid "Once the new :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:72 -msgid "This form also provides the option to adjust the :guilabel:`Quantity`, assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and assign this specific lot or serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:77 -msgid "A detailed description of this specific lot or serial number can also be added in the :guilabel:`Description` tab below." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:80 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:81 -msgid "When all desired configurations are complete, click the :guilabel:`Save` button to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 -msgid "New lot number creation form with assigned product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:86 -msgid "After a new lot number has been created, saved, and assigned to the desired product, navigate back to the product form in the :menuselection:`Inventory` app, by going to :menuselection:`Products --> Products`, and selecting the product to which this newly-created lot number was just assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:90 -msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new lot number. When additional quantity of this product is received or manufactured, this new lot number can be selected and assigned to it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:95 -msgid "Manage lots for shipping and receiving" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:97 -msgid "Lot numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are assigned directly on the sales order form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:102 -msgid "Manage lots on receipts" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:104 -msgid "Assigning lot numbers to **incoming** goods can be done directly from the purchase order (PO)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:106 -msgid "To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:109 -msgid "On this :abbr:`RFQ (request for quotation)`, fill out the necessary information by adding a :guilabel:`Vendor`, and adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` (under the :guilabel:`Products` tab)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:113 -msgid "Choose the desired quantity of the product to order by changing the number in the :guilabel:`Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:116 -msgid "Once the :abbr:`RFQ (request for quotation)` has been filled out, click :guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is confirmed, it becomes a :guilabel:`Purchase Order`, and a :guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:122 -msgid "Clicking :guilabel:`Validate` before assigning a lot number to the ordered product quantities will result in a :guilabel:`User Error` pop-up. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a lot number being assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 -msgid "Add lot/serial number user error popup." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:131 -msgid "From here, click the :guilabel:`Additional Options` menu, represented by a :guilabel:`hamburger (four horizontal lines)` icon, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:135 -msgid "In this pop-up, configure a number of different fields, including the assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:138 -msgid "There are two ways to assign lot numbers: **manually** and **copy/paste**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:140 -msgid "**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` quantity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 -msgid "Assign lot number detailed operations popup." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:149 -msgid "If quantities should be processed in multiple locations and lots, click :guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for additional quantities. Repeat until the :guilabel:`Quantity Done` matches the :guilabel:`Demand`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:153 -msgid "**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 -msgid "List of lot numbers copied on excel spreadsheet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:163 -msgid "Once all product quantities have been assigned a lot number, click :guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:166 -msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #` assigned, and more." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:172 -msgid "Manage lots on delivery orders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:174 -msgid "Assigning lot numbers to **outgoing** goods can be done directly from the sales order (SO)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:176 -msgid "To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app --> Create`. Doing so reveals a new, blank quotation form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:179 -msgid "On this blank quotation form, fill out the necessary information by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:183 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:221 -msgid "Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:185 -msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, it becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:189 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:227 -msgid "Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific :abbr:`SO (sales order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:192 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:132 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:230 -msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:196 -msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with the full :guilabel:`Reserved` quantity taken from that specific lot (if there is enough stock in that particular lot)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:200 -msgid "If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand` should be taken from multiple lots, change the quantity in the :guilabel:`Done` column to only include that specific part of the total quantity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:205 -msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough quantity in one lot to fulfill the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:213 -msgid "Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 -msgid "Detailed operations popup for source lot number on sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:221 -msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:226 -msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order, if the product quantities shared the same lot number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:230 -msgid "Manage lots for different operations types" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:232 -msgid "In Odoo, the creation of new lots is only allowed upon **receiving** products from a purchase order, by default. **Existing** lot numbers cannot be used." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:235 -msgid "For sales orders, the opposite is true: new lot numbers cannot be created on the delivery order, only existing lot numbers can be used." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:238 -msgid "To change the ability to use new (or existing) lot numbers on any operation type, go to the :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:242 -msgid "For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:247 -msgid "For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. Be sure to click the :guilabel:`Save` button to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 -msgid "Enabled traceability setting on operations type form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:256 -msgid "For inter-warehouse transfers involving products tracked by lots, it can be useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for warehouse receipts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:260 -msgid "Lots traceability" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:262 -msgid "Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a product: where (and when) it came from, where it was stored, and who (and when) it went to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:265 -msgid "To see the full traceability of a product, or group by lots, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :menuselection:`Lots/Serial Numbers` dashboard." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:269 -msgid "From here, products with lot numbers assigned to them will be listed by default, and can be expanded to show the lot numbers those products have assigned to them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:272 -msgid "To group by lots (or serial numbers), begin by removing any filters in the search bar. Then, click the :guilabel:`Group By` drop-down, select :guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from the drop-down menu. Then, click :guilabel:`Apply`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:276 -msgid "Doing so displays all existing lots and serial numbers, and can be expanded to show all quantities of products with that assigned number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:-1 -msgid "Lots and serial numbers traceability report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:284 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:319 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:3 -msgid "Use serial numbers to track products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:5 -msgid "*Serial numbers* are one of the two ways to identify and track products in Odoo. A serial number is a unique identifier assigned incrementally (or sequentially) to an item or product, used to distinguish it from other items and products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:9 -msgid "Serial numbers can consist of many different types of characters: they can be strictly numerical, they can contain letters and other typographical symbols, or they can be a mix of all of the above." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:12 -msgid "The goal of assigning serial numbers to individual products is to make sure that every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services to products that they sell and deliver." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:22 -msgid "To track products using serial numbers, the :guilabel:`Lots & Serial Numbers` feature must be enabled. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` button to save changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "Enabled lots and serial numbers setting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:34 -msgid "Configure serial number tracking on products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:36 -msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be tracked using serial numbers. To configure this, go to :menuselection:`Inventory app --> Products --> Products`, and choose a desired product to track." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:40 -msgid "Once on the product form, click :guilabel:`Edit`, and click the :guilabel:`Inventory` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:42 -msgid "Once on the product form, click :guilabel:`Edit`, navigate to the :guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` section. Then, select the :guilabel:`By Unique Serial Number` option, and click :guilabel:`Save` to save the changes. Existing or new serial numbers can now be selected and assigned to newly-received or manufactured batches of this product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "Enabled serial number tracking on product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:52 -msgid "If a product doesn't have a serial number assigned to it, a user error pop-up window will appear. The error message states that the product(s) in stock have no lot/serial number. However, a lot/serial number can be assigned to the product by making an inventory adjustment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:57 -msgid "Create new serial numbers for products already in stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:59 -msgid "New serial numbers can be created for products already in stock with no assigned serial number. To do this, go to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a blank lots/serial numbers form. On this form, a new :guilabel:`Lot/Serial Number` is generated automatically." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:65 -msgid "While Odoo automatically generates a new lot/serial number to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:69 -msgid "Once the :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:73 -msgid "This form also provides the option to adjust the :guilabel:`Quantity`, to assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and to assign this specific lot/serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:78 -msgid "A detailed description of this specific lot/serial number can also be added in the :guilabel:`Description` tab below." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "New serial number created for existing product stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:87 -msgid "After a new serial number has been created, assigned to the desired product, and saved, navigate back to the product form, by going to :menuselection:`Products --> Products`, and selecting the product that this newly-created serial number was just assigned to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:91 -msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new serial number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:95 -msgid "Manage serial numbers for shipping and receiving" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:97 -msgid "Serial numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, serial numbers are assigned directly on the purchase order form. For outgoing goods, serial numbers are assigned directly on the sales order form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:102 -msgid "Manage serial numbers on receipts" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:104 -msgid "Assigning serial numbers to **incoming** goods can be done directly from the purchase order (PO)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:106 -msgid "To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:109 -msgid "On this :abbr:`RFQ (request for quotation)` form, fill out the necessary information, by adding a :guilabel:`Vendor`, and by adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product`, under the :guilabel:`Products` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:113 -msgid "Choose the desired quantity of the product to order, by changing the number in the :guilabel:`Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:116 -msgid "When the necessary configurations are complete, click :guilabel:`Confirm Order`. This will convert the :abbr:`RFQ (request for quotation)` to a purchase order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:119 -msgid "Then, click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form page for that specific :abbr:`PO (purchase order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:123 -msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities will cause a :guilabel:`User Error` pop-up to appear. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a serial number being assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "User error popup prompting serial number entry." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:136 -msgid "In this pop-up, configure a number of different fields, including the assignation of a serial number (or serial numbers) under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:140 -msgid "There are three ways to do this: manually assigning serial numbers, automatically assigning serial numbers, and copy/pasting serial numbers from a spreadsheet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:144 -msgid "Assign serial numbers manually" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:146 -msgid "To assign serial numbers manually, click :guilabel:`Add a line` from the :guilabel:`Detailed Operations` pop-up, and first choose the location where the product will be stored under the :guilabel:`To` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:150 -msgid "Then, type a new :guilabel:`Serial Number Name`, and set the :guilabel:`Done` quantity in the appropriate columns." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:153 -msgid "Repeat this process for the quantity of products shown in the :guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field displays the correct (matching) number of products processed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:157 -msgid "Assign serial numbers automatically" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:159 -msgid "If a large quantity of products need individual serial numbers assigned to them, Odoo can automatically generate and assign serial numbers to each of the individual products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:162 -msgid "To accomplish this, start with the :guilabel:`First SN` field in the :guilabel:`Detailed Operations` pop-up window, and type the first serial number in the desired order to be assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:165 -msgid "Then, in the :guilabel:`Number of SN` field, type the total number of items that need newly-generated unique serial numbers assigned to them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:168 -msgid "Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate with new serial numbers matching the ordered quantity of products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "Automatic serial number assignment in detailed operations popup." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:176 -msgid "Copy/paste serial numbers from a spreadsheet" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:178 -msgid "To copy and paste serial numbers from an existing spreadsheet, first populate a spreadsheet with all of the serial numbers received from the supplier (or manually chosen upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:183 -msgid "From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the serial number lines." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "List of serial numbers copied in Excel spreadsheet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:191 -msgid "For purchase orders that include large quantities of products to receive, the best method of serial number assignment is to automatically assign serial numbers using the :guilabel:`Assign Serial Numbers` button located on the :abbr:`PO (purchase order)`. This prevents any serial numbers from being reused or duplicated, and improves traceability reporting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:196 -msgid "Once all product quantities have been assigned a serial number, click the :guilabel:`Confirm` button to close the pop-up. Then, click :guilabel:`Validate`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:199 -msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:204 -msgid "Once all product quantities have been assigned a serial number, click :guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:211 -msgid "Manage serial numbers on delivery orders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:213 -msgid "Assigning serial numbers to **outgoing** goods can be done directly from the sales order (SO)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:215 -msgid "To create an :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing so reveals a new, blank quotation form. On this blank quotation form, fill out the necessary information, by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab), by clicking :guilabel:`Add a product`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:223 -msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, the quotation becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:234 -msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with each product of the total :guilabel:`Reserved` quantity listed with their unique serial numbers (most likely listed in sequential order)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:238 -msgid "To manually change a product's serial number, click the drop-down menu under :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial number. Then, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:242 -msgid "Finally, click the :guilabel:`Validate` button to deliver the products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "Serial numbers listed in detailed operations popup." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:248 -msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:253 -msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order (PO), if any of the product quantities shared a serial number assigned during receipt of that specific :abbr:`PO (purchase order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:258 -msgid "Manage serial numbers for different operations types" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:260 -msgid "By default in Odoo, the creation of new serial numbers is only allowed upon **receiving** products from a purchase order. **Existing** serial numbers cannot be used. For sales orders, the opposite is true: new serial numbers cannot be created on the delivery order, only existing serial numbers can be used." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:265 -msgid "To change the ability to use new (or existing) serial numbers on any operation type, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:269 -msgid "For the :guilabel:`Receipts` operation type, found on the :guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:275 -msgid "For the :guilabel:`Delivery Orders` operation type, located on the :guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Be sure to click :guilabel:`Save` to save changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "Enabled traceability setting in operations type form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:286 -msgid "Serial number traceability" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:288 -msgid "Manufacturers and companies can refer to the traceability reports to see the entire lifecycle of a product: where it came from (and when), where it was stored, and who it went to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:291 -msgid "To see the full traceability of a product, or group by serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:295 -msgid "From here, products with serial numbers assigned to them will be listed by default, and can be expanded to show what serial numbers have been specifically assigned to them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:298 -msgid "To group by serial numbers (or lots), first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:303 -msgid "Doing so reveals all existing serial numbers and lots, and can be expanded to show all quantities of products with that assigned number. For unique serial numbers that are not reused, there should be just one product per serial number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:-1 -msgid "Serial numbers reporting page with drop-down lists." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:312 -msgid "For additional information regarding an individual serial number (or lot number), click the line item for the serial number to reveal that specific serial number's :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number, and any operations made using that serial number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc.rst:5 -msgid "Miscellaneous Operations" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:3 -msgid "Batch picking" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:5 -msgid "*Batch picking* enables a single picker to handle multiple orders at once, reducing the time needed to navigate to the same location in a warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:8 -msgid "When picking in batches, orders are grouped and consolidated into a picking list. After the picking, the batch is taken to an output location, where the products are sorted into their respective delivery packages." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:13 -msgid ":ref:`Use Barcode app for pickings `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:15 -msgid "Since orders *must* be sorted at the output location after being picked, this picking method suits businesses with a few products that are ordered often. Storing high-demand items in easily accessible locations can increase the number of orders that are fulfilled efficiently." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:22 -msgid "To activate the batch picking option, begin by going to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` section, check the :guilabel:`Batch Transfers` box." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Enable the *Batch Transfers* in Inventory > Configuration > Settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:30 -msgid "Since batch picking is a method to optimize the *pick* operation in Odoo, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options under the :guilabel:`Warehouse` heading must also be checked on this settings page. When finished, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration > Settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:38 -msgid "Lastly, enable the warehouse picking feature, by navigating to the warehouse settings page, which is accessible from :menuselection:`Inventory app --> Configuration --> Warehouses`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:41 -msgid "From here, select the desired warehouse from the list. Then, from the radio options available for :guilabel:`Outgoing Shipments`, select either the :guilabel:`Send goods in output and then deliver (2 steps)` or :guilabel:`Pack goods, send goods in output and then deliver (3 steps)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:46 -msgid ":ref:`Delivery in two steps `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:47 -msgid ":ref:`Delivery in three steps `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Set up 2-step or 3-step outgoing shipments." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:54 -msgid "Create batch transfers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:56 -msgid "Manually create batch transfers directly from the :menuselection:`Inventory app --> Operations --> Batch Transfers` page. Click the :guilabel:`New` button to begin creating a batch transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:59 -msgid "On the batch transfer form, fill the following fields out accordingly:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:61 -msgid ":guilabel:`Responsible`: employee assigned to the picking. Leave this field blank if *any* worker can fulfill this picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:63 -msgid ":guilabel:`Operation Type`: from the drop-down menu, select the operation type under which the picking is categorized." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:65 -msgid ":guilabel:`Scheduled Date`: specifies the date by which the :guilabel:`Responsible` person should complete the transfer to the output location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:68 -msgid "Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to open the :guilabel:`Add: Transfers` window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:71 -msgid "If the :guilabel:`Operation Type` field was filled, the list will filter transfer records matching the selected :guilabel:`Operation Type`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:74 -msgid "Click the :guilabel:`New` button to create a new transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:76 -msgid "Once the transfer records are selected, click :guilabel:`Confirm` to confirm the batch picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:79 -msgid "A new batch transfer assigned to the :guilabel:`Responsible`, `Joel Willis`, for the `Pick` :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` is set to `August 11`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:0 -msgid "View of *Batch Transfers* form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:86 -msgid "Clicking the :guilabel:`Add a line` button opens the :guilabel:`Add:Transfers` window, displaying only pickings. This is because the :guilabel:`Operation Type` was set to `Pick` on the batch transfer form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:90 -msgid "Click the checkbox to the left of the transfers, `WH/PICK/00001` and `WH/PICK/00002`, to include them in the new transfer. Then, click the :guilabel:`Select` button to close the :guilabel:`Add:Transfers` window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:0 -msgid "Select multiple transfers from the *Add:Transfers* window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:99 -msgid "Add batch from transfers list" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:101 -msgid "Another method of creating batch transfers is available using the :guilabel:`Add to batch` option in a list. Navigate to the :menuselection:`Inventory app --> Operations` drop-down menu, and select any of the :guilabel:`Transfers` to open a filtered list of transfers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,\n" -"Manufacturings, Batch Transfers, Dropships." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:110 -msgid "On the transfers list, select the checkbox to the left of the selected transfers to add in a batch. Next, navigate to the :guilabel:`Actions āš™ļø (gear)` button, and click :guilabel:`Add to batch` from the resulting drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Use *Add to batch* button, from the *Action* button's list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:118 -msgid "Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the employee :guilabel:`Responsible` for the picking can be assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:121 -msgid "Choose from the two radio options to add to :guilabel:`an existing batch transfer` or create :guilabel:`a new batch transfer`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:124 -msgid "To begin with a draft, select the :guilabel:`Draft` checkbox." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:126 -msgid "Conclude the process by clicking :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Show *Add to batch* window to create a batch transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:133 -msgid "Process batch transfer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:135 -msgid "Handle batch transfers in the :menuselection:`Inventory app --> Operations --> Batch Transfers` page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:138 -msgid "From here, select the intended transfer from the list. Then, on the batch transfer form, input the :guilabel:`Done` quantities for each product, under the :guilabel:`Detailed Operations` tab. Finally, select :guilabel:`Validate` to complete the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:143 -msgid "Be certain the batch transfer is complete when the :guilabel:`Validate` button is highlighted in purple. If the :guilabel:`Check Availability` button is highlighted instead, that means there are items in the batch that are currently *not* available in-stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:150 -msgid "In a batch transfer involving products from pickings, `WH/PICK/00001` and `WH/PICK/00002`, the :guilabel:`Detailed Operations` tab shows that the product, `Cabinet with Doors`, has been picked because the :guilabel:`Done` column matches the value in the :guilabel:`Reserved` column. However, `0.00` quantities have been picked for the other product, `Cable Management Box`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:0 -msgid "Show batch transfer of products from two pickings in the *Detailed Operations* tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:159 -msgid "Only in-stock products are visible in the :guilabel:`Detailed Operations` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:161 -msgid "To view the complete product list, switch to the :guilabel:`Operations` tab. On this list, the :guilabel:`Demand` column indicates the required quantity for the order. The :guilabel:`Reserved` column shows the available stock to fulfill the order. Lastly, the :guilabel:`Done` column specifies the products that have been picked, and are ready for the next step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:167 -msgid "The product, `Desk Pad`, from the same batch as the :ref:`example above `, is only visible in the :guilabel:`Operations` tab because there are no :guilabel:`Reserved` quantities in-stock to fulfill the batch picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:171 -msgid "Click the :guilabel:`Check Availability` button to search the stock again for available products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:0 -msgid "Show unavailable reserved quantities in the *Operations* tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:178 -msgid "Create backorder" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:180 -msgid "On the batch transfer form, if the :guilabel:`Done` quantity of the product is *less* than the :guilabel:`Reserved` quantity, a pop-up window appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:183 -msgid "This pop-up window provides the option: :guilabel:`Create Backorder?`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:185 -msgid "Clicking the :guilabel:`Create Backorder` button automatically creates a new batch transfer, containing the remaining products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:188 -msgid "Click :guilabel:`No Backorder` to finish the picking *without* creating another batch picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:190 -msgid "Click :guilabel:`Discard` to cancel the validation, and return to the batch transfer form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Show the *Create Backorder* pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:199 -msgid "Process batch transfer: Barcode app" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:201 -msgid "Created batch transfers are also listed in the :menuselection:`Barcode` app, accessible by selecting the :guilabel:`Batch Transfers` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:204 -msgid "By default, confirmed batch pickings appear on the :guilabel:`Batch Transfers` page. On that page, click on the desired batch transfer to open the detailed list of products for the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:-1 -msgid "Show list of to-do batch transfers in *Barcode* app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:211 -msgid "For the chosen batch transfer, follow the instructions at the top of the page in the black background. Begin by scanning the product's barcode to record a single product for picking. To record multiple quantities, click the :guilabel:`āœļø (pencil)` icon, and enter the required quantities for the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:217 -msgid "Products from the same order are labeled with the same color on the left. Completed pickings are highlighted in green." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:221 -msgid "In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, and 4 `Four Person Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate that the last two product pickings are complete." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:225 -msgid "`1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the unique serial number for :ref:`product tracking `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:0 -msgid "Display products to be picked in barcode view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:233 -msgid "Once all the products have been picked, click on :guilabel:`Validate` to mark the batch transfer as :guilabel:`Done`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:3 -msgid "Consignment: buy and sell stock without owning it" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:5 -msgid "Most of the time, products stored in a company's warehouse are either purchased from suppliers, or are manufactured in-house. However, suppliers will sometimes let companies store and sell products in the company's warehouse, without having to buy those items up-front. This is called *consignment*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:10 -msgid "Consignment is a useful method for suppliers to launch new products, and easily deliver to their customers. It's also a great way for the company storing the products (the consignee) to earn something back for their efforts. Consignees can even charge a fee for the convenience of storing products they don't actually own." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:16 -msgid "Enable the consignment setting" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:18 -msgid "To receive, store, and sell consignment stock, the feature needs to be enabled in the settings. To do this, go to :menuselection:`Inventory --> Configuration --> Settings`, and under the :guilabel:`Traceability` section, check the box next to :guilabel:`Consignment`, and then click :guilabel:`Save` to finish." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 -msgid "Enabled Consignment setting in Inventory configuration." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:28 -msgid "Receive (and store) consignment stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:30 -msgid "With the feature enabled in Odoo, consignment stock can now be received into a warehouse. From the main :menuselection:`Inventory` dashboard, click into the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:35 -msgid "Consignment stock is not actually purchased from the vendor; it is simply received and stored. Because of this, there are no quotations or purchase orders involved in receiving consignment stock. So, *every* receipt of consignment stock will start by creating manual receipts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:39 -msgid "Choose a vendor to enter in the :guilabel:`Receive From` field, and then choose the same vendor to enter in the :guilabel:`Assign Owner` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:43 -msgid "Since the products received from the vendor will be owned by the same vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields must match." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:46 -msgid "Once the vendor-related fields are set, enter products into the :guilabel:`Product` lines, and set the quantities to be received into the warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be changed, as well. Once all the consignment stock has been received, :guilabel:`Validate` the receipt." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 -msgid "Matching vendor fields in consignment Receipt creation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:56 -msgid "Sell and deliver consignment stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:58 -msgid "Once consignment stock has been received into the warehouse, it can be sold the same as any other in-stock product that has the :guilabel:`Can Be Sold` option enabled on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:61 -msgid "To create a sales order, navigate to the :menuselection:`Sales` app, and from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, choose a customer to enter into the :guilabel:`Customer` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:66 -msgid "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` that supplied the consignment stock received (and stored) in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:69 -msgid "Add the consignment product under the :guilabel:`Product` column in the order lines, set the :guilabel:`Quantity`, and fill out any other pertinent product details on the form. Once the quotation is complete, click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 -msgid "Sales order of consignment stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:77 -msgid "Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will become a sales order. From here, the products can be delivered by clicking on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate` to validate the delivery." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:82 -msgid "Traceability and reporting of consignment stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:84 -msgid "Although consignment stock is owned by the vendor who supplied it, and not by the company storing it in their warehouse, consignment products will *still* appear in certain inventory reports." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:87 -msgid "To find inventory reports, go to :menuselection:`Inventory --> Reporting`, and choose a report to view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:91 -msgid "Since the consignee does not actually own consigment stock, these products are *not* reflected in the :guilabel:`Stock Valuation` report, and have no impact on the consignee's inventory valuation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:96 -msgid "Product moves report" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:98 -msgid "To view all information about on-hand stock moves, navigate to the the :guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory --> Reporting --> Product Moves`. For consignment products, the information in this report is the same as any other product: the history of its product moves can be reviewed; the :guilabel:`Quantity Done` and :guilabel:`Reference` document are available; and its :guilabel:`Locations` are available, as well. The consignment stock will originate from :guilabel:`Partner Location/Vendors`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:106 -msgid "To view a consignment product's moves by ownership, select the :guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to finish." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1 -msgid "Consignment stock moves history." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:115 -msgid "To see forecasted units of consignment stock, go to :menuselection:`Inventory --> Reporting --> Forecasted Inventory`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:119 -msgid "Stock on hand report" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:121 -msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consigment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/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:-1 -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:-1 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:3 -msgid "How is the Scheduled Delivery Date Computed" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:5 -msgid "Providing the best possible service to customers is vital for business. It implies planning every move: manufacturing orders, deliveries, receptions, and so on. To do so, you need to configure lead time properly and coordinate scheduled dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:9 -msgid "By using lead times, Odoo provides end dates, the **Commitment Date**, for each process. On a sales order, for example, this is the date your customer will get the products he ordered." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:13 -msgid "From the customersā€™ side, the commitment date is important because it gives them an estimation of when they will receive their products. The dates take all other lead times, such as manufacturing, delivery, or suppliers, into account." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:19 -msgid "How are Lead Times Calculated?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:27 -msgid "As said above, there are several types of lead times. Each is calculated based on various indicators. Before going through the configuration, here is a brief summary of how lead times are calculated and what they are:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:32 -msgid "**Customer Lead Time**: the customer lead time is the default duration you set. Therefore, the expected date on the sales orders is today + customer lead time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:36 -msgid "**Sales Security Lead Time**: the purpose is to be ready shipping that many days before the actual commitment taken with the customer. Then, the default scheduled date on the delivery order is **SO delivery date - Security Lead Time**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41 -msgid "**Purchase Security Lead Time**: margin of error for vendor lead times. When the system generates Purchase Orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:46 -msgid "**Purchase Delivery Lead Time**: this is the expected time between a PO being confirmed and the receipt of the ordered products. The **Receipt scheduled date - Vendor delivery date** is the default *PO Order By* date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:51 -msgid "**Days to Purchase**: number of days the purchasing department takes to validate a PO. If another RFQ to the same vendor is already opened, Odoo adds the line to the RFQ instead of creating a new one. Then, the specific date is set on the line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:56 -msgid "**Manufacturing Lead Time**: this is the expected time it takes to manufacture a product. This lead time is independent of the quantity to produce and does not take the routing time into account." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:61 -msgid "**Manufacturing Security Lead Time**: additional time to mitigate the risk of a manufacturing delay. In case of a *Replenish to Order*, the **Delivery Order scheduled date - Manufacturing Lead Time - Manufacturing Security Lead Time** is the default *Manufacturing Order* planned date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:68 -msgid "Sales - Lead Times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:70 -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:-1 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:91 -msgid "Customer Lead Time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:93 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:108 -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:180 -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:217 -msgid "Security Lead Time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:110 -msgid "In sales, *Security Lead Time* corresponds to backup days to ensure you are able to deliver the products in time. The purpose is to be ready shipping earlier in order to arrive on time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:114 -msgid "The number of security days is subtracted from the calculation to compute a scheduled date earlier than the one promised to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:117 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:129 -msgid "Deliver several products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:131 -msgid "In many cases, customers order several products at the same time. Those can have different lead times but still need to be delivered, at once or separately. Fortunately, Odoo can help you handle these cases easily." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:135 -msgid "From the *Other Info* tab of your *Sale Order*, you can choose between *When all products are ready* and *As soon as possible*. The first one is to deliver products at once, while the second is to deliver them separately." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:140 -msgid "For example, products A and B are ordered at the same time. A has 8 lead days and B has 5. With the first option, the *Expected Date* is calculated based on the product with the most lead days, here A. If the order is confirmed on the 2nd of April, then the *Expected Date* is on the 10th of April." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:146 -msgid "With the second option, the *Expected Date* is calculated based on the product with the least customer lead days. In this example, B is the product with the least lead days. So, the *Expected Date* is on the 7th of April." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:152 -msgid "Purchase - Lead Times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:155 -msgid "Supplier Lead Time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:157 -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:-1 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:182 -msgid "The *Security Lead Time* for purchase follows the same logic as the one for *Sales*, except that you are the customer. Then, it is the margin of error for your supplier to deliver your order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:186 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:198 -msgid "Manufacturing - Lead Times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:201 -msgid "Manufacturing Lead Time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:203 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:219 -msgid "The *Security Lead Time* for manufacturing allows generating manufacturing orders earlier to cope with the risk of manufacturing delays." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:223 -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:-1 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:236 -msgid "Global Example" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:238 -msgid "Here is a configuration:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:240 -msgid "1 day of security lead time for Sales" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:241 -msgid "2 days of security lead time for Manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:242 -msgid "3 days of manufacturing lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:243 -msgid "1 day of security lead time for Purchase" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:244 -msgid "4 days of supplier lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:246 -msgid "Letā€™s say that a customer orders B on the 1st of September and the delivery date is planned to be within 20 days (September 20th). In such a scenario, here is when all the various steps are triggered." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:250 -msgid "**September 1st**: the sales order is created" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:251 -msgid "**September 10th**: the deadline to order components from the supplier because of the manufacturing process (4 days of supplier lead time)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:254 -msgid "**September 13th**: the reception of the product from the supplier (1 day of security lead time for Purchase)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:256 -msgid "**September 14th**: the deadline start date for the manufacturing (19th - 3 days of manufacturing lead time - 2 days of security lead time for Manufacturing)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:259 -msgid "**September 19th**: the expected date on the delivery order form (1 day of security lead time for sales)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products.rst:5 -#: ../../content/applications/inventory_and_mrp/purchase/products.rst:5 -msgid "Products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:3 msgid "Replenish on order (MTO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:9 msgid "*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates a draft order for a product every time a sales order is created for it. For products that are purchased from a vendor, a request for quotation (RFQ) is created, while a sales order for a product manufactured in-house triggers the creation of a manufacturing order. The creation of a |RFQ| or manufacturing order occurs every time a sales order is created, regardless of the current stock level of the product being ordered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:17 msgid "Unarchive the Replenish on Order (MTO) route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:19 msgid "By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| is a somewhat niche workflow that is only used by certain companies. However, it is easy to unarchive the route in just a few simple steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:23 msgid "To do so, begin by navigating to :menuselection:`Inventory --> Configuration --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` button and select the :guilabel:`Archived` option. This shows all routes that are currently archived." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 msgid "The archived filter on the Routes page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:31 msgid "Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click the :guilabel:`Action` button to reveal a drop-down menu. From the drop-down menu, select :guilabel:`Unarchive`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 msgid "The unarchive action on the Routes page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:38 msgid "Finally, remove the :guilabel:`Archived` filter from the :guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all available routes, including :guilabel:`Replenish on Order (MTO)`, which is now selectable on the inventory tab of each product page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 msgid "The MTO route appears on the Routes page after unarchiving it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:47 msgid "Configure a product to use the MTO route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:49 msgid "With the |MTO| route unarchived, products can now be properly configured to use replenish on order. To do so, begin by going to :menuselection:`Inventory --> Products --> Products`, then select an existing product, or click :guilabel:`Create` to configure a new one." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:53 msgid "On the product page, select the :guilabel:`Inventory` tab and enable the :guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` section, along with one other route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:57 msgid "The :guilabel:`Replenish on Order (MTO)` route **does not** work unless another route is selected as well. This is because Odoo needs to know how to replenish the product when an order is placed for it (buy it, manufacture it, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 msgid "Select the MTO route and a second route on the Inventory tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:65 msgid "If the product is purchased from a vendor to fulfill sales orders, enable the :guilabel:`Can be Purchased` checkbox under the product name. Doing so makes the :guilabel:`Purchase` tab appear alongside the other settings tabs below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:69 msgid "Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the :guilabel:`Price` they sell the product for." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 msgid "Enable \"Can be Purchased\" and specify a vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:76 msgid "If the product is manufactured, make sure that it has a bill of materials (BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` smart button at the top of the screen, then click :guilabel:`Create` on the :guilabel:`Bill of Materials` page to configure a new |BOM| for the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:81 msgid "On the blank |BOM| form, add the components used to manufacture the product on the :guilabel:`Components` tab, along with the operations required for the manufacturing workflow on the :guilabel:`Operations` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:85 msgid "Finally, click :guilabel:`Save` to save the |BOM|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:88 msgid "Fulfill a sales order using the MTO route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:90 msgid "After configuring a product to use the |MTO| route, a replenishment order is created for it every time a sales order including the product is confirmed. The type of order created depends on the second route selected in addition to |MTO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:94 msgid "For example, if *Buy* was the second route selected, then a purchase order is created upon confirmation of a sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:98 msgid "When the |MTO| route is enabled for a product, a replenishment order is always created upon confirmation of a sales order. This is the case even if there is enough stock of the product on-hand to fulfill the sales order, without buying or manufacturing additional units of it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:102 msgid "While the |MTO| route can be used in unison with a variety of other routes, the *Buy* route is used as the example for this workflow. Begin by navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`, which opens a blank quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:106 msgid "On the blank quotation form, add a :guilabel:`Customer`, then click :guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a product that has been configured to use the *MTO* and *Buy* routes. Click :guilabel:`Confirm` and the quotation is turned into a sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:110 msgid "A :guilabel:`Purchase` smart button now appears in the top-right corner of the sales order. Clicking it opens the |RFQ| associated with the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:113 msgid "Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a purchase order. A green :guilabel:`Receive Products` button now appears at the top of the purchase order. Once the products are received, click :guilabel:`Receive Products` to register them into inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:117 msgid "Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:120 msgid "Finally, click the :guilabel:`Delivery` smart button in the top-right of the order to be taken to the delivery order. Once the products have been shipped to the customer, click :guilabel:`Validate` to confirm the delivery." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:3 msgid "Reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:7 msgid "Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:11 msgid "Reordering rules can be configured for each product based on the route used to replenish it. If a product uses the *Buy* route, then a Request for Quotation (RFQ) is created when the reordering rule is triggered. If a product uses the *Manufacture* route, then a Manufacturing Order (MO) is created instead. This is the case regardless of the selected replenishment route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:17 msgid "Configure products for reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:19 msgid "In order to use reordering rules for a product, it must first be correctly configured. Begin by navigating to :guilabel:`Inventory --> Products --> Products`, then select an existing product, or create a new one by clicking :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:23 msgid "First, on the :guilabel:`General Information` tab, make sure that the :guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is necessary because Odoo only tracks stock quantities for storable products, and this number is used to trigger reordering rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 msgid "Set the Product Type as Storable." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:29 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:31 msgid "Next, click on the :guilabel:`Inventory` tab and select one or more routes from the :guilabel:`Routes` section. Doing so tells Odoo which route to use to replenish the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 msgid "Select one or more routes on the Inventory tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:38 msgid "If the product is reordered using the :guilabel:`Buy` route, confirm that the :guilabel:`Can be Purchased` checkbox is enabled under the product name. This makes the :guilabel:`Purchase` tab appear. Click on the :guilabel:`Purchase` tab, and specify at least one vendor, and the price that they sell the product for, so that Odoo knows which company the product should be purchased from." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 msgid "Specify a vendor and price on the Purchase tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:47 msgid "If the product is replenished using the :guilabel:`Manufacture` route, it needs to have at least one Bill of Materials (BoM) associated with it. This is necessary because Odoo only creates manufacturing orders for products with a :abbr:`BoM (Bill of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:51 msgid "If a :abbr:`BoM (Bill of Materials)` does not already exist for the product, select the :guilabel:`Bill of Materials` smart button at the top of the product form, then click :guilabel:`Create` to configure a new :abbr:`BoM (Bill of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 msgid "The Bill of Materials smart button on a product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:60 msgid "Create new reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:62 msgid "To create a new reordering rule, navigate to :menuselection:`Inventory --> Configuration --> Reordering Rules`, then click :guilabel:`Create`, and fill out the new line as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:65 msgid ":guilabel:`Product`: The product that is replenished by the rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:66 msgid ":guilabel:`Location`: The location where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:67 msgid ":guilabel:`Min Quantity`: The minimum quantity that can be forecasted without the rule being triggered. When forecasted stock falls below this number, a replenishment order for the product is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:70 msgid ":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:71 msgid ":guilabel:`Multiple Quantity`: Specify if the product should be replenished in batches of a certain quantity (e.g., a product could be replenished in batches of 20)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:73 msgid ":guilabel:`UoM`: The unit of measure used for reordering the product. This value can simply be `Units` or a specific unit of measurement for weight, length, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 msgid "The form for creating a new reordering rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:81 msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory --> Products --> Products`, then select a product. Click on :menuselection:`Reordering Rules --> Create`, then fill out the new line as detailed above." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:85 msgid "Once a reordering rule has been created for a product, if its forecasted quantity is below the rule's minimum quantity when the scheduler runs, a replenishment order for the product is automatically generated. By default, the scheduler runs once each day." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:90 msgid "To manually trigger a reordering rule before the scheduler runs, select :menuselection:`Inventory --> Operations --> Run Scheduler`. Then, select the green :guilabel:`Run Scheduler` button on the pop-up that appears. Be aware that this also triggers any other scheduled actions." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:94 msgid "If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for Quotation)`, navigate to :menuselection:`Purchase --> Orders --> Requests for Quotation`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:98 msgid "If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO (Manufacturing Order)` is generated. To view and manage :abbr:`MOs (Manufacturing Orders)`, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:103 msgid "Set a preferred route for reordering" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:105 msgid "Odoo allows for multiple routes to be selected under the :guilabel:`Inventory` tab on each product form. For instance, it is possible to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling the functionality of both routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:109 msgid "Odoo also enables users to set a preferred route for a product's reordering rule. This is the route that the rule defaults to if multiple are selected. To select a preferred route, begin by navigating to :menuselection:`Inventory --> Configuration --> Reordering Rules`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:113 msgid "By default, the :guilabel:`Preferred Route` column is hidden on the :guilabel:`Reordering Rules` page. Enable it by selecting the :guilabel:`ā‹® (three-dot)` option button on the right side of the page and checking the :guilabel:`Preferred Route` checkbox. Doing so reveals the :guilabel:`Preferred Route` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:118 msgid "Click inside of the column on the row of a reordering rule and a drop-down menu shows all available routes for that rule. Select one to set it as the preferred route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 msgid "Select a preferred route from the drop-down." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:126 msgid "If multiple routes are enabled for a product but no preferred route is set for its reordering rule, the product is reordered using the selected route that is listed first on the :guilabel:`Inventory` tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:3 +msgid "Scrap inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:5 +msgid "In some cases, a product in inventory may be damaged or found to be defective. If it is not possible to repair or return the product, Odoo *Inventory* allows users to scrap it, ensuring that usable inventory counts remain accurate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:19 +msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:14 +msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`. Remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display virtual locations. Finally, select the :guilabel:`Virtual Locations/Scrap` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:19 +msgid "By default, scrapping a product removes it from physical inventory, and places it in a virtual location titled *Virtual Locations/Scrap*. A virtual location is **not** a physical space, but rather a designation in Odoo that is used to track items that are no longer in physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:30 +msgid "Learn more" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:25 +msgid "For more information about virtual locations, see the documentation about the different types of :ref:`locations `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:29 +msgid "Scrap from stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:31 +msgid "To scrap a product located in inventory, begin by navigating to :menuselection:`Inventory --> Operations --> Scrap`. On the :guilabel:`Scrap Orders` page, click :guilabel:`Create` to configure a new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:35 +msgid "On the scrap order, select the product being scrapped from the :guilabel:`Product` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:-1 +msgid "A new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:45 +msgid "Finally, click :guilabel:`Validate` to scrap the product. The on-hand inventory count for the scrapped product updates to subtract the scrapped quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:49 +msgid "Scrap from a receipt, transfer, or delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:51 +msgid "It is also possible to scrap products during the receipt, transfer, and delivery operations. This can be necessary if any products are found to be defective when receiving them into inventory, transferring them from one location to another, or preparing them for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:55 +msgid "To scrap a product during the receipt, transfer, or delivery operations, begin by navigating to the :menuselection:`Inventory` app. On the :guilabel:`Overview` page, select the :guilabel:`# TO PROCESS` button on the :guilabel:`Receipts`, :guilabel:`Internal Transfers`, or :guilabel:`Delivery Orders` card, depending on the type of operation the product is being scrapped from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:61 +msgid "For the :guilabel:`Internal Transfers` card to appear on the :menuselection:`Overview` page of the :menuselection:`Inventory` app, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Configuration --> Settings`, then enable the checkbox next to :guilabel:`Storage Locations` under the :guilabel:`Warehouse` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:66 +msgid "Alternatively, a list of all delivery orders, receipts, and transfers can be viewed by navigating to :menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:69 +msgid "Next, open a delivery order, receipt, or transfer from the corresponding page by clicking on it. A :guilabel:`Scrap` button appears at the top of the page. Click it to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:-1 +msgid "The scrap pop-up in the Inventory app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:78 +msgid "The :guilabel:`Scrap` button will only appear on a receipt that has been validated. This is because Odoo only allows products to be scrapped once they have been entered into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:81 +msgid "On the :guilabel:`Scrap` pop-up window, select the product being scrapped from the :guilabel:`Product` drop-down menu. Then, enter the quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:84 +msgid "The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:88 +msgid "Finally, click :guilabel:`Done` to scrap the product. After doing so, the :guilabel:`Scrap` pop-up window disappears and a :guilabel:`Scraps` smart button appears in the top right of the page. Click it to view all of the scrap orders created from that operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:-1 +msgid "The Scraps smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:3 msgid "Selecting a replenishment strategy" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:10 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:10 msgid "In Odoo, there are two strategies for automatically replenishing inventory: *reordering rules* and the *make to order (MTO)* route. Although these strategies differ slightly, they both have similar consequences: triggering the automatic creation of a |PO| or |MO|. The choice of which strategy to use depends on the business's manufacturing and delivery processes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:6 msgid "Terminology" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:19 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:56 msgid "Replenishment report and reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:21 msgid "The replenishment report is a list of all products that have a negative forecast quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:23 msgid "*Reordering rules* are used to ensure there's always a minimum amount of a product in-stock, in order to manufacture products and/or fulfill sales orders. When the stock level of a product reaches its minimum, Odoo automatically generates a purchase order with the quantity needed to reach the maximum stock level." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:28 msgid "Reordering rules can be created and managed in the replenishment report, or from the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:33 msgid "Make to order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:35 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:36 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:38 msgid "Unlike products replenished using reordering rules, Odoo automatically links the sales order to the |PO| or |MO| generated by the |MTO| route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:41 msgid "Another difference between reordering rules and |MTO| is, with |MTO|, Odoo generates a draft |PO| or |MO| immediately after the |SO| is confirmed. With reordering rules, Odoo generates a draft |PO| or |MO| when the product's forecasted stock falls below the set minimum quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:45 msgid "In addition, Odoo automatically adds quantities to the |PO| or |MO| as the forecast changes, so long as the |PO| or |MO| is not confirmed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:48 msgid "The |MTO| route is the best replenishment strategy for products that are customized, and/or for products that have no stock kept on-hand." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:58 msgid "To access the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment.`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:61 msgid "By default, the replenishment report dashboard shows every product that needs to be manually reordered. If there is no specific rule for a product, Odoo assumes the :guilabel:`Min Quantity` and :guilabel:`Max Quantity` stock are both `0.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:66 msgid "For products that don't have a set reordering rule, Odoo calculates the forecast based on confirmed sales orders, deliveries, and receipts. For products that have a set reordering rule, Odoo calculates the forecast normally, but also takes into account the purchase/manufacturing lead time and security lead time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:72 msgid "Before creating a new reordering rule, make sure the product has a *vendor* or a *bill of materials* configured on the product form. To check this, go to :menuselection:`Inventory app --> Products --> Products`, and select the product to open its product form. The vendor, if configured, is listed in the :guilabel:`Purchase` tab, and the bill on materials, if configured, is found in the :guilabel:`Bill of Materials` smart button at the top of the form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:78 msgid "The :guilabel:`Product Type`, located in the :guilabel:`General Information` tab on the product form, **must** be set to :guilabel:`Storable Product`. By definition, a consumable product does not have its inventory levels tracked, so Odoo cannot account for a consumable product in the replenishment report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 msgid "Replenishment report listing all items needing to be purchased to meet current needs." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:87 msgid "To create a new reordering rule from the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment`, click :guilabel:`Create`, and select the desired product from the drop-down menu in the :guilabel:`Product` column. If necessary, a :guilabel:`Min Quantity` and a :guilabel:`Max Quantity` can be configured in the corresponding columns on the :guilabel:`Replenishment` report page, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:93 msgid "To create a new reordering rule from the product form, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to open its product form. Click the :guilabel:`Reordering Rules` smart button, click :guilabel:`Create`, and fill out the fields." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:98 msgid "Replenishment report fields" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:100 msgid "The following fields are on the :guilabel:`Replenishment` report. If any of these fields are not visible, click the :guilabel:`ā‹® (additional options)` icon on the far right side of the report, then click the checkbox next to a field to make it visible." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:104 msgid ":guilabel:`Product`: the product that requires a replenishment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:105 msgid ":guilabel:`Location`: the specific location where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:106 msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:107 msgid ":guilabel:`On Hand`: the amount of product currently available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:108 msgid ":guilabel:`Forecast`: the amount of product available after all current orders (sales, manufacturing, purchase, etc.) are taken into account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:110 msgid ":guilabel:`Preferred Route`: how the product is procured, either :guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:112 msgid ":guilabel:`Vendor`: the company from which the product is acquired." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:113 msgid ":guilabel:`Bill of Materials`: the bill of materials for the product (if one is configured)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:114 msgid ":guilabel:`Trigger`: how the replenishment is created, either :guilabel:`Auto` (automatically, once the :guilabel:`On Hand` quantity goes below the :guilabel:`Min Quantity`) or :guilabel:`Manual` (only when the replenishment is requested)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:117 msgid ":guilabel:`Procurement Group`: the reference number for how the product is being acquired, such as a sales order, purchase order, or manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:119 msgid ":guilabel:`Min Quantity`: the minimum amount of product that should be available. When inventory levels goes below this number, the replenishment is triggered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:121 msgid ":guilabel:`Max Quantity`: the amount of product that should be available after replenishing the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:123 msgid ":guilabel:`Multiple Quantity`: if the product should be ordered in specific quantities, enter the number that should be ordered. For example, if the :guilabel:`Multiple Quantity` is set to `5`, and only 3 are needed, 5 products are replenished." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:126 msgid ":guilabel:`To Order`: the amount of product that is currently needed, and will be ordered, if the :guilabel:`Order Once` or :guilabel:`Automate Orders` button is clicked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:128 msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:129 msgid ":guilabel:`Company`: the company for which the product is acquired." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:131 msgid "By default, the quantity in the :guilabel:`To Order` field is the quantity required to reach the set :guilabel:`Max Quantity`. However, the :guilabel:`To Order` quantity can be adjusted by clicking on the field and changing the value. To replenish a product manually, click :guilabel:`Order Once`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:135 msgid "To automate a replenishment from the :guilabel:`Replenishment` page, click :guilabel:`Automate Orders` on the right-side of the line, represented by a :guilabel:`šŸ”„ (circular arrow)` icon." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:138 msgid "When this button is clicked, Odoo will automatically generate a draft |PO|/|MO| every time the forecasted stock level falls below the set :guilabel:`Min Quantity` of the reordering rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:139 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:141 msgid "On the :guilabel:`Replenishment` page, a reordering rule or manual replenishment can be temporarily deactivated for a given period, by clicking the :guilabel:`šŸ”• (snooze)` icon on the far-right of the line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 msgid "Snooze options to turn off notifications for reordering for a period of time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:149 msgid "A |PO| or |MO| created by a manual replenishment has a :guilabel:`Replenishment Report` as the source document. A |PO| or |MO| created by an automated reordering rule has the |SO| reference number(s) that triggered the rule as the source document." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 msgid "Quote request list shows which quotes are directly from the replenishment report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:158 msgid "Make to order (MTO) route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:158 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:160 msgid "Since the |MTO| route is recommended for customized products, the route is hidden by default." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:169 msgid "To activate the |MTO| route in Odoo:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:161 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:163 msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:164 msgid "Activate the :guilabel:`Multi-Step Routes` setting, located under the :guilabel:`Warehouse` section, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:164 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:166 msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:167 msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:168 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:170 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:172 msgid "Activating the :guilabel:`Multi-Step Routes` setting also activates :guilabel:`Storage Locations`. If these features aren't applicable to the warehouse, disable these settings after unarchiving the |MTO| route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:174 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:176 msgid "To set a product's procurement route to |MTO|, go to :menuselection:`Inventory app --> Products --> Products`, and click on the desired product to open its product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:179 msgid "Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` section of options, select :guilabel:`Replenish on Order (MTO)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:182 msgid "For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a vendor is configured in the :guilabel:`Purchase` tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:184 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:186 msgid "For products manufactured in-house, make sure the :guilabel:`Manufacture` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a bill of materials is configured for the product, which is accessible via the :guilabel:`Bill of Materials` smart button on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:190 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:192 msgid "The |MTO| route cannot be selected alone. |MTO| **only** works if the :guilabel:`Manufacture` or :guilabel:`Buy` route is also selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 msgid "Replenish on Order selected on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:3 msgid "Use different units of measure" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:7 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:13 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:13 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 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:18 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:-1 msgid "Enable Units of Measure in the Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:27 msgid "Units of measure categories" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:29 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:29 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:-1 msgid "Set units of measure categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:38 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:42 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:42 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:49 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:49 msgid "Click on the :guilabel:`Unit` category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:51 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:-1 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:60 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:60 msgid "Specify a product's units of measure" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:62 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:65 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:65 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:71 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:71 msgid "Unit conversion" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:74 msgid "Buy products in the Purchase UoM" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:76 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:80 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:80 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:85 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:85 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:90 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:90 msgid "Replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:92 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:97 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:97 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:102 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:102 msgid "Sell in a different UoM" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:104 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:107 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:107 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:112 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:112 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 -msgid "Units of measure, packages, and packagings" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:5 +msgid "Product tracking" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:5 -msgid "In Odoo, there are a variety of ways to specify the amount of products being bought, stocked, and sold. *Units of measure*, *packages*, and *packagings* are all available to streamline inventory flows, allowing for a variety of configurations for products as they enter and leave the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:3 +msgid "What's the difference between lots and serial numbers?" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:12 -msgid "Units of measure" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:6 +msgid "Introduction" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:14 -msgid "A *unit of measure (UoM)* refers to any of the different standards used to measure and handle a quantifiable amount of products, such a units, weight, time, or size. Different :abbr:`UoMs (Units of Measure)` for weight, for example, can be kilos, pounds, ounces, grams, and so on." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:8 +msgid "In Odoo, lots and serial numbers have similarities in their functional system but are different in their behavior. They are both managed within the **Inventory**, **Purchases** and **Sales** app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:18 -msgid "In Odoo, stock management and purchasing from suppliers are streamlined by specifying different :abbr:`UoMs (Units of Measure)` for both buying and selling products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:12 +msgid "**Lots** correspond to a certain number of products you received and store altogether in one single pack." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:-1 -msgid "Specify unit of measure for selling a product vs purchasing." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:15 +msgid "**Serial numbers** are identification numbers given to one product in particular, to allow to track the history of the item from reception to delivery and after-sales." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:25 -msgid "Once a product has a default :guilabel:`Unit of Measure` and :guilabel:`Purchase Unit of Measure` set on the product form, Odoo automatically converts the different units in the product's purchase/sales orders and the corresponding delivery orders/receipts." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:20 +msgid "When to use" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:29 -msgid "The only condition is that all of the units have to be in the *same category* (unit, weight, volume, length, etc.)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:22 +msgid "**Lots** are interesting for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:33 -msgid "On the product form for `Rope`, the following fields are set as:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:28 +msgid "**Serial numbers** are interesting for items that could require after-sales service, such as smartphones, laptops, fridges, and any electronic devices. You could use the manufacturer's serial number or your own, depending on the way you manage these products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:35 -msgid ":guilabel:`Unit of Measure` in `ft` (feet), and" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:34 +msgid "When not to use" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:36 -msgid ":guilabel:`Purchase Unit of Measure` in `cm` (centimeters)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:36 +msgid "Storing consumable products such as kitchen roll, toilet paper, pens and paper blocks in lots would make no sense at all, as there are very few chances that you can return them for production fault." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:38 -msgid "Because the vendor sells rope in `cm`, the purchase :guilabel:`UoM` is used to represent the quantity on the :abbr:`PO (Purchase Order)`, which is also in centimeters." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:40 +msgid "On the other hand, giving a serial number to every product is a time-consuming task that will have a purpose only in the case of items that have a warranty and/or after-sales services. Putting a serial number on bread, for instance, makes no sense at all." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "Display purchase order for the product, rope, in centimeters." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:46 +msgid ":doc:`serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:45 -msgid "After confirming the :abbr:`PO (Purchase Order)`, the quantity of product (found under the now visible :guilabel:`Demand` column) is converted from the purchase :abbr:`UoM (Unit of Measure)` to the :guilabel:`Unit of Measure`. Then, when the product is received by clicking the :guilabel:`Validate` button, the quantity in :guilabel:`Done` is automatically adjusted to match the :guilabel:`Demand` column." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:47 +msgid ":doc:`lots`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:52 -msgid "On the *receipt* for `Rope`, the quantities are automatically converted from `500 cm` that was requested on the purchase order, to `16.40 ft` to match the internal/stock :guilabel:`Unit of Measure` value." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:3 +msgid "Expiration dates" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "Rope quantity is converted from cm to ft during warehouse reception." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:7 +msgid "In Odoo, *expiration dates* can be used to manage and track the lifecycles of perishable products, from purchase to sale. Using expiration dates reduces product loss due to unexpected expiry, and helps to avoid sending expired products to customers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:61 -msgid ":ref:`Use Different Units of Measure `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:11 +msgid "In Odoo, only products that are tracked using *lots* and *serial numbers* can be assigned expiration information. Once a lot or serial number has been assigned, an expiration date can be set. This is especially helpful for companies (such as food manufacturers) that consistently, or exclusively, buy and sell perishable products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:64 -msgid "Packages" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:17 +msgid ":doc:`../product_tracking/lots`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:66 -msgid "Packages are a physical container that holds one or several products from a picking, typically used for outgoing deliveries or internal transfers. Packages can be a reusable or disposable (shipping) box, and are **not** specific to a product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:18 +msgid ":doc:`../product_tracking/serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:70 -msgid "Reusable boxes temporarily hold products during a picking to be brought to either a packing or shipping area. Disposable boxes are the actual shipping containers (e.g. cardboard boxes, envelopes, shipping bags, etc). These are used to ship the products out to customers." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:21 +msgid "Enable expiration dates" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:74 -msgid "Multiple items in a sales order (SO) can be separated into different packages to accommodate the products. For example, an :abbr:`SO (Sales Order)` that has 20 boxes of pencils and 4 boxes of erasers can be separated into two separate packages, each containing 10 boxes of pencils and 2 boxes of erasers." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:23 +msgid "To enable the use of *expiration dates*, go to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Traceability` section. Then, click the checkbox to enable the :guilabel:`Lots & Serial Numbers` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:80 -msgid "Products do *not* have to be divided equally. Products can be divided into as many packages that are needed to accommodate the :abbr:`SO (Sales Order)`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:27 +msgid "Once that feature is activated, a new option will appear to enable :guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and be sure to :guilabel:`Save` changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:83 -msgid "In Odoo, the quantity of products in each package needs to be recorded, so there is a full history for each product, including which package each item is shipped out in." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:-1 +msgid "Enabled lots and serial numbers and expiration dates settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:86 -msgid "To use this method, ensure the :guilabel:`Packages` option is enabled, by navigating to :menuselection:`Inventory app --> Configuration --> Settings --> Operations`. Click the :guilabel:`Packages` check box, and then :guilabel:`Save` to activate the feature." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:35 +msgid "Once the :guilabel:`Lots & Serial Numbers` feature is activated, additional features appear to :guilabel:`Display Lots & Serial Numbers on Delivery Slips`; to :guilabel:`Display Lots & Serial Numbers on Invoices`; and to :guilabel:`Display Expiration Dates on Delivery Slips`. Activating these features helps with end-to-end traceability, making it easier to manage product recalls, identify \"bad\" batches of products, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:90 -msgid "On a delivery order, assign which package to use by clicking on the :guilabel:`ā‰£ (Detailed Operations)` icon to the right of each product in the :guilabel:`Operations` tab." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:42 +msgid "Configure expiration dates on products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:-1 -msgid "Find detailed operations icon to the right on the product line." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:44 +msgid "Once the :guilabel:`Lots & Serial Numbers` and :guilabel:`Expiration Dates` features have been enabled in the settings of the *Inventory* app, expiration information can be configured on individual products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:97 -msgid "Clicking the :guilabel:`ā‰£ (Detailed Operations)` icon of a product reveals a pop-up window. In this window, the :guilabel:`Product` name, :guilabel:`Demand`, and :guilabel:`Quantity Done` are clearly displayed above the customizable product line." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:48 +msgid "To do so, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to edit. Selecting a product reveals the product form for that particular item. Once on the product form, click :guilabel:`Edit` in the upper-left corner to make changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:101 -msgid "Here, the warehouse location the product is coming from can be modified, in addition to the :guilabel:`Source Package` and :guilabel:`Destination Package`, which represents what package(s) the product(s) will be packaged into." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:53 +msgid "To be tracked using lots or serial numbers, or to configure expiration information, products *must* have their :guilabel:`Product Type` set as :guilabel:`Storable Product` under the :guilabel:`General Information` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:105 -msgid "Click :guilabel:`Add a line` to include each additional package used. Enter the desired amount in the :guilabel:`Done` field to specify the amount of products that will go into the :guilabel:`Destination Package`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:57 +msgid "Then, click the :guilabel:`Inventory` tab, and scroll down to the :guilabel:`Traceability` section. From here, make sure that either :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:110 -msgid "Multiple packages in a single delivery" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:61 +msgid "Once it is, a new :guilabel:`Expiration Date` checkbox appears that must also be clicked. When both are enabled, a new :guilabel:`Dates` field appears to the right." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:112 -msgid "Although a :abbr:`DO (Delivery Order)` is typically associated with a single package, orders can be split by clicking the :guilabel:`ā‰£ (Detailed Operations)` icon next to the products on an :abbr:`SO (Sales Order)` line. This opens the :guilabel:`Detailed Operations` window with an editable table to specify which products are intended for which package." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:65 +msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed in order to assign lot numbers to the existing stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:118 -msgid "To package 10 boxes of pencils with 2 boxes of erasers from the same :abbr:`SO (Sales Order)`, begin by navigating to the :abbr:`DO (Delivery Order)`. Then, select the :guilabel:`ā‰£ (four horizontal lines)` icon to the right of the product, `Box of Pencils`. Clicking the icon opens the :guilabel:`Detailed Operations` window that is used to detail how products, like the 20 `Box of Pencils`, are packaged." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:70 +msgid "For processing large quantities of products on receipts or deliveries, it is recommended to track using lots, so multiple products can be traced back to the same lot, if any issues arise." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:124 -msgid "Type in `10` under the :guilabel:`Done` field to package 10 products into the :guilabel:`Destination Package`. To specify the destination package, type the name of an existing package (such as `PACK0000006`) under the field, :guilabel:`Destination Package`. If the package does not exist, Odoo displays the :guilabel:`Create` button to create a new package. Click :guilabel:`Add a line` to assign the remaining products in another package, `PACK0000007`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:-1 +msgid "Expiration dates configuration on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "Detailed operations pop-up where the amount of product going in a pack can be specified." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:77 +msgid "Under the :guilabel:`Dates` field, there are four categories of expiration information to configure for the product:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:134 -msgid "Select :guilabel:`Detailed Operations` on the product line for `Box of Erasers` and similarly set 2 :guilabel:`Done` products to `PACK0000006` and `PACK0000007` each." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:80 +msgid ":guilabel:`Expiration Time`: the number of days after receiving products (either from a vendor or in stock after production) in which goods may become dangerous and should not be used or consumed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "Put in pack button to match the done amount matches the demand." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:82 +msgid ":guilabel:`Best Before Time`: the number of days before the expiration date in which the goods start deteriorating, **without** necessarily being dangerous yet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:141 -msgid "Once all the products for each line have been entered, click :guilabel:`Confirm` to return to the :abbr:`DO (Delivery Order)`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:84 +msgid ":guilabel:`Removal Time`: the number of days before the expiration date in which the goods should be removed from stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:144 -msgid "The :guilabel:`Done` quantity on the :abbr:`DO (Delivery Order)` updates as products are selected for each package. When the :guilabel:`Done` amount matches the :guilabel:`Demand` amount, click the :guilabel:`Validate` button to complete the delivery order." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:86 +msgid ":guilabel:`Alert Time`: the number of days before the expiration date in which an alert should be raised on goods in a particular lot or containing a particular serial number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:149 -msgid "The :guilabel:`Put In Pack` button is intended to quickly package all products in the :abbr:`DO (Delivery Order)` into one new package. The option to rename the package, or modify its contents, is available in the :guilabel:`Detailed Operations` pop-up." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:90 +msgid "The values entered into these fields automatically compute the expiration date for goods entered into stock, whether purchased from a vendor or manufactured in-house." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:153 -msgid "Clicking on the :guilabel:`Packages` smart button in the upper-right corner of the delivery order reveals a separate page, showing all the packages used in that :abbr:`DO (Delivery Order)`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:93 +msgid "Once all the expiration information has been configured, click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:157 -msgid "Packagings" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:96 +msgid "If the :guilabel:`Dates` field is not populated with any values for expiration information, dates (and lots) can be manually assigned upon receipts and deliveries in and out of the warehouse. Even when assigned, they can still be overwritten and changed manually if needed, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:159 -msgid "*Packaging* is product specific, and refers to a disposable container that holds several units of a specific product. Unlike packages, packagings cannot be reusable, and each specific packaging must be defined on the individual product form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:101 +msgid "Set expiration dates on receipts with lots & serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:163 -msgid "For example, different packages for cans of soda can be configured as a 6-pack, a 12-pack, or a case of 36. Each flavor of soda would need a `6`, `12`, and `36` can packaging configured on the individual product since packagings are product specific, not generic." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:103 +msgid "Generating expiration dates for **incoming** goods can be done directly from the purchase order. To create a purchase order, go to the :menuselection:`Purchase` app and click :guilabel:`Create` to create a new request for quotation (RFQ)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:168 -msgid "Set up packagings" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:107 +msgid "Then, fill out the information by adding a :guilabel:`Vendor`, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a product`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:170 -msgid "To use packagings, ensure the :guilabel:`Product Packagings` feature is enabled. To do that, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Then, under the :guilabel:`Products` heading, check the box next to :guilabel:`Product Packagings`, and click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:110 +msgid "Choose the desired quantity to order by changing the number in the :guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This converts the :abbr:`RFQ (request for quotation)` into a purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:175 -msgid "In Odoo, product packagings are used on sales/purchase orders and inventory transfers." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:114 +msgid "Click the :guilabel:`Receipt` smart button at the top of the purchase order to be taken to the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:177 -msgid "Next, to create packagings, navigate to :menuselection:`Inventory app --> Products --> Products` and click on the desired product, then click :guilabel:`Edit` on the product page." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:118 +msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities causes a :guilabel:`User Error` popup to appear. The popup requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` cannot be validated without an assigned lot or serial number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:180 -msgid "Under the :guilabel:`Inventory` tab, scroll down to the :guilabel:`Packaging` section, and click :guilabel:`Add a line`. Then, a pop-up window appears, in which the following information for each packaging should be entered:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:0 +msgid "User error popup when validating an order with no lot number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:184 -msgid ":guilabel:`Packaging`: name of packaging that appears on sales/purchase orders as a packaging option for the product" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:127 +msgid "From here, click the :guilabel:`Additional Options` menu (hamburger) icon located on the far-right of the product line. When clicked, a :guilabel:`Detailed Operations` pop-up will appear." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:186 -msgid ":guilabel:`Contained quantity`: amount of product in the packaging" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:130 +msgid "In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial number under the :guilabel:`Lot/Serial Number Name` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:187 -msgid ":guilabel:`Barcode`: identifier used with the :ref:`Barcode app ` to trace the packaging of a product during stock moves or pickings. Leave blank if not in use" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:133 +msgid "An expiration date automatically populates, based on the configuration on the product form (if previously configured)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:189 -msgid ":guilabel:`Company`: indicates the packaging is only available at the selected company. Leave blank to make the packaging available across all companies." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:137 +msgid "If the :guilabel:`Dates` field on the product form has not been configured, this date can be manually entered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:193 -msgid "Create a packaging type for 6 cans of the product, `Grape Soda`, by naming the :guilabel:`Packaging` to `6-pack` and setting the :guilabel:`Contained quantity` to `6` in the pop-up window that appears after clicking on :guilabel:`Add a line`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:140 +msgid "After the expiration date has been established, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, click :guilabel:`Validate`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "Create 6-pack case for product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:-1 +msgid "Detailed operations popup showing expiration dates for ordered products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:201 -msgid "When all the necessary information has been entered, either click :guilabel:`Save & Close` to save the packaging and return to the product detail form, or :guilabel:`Save & New` to save the packaging and create another one in a fresh pop-up window." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:147 +msgid "A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial #`; and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:206 -msgid "View all product packagings in the :guilabel:`Inventory` tab of the product form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:153 +msgid "Set expiration dates on manufactured products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "Show packaging and contained quantities, specified on the product page form in the\n" -"Inventory tab." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:155 +msgid "Expiration dates can also be generated for products manufactured in-house. To assign expiration dates to manufactured products, a manufacturing order (MO) needs to be completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:214 -msgid "View all packagings" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:158 +msgid "To create a :abbr:`MO (manufacturing order)`, go to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, and click :guilabel:`Create`. Choose a product to manufacture from the :guilabel:`Product` field drop-down menu, then select the :guilabel:`Quantity` to produce." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:216 -msgid "To view all packagings that have been created, go to :menuselection:`Inventory app --> Configuration --> Product Packagings`. Doing so reveals the :guilabel:`Product Packagings` page with a complete list of all packagings that have been created for all products. Create new packagings by clicking :guilabel:`Create`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:-1 +msgid "Manufacturing order for product with expiration date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:222 -msgid "Two soda products, `Grape Soda` and `Diet Coke`, have three types of packaging configured. On the :guilabel:`Product Packagings` page, each product can sold as a `6-Pack` that contains 6 products, `12-Pack` of 12 products, or a `Case` of 32 products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:167 +msgid "To manufacture a product, there must be materials to consume in the lines in the :guilabel:`Product` column. This can be achieved either by creating a :guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding materials to consume by clicking :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "List of different packagings for products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:172 +msgid "Once ready, click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:231 -msgid "Apply packagings" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:174 +msgid "Next to :guilabel:`Lot/Serial Number`, either select an existing lot number from the drop-down menu, or click the green :guilabel:`+` sign to automatically assign a new lot number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:233 -msgid "When creating a sales order in the :menuselection:`Sales` app, specify the packagings that should be used for the product(s). The chosen packaging is displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Package` field." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:177 +msgid "Then, select a number of units for the :guilabel:`Quantity` field, and click :guilabel:`Mark as Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:238 -msgid "18 cans of the product, `Grape Soda`, is packed using three 6-pack packagings." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:180 +msgid "Click on the :guilabel:`External Link` icon in the assigned :guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail form for that specific number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:0 -msgid "Assign packagings on the Sales Order Line." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:183 +msgid "On that pop-up, under the :guilabel:`Dates` tab, all expiration information that was previously configured for the product is displayed. That same information is also available on the detail form for that specific product, or by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:245 -msgid "Packaging can be used in conjunction with Odoo :ref:`Barcode `. When receiving products from suppliers, scanning the packaging barcode automatically adds the number of units in the packaging to the internal count of the product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:-1 +msgid "Dates tab with expiration information for specific lot number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting.rst:5 -msgid "Valuation Methods" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:193 +msgid "Sell products with expiration dates" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:3 -msgid "Integrating additional costs to products (landed costs)" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:195 +msgid "Selling perishable products with expiration dates is done the same as any other type of product. The first step in selling perishable products is to create a sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:5 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:198 +msgid "To do that, go to :menuselection:`Sales app --> Create` to create a new quotation, and fill out the information on the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:201 +msgid "Add a :guilabel:`Customer`, click :guilabel:`Add a product` to add the desired products to the :guilabel:`Product` lines, and set a :guilabel:`Quantity` for the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:-1 -msgid "Activate the landed cost feature in Inventory settings." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:204 +msgid "Then, click the :guilabel:`Other Info` tab. Under the :guilabel:`Delivery` section, change the :guilabel:`Delivery Date` to a date after the expected date, and click the :guilabel:`green checkmark` icon to confirm the date. Finally, click :guilabel:`Confirm` to confirm the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:20 -msgid "Add costs to products" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:208 +msgid "Next, click the :guilabel:`Delivery` smart button at the top of the sales order to see the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:23 -msgid "Receive the vendor bill" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:211 +msgid "On the warehouse receipt form, click :guilabel:`Validate`, and then :guilabel:`Apply` in the accompanying pop-up window, to automatically process all :guilabel:`Done` quantities, and deliver the products to the customer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:215 +msgid "If the products are delivered before the :guilabel:`Alert Date` set on the product form, then no alerts will be created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:-1 -msgid "Enable Landed Costs option on vendor bill line." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:219 +msgid "To sell perishable products with expiration dates, the :guilabel:`Removal Strategy` for the :guilabel:`Location` the products are stored in must be set to :abbr:`FEFO (First Expiry, First Out)`. If there is not enough stock of perishable products in one lot, Odoo will automatically take the remaining quantity required from a second lot with the next-soonest expiration date. Removal strategies can also be set on :guilabel:`Product Categories`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:226 +msgid ":doc:`../../warehouses_storage/advanced_operations_warehouse/removal`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:37 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:229 +msgid "View expiration dates for lots & serial numbers" msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:231 +msgid "To view (and/or group) all products with expiration dates by lot number, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:-1 -msgid "Option to define a product as a landed cost." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:234 +msgid "Once there, remove any default search filters from the :guilabel:`Search...` bar. Then, click :guilabel:`Group By`, choose :guilabel:`Add Custom Group`, and select the :guilabel:`Expiration Date` parameter from the drop-down menu. Finally, click :guilabel:`Apply` to apply the filter." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/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`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:238 +msgid "Doing so breaks down all perishable products, their expiration dates, and the assigned lot number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:-1 -msgid "Use a warehouse transfer to cover a landed cost in the accounting journal." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:-1 +msgid "Group by expiration dates on lots and serial numbers page." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:245 +msgid "Expiration alerts" 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`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:247 +msgid "To see expiration alerts, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." 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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:249 +msgid "Then, click into a :guilabel:`Lot/Serial Number` with perishable products. Doing so reveals the serial number detail form. On the serial number detail form, click the :guilabel:`Dates` tab to see all expiration information related to the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:-1 -msgid "Landed cost journal entry" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:253 +msgid "To edit the form, click :guilabel:`Edit` in the upper-left corner of the form, then change the :guilabel:`Expiration Date` to today's date (or earlier), and click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:257 +msgid "After saving, the lot number form displays a red :guilabel:`Expiration Alert` at the top of the form to indicate that the products in this lot are either expired or expiring soon. From here, click back to the :guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:3 -msgid "Inventory valuation configuration" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:261 +msgid "To see the new expiration alert, or any expiration alerts for products that are expired (or will expire soon), remove all of the search filters from the :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:7 -msgid "All of a company's stock on-hand contributes to the valuation of its inventory. That value should be reflected in the company's accounting records to accurately show the value of the company and all of its assets." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:265 +msgid "Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:11 -msgid "By default, Odoo uses a periodic inventory valuation (also known as manual inventory valuation). This method implies that the accounting team posts journal entries based on the physical inventory of the company, and that warehouse employees take the time to count the stock. In Odoo, this method is reflected inside each product category, where the :guilabel:`Costing Method` field will be set to `Standard Price` by default, and the :guilabel:`Inventory Valuation` field will be set to `Manual`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:-1 +msgid "Expiration alert for product past the expiration date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:-1 -msgid "The Inventory Valuation fields are located on the Product Categories form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:3 +msgid "Use lots to manage groups of products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:22 -msgid "Alternatively, automated inventory valuation is an integrated valuation method that updates the inventory value in real-time by creating journal entries whenever there are stock moves initiated between locations in a company's inventory." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:5 +msgid "*Lots* are one of the two ways to identify and track products in Odoo. A lot usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse, but can also pertain to a batch of products manufactured in-house, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:27 -msgid "Automated inventory valuation is a method recommended for expert accountants, given the extra steps involved in journal entry configuration. Even after the initial setup, the method will need to be periodically checked to ensure accuracy, and adjustments may be needed on an ongoing basis depending on the needs and priorities of the business." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:9 +msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps to identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their lifecycles." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:33 -msgid "Types of accounting" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:14 +msgid "Lots are useful for products that are manufactured or received in large quantities (such as clothes or food), and can be used to trace a product back to a group. This is especially useful when managing product recalls or expiration dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:35 -msgid "Accounting entries will depend on the accounting mode: *Continental* or *Anglo-Saxon*." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:38 -msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:20 +msgid "Enable lots & serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:41 -msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. *Interim Stock Accounts* are used for the input and output accounts, and are both *Asset Accounts* in the balance sheet." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 +msgid "To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:46 -msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Additionally, a single *Expense* account is used for both input and output accounts in the balance sheet." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Enabled lots and serial numbers feature in inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:51 -msgid "Costing methods" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:36 +msgid "Track products by lots" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:53 -msgid "Below are the three costing methods that can be used in Odoo for inventory valuation." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:38 +msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be configured to be tracked using lots. To do this, go to the :menuselection:`Inventory app --> Products --> Products`, and choose a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:55 -msgid "**Standard Price**: is the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:42 +msgid "Once on the product form, click :guilabel:`Edit` to make changes to the form. Then, click the :guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click :guilabel:`Save` to save changes. Existing or new lot numbers can now be assigned to newly-received or manufactured batches of this product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:59 -msgid "**Average Cost (AVCO)**: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:48 +msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed to assign lot numbers to the existing stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:62 -msgid "**First In First Out (FIFO)**: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it's highly sensitive to input data and human error." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Enabled tracking by lots feature on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:70 -msgid "Changing the costing method greatly impacts inventory valuation. It's highly recommended to consult an accountant first before making any adjustments here." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:56 +msgid "Create new lots for products already in stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:74 -msgid "Configure automated inventory valuation in Odoo" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:58 +msgid "New lots can be created for products already in stock with no assigned lot number. To do this, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a separate page where a new :guilabel:`Lot/Serial Number` is generated automatically." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:76 -msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory --> Configuration --> Product Categories`, and choose the category/categories where the automated valuation method should apply." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:64 +msgid "While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:81 -msgid "It is possible to use different valuation settings for different product categories." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:68 +msgid "Once the new :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:83 -msgid "Under the :guilabel:`Inventory Valuation` heading are two labels: :guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the desired :guilabel:`Costing Method` using the drop-down menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to :guilabel:`Automated`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:72 +msgid "This form also provides the option to adjust the :guilabel:`Quantity`, assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and assign this specific lot or serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:89 -msgid ":doc:`Using the inventory valuation `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:77 +msgid "A detailed description of this specific lot or serial number can also be added in the :guilabel:`Description` tab below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:93 -msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:81 +msgid "When all desired configurations are complete, click the :guilabel:`Save` button to save all changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:99 -msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "New lot number creation form with assigned product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:105 -msgid "On the same screen, the :guilabel:`Account Stock Properties` fields will appear, as they are now required fields given the change to automated inventory valuation. These accounts are defined as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:86 +msgid "After a new lot number has been created, saved, and assigned to the desired product, navigate back to the product form in the :menuselection:`Inventory` app, by going to :menuselection:`Products --> Products`, and selecting the product to which this newly-created lot number was just assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:109 -msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:90 +msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new lot number. When additional quantity of this product is received or manufactured, this new lot number can be selected and assigned to it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:111 -msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:95 +msgid "Manage lots for shipping and receiving" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:115 -msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:97 +msgid "Lot numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are assigned directly on the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:121 -msgid "Access reporting data generated by inventory valuation" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:102 +msgid "Manage lots on receipts" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:123 -msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:104 +msgid "Assigning lot numbers to **incoming** goods can be done directly from the purchase order (PO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:128 -msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:106 +msgid "To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:132 -msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:109 +msgid "On this :abbr:`RFQ (request for quotation)`, fill out the necessary information by adding a :guilabel:`Vendor`, and adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` (under the :guilabel:`Products` tab)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:-1 -msgid "See the full inventory valuation breakdown in Odoo Accounting app." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:113 +msgid "Choose the desired quantity of the product to order by changing the number in the :guilabel:`Quantity` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:3 -msgid "Using inventory valuation" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:116 +msgid "Once the :abbr:`RFQ (request for quotation)` has been filled out, click :guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is confirmed, it becomes a :guilabel:`Purchase Order`, and a :guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:5 -msgid "*Inventory valuation* is a quintessential accounting procedure that calculates the value of on-hand stock. Once determined, the inventory valuation amount is then incorporated into a company's overall value." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:122 +msgid "Clicking :guilabel:`Validate` before assigning a lot number to the ordered product quantities will result in a :guilabel:`User Error` pop-up. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a lot number being assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:9 -msgid "In Odoo, this process can be conducted manuallyā€” by warehouse employees physically counting the productsā€” or automatically through the database." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Add lot/serial number user error popup." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:13 -msgid "Automatic inventory valuation" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:131 +msgid "From here, click the :guilabel:`Additional Options` menu, represented by a :guilabel:`hamburger (four horizontal lines)` icon, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:15 -msgid "To use Odoo to automatically generate a trail of inventory valuation entries, first navigate to the :menuselection:`Product Categories` list by going to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category. On the form, set the :guilabel:`Inventory Valuation` as :guilabel:`Automated` and the :guilabel:`Costing Method` to any of the three options." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:135 +msgid "In this pop-up, configure a number of different fields, including the assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:22 -msgid ":ref:`Set up inventory valuation `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:138 +msgid "There are two ways to assign lot numbers: **manually** and **copy/paste**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:24 -msgid "In order to understand how moving products in and out of stock affects the company's overall value, consider the following product and stock moves scenario below." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 +msgid "**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:28 -msgid "Receive a product" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "Assign lot number detailed operations popup." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:30 -msgid "To track the value of incoming products, such as a simple *table*, configure the product category on the the product itself. To get there, navigate to :menuselection:`Inventory app --> Products --> Products` and click the desired product. On the product form, click the :guilabel:`āž”ļø (right arrow)` icon beside the :guilabel:`Product Category` field, which opens an internal link to edit the product category. Next, set the :guilabel:`Costing Method` as :guilabel:`First In First Out (FIFO)` and :guilabel:`Inventory Valuation` as :guilabel:`Automated`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:149 +msgid "If quantities should be processed in multiple locations and lots, click :guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for additional quantities. Repeat until the :guilabel:`Quantity Done` matches the :guilabel:`Demand`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:38 -msgid "Alternatively access the :guilabel:`Product Categories` dashboard by navigating to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:153 +msgid "**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:42 -msgid "Next, assume 10 tables are purchased at a price of $10.00, each. The :abbr:`PO (Purchase Order)` for those tables will show the subtotal of the purchase as $100, plus any additional costs or taxes." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "List of lot numbers copied on excel spreadsheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Purchase order with 10 tables products valued at $10.00 each." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:163 +msgid "Once all product quantities have been assigned a lot number, click :guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:49 -msgid "After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, the :guilabel:`Valuation` smart button is enabled. Clicking on this button displays a report showing how the inventory valuation for the table was affected by this purchase." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:166 +msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #` assigned, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:54 -msgid ":ref:`Developer mode ` **must** be turned on to see the :guilabel:`Valuation` smart button." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:172 +msgid "Manage lots on delivery orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:58 -msgid "The :doc:`consignment ` feature allows ownership to items in stock. Thus, products owned by other companies are not accounted for in the host company's inventory valuation." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:174 +msgid "Assigning lot numbers to **outgoing** goods can be done directly from the sales order (SO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "See Valuation smart button on a receipt, with Developer mode enabled." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:176 +msgid "To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app --> Create`. Doing so reveals a new, blank quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:66 -msgid "For a comprehensive dashboard that includes the inventory valuation of all product shipments, inventory adjustments, and warehouse operations, refer to the :ref:`stock valuation report `." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:179 +msgid "On this blank quotation form, fill out the necessary information by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:71 -msgid "Deliver a product" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:221 +msgid "Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:73 -msgid "In the same logic, when a table is shipped to a customer and leaves the warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock valuation record as it does on a :abbr:`PO (Purchase Order)`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:185 +msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, it becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Decreased stock valuation after a product is shipped." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:227 +msgid "Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific :abbr:`SO (sales order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:84 -msgid "Inventory valuation report" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:192 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:230 +msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:86 -msgid "To view the current value of all products in the warehouse, first turn on :ref:`Developer mode ` and navigate to :menuselection:`Inventory app --> Reporting --> Valuation`. The :guilabel:`Stock Valuation` dashboard displays detailed records of products with the :guilabel:`Date`, :guilabel:`Quantity`, :guilabel:`Unit Value`, and :guilabel:`Total Value` of the inventory." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:196 +msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with the full :guilabel:`Reserved` quantity taken from that specific lot (if there is enough stock in that particular lot)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:93 -msgid ":ref:`Developer mode ` **must** be enabled to see the :guilabel:`Valuation` option under :guilabel:`Reporting`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:200 +msgid "If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand` should be taken from multiple lots, change the quantity in the :guilabel:`Done` column to only include that specific part of the total quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Inventory valuation report showing multiple products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:205 +msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough quantity in one lot to fulfill the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:100 -msgid "The :guilabel:`Valuation At Date` button, located in the top-left corner of the :guilabel:`Stock Valuation` page, reveals a pop-up window. In this pop-up, the inventory valuation of products available during a prior specified date can be seen and selected." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:211 +msgid ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:105 -msgid "View a detailed record of a product's inventory value, stock move, and on-hand stock by selecting the teal :guilabel:`āž”ļø (right arrow)` button to the right of the :guilabel:`Reference` column value." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:213 +msgid "Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:110 -msgid "Update product unit price" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Detailed operations popup for source lot number on sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:112 -msgid "For any company: lead times, supply chain failures, and other risk factors can contribute to invisible costs. Although Odoo attempts to accurately represent the stock value, *manual valuation* serves as an additional tool to update the unit price of products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:221 +msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:117 -msgid "Manual valuation is intended for products that can be purchased and received for a cost greater than 0, or have product categories set with :guilabel:`Costing Method` set as either :guilabel:`Average Cost (AVCO)` or :guilabel:`First In First Out (FIFO)`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:226 +msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order, if the product quantities shared the same lot number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Add manual valuation of stock value to a product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:230 +msgid "Manage lots for different operations types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:125 -msgid "Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard by first navigating to :menuselection:`Inventory app --> Reporting --> Valuation`. Next, to enable the *product revaluation* feature, select :menuselection:`Group by --> Product` to organize all the records by product. Click on the gray :guilabel:`ā–¶ļø (drop-down triangle)` icon to reveal stock valuation line items below, as well as a teal :guilabel:`āž• (plus)` button on the right." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:232 +msgid "In Odoo, the creation of new lots is only allowed upon **receiving** products from a purchase order, by default. **Existing** lot numbers cannot be used." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:131 -msgid "Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product Revaluation` form. Here, the inventory valuation for a product can be recalculated, by increasing or decreasing the unit price of each product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:235 +msgid "For sales orders, the opposite is true: new lot numbers cannot be created on the delivery order, only existing lot numbers can be used." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:136 -msgid "The :guilabel:`ā–¶ļø (drop-down triangle)` and :guilabel:`āž• (plus)` buttons are only visible after grouping entries by product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:238 +msgid "To change the ability to use new (or existing) lot numbers on any operation type, go to the :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Product revaluation form adding a value of $1.00 with the reason being inflation." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:242 +msgid "For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:144 -msgid "Inventory valuation journal entries" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:247 +msgid "For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. Be sure to click the :guilabel:`Save` button to save all changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:146 -msgid "In Odoo, automatic inventory valuation records are also recorded in the :menuselection:`Accounting app --> Accounting --> Journal Entries` dashboard. On this comprehensive list of accounting entries, inventory valuation records are identified by checking values in the :guilabel:`Journal` column, or looking for the :guilabel:`Reference` column value which matches the warehouse operation reference (e.g. `WH/IN/00014` for receipts)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Enabled traceability setting on operations type form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:152 -msgid "Clicking on an inventory valuation journal entry opens a *double-entry accounting* record. These records are generated by Odoo to track the change of value in inventory valuation as products are moved in and out of the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:256 +msgid "For inter-warehouse transfers involving products tracked by lots, it can be useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for warehouse receipts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:157 -msgid "To view the inventory valuation of 10 *tables*, costing $10.00 each, upon reception from the vendor, go to the :menuselection:`Journal Entries` page found in :menuselection:`Accounting app --> Accounting --> Journal Entries`. Here, click the journal line where the :guilabel:`Reference` column value matches the reference on the receipt, `WH/IN/00014`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:260 +msgid "Lots traceability" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:0 -msgid "Stock valuation page depicting the products within a shipment." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:262 +msgid "Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a product: where (and when) it came from, where it was stored, and who (and when) it went to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:166 -msgid "`Stock interim` is a holding account for money intended to pay vendors for the product. The `stock valuation` account stores the value of all on-hand stock." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:265 +msgid "To see the full traceability of a product, or group by lots, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :menuselection:`Lots/Serial Numbers` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:0 -msgid "Accounting entry for the inventory valuation of 10 tables." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:269 +msgid "From here, products with lot numbers assigned to them will be listed by default, and can be expanded to show the lot numbers those products have assigned to them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:174 -msgid "`Odoo Tutorial: Inventory Valuation `_" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:272 +msgid "To group by lots (or serial numbers), begin by removing any filters in the search bar. Then, click the :guilabel:`Group By` drop-down, select :guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from the drop-down menu. Then, click :guilabel:`Apply`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:6 -msgid "Incoming shipments and delivery orders" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:276 +msgid "Doing so displays all existing lots and serial numbers, and can be expanded to show all quantities of products with that assigned number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:8 -msgid "There are several ways to handle how a warehouse receives products (receipts) and ships products (deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse size, and the amount of daily confirmed receipts and delivery orders, the way products are handled when coming in and out of the warehouse can vary a lot. Different settings can be configured for receipts and deliveries; they do not have to be configured to have the same number of steps." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Lots and serial numbers traceability report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:15 -msgid "`Using Routes (eLearning Tutorial) `_" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:284 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:319 +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:16 -msgid "`Push & Pull Rules (eLearning Tutorial) `_" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:3 +msgid "Use serial numbers to track products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:20 -msgid "Choosing the right inventory flow to handle receipts and deliveries" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:5 +msgid "*Serial numbers* are one of the two ways to identify and track products in Odoo. A serial number is a unique identifier assigned incrementally (or sequentially) to an item or product, used to distinguish it from other items and products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:22 -msgid "By default, Odoo handles shipping and receiving in three different ways: in one, two, or three steps. The simplest configuration is one step, which is the default. Each additional step required for a warehouse for either the receiving or shipping process will add an additional layer of operations to perform before a product is either received or shipped. These configurations depend entirely on the requirements for the products stored, such as performing quality checks on received products, or using special packaging on shipped products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:9 +msgid "Serial numbers can consist of many different types of characters: they can be strictly numerical, they can contain letters and other typographical symbols, or they can be a mix of all of the above." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:30 -msgid "One-step flow" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:12 +msgid "The goal of assigning serial numbers to individual products is to make sure that every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services to products that they sell and deliver." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:32 -msgid "The receiving and shipping rules for a one-step configuration are as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:17 +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:34 -msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 +msgid "To track products using serial numbers, the :guilabel:`Lots & Serial Numbers` feature must be enabled. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` button to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:36 -msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "Enabled lots and serial numbers setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:38 -msgid "Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:34 +msgid "Configure serial number tracking on products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:40 -msgid "Receipts and/or deliveries are handled quickly." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:36 +msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be tracked using serial numbers. To configure this, go to :menuselection:`Inventory app --> Products --> Products`, and choose a desired product to track." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:41 -msgid "Recommended for small warehouses with low stock levels, and for non-perishable items." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:40 +msgid "Once on the product form, click :guilabel:`Edit`, and click the :guilabel:`Inventory` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:42 -msgid "Items are received or shipped directly into/from stock." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:42 +msgid "Once on the product form, click :guilabel:`Edit`, navigate to the :guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` section. Then, select the :guilabel:`By Unique Serial Number` option, and click :guilabel:`Save` to save the changes. Existing or new serial numbers can now be selected and assigned to newly-received or manufactured batches of this product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:45 -msgid ":ref:`Process receipts and deliveries in one step `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "Enabled serial number tracking on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:48 -msgid "Two-step flow" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:52 +msgid "If a product doesn't have a serial number assigned to it, a user error pop-up window will appear. The error message states that the product(s) in stock have no lot/serial number. However, a lot/serial number can be assigned to the product by making an inventory adjustment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:50 -msgid "The receiving and shipping rules for a two-step configuration are as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:57 +msgid "Create new serial numbers for products already in stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:52 -msgid "**Input + stock**: Bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:59 +msgid "New serial numbers can be created for products already in stock with no assigned serial number. To do this, go to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a blank lots/serial numbers form. On this form, a new :guilabel:`Lot/Serial Number` is generated automatically." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:55 -msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:65 +msgid "While Odoo automatically generates a new lot/serial number to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:57 -msgid "Minimum requirement to use lot numbers or serial numbers to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or :abbr:`FEFO (First Expired, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:69 +msgid "Once the :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:60 -msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:73 +msgid "This form also provides the option to adjust the :guilabel:`Quantity`, to assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and to assign this specific lot/serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:62 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:83 -msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:78 +msgid "A detailed description of this specific lot/serial number can also be added in the :guilabel:`Description` tab below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:66 -msgid ":ref:`Process receipts and deliveries in two steps `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "New serial number created for existing product stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:69 -msgid "Three-step flow" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:87 +msgid "After a new serial number has been created, assigned to the desired product, and saved, navigate back to the product form, by going to :menuselection:`Products --> Products`, and selecting the product that this newly-created serial number was just assigned to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:71 -msgid "The receiving and shipping rules for a three-step configuration are as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:91 +msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new serial number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:73 -msgid "**Input + quality + stock**: Receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:95 +msgid "Manage serial numbers for shipping and receiving" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:75 -msgid "**Pick + pack + ship**: Pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:97 +msgid "Serial numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, serial numbers are assigned directly on the purchase order form. For outgoing goods, serial numbers are assigned directly on the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:77 -msgid "Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:102 +msgid "Manage serial numbers on receipts" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:80 -msgid "Recommended for very large warehouses with very high stock levels." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:104 +msgid "Assigning serial numbers to **incoming** goods can be done directly from the purchase order (PO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:81 -msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:106 +msgid "To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:87 -msgid ":ref:`Process receipts in three steps `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:109 +msgid "On this :abbr:`RFQ (request for quotation)` form, fill out the necessary information, by adding a :guilabel:`Vendor`, and by adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product`, under the :guilabel:`Products` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:88 -msgid ":ref:`Process deliveries in three steps `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:113 +msgid "Choose the desired quantity of the product to order, by changing the number in the :guilabel:`Quantity` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:91 -msgid "Inventory flow table of contents" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:116 +msgid "When the necessary configurations are complete, click :guilabel:`Confirm Order`. This will convert the :abbr:`RFQ (request for quotation)` to a purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:3 -msgid "Process deliveries in three steps" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:119 +msgid "Then, click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form page for that specific :abbr:`PO (purchase order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:7 -msgid "Some companies process large amounts of deliveries every day, many of which include multiple products or require special packaging. To make this efficient, a packing step is needed before shipping out products. For this, Odoo has a three step process for delivering goods." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:123 +msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities will cause a :guilabel:`User Error` pop-up to appear. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a serial number being assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:11 -msgid "In the default three-step delivery process, products that are part of a delivery order are picked in the warehouse according to their removal strategy, and brought to a packing zone. After the items have been packed into the different shipments in the packing zone, they are brought to an output location before being shipped. These steps can be modified if they do not fit the needs of the business." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "User error popup prompting serial number entry." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:20 -msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three step deliveries. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:136 +msgid "In this pop-up, configure a number of different fields, including the assignation of a serial number (or serial numbers) under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 -msgid "Activate multi-step routes and storage locations in inventory settings." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:140 +msgid "There are three ways to do this: manually assigning serial numbers, automatically assigning serial numbers, and copy/pasting serial numbers from a spreadsheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:30 -msgid "Next, the warehouse needs to be configured for three step deliveries. To do this, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the :guilabel:`Warehouse`. Then, select :guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for :guilabel:`Outgoing Shipments`. Then :guilabel:`Save` the changes." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:144 +msgid "Assign serial numbers manually" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 -msgid "Set outgoing shipment option to deliver in three steps." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:146 +msgid "To assign serial numbers manually, click :guilabel:`Add a line` from the :guilabel:`Detailed Operations` pop-up, and first choose the location where the product will be stored under the :guilabel:`To` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:39 -msgid "Activating three-step receipts and deliveries will create two new internal locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:150 +msgid "Then, type a new :guilabel:`Serial Number Name`, and set the :guilabel:`Done` quantity in the appropriate columns." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:45 -msgid "Process a delivery order in three steps (pick + pack + ship)" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:153 +msgid "Repeat this process for the quantity of products shown in the :guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field displays the correct (matching) number of products processed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:48 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:89 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:141 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:157 +msgid "Assign serial numbers automatically" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:159 +msgid "If a large quantity of products need individual serial numbers assigned to them, Odoo can automatically generate and assign serial numbers to each of the individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:162 +msgid "To accomplish this, start with the :guilabel:`First SN` field in the :guilabel:`Detailed Operations` pop-up window, and type the first serial number in the desired order to be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:165 +msgid "Then, in the :guilabel:`Number of SN` field, type the total number of items that need newly-generated unique serial numbers assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:168 +msgid "Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate with new serial numbers matching the ordered quantity of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "Automatic serial number assignment in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:176 +msgid "Copy/paste serial numbers from a spreadsheet" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:178 +msgid "To copy and paste serial numbers from an existing spreadsheet, first populate a spreadsheet with all of the serial numbers received from the supplier (or manually chosen upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:183 +msgid "From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the serial number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "List of serial numbers copied in Excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:191 +msgid "For purchase orders that include large quantities of products to receive, the best method of serial number assignment is to automatically assign serial numbers using the :guilabel:`Assign Serial Numbers` button located on the :abbr:`PO (purchase order)`. This prevents any serial numbers from being reused or duplicated, and improves traceability reporting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:196 +msgid "Once all product quantities have been assigned a serial number, click the :guilabel:`Confirm` button to close the pop-up. Then, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:199 +msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:204 +msgid "Once all product quantities have been assigned a serial number, click :guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:211 +msgid "Manage serial numbers on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:213 +msgid "Assigning serial numbers to **outgoing** goods can be done directly from the sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:215 +msgid "To create an :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing so reveals a new, blank quotation form. On this blank quotation form, fill out the necessary information, by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab), by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:223 +msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, the quotation becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:234 +msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with each product of the total :guilabel:`Reserved` quantity listed with their unique serial numbers (most likely listed in sequential order)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:238 +msgid "To manually change a product's serial number, click the drop-down menu under :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial number. Then, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:242 +msgid "Finally, click the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "Serial numbers listed in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:248 +msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:253 +msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order (PO), if any of the product quantities shared a serial number assigned during receipt of that specific :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:258 +msgid "Manage serial numbers for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:260 +msgid "By default in Odoo, the creation of new serial numbers is only allowed upon **receiving** products from a purchase order. **Existing** serial numbers cannot be used. For sales orders, the opposite is true: new serial numbers cannot be created on the delivery order, only existing serial numbers can be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:265 +msgid "To change the ability to use new (or existing) serial numbers on any operation type, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:269 +msgid "For the :guilabel:`Receipts` operation type, found on the :guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:275 +msgid "For the :guilabel:`Delivery Orders` operation type, located on the :guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Be sure to click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "Enabled traceability setting in operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:286 +msgid "Serial number traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:288 +msgid "Manufacturers and companies can refer to the traceability reports to see the entire lifecycle of a product: where it came from (and when), where it was stored, and who it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:291 +msgid "To see the full traceability of a product, or group by serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:295 +msgid "From here, products with serial numbers assigned to them will be listed by default, and can be expanded to show what serial numbers have been specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:298 +msgid "To group by serial numbers (or lots), first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:303 +msgid "Doing so reveals all existing serial numbers and lots, and can be expanded to show all quantities of products with that assigned number. For unique serial numbers that are not reused, there should be just one product per serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "Serial numbers reporting page with drop-down lists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:312 +msgid "For additional information regarding an individual serial number (or lot number), click the line item for the serial number to reveal that specific serial number's :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number, and any operations made using that serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving.rst:5 +msgid "Shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse.rst:5 +msgid "Advanced operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:8 +msgid "Odoo can handle various delivery methods, including third party shippers. Odoo will be linked with the transportation company tracking system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:12 +msgid "It will allow you to manage the transport company, the real prices and the destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:15 +msgid "You can easily cancel the request made to the carrier system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:18 +msgid "How to cancel a shipping request?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:20 +msgid "If the delivery order is not **Validated**, then the request hasn't been made. You can choose to cancel the delivery or to change the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:24 +msgid "If you have clicked on **Validate**, the request has been made and you should have received the tracking number and the label. You can still cancel the request. Simply click on the **Cancel** button next to the **Carrier Tracking Ref**:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:32 +msgid "You will now see that the shipment has been cancelled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:37 +msgid "You can now change the carrier if you wish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:40 +msgid "How to send a shipping request after cancelling one?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:42 +msgid "After cancelling the shipping request, you can change the carrier you want to use. Confirm it by clicking on the **Send to shipper** button. You will get a new tracking number and a new label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:115 +msgid ":doc:`invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:116 +msgid ":doc:`multipack`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:3 +msgid "Use dropshipping to ship directly from suppliers to customers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:5 +msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:12 +msgid "Configure products to be dropshipped" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:14 +msgid "To use dropshipping as a fulfillment strategy, navigate to the :menuselection:`Purchase` app and select :menuselection:`Configuration --> Settings`. Under the :guilabel:`Logistics` heading, click the :guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:18 +msgid "Next, go to the :menuselection:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the :guilabel:`Product` page, make sure that the :guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 +msgid "Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:27 +msgid "Click on the :guilabel:`Purchase` tab and specify a vendor and the price that they sell the product for. Multiple vendors can be added, but the vendor at the top of the list will be the one automatically selected for purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 +msgid "The product form with a vendor specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:35 +msgid "Finally, select the :guilabel:`Inventory` tab and enable the :guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 +msgid "Enable the Dropship option in the product inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:43 +msgid "Fulfill orders using dropshipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:45 +msgid "When a customer completes an online purchase for a dropshipped product, a sales order will be automatically created with an associated request for quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:52 +msgid "Dropship sales orders can also be created manually through the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for dropshipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 +msgid "A dropship sales order with the Purchase smart button in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:60 +msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Receipt` smart button in the top right corner of the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 +msgid "A dropship purchase order with the Receipt smart button in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:68 +msgid "The dropship receipt will list the supplier in the :guilabel:`Receive From` section and the customer in the :guilabel:`Destination Location` section. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top left of the dropship receipt to confirm the delivered quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 +msgid "Validate the dropship receipt after delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:77 +msgid "To view all dropship orders, simply navigate to the :menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 +msgid "Click the green button on the Dropship card to view all dropship orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:3 +msgid "How to invoice the shipping cost to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:10 +msgid "There are two ways to invoice the shipping costs:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:12 +msgid "Agree with the customer over a cost and seal it down in the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:15 +msgid "Invoice the real cost of the shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:20 +msgid "To configure the price of your delivery methods, go to the **Inventory** app, click on :menuselection:`Configuration --> Delivery --> Delivery Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:23 +msgid "You can manually set a price for the shipping: It can be fixed or based on rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:26 +msgid "Or you can use the transportation company computation system by :doc:`integrating a third-party shipper <../setup_configuration/third_party_shipper>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:30 +msgid "How to invoice the shipping costs to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:33 +msgid "Invoice the price set on the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:57 +msgid "On your sale order, choose the carrier that will be used. Click on **Delivery Method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:41 +msgid "The price is computed when you **save** the sale order or when you click on **Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:44 +msgid "To invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:48 +msgid "When you create the invoice, it will take the price set on the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:55 +msgid "Invoice the real shipping costs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:63 +msgid "The price is computed when you **save** the sale order. Confirm the sale order and proceed to deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:66 +msgid "The real shipping cost is computed when the delivery order is validated, you can see the real cost in the chatter of the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:72 +msgid "Go back to the sale order, the real cost is now added to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:78 +msgid "When you create the invoice, it will take the price computed by the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:85 +msgid "If you split the delivery and make several ones, each delivery order will add a line to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:89 +msgid ":doc:`../setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:90 +msgid ":doc:`labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:3 +msgid "Change shipping label size" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:8 +msgid "In Odoo, there are a variety of different types of shipping labels that can be selected for delivery orders. Depending on the types of shipping packages used, different label sizes may be more appropriate, and can be configured to fit the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:15 +msgid "In the :menuselection:`Inventory` module, go to :menuselection:`Configuration --> Delivery --> Shipping Methods.` Click on a delivery method to choose it. For the following example, *FedEx International* will be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 +msgid "Different shipping methods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:23 +msgid "In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose one of the label types available. The availability varies depending on the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 +msgid "Select a label type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:30 +msgid "When a sales order with the corresponding shipping company is confirmed and a delivery order is validated, the shipping label will be automatically created as a PDF and appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 msgid "Create a sales order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:37 +msgid "In the :menuselection:`Sales` application, click :guilabel:`Create` and select an international customer. Click :guilabel:`Add A Product` and select an item. Click :guilabel:`Add Shipping`, select a shipping method, then click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 +msgid "Add a shipping method and rate to a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:45 +msgid "Once the quotation is confirmed by clicking :guilabel:`Confirm`, a :guilabel:`Delivery` smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 +msgid "Delivery order smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:52 +msgid "Once the delivery order is validated by clicking :guilabel:`Validate` in the delivery order, the shipping documents appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 +msgid "Shipping PDF documents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:60 +msgid "Example labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:62 +msgid "The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example of a FedEx letter sized label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 +msgid "Full page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:69 +msgid "For comparison, an example of a FedEx bottom-half label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 +msgid "Half page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:85 +msgid "How to print shipping labels?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:8 +msgid "Odoo can handle various delivery methods, including third party shippers linked with the transportation company tracking system. It allows you to manage the transport company, the real prices and the destination. And finally, you will be able to print the shipping labels directly from Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:19 +msgid "Install the shipper company connector module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:20 +msgid "In the **Inventory** module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:28 +msgid "Then click on **Apply**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:35 +msgid "Configure the delivery method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:37 +msgid "To configure your delivery methods, go to the **Inventory** module, click on :menuselection:`Configuration --> Delivery Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:35 +msgid "The delivery methods for the chosen shippers have been automatically created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:41 +msgid "In the **Pricing** tab, the name of the provider means that the delivery will be handled and computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:44 +msgid "The configuration of the shipper is split into two columns :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:46 +msgid "The first one is linked to **your account** (develop key, password,...). For more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:64 +msgid "The second column varies according to the **provider**. You can choose the packaging type, the service type, the weight unit..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:67 +msgid "Uncheck **Test Mode** when you are done with the testings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:79 +msgid "Company configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:81 +msgid "In order to compute the right price, the provider needs your company information. Be sure your address and phone number are correctly encoded." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:88 +msgid "To check your information, go to the **Settings** application and click on **General Settings**. Click on the first link **Configure your company data**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:92 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:94 +msgid "The shipper companies need the weight of your product, otherwise the price computation cannot be done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:73 +msgid "Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open the products you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:80 +msgid "The weight on the product form is expressed in kilograms. Don't forget to do the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:87 +msgid "The delivery order created from the sale order will take the shipping information from it, but you can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:137 +msgid "If you create a delivery transfer from the inventory module, you can add the third party shipper in the additional info tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:96 +msgid "Click on **Validate** to receive the tracking number and **the label(s)**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:153 +msgid "The label to stick on your package is available in the history underneath :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:104 +msgid "Click on it to open the document and print it :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:110 +msgid "If you are doing multi-packages shippings, most of the time, there will be one label per package. Each label will appear in the delivery history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:3 +msgid "Multi-package shipments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:5 +msgid "In some cases, a delivery order with multiple items may need to be shipped in more than one package. This may be necessary if the items are too large to ship in a single package, or if certain items cannot be packaged together. Shipping a single delivery order in multiple packages provides flexibility for how each item is packaged, without the need to create multiple delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:13 +msgid "In order to split a delivery order across multiple packages, the *Packages* setting must be enabled. To do so, navigate to :menuselection:`Inventory --> Configuration --> Settings`, then enable the checkbox next to :guilabel:`Packages`. Click :guilabel:`Save` to confirm the change." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 +msgid "The Packages setting on the Inventory app settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:24 +msgid "Ship items in multiple packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:26 +msgid "To split items in the same delivery order across multiple packages, begin by navigating to :menuselection:`Inventory --> Delivery Orders`, then select a delivery order that has multiple items, a multiple quantity of the same item, or both." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:30 +msgid "On the :guilabel:`Operations` tab, select the :guilabel:`āžā‰£ (menu)` icon in the line of the product that will be shipped in the first package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 +msgid "The menu icon for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:37 +msgid "This makes a :guilabel:`Detailed Operations` pop-up window appear. In the table at the bottom of the pop-up window, the :guilabel:`Reserved` column shows the total quantity of the product included in the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:41 +msgid "If the full quantity will be shipped in the first package, enter the number from the :guilabel:`Done` column in the :guilabel:`Reserved` column. If less than the full quantity will be shipped in the first package, enter a smaller number than the one that appears in the :guilabel:`Reserved` column. Click :guilabel:`Confirm` to confirm the :guilabel:`Done` quantities and close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 +msgid "The Detailed Operations pop-up for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:51 +msgid "Repeat the same steps for every item quantity that is included in the first package. Then, click :guilabel:`Put In Pack` to create a package with all of the selected items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 +msgid "The Put In Pack button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:58 +msgid "For the next package, follow the same steps as detailed above, marking the quantity of each item to be included in the package as :guilabel:`Done` before clicking :guilabel:`Put In Pack` on the delivery order. Continue doing so until the full quantity of all items are added to a package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:62 +msgid "Finally, after all of the packages have been shipped, click :guilabel:`Validate` to confirm that the delivery order has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:66 +msgid "After one or more packages are created, a :guilabel:`Packages` smart button appears in the top-right corner of the delivery order. Click the :guilabel:`Packages` smart button to go to the :guilabel:`Packages` page for the delivery order, where each package can be selected to view all of the items included in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:0 +msgid "The Packages smart button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:76 +msgid "Create a backorder for items to be shipped later" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:78 +msgid "If some items will be shipped at a later date than others, there is no need to put them in a package until they are ready to be shipped. Instead, create a backorder for the items being shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:81 +msgid "Begin by shipping the items that will be shipped immediately. If they will be shipped in multiple packages, follow the :ref:`steps above ` to package them as required. If they will be shipped in a single package, simply mark in the :guilabel:`Done` column the quantity of each item being shipped, but **do not** click the :guilabel:`Put In Pack` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:86 +msgid "After all quantities being shipped immediately are marked as :guilabel:`Done`, click the :guilabel:`Validate` button, and a :guilabel:`Create Backorder?` pop-up window appears. Then, click the :guilabel:`Create Backorder` button. Doing so confirms the items being shipped immediately and creates a new delivery order for the items that will be shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 +msgid "The Create Backorder? pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:95 +msgid "The backorder delivery order will be listed in the chatter of the original delivery order in a message that reads :guilabel:`The backorder WH/OUT/XXXXX has been created.`. Click on :guilabel:`WH/OUT/XXXXX` in the message to view the backorder delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 +msgid "The backorder delivery order listed in the chatter of the original delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:103 +msgid "The backorder delivery order can also be accessed by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# Back Orders` button on the :guilabel:`Delivery Orders` card, and selecting the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 +msgid "The Back Orders button on the Delivery Orders card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:111 +msgid "Once the remaining items are ready to be shipped, navigate to the backorder delivery order. The items can be shipped in a single package by clicking :guilabel:`Validate` and selecting :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears, or shipped in multiple packages by following the steps detailed in the section above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:116 +msgid "It is also possible to ship out some of the items while creating another backorder for the rest. To do so, simply follow the same steps used to create the first backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:3 +msgid "Scheduled delivery dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:5 +msgid "Accurately forecasting delivery dates is vital for fulfilling customer expectations. In Odoo, the *Inventory* app allows for comprehensive lead time configuration, allowing coordination and planning of manufacturing orders, deliveries, and receptions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:10 +msgid "Lead time types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:12 +msgid "Different lead times for different operations can impact various stages of the order fulfillment process. Here's a summary of the types of lead times in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "Show graphic of all lead times working together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:19 +msgid ":ref:`Customer lead time `: The default time frame for fulfilling customer orders. The customer lead time is the number of days from the date the sales order (SO) is confirmed to the date the products are shipped from the warehouse. This is also known as *delivery lead time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:24 +msgid ":ref:`Sales security lead time `: moves the *scheduled delivery date* forward by a specified number of days. This serves as a buffer to allow the team ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:29 +msgid ":ref:`Purchase lead time `: the number of days from the confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time it takes for products to arrive at the warehouse, facilitating effective scheduling and planning of supplier deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:34 +msgid ":ref:`Purchase security lead time `: advances the order deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive approach of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for products that are set to replenish to order, the need appears on the *Replenishment report* earlier, according to the specified number of days." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:40 +msgid ":ref:`Manufacturing lead time `: the number of days needed to complete a manufacturing order (MO) from the date of confirmation. This lead time includes weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a finished good." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:45 +msgid ":ref:`Manufacturing security lead time `: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` forward by a specified number of days. When used in conjunction with :ref:`replenish to order `, the security lead time makes the need appear earlier on the replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:53 +msgid "Sales lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:55 +msgid "Customer lead times and sales security lead times can be configured to automatically compute an *expected delivery date* on a :abbr:`SO (Sales Order)`. The expected delivery date ensures a realistic *delivery dates* setting for shipments from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:59 +msgid "Odoo issues a warning message if the set delivery date is earlier than the expected date, as it may not be feasible to fulfill the order by that time, which would impact other warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:63 +msgid "A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is confirmed on July 11th. The product has a customer lead time of 14 days, and the business uses a sales security lead time of 1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Set *Delivery Date* in a sales order. Enables delivery lead times feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:71 +msgid "The following sections demonstrate how to automatically compute expected delivery dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:74 +msgid "Customer lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:76 +msgid "Set the customer lead time on each product form, by navigating to the products page. To do so, go to :menuselection:`Sales app --> Products --> Products`. From there, select the desired product, and switch to the :guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` field, fill in the number of calendar days required to fulfill the delivery order from start to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:82 +msgid "Set a 14-day customer lead time for the `Coconut-scented candle` by navigating to its product form. Then, in the :guilabel:`Inventory` tab, type `14.00` days into the :guilabel:`Customer Lead Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Set *Customer Lead Time* on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:93 +msgid "Sales security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:95 +msgid "*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:98 +msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Sales`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:101 +msgid "Next, enter the desired number of calendar days. This security lead time is a buffer notifying the team to prepare for outgoing shipments earlier than the scheduled date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:105 +msgid "Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes the :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. In that case, if a product is initially scheduled for delivery on April 6th, but with a one-day security lead time, the new scheduled date for the delivery order would be April 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "View of the security lead time for sales configuration from the sales settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:115 +msgid "Deliver several products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:117 +msgid "For orders that include multiple products with different lead times, the lead times can be configured directly from the quotation itself. On a quotation, click the :guilabel:`Other Info` tab, and set the :guilabel:`Shipping Policy` to:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:121 +msgid ":guilabel:`As soon as possible` to deliver products as soon as they are ready. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the shortest lead time among the products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:125 +msgid ":guilabel:`When all products are ready` to wait to fulfill the entire order at once. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the longest lead time among the products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "Show *Shipping Policy* field in the *Other Info* tab of a quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:134 +msgid "In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the products have a lead time of 8 days and 5 days, respectively. Today's date is April 2nd." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:137 +msgid "When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as possible`, the scheduled delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel:`When all products are ready` configures the scheduled date to be 8 days from today: April 10th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:144 +msgid "Purchase lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:146 +msgid "Automatically determining the dates on which to place orders from suppliers can help simplify the procurement process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:149 +msgid "Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO (Purchase Order)` deadline, based on the required date the product is needed in the warehouse. By working backwards from the receipt date, vendor lead times and purchase security lead times are taken into account, in order to determine the :abbr:`PO (Purchase Order)` deadline." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:154 +msgid "This deadline is the date by which the order should be confirmed, in order to ensure timely arrival by the expected receipt date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "Visualization of PO deadline and receipt date used with vendor lead times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:162 +msgid ":ref:`PO scheduling with reordering rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:165 +msgid "Vendor lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:167 +msgid "To set a vendor lead time for orders arriving in the warehouse from a vendor location, begin by navigating to a product form through :menuselection:`Purchase app --> Products --> Products`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:170 +msgid "Next, select the desired product, and switch to the :guilabel:`Purchase` tab. In the editable vendor pricelist, click the :guilabel:`Add a line` button to add vendor details, such as the :guilabel:`Vendor` name, :guilabel:`Price` offered for the product, and lastly, the :guilabel:`Delivery Lead Time`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:176 +msgid "Multiple vendors and lead times can be added to the vendor pricelist. The default vendor and lead time selected will be the entry at the top of the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:180 +msgid "On the vendor pricelist of the product form, the :guilabel:`Delivery Lead Time` for the selected vendor is set to `10 days.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Add delivery lead times to vendor pricelist on a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:187 +msgid "By setting the vendor lead time, the expected arrival date of the item is automatically determined as the date of the :abbr:`PO (Purchase Order)` confirmation, plus the vendor lead time. This ensures that warehouse employees are notified, if the products do **not** arrive within the expected timeframe." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:193 +msgid "On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product configured with a 10-day vendor lead time, Odoo automatically sets the :guilabel:`Receipt Date` to July 21st. The receipt date also appears as the :guilabel:`Scheduled Date` on the warehouse receipt form, accessible from the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Show expected *Receipt Date* of the product from the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Show expected *Scheduled Date* of arrival of the product from the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:209 +msgid "Purchase security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:211 +msgid "*Purchase security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:214 +msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Purchase`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:217 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in supplier deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:221 +msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by one day. In that case, if a product is initially scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for the receipt would be April 8th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Set security lead time for purchase from the Inventory > Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:233 +msgid "Manufacturing lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:235 +msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:238 +msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the deadline to begin the manufacturing process to complete the product by the scheduled delivery date, can be determined by configuring the manufacturing lead times and manufacturing security lead times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "Visualization of the determination of planned MO date manufacturing lead times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:247 +msgid "Manufacturing lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:249 +msgid "Configure the manufacturing lead time directly on the product form, by navigating to :menuselection:`Manufacturing app --> Products --> Products`, and select the desired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:252 +msgid "In the :guilabel:`Inventory` tab of the product, specify the calendar days needed to the manufacture the product in the :guilabel:`Manufacturing Lead Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:256 +msgid "Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly in the :guilabel:`Inventory` tab of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "View of the manufacturing lead time configuration from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 +msgid "Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the *expected delivery date*, indicated in the :guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:266 +msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the :guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is calculated as the *expected delivery date* subtracted by the manufacturing lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:270 +msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:272 +msgid "However, it's important to note that lead times are based on calendar days. Lead times do **not** consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be performed at the work center simultaneously`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 +msgid ":ref:`Manufacturing planning `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:278 +msgid ":ref:`Configure automatic MO scheduling with reordering rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:282 +msgid "A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment date is August 1st." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:289 +msgid "Manufacturing security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:291 +msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead Time`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:295 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in the manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "View of the security lead time for manufacturing from the manufacturing app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:303 +msgid "A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` set for August 15th. The manufacturing lead time is 7 days, and manufacturing security lead time is 3 days. So, the :guilabel:`Scheduled Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to begin the manufacturing order. In this example, the planned date on the :abbr:`MO (Manufacturing Order)` is August 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:310 +msgid "Global example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:312 +msgid "See the following example to understand how all the lead times work together to ensure timely order fulfillment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:315 +msgid "**Sales security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:316 +msgid "**Manufacturing security lead time**: 2 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:317 +msgid "**Manufacturing lead time**: 3 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:318 +msgid "**Purchase security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:319 +msgid "**Vendor lead time**: 4 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:321 +msgid "The customer places an order for a manufactured product on September 1st, and the scheduled delivery date from the warehouse is on September 20th. Odoo uses lead times and automated reordering rules to schedule the necessary operations, based on the outgoing shipment delivery date, September 20th:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "Show timeline of how lead times work together to schedule warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:329 +msgid "**September 1st**: Sales order created, confirmed by salesperson." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:331 +msgid "**September 9th**: Deadline to order components to ensure they arrive in time when manufacturing begins (4-day supplier lead time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:334 +msgid "**September 13th**: Scheduled date of receipt for components. Initially, it was set to 9/14, but the 1-day purchase security lead time pushed the date earlier by 1 day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:337 +msgid "**September 14th**: Deadline to begin manufacturing. Calculated by subtracting the manufacturing lead time of 3 days, and the manufacturing security lead time of 2 days, from the expected delivery date of September 19th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:341 +msgid "**September 19th**: :guilabel:`Scheduled Date` on the delivery order form indicates the updated expected delivery date, which was originally set as September 20th. But the sales security lead time pushed the date forward by a day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:345 +msgid "Odoo's replenishment planning maps a business' order fulfillment process, setting pre-determined deadlines and raw material order dates, including buffer days for potential delays. This ensures products are delivered on time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:3 +msgid "Process deliveries in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:7 +msgid "Some companies process large amounts of deliveries every day, many of which include multiple products or require special packaging. To make this efficient, a packing step is needed before shipping out products. For this, Odoo has a three step process for delivering goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:11 +msgid "In the default three-step delivery process, products that are part of a delivery order are picked in the warehouse according to their removal strategy, and brought to a packing zone. After the items have been packed into the different shipments in the packing zone, they are brought to an output location before being shipped. These steps can be modified if they do not fit the needs of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:20 +msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three step deliveries. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 +msgid "Activate multi-step routes and storage locations in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:30 +msgid "Next, the warehouse needs to be configured for three step deliveries. To do this, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the :guilabel:`Warehouse`. Then, select :guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for :guilabel:`Outgoing Shipments`. Then :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 +msgid "Set outgoing shipment option to deliver in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:39 +msgid "Activating three-step receipts and deliveries will create two new internal locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:45 +msgid "Process a delivery order in three steps (pick + pack + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:50 msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Customer`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:53 msgid "A :guilabel:`Delivery` smart button will appear in the top right. Clicking on it will show the picking order, packing order, and the delivery order, which are all associated with the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 msgid "After confirming the sales order, the Delivery smart button appears showing three items\n" "associated with it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:62 msgid "Process a picking" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:64 msgid "The picking, packing, and delivery orders will be created once the sales order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 msgid "Ready status for the pick operation while the packing and delivery operations are waiting\n" "another operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:72 msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be packed. The status of the packing order and delivery order will both be :guilabel:`Waiting Another Operation`, since the packing and delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` when the packing has been marked :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:78 msgid "The receipt can also be found in the *Inventory* application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Pick` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 msgid "The pick order can be seen in the Inventory Kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:85 msgid "Click on the picking to process. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as done, and complete the transfer to the :guilabel:`Packing Zone`. Then the packing order will be ready. Since the documents are linked, the products which have been previously picked are automatically reserved on the packing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Validate the picking by clicking Validate." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:95 msgid "Process a packing" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:97 msgid "The packing order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Pack` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 msgid "The packing order can be seen in the Inventory kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:105 msgid "Click on the packing order associated with the sales order, then click on :guilabel:`Validate` to complete the packing." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 msgid "Click Validate on the packing order to transfer the product from the packing zone to the\n" "output location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:113 msgid "Once the packing order is validated, the product leaves the :guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:118 msgid "Process a delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:120 msgid "The delivery order will be ready to be processed once the packing is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Delivery Orders` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 msgid "The delivery order can be seen in the Delivery Orders Kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:128 msgid "Click on the delivery order associated with the sales order, then click on :guilabel:`Validate` to complete the move." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Click Validate on the delivery order to transfer the product from the output location to\n" "the customer location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:136 msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:3 msgid "Process receipts and deliveries in one step" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:7 msgid "By default, incoming shipments are configured to be received directly into stock, and outgoing shipments are configured to be delivered directly from stock to the customer; the default setting for warehouses in Odoo is one step receipts and deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:12 msgid "Incoming and outgoing shipments do not need to be configured with the same steps. For example, products can be received in one step, but shipped in three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:15 msgid "In the following example, one step will be used for both receipts and deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:18 msgid "Configure the warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:20 msgid "If another receiving or shipping configuration is set on the warehouse, they can easily be set back to the one step setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:23 msgid "Begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, and click on the desired warehouse to edit. Next, on the :guilabel:`Warehouse Configuration` tab, under the :guilabel:`Shipments` section, select :guilabel:`Receive goods directly (1 step)` for :guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 step)` for :guilabel:`Outgoing Shipments`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 msgid "Set incoming and outgoing shipment options to receive and deliver in one step." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:34 msgid "Receive goods directly (1 step)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:37 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:46 msgid "Create a purchase order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:39 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:71 msgid "On the main :menuselection:`Purchase` application dashboard, start by making a new quote by clicking :guilabel:`New`. Then, select (or create) a :guilabel:`Vendor` from the drop-down field, add a storable :guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` to finalize the quote as a new purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:44 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:96 msgid "A :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (purchase order)` form ā€” click it to reveal the associated receipt for the purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 msgid "Receipt smart button appears on the confirmed purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:52 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 msgid "Purchase order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Receipts` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 msgid "Receipt kanban card's 1 to Process smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:61 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:100 -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 msgid "Process the receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 msgid "When viewing the receipt (associated with the purchase order above), click :guilabel:`Validate` to then complete the receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 msgid "Validate the purchase order via the Validate smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:71 msgid "If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`ā‰£ (bullet list)` details icon next to the :guilabel:`šŸ—‘ļø (trash)` delete icon enables the :guilabel:`Detailed Operations` screen to pop-up. This allows the location(s) to be specified for the received product(s)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 msgid "Select the Storage Location for the products being received in the Detailed Operations\n" "pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:80 msgid "Once the receipt is validated, the product leaves the :guilabel:`Supplier Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives here, it will be available for manufacturing, sales, etc. Then, the status of the document will change to :guilabel:`Done`, thus completing the reception process in one step." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:86 msgid "Deliver goods directly (1 step)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:91 msgid "Start my navigating to the main :menuselection:`Sales` app dashboard, and make a new quote by clicking :guilabel:`New`. Then select (or create) a :guilabel:`Customer` from the drop-down field, add a storable :guilabel:`Product` that is in stock to the order lines, and click :guilabel:`Confirm` to finalize the quotation as a sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:99 msgid "A :guilabel:`Delivery` smart button will appear in the top-right corner of the :abbr:`SO (Sales Order)` form ā€” click it to reveal the associated delivery order for the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 msgid "The Delivery smart button appears after the sales order is confirmed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:107 msgid "Delivery orders can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Delivery Orders` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 msgid "Delivery Orders kanban card's 1 to Process smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:116 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:194 msgid "Process the delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:118 msgid "When viewing the delivery order (associated with the sales order above), click :guilabel:`Validate` to then complete the delivery." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 msgid "Validate the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:125 msgid "Once the picking order is validated, the product leaves the :guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers location`. Then, the status of the document will change to :guilabel:`Done`, thus completing delivery in one step." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:3 msgid "Process receipts and deliveries in two steps" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:7 msgid "Depending on a company's business processes, multiple steps may be needed before receiving or shipping products. In the two-step receipt process, products are received in an input area, then transferred to stock. Two-step receipts work best when various storage locations are being used, such as locked or secured areas, freezers and refrigerators, or various shelves." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:12 msgid "Products can be sorted according to where they are going to be stored, and employees can stock all the products going to a specific location. The products are not available for further processing until they are transferred into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:16 msgid "In the two-step delivery process, products that are part of a delivery order are picked from the warehouse according to their removal strategy, and brought to an output location before being shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:20 msgid "One situation where this would be useful is when using either a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy, where the products that are being picked need to be selected based on their receipt date or expiration date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:25 msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize two-step receipts and deliveries. Incoming and outgoing shipments do not need to be set to have the same steps. For example, products can be received in two steps, but shipped in one step. In the following example, two steps will be used for both receipts and deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:32 msgid "Configure multi-step routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:34 msgid "First, make sure the :guilabel:`Multi-Step Routes` option is enabled in :menuselection:`Inventory --> Configuration --> Settings`, under the :guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:39 msgid "Activating the :guilabel:`Multi-Step Routes` setting will also activate the :guilabel:`Storage Locations` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:46 msgid "Next, the warehouse needs to be configured for two-step receipts and deliveries. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click on the warehouse to change the warehouse settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:50 msgid "Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and then deliver (2 steps)` for :guilabel:`Outgoing Shipments`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Set incoming and outgoing shipment options to receive and deliver in two steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:59 msgid "Activating two-step receipts and deliveries will create new *input* and *output* locations, which by default, are labeled :guilabel:`WH/Input` and :guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard. To rename these locations, go to :menuselection:`Configuration --> Locations`, and select the :guilabel:`Location` to change. On the location form, update the :guilabel:`Location Name`, and make any other changes (if necessary)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:66 msgid "Process a receipt in two steps (input + stock)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77 msgid "For businesses with multiple warehouses that have different step configurations, the :guilabel:`Deliver To` field on the :abbr:`PO (Purchase Order)` form may need to be specified as the correct *input location* connected to the two-step warehouse, which can be done by selecting the warehouse from the drop-down selection that includes the `Receipts` label at the end of the name." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:83 msgid "After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button will appear in the top of the :abbr:`PO (Purchase Order)` form ā€” click it to reveal the associated receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "After confirming a purchase order, a Receipt smart button will appear." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 msgid "One receipt ready to process in the Inventory Overview kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:102 msgid "The receipt and internal transfer will be created once the purchase order is confirmed. The status of the receipt will be :guilabel:`Ready`, since the receipt must be processed first. The status of the internal transfer will be :guilabel:`Waiting Another Operation`, since the transfer cannot happen until the receipt is completed. The status of the internal transfer will only change to :guilabel:`Ready` once the receipt has been marked as :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 msgid "Click on the :guilabel:`Receipt` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Validate the receipt by clicking Validate, then the product will be transferred to the\n" "WH/Input location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:117 msgid "Process the internal transfer" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:119 msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product into stock. Navigate to the :menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Internal Transfers` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "One Internal Transfer ready to process in the Inventory Overview kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Validate the internal transfer to move the item to stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:138 msgid "Process a delivery order in two steps (pick + ship)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:143 msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`New`. Select (or create) a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:147 msgid "After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart button will appear in the top, above the :abbr:`SO (Sales Order)` form. Click the :guilabel:`Delivery` smart button to reveal the associated receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "After confirming the sales order, the Delivery smart button appears showing two items\n" "associated with it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:157 msgid "Sales order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Pick` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 msgid "The pick order can be seen in the Inventory kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:166 msgid "Process the picking" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:168 msgid "The picking and delivery order will be created once the sales order is confirmed. When the :guilabel:`Delivery` smart button appears, click it to reveal the :guilabel:`Transfers` dashboard, which lists both the picking and the delivery orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:172 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be shipped. The status of the delivery order will be :guilabel:`Waiting Another Operation`, since the delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` once the picking has been marked as :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Ready status for the pick operation while the delivery operation is Waiting Another\n" "Operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:183 msgid "Click on the picking delivery order to begin processing it. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the delivery order will be ready for processing. Since the documents are linked, the products which have been previously picked are automatically reserved on the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:196 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:196 msgid "The delivery order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application, on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To Process` smart button in the :guilabel:`Delivery Orders` kanban card to begin." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:201 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:201 msgid "The delivery order associated with the :abbr:`SO (Sales Order)` can also be quickly accessed by clicking on the :guilabel:`Delivery` smart button again, and choosing the delivery order on the :guilabel:`Transfers` page (which should now be marked as :guilabel:`Ready`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "The delivery order can be seen in the Inventory Kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:209 msgid "Click on the delivery order associated with the :abbr:`SO (Sales Order)`, then click on :guilabel:`Validate` to complete the move." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:217 msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:3 msgid "Process receipts in three steps" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:7 msgid "Some companies require a quality control process before receiving goods from suppliers. To accomplish this, Odoo has a three-step process for receiving goods." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:10 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:10 msgid "In the three-step receipt process, products are received in an input area, then transferred to a quality area for inspection. Products that pass the quality inspection are then transferred into stock. The products are not available for further processing until they are transferred out of the quality area and into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:18 msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three-step receipts. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "Activate multi-step routes and storage locations in Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:28 msgid "Next, the warehouse needs to be configured for three-step receipts. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the warehouse. Then, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`. Then, :guilabel:`Save` the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "Set incoming shipment option to receive in three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:37 msgid "Activating three-step receipts and deliveries will create two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:43 msgid "Process a receipt in three steps (input + quality + stock)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 msgid "In the :menuselection:`Purchase` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:52 msgid "A :guilabel:`Receipt` smart button will appear in the top right, and the receipt will be associated with the purchase order. Clicking on the :guilabel:`Receipt` smart button will show the receipt order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:61 msgid "Process a receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 msgid "One receipt and two internal transfers (one transfer to quality, and a subsequent transfer to stock) will be created once the purchase order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "The status of the three receipt transfers will show which operation is ready and which ones\n" "are waiting another operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:72 msgid "The status of the receipt transferring the product to the input location will be :guilabel:`Ready`, since the receipt must be processed before any other operation can occur. The status of the two internal transfers will be :guilabel:`Waiting Another Operation`, since the transfers cannot be processed until the linked step before each transfer is completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:77 msgid "The status of the first internal transfer to *quality* will only change to :guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The status for the second internal transfer to *stock* will be marked :guilabel:`Ready` only after the transfer to quality has been marked :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:82 msgid "The receipt can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Receipts` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "One Receipt ready to process in the Inventory Overview kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:90 msgid "Click on the receipt associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "Validate the receipt by clicking Validate, and the product will be transferred to the\n" "WH/Quality location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:99 msgid "Process a transfer to Quality Control" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product to :guilabel:`Quality Control`. In the :menuselection:`Inventory` :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:110 msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to the :guilabel:`Quality Control` location. Once the transfer is validated, the product is ready for the quality inspection, but is not available for manufacturing or delivery orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "Validate the internal transfer to move the item to the Quality Control location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:120 msgid "Process a transfer to stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 msgid "Once the product is in the :guilabel:`Quality Control` location, the final internal transfer is ready to move the product to :guilabel:`Stock`. In the :guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` Kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:126 msgid "Click on the final :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses.rst:5 -msgid "Warehouses" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:3 +msgid "Incoming shipments and delivery orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:3 -msgid "Create a second warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:5 +msgid "There are several ways to handle how a warehouse receives products (receipts) and ships products (deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse size, and the amount of daily confirmed receipts and delivery orders, the way products are handled when coming in and out of the warehouse can vary a lot. Different settings can be configured for receipts and deliveries; they do not have to be configured to have the same number of steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:5 -msgid "A *warehouse* is a physical building or space where items are stored. In Odoo, it is possible to set up multiple warehouses and transfer stored items between them." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:12 +msgid "`Using Routes (eLearning Tutorial) `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:8 -msgid "By default, the Odoo platform has one warehouse that is already configured, with the address set as the company's address. To create a second warehouse, select :menuselection:`Configuration --> Warehouses`, then click :guilabel:`Create` and configure the form as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:13 +msgid "`Push & Pull Rules (eLearning Tutorial) `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:12 -msgid ":guilabel:`Warehouse`: the full name of the warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:17 +msgid "Choosing the right inventory flow to handle receipts and deliveries" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:13 -msgid ":guilabel:`Short Name`: the abbreviated code by which the warehouse is referred to; the short name for the default warehouse in Odoo is **WH**" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:19 +msgid "By default, Odoo handles shipping and receiving in three different ways: in one, two, or three steps. The simplest configuration is one step, which is the default. Each additional step required for a warehouse for either the receiving or shipping process will add an additional layer of operations to perform before a product is either received or shipped. These configurations depend entirely on the requirements for the products stored, such as performing quality checks on received products, or using special packaging on shipped products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:15 -msgid ":guilabel:`Company`: the company that owns the warehouse; this can be set as the company that owns the Odoo database or the company of a customer or vendor" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:27 +msgid "One-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:17 -msgid ":guilabel:`Address`: the address where the warehouse is located" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:29 +msgid "The receiving and shipping rules for a one-step configuration are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:20 -msgid "The options below will only appear if the :guilabel:`Multi-Step Routes` checkbox is enabled in :menuselection:`Configuration --> Settings` under the :guilabel:`Warehouse` heading. For more information about routes and how they work in Odoo, see :ref:`Using Routes and Pull/Push Rules `." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:31 +msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:25 -msgid ":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and outgoing shipments should follow" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:33 +msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:27 -msgid ":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied from this warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:35 +msgid "Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:28 -msgid ":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in this warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:37 +msgid "Receipts and/or deliveries are handled quickly." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:29 -msgid ":guilabel:`Manufacture`: select the route that should be followed when manufacturing goods inside the warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:38 +msgid "Recommended for small warehouses with low stock levels, and for non-perishable items." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:31 -msgid ":guilabel:`Buy to Resupply`: check the box to allow for purchased products to be delivered to the warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:39 +msgid "Items are received or shipped directly into/from stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:33 -msgid ":guilabel:`Resupply From`: select warehouses that can be used to resupply the warehouse being created" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:42 +msgid ":ref:`Process receipts and deliveries in one step `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:-1 -msgid "A filled out form for creating a new warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:45 +msgid "Two-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:41 -msgid "Creating a second warehouse will automatically enable the *Storage Locations* setting, which allows location tracking of products within a warehouse. To toggle this setting, navigate to :menuselection:`Configuration --> Settings` and click the checkbox under the :guilabel:`Warehouse` heading." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:47 +msgid "The receiving and shipping rules for a two-step configuration are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:46 -msgid "After filling out the form, click :guilabel:`Save` and the new warehouse will be created." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:49 +msgid "**Input + stock**: Bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:49 -msgid "Add inventory to a new warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:52 +msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:51 -msgid "If a new warehouse is created that has existing inventory in it, the inventory counts should be added to Odoo so that the stock listed in the Odoo database reflects what is in the physical warehouse. To add inventory to a new warehouse, navigate to :menuselection:`Inventory --> Operations --> Inventory Adjustments`, and then click :guilabel:`Create`. The inventory adjustment form can then be filled out as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:54 +msgid "Minimum requirement to use lot numbers or serial numbers to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or :abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:57 -msgid ":guilabel:`Inventory Reference`: the name or code that the inventory adjustment can be referred to by" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:57 +msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:59 -msgid ":guilabel:`Locations`: the location(s) where the inventory is stored; include the new warehouse and any locations within it that inventory will be added to" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 +msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:61 -msgid ":guilabel:`Products`: include all products that will be added to inventory or leave blank to select any product during the next step" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:63 +msgid ":ref:`Process receipts and deliveries in two steps `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:63 -msgid ":guilabel:`Include Exhausted Products`: include products with a quantity of zero; does not affect inventory adjustments for new warehouses since they have no existing inventory" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:66 +msgid "Three-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:65 -msgid ":guilabel:`Accounting Date`: the date used by accounting teams for bookkeeping related to the inventory" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:68 +msgid "The receiving and shipping rules for a three-step configuration are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:67 -msgid ":guilabel:`Company`: the company that owns the inventory; can be set as the user's company or as a customer or vendor" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:70 +msgid "**Input + quality + stock**: Receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:69 -msgid ":guilabel:`Counted Quantities`: choose whether the counted quantities for products being added should default to stock on hand or zero; does not affect inventory adjustments for new warehouses since they have no existing inventory" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:72 +msgid "**Pick + pack + ship**: Pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:-1 -msgid "A filled out form for an inventory adjustment." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:74 +msgid "Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:77 -msgid "Once the form is properly configured, click on :guilabel:`Start Inventory` to be taken to the next page where products can be added to the inventory adjustment. Add a new product by clicking on :guilabel:`Create` and then fill out the product line as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:77 +msgid "Recommended for very large warehouses with very high stock levels." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:81 -msgid ":guilabel:`Product`: the product being added to inventory" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:78 +msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:82 -msgid ":guilabel:`Location`: the location where the product is currently stored in the new warehouse; this can be set as the overall warehouse or a location within the warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:84 +msgid ":ref:`Process receipts in three steps `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:84 -msgid ":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the serial number used to identify it" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:85 +msgid ":ref:`Process deliveries in three steps `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:86 -msgid ":guilabel:`On Hand`: the total quantity of the product stored in the location for which inventory is being adjusted; this should be zero for a new location or warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:5 +msgid "Setup and configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:88 -msgid ":guilabel:`Counted`: the amount of the product that is being added to inventory" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:3 +msgid "Delivery methods" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:89 -msgid ":guilabel:`Difference`: the difference between the *On Hand* and *Counted* values; this will automatically update to reflect the value entered in the :guilabel:`Counted` column" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:5 +msgid "When activated in Odoo, the *Delivery Methods* setting adds the option of calculating the cost of shipping on sales orders and e-commerce shopping carts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:91 -msgid ":guilabel:`UoM`: the unit of measure used for counting the product" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:8 +msgid "When integrated with a :ref:`third-party carrier `, shipping prices are calculated based on the carrier's pricing and packaging information." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:-1 -msgid "Include a line for each product being added to inventory." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:12 +msgid ":ref:`Third-party shipping carrier setup `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:97 -msgid "After adding all the products already stored in the new warehouse, click :guilabel:`Validate Inventory` to complete the inventory adjustment. The values in the :guilabel:`On Hand` column will update to reflect those in the :guilabel:`Counted` column and the products added will appear in the inventory of the new warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:13 +msgid "`Odoo Tutorials: Delivery Prices `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:3 -msgid "Resupply from another warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:19 +msgid "To calculate shipping on sales orders and e-commerce, the *Delivery Costs* module must be installed. To do so, navigate to the :menuselection:`Apps` application from the main Odoo dashboard." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:22 +msgid "Then, remove the :guilabel:`Apps` filter, and type in `Delivery Costs` in the :guilabel:`Search...` bar. After finding the :guilabel:`Delivery Costs` module, click :guilabel:`Activate` to install it." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:-1 +msgid "Install the *Delivery Costs* module." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:-1 -msgid "Enable Multi-Step Routes in Inventory settings." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 +msgid "Add shipping method" msgstr "" -#: ../../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`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:32 +msgid "To configure delivery methods, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:36 +msgid "If the :guilabel:`Shipping Methods` option is not available from the :guilabel:`Configuration` drop-down menu, verify whether the feature is enabled by following these steps:" msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:39 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:-1 -msgid "Supply one warehouse with another in the Warehouse Configuration tab." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:40 +msgid "Scroll to the :guilabel:`Shipping` section and enable the :guilabel:`Delivery Methods` feature by checking the corresponding checkbox." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:39 -msgid "Set route on a product" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Enable the *Delivery Methods* feature by checking the box in Configuration > Settings." 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:47 +msgid "On the :guilabel:`Shipping Methods` page, add a method by clicking :guilabel:`New`. Doing so opens a form to provide details about the shipping provider, including:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:-1 -msgid "Route setting which enables a product to resupplied from a second warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:50 +msgid ":guilabel:`Shipping Method` (*Required field*): the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:52 +msgid ":guilabel:`Provider` (*Required field*): choose the delivery service, like Fedex, if using a :ref:`third-party carrier `. Ensure the integration with the shipping carrier is properly installed and select the provider from the drop-down menu." 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:56 +msgid "For more details on configuring custom shipping methods, such as :ref:`fixed price `, :ref:`based on rules `, or :ref:`pickup in store ` options, refer to their respective sections below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:-1 -msgid "A reordering rule automatically creates two receipts for stock between warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 +msgid ":guilabel:`Website`: configure shipping methods for an e-commerce page. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:-1 -msgid "A warehouse order for resupplying one warehouse's stock with another." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 +msgid ":guilabel:`Company`: if the shipping method should apply to a specific company, select it from the drop-down menu. Leave the field blank to apply the method to all companies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:-1 -msgid "A receipt for stock received to one warehouse from another." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:63 +msgid ":guilabel:`Delivery Product` (*Required field*): the product listed on the :ref:`sales order line ` as the delivery charge." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:3 -msgid "Transfer products between warehouses using replenishment" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:65 +msgid ":guilabel:`Free if order amount is above`: checking this box enables free shipping if the customer spends above the specified amount." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:5 -msgid "For companies that use multiple warehouses, it is often necessary to transfer items between them. This is referred to as an *inter-warehouse transfer*. Odoo *Inventory* handles the administrative process of inter-warehouse transfers to ensure that inventory counts remain accurate during and after the transfer. This document will detail the method for conducting an inter-warehouse transfer using replenishment." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 +msgid "For examples on how to configure specific shipping methods, refer to the sections below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:12 -msgid "Configure warehouses for inter-warehouse replenishment" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:73 +msgid "Fixed price" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:14 -msgid "First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by navigating to :menuselection:`Inventory --> Configuration --> Settings`, and then check the box under the :guilabel:`Warehouse` tab. This will provide additional configuration options when creating a second warehouse that are needed for inter-warehouse replenishment." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:75 +msgid "To configure a shipping price that is the same for all orders, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`. Then, click :guilabel:`New`, and on the shipping method form, set the :guilabel:`Provider` to the :guilabel:`Fixed Price` option. Selecting this option makes the :guilabel:`Fixed Price` field become available, which is where the fixed rate shipping amount is defined." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:19 -msgid "By default, Odoo comes with a main warehouse already configured. If an additional warehouse has not already been created, do so now from the :guilabel:`Inventory` module by selecting :menuselection:`Configuration --> Warehouses --> Create`. Otherwise, select the warehouse that products will be transferred to from the :guilabel:`Warehouses` page and then click :guilabel:`Edit` to change its settings. Configure the warehouse as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:81 +msgid "To enable free shipping if the amount of the order exceeds a specified amount, check the box :guilabel:`Free if order amount is above` and fill in the amount." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:25 -msgid ":guilabel:`Warehouse`: choose a name that is not already being used for another warehouse (e.g. `Alternative Warehouse`)" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:85 +msgid "To set up `$20` flat-rate shipping that becomes free if the customer spends over `$100`, fill in the following fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:27 -msgid ":guilabel:`Short Name`: choose a short name by which the warehouse will be identified (e.g. `ALT_WH`)" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:88 +msgid ":guilabel:`Shipping Method`: `Flat-rate shipping`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:30 -msgid "Click :guilabel:`Save` and the new warehouse will be created. In addition, a new :guilabel:`Resupply From` field will appear on the warehouse's form. Click :guilabel:`Edit` and then check the box next to the warehouse that will be used to resupply the warehouse that is currently being configured." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:89 +msgid ":guilabel:`Provider`: :guilabel:`Fixed Price`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 -msgid "A warehouse settings form configured to allow resupplying between warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:90 +msgid ":guilabel:`Fixed Price`: `$20.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:39 -msgid "For the purposes of this demonstration, the warehouse that products are transferred from (outgoing) will be titled \"San Francisco\", and the warehouse that products are transferred to (incoming) will be titled \"San Francisco 2\"." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:91 +msgid ":guilabel:`Free if order amount is above`: `$100.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:44 -msgid "Configure products for inter-warehouse replenishment" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:92 +msgid ":guilabel:`Delivery Product`: `[SHIP] Flat`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:46 -msgid "Products must also be configured properly in order for them to be transferred between warehouses. Navigate to :menuselection:`Inventory --> Products --> Products` and select an existing product or :guilabel:`Create` a new one, if necessary." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Example of filling out a shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:50 -msgid "Then, on the product form, go to the :guilabel:`Inventory` tab and enable the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the warehouse receiving the transferred products and *Y* being the warehouse that products are transferred from." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:101 +msgid "Based on rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 -msgid "Enable the checkbox to resupply one warehouse from another." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:103 +msgid "To calculate the price of shipping based on pricing rules, set the :guilabel:`Provider` field to the :guilabel:`Based on Rules` option. Optionally, adjust :guilabel:`Margin on Rate` and :guilabel:`Additional margin` to include additional shipping costs." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:59 -msgid "Replenish one warehouse from another" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:108 +msgid "Create pricing rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:61 -msgid "Starting in the :menuselection:`Inventory` module, select :menuselection:`Products --> Products` and then choose the product that will be replenished. Click the :guilabel:`Replenish` button on the top left of the product page and fill out the pop-up form as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:110 +msgid "Navigate to the :guilabel:`Pricing` tab and click :guilabel:`Add a line`. Doing so opens the :guilabel:`Create Pricing Rules` window, where the :guilabel:`Condition` related to the product weight, volume, price, or quantity is compared to a defined amount to calculate the :guilabel:`Delivery Cost`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:65 -msgid ":guilabel:`Quantity`: the number of units that will be sent to the warehouse being replenished" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:115 +msgid "Once finished, click either :guilabel:`Save & New` to add another rule, or :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:66 -msgid ":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to take place" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:118 +msgid "To charge customers $20 in shipping for orders with five or fewer products, set the :guilabel:`Condition` to `Quantity <= 5.00`, and the :guilabel:`Delivery Cost` to `$20`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:67 -msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Display window to add a pricing rule. Set a condition and delivery cost." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:68 -msgid ":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* being the warehouse to be replenished and *Y* being the warehouse that the product will be transferred from" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:125 +msgid "To restrict shipping to specific destinations on the eCommerce website, in the shipping method form, navigate to the :guilabel:`Destination Availability` tab and define the :guilabel:`Countries`, :guilabel:`States`, and :guilabel:`Zip Prefixes`. Leave these fields empty if all locations apply." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 -msgid "The form for replenishing a product." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:130 +msgid "Calculate delivery cost" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:75 -msgid "Click :guilabel:`Confirm` and a delivery order will be created for the outgoing warehouse along with a receipt for the warehouse that will receive the product. Depending on the configuration settings for the outgoing and incoming warehouses, processing delivery orders and receipts will require between one and three steps. This document will detail how to process one-step deliveries and receipts." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:132 +msgid "Shipping cost is the :guilabel:`Delivery cost` specified in the rule that satisfies the :guilabel:`Condition`, plus any extra charges from the :guilabel:`Margin on rate` and :guilabel:`Additional margin`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:82 -msgid "Process the delivery order" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:136 +msgid "Total = Rule's~Delivery~Cost + (Margin~on~rate \\times Rule's~Delivery~Cost) + Additional~margin\n" +"\n" +"" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:84 -msgid "The first stage of a replenishment order is processing the delivery from the warehouse that the product is being transferred from. On the :menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, then the delivery order created for the replenishment. On the delivery order page, click the :guilabel:`Check Availability` button in the top left to reserve the quantity of the product to be transferred. Once the delivery has been dispatched, click the :guilabel:`Validate` button to register the quantities shipped." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:140 +msgid "With the two following rules set up:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 -msgid "The delivery orders card for the outgoing warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:142 +msgid "If the order contains five or fewer products, shipping is $20" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:99 -msgid "Once the goods arrive at the incoming warehouse, the receipt created for that warehouse must be processed as well. Return to the :menuselection:`Inventory` dashboard and select the :guilabel:`X to Process` button on the :guilabel:`Receipts` card for the incoming warehouse, then the receipt created for the replenishment. On the receipt page, click the :guilabel:`Validate` button in the top left of the page to register the quantities received." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:143 +msgid "If the order contains more than five products, shipping is $50." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:109 -msgid "After processing the receipt, the products transferred will now appear in the inventory of the incoming warehouse. The stock numbers for both warehouses can be viewed by returning to the product page and selecting the :guilabel:`X Units On Hand` button at the top of the screen." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:145 +msgid ":guilabel:`Margin on Rate` is `10%` and :guilabel:`Additional margin` is `$9.00`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:114 -msgid "Automate inter-warehouse replenishment" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:-1 +msgid "Show example of \"Based on rules\" shipping method with margins configured." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:116 -msgid "Using reordering rules, it is possible to automate the process of replenishing one warehouse from another." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:151 +msgid "When the first rule is applied, the delivery cost is $31 (20 + (0.1 * 20) + 9). When the second rule is applied, the delivery cost is $64 (50 + (0.1 * 50) + 9)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:119 -msgid "To get started, navigate to :menuselection:`Inventory --> Products --> Products`, and then choose the product that will be replenished. From the product page, select the :guilabel:`Reordering Rules` smart button at the top of the form, and then on the next page, click :guilabel:`Create` to configure the form as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:157 +msgid "Pickup in store" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:124 -msgid ":guilabel:`Location`: the location that the reordering rule will replenish when triggered, in this case, the incoming warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:159 +msgid "To configure in-store pickup, select :guilabel:`Pickup in store` in the :guilabel:`Provider` field and specify the pickup location in :guilabel:`Warehouse`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:126 -msgid ":guilabel:`Min Quantity`: when the quantity on hand at the incoming warehouse falls below this number, the reordering rule will be triggered" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:162 +msgid "To invoice the customer for the shipping cost to the pickup location, choose the :guilabel:`Get Rate and Create Shipment` option in the :guilabel:`Integration Level` field. Then, pick either the :guilabel:`Estimated cost` or :guilabel:`Real cost` radio options in the :guilabel:`Invoicing Policy` field to decide whether the added shipping charge on the sales order is the precise cost from the shipping carrier." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:128 -msgid ":guilabel:`Max Quantity`: when the reordering rule is triggered, the product will be replenished at the incoming warehouse up to this quantity" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:169 +msgid ":ref:`Invoice cost of shipping `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:130 -msgid ":guilabel:`Multiple Quantity`: specify if the product should be replenished in batches of a certain quantity; for example, a product could be replenished in batches of 20" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:174 +msgid "Add shipping" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:132 -msgid ":guilabel:`UoM`: the unit of measure used for reordering the product; this value can simply be `Units`, or a specific unit of measurement for weight, length, etc." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:176 +msgid "Shipping methods can be added to sales orders in the form of delivery products, which appear as individual line items. First, navigate to the desired sales order by going to :menuselection:`Sales app --> Orders --> Orders`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:-1 -msgid "A fully configured reordering rule." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:180 +msgid "On the sales order, click the :guilabel:`Add shipping` button, which opens the :guilabel:`Add a shipping method` pop-up window. Then, choose a :guilabel:`Shipping Method` from the list." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:139 -msgid "Finish by clicking :guilabel:`Save` and the reordering rule will be created. Now, when the scheduler runs automatically each day, a transfer will be created for each reordering rule that has been triggered." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:183 +msgid "The :guilabel:`Total Order Weight` is pre-filled based on product weights (that are defined in the :guilabel:`Inventory` tab for each product form). Edit the field to specify the exact weight, and then click :guilabel:`Add` to add the shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:144 -msgid "To manually trigger reordering rules, start from the :menuselection:`Inventory` module and select :menuselection:`Operation --> Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the pop-up that appears." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:188 +msgid "The amount defined in :guilabel:`Total Order Weight` overwrites the total product weights defined on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:148 -msgid "After the scheduler runs, a delivery order and receipt will be created for the outgoing and incoming warehouses, respectively. Both the delivery order and receipt should be processed using the same method as detailed above." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:191 +msgid "The shipping cost is added to the *sales order line* as the :guilabel:`Delivery Product` detailed on the shipping method form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:3 -msgid "Manage Warehouses and Locations" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:195 +msgid "`Furniture Delivery`, a delivery product with a fixed rate of `$200`, is added to sales order `S00088`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:9 -msgid "Warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Show delivery order on the sales order line." 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:203 +msgid "Delivery order" 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:205 +msgid "The shipping method added to the sales order is linked to the shipping carrier details on the delivery order. To add or change the delivery method on the delivery itself, go to the :guilabel:`Additional Info` tab and modify the :guilabel:`Carrier` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:22 -msgid "There are three types of locations:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:-1 +msgid "Shipping carrier information on the delivery form." 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:3 +msgid "How to get DHL credentials for integration with Odoo?" 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:5 +msgid "In order to use the Odoo DHL API, you will need:" 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**)." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:7 +msgid "A DHL.com SiteID" 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:9 +msgid "A DHL Password" 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`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:11 +msgid "A DHL Account Number" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:-1 -msgid "Enable the storage location feature in Odoo Inventory settings." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:15 +msgid "Getting SiteID and password for countries other than United States (UK and Rest of the world)" 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`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:17 +msgid "You should contact DHL account manager and request integration for XML Express API. The presales should provide you live credentials." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:56 -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:41 -msgid "Create a new warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:20 +msgid "Getting SiteID and Password for United States" 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`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:22 +msgid "You need to write to xmlrequests@dhl.com along with your full Account details like account number, region, address, etc. to get API Access." 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:3 +msgid "Set up Sendcloud shipping services in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:-1 -msgid "Short name field of a warehouse on Odoo Inventory." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:5 +msgid "Sendcloud is a shipping service aggregator that facilitates the integration of European shipping carriers with Odoo. Once integrated, users can select shipping carriers on inventory operations in their Odoo database." 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]\"." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:10 +msgid "`Sendcloud integration documentation `_" 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:14 +msgid "Setup in Sendcloud" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:-1 -msgid "Inventory app dashboard displaying new transfer types for the recently created warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:17 +msgid "Create an account and activate carriers" 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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:19 +msgid "To get started, go to `Sendcloud's platform `_ to configure the account and generate the connector credentials. Log in with the Sendcloud account, or create a new one if needed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:83 -msgid "Create a new location" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:24 +msgid "For new account creation, Sendcloud will ask for a :abbr:`VAT (Value-Added Tax Identification)` number or :abbr:`EORI (Economic Operators' Registration and Identification)` number. After completing the account setup, activate (or deactivate) the shipping carriers that will be used in the Odoo database." 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`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:30 +msgid "Odoo integration of Sendcloud works on free Sendcloud plans *only* if a bank account is linked, since Sendcloud won't ship for free. To use shipping rules or individual custom carrier contacts, a paid plan of Sendcloud is required." 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`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:35 +msgid "Warehouse configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:-1 -msgid "Create a new warehouse location in Odoo Inventory." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:37 +msgid "Once logged into the Sendcloud account, navigate to :menuselection:`Settings --> Shipping --> Addresses`, and fill in the field for :guilabel:`Warehouse address`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes.rst:5 -msgid "Advanced routes" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:-1 +msgid "Adding addresses in the Sendcloud settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts.rst:5 -msgid "Concepts" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:44 +msgid "To allow Sendcloud to process returns as well, a :guilabel:`Return Address` is required. Under the :guilabel:`Miscellaneous section`, there is a field called :guilabel:`Address Name (optional)`. The Odoo warehouse name should be entered here, and the characters should be exactly the same." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid "**SendClould configuration**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Miscellaneous`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Address Name (optional)`: `Warehouse #1`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Brand`: `Default`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid "**Odoo warehouse configuration**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Warehouse`: `Warehouse #1`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Short Name`: `WH`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Company`: `My company (San Francisco)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Address`: `My Company (San Francisco)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:61 +msgid "Notice how the inputs for the :guilabel:`Warehouse` field, for both the Odoo configuration and the Sendcloud configuration, are the exact same." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:65 +msgid "Generate Sendcloud credentials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:67 +msgid "In the Sendcloud account, navigate to :menuselection:`Settings --> Integrations` in the menu on the right. Next, search for :guilabel:`Odoo Native`. Then, click on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:70 +msgid "After clicking on :guilabel:`Connect`, the page redirects to the :guilabel:`Sendcloud API` settings page, where the :guilabel:`Public and Secret Keys` are produced. The next step is to name the :guilabel:`Integration`. The naming convention is as follows: `Odoo CompanyName`, with the user's company name replacing `CompanyName` (e.g. `Odoo StealthyWood`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:75 +msgid "Then, check the box next to :guilabel:`Service Points` and select the shipping services for this integration. After saving, the :guilabel:`Public and Secret Keys` are generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:-1 +msgid "Configuring the Sendcloud integration and receiving the credentials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:83 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:86 +msgid "Install the Sendcloud shipping module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:88 +msgid "After the Sendcloud account is set up and configured, it's time to configure the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, search for the :guilabel:`Sendcloud Shipping` integration, and install it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:-1 +msgid "Sendcloud Shipping module in the Odoo Apps module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:97 +msgid "Sendcloud shipping connector configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:99 +msgid "Once installed, activate the :guilabel:`Sendcloud Shipping` module in :menuselection:`Inventory --> Configuration --> Settings`. The :guilabel:`Sendcloud Connector` setting is found under the :guilabel:`Shipping Connectors` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:103 +msgid "After activating the :guilabel:`Sendcloud Connector`, click on the :guilabel:`Sendcloud Shipping Methods` link below the listed connector. Once on the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:108 +msgid ":guilabel:`Shipping Methods` can also be accessed by going to :menuselection:`Inventory --> Configuration --> Delivery --> Shipping Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:111 +msgid "Fill out the following fields in the :guilabel:`New Shipping Method` form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:113 +msgid ":guilabel:`Shipping Method`: type `Sendcloud DPD`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:114 +msgid ":guilabel:`Provider`: select :guilabel:`Sendcloud` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:115 +msgid ":guilabel:`Delivery Product`: set the product that was configured for this shipping method or create a new product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:117 +msgid "In the :guilabel:`SendCloud Configuration` tab, enter the :guilabel:`Sendcloud Public Key`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:118 +msgid "In the :guilabel:`SendCloud Configuration` tab, enter the :guilabel:`Sendcloud Secret Key`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:119 +msgid "Manually :guilabel:`Save` the form by clicking the cloud icon next to the :guilabel:`Shipping Methods / New` breadcrumbs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:122 +msgid "After configuring and saving the form, follow these steps to load the shipping products:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:124 +msgid "In the :guilabel:`SendCloud Configuration` tab of the :guilabel:`New Shipping Method` form, click on the :guilabel:`Load your SendCloud shipping products` link." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:126 +msgid "Select the shipping products the company would like to use for deliveries and returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:127 +msgid "Click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:130 +msgid "Sample Sendcloud shipping products configured in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`DELIVERY`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Shipping Product`: `DPD Home 0-31.5kg`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Carrier`: `DPD`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Minimum Weight`: `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Maximum Weight`: `31.50`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:138 +msgid ":guilabel:`Countries`: `Austria` `Belgium` `Bosnia` `Herzegovina` `Bulgaria` `Croatia` `Czech` `Republic` `Denmark` `Estonia` `Finland` `France` `Germany` `Greece` `Hungary` `Iceland` `Ireland` `Italy` `Latvia` `Liechtenstein` `Lithuania` `Luxembourg` `Monaco` `Netherlands` `Norway` `Poland` `Portugal` `Romania` `Serbia` `Slovakia` `Slovenia` `Spain` `Sweden` `Switzerland`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`RETURN`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Shipping Product`: `DPD Return 0-20kg`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Carrier`: `DPD`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Minimum Weight`: `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Maximum Weight`: `20.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Countries`: `Belgium` `Netherlands`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:-1 +msgid "Example of shipping products configured in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:156 +msgid "Sendcloud does not provide test keys when a company tests the sending of a package in Odoo. This means if a package is created, the configured Sendcloud account will be charged, unless the associated package is canceled within 24 hours of creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:160 +msgid "Odoo has a built-in layer of protection against unwanted charges when using test environments. Within a test environment, if a shipping method is used to create labels, then those labels are immediately canceled after the creation ā€” this occurs automatically. The test and production environment settings can be toggled back and forth from the :guilabel:`Smart Buttons`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:166 +msgid "Generate a label with Sendcloud" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:168 +msgid "When creating a quotation in Odoo, add shipping and a :guilabel:`Sendcloud shipping product`. Then, :guilabel:`Validate` the delivery. Shipping label documents are automatically generated in the chatter, which include the following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:172 +msgid ":guilabel:`Shipping label(s)` depending on the number of packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:173 +msgid ":guilabel:`Return label(s)` if the Sendcloud connector is configured for returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:174 +msgid ":guilabel:`Customs document(s)` should the destination country require them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:176 +msgid "Additionally, the tracking number is now available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:179 +msgid "When return labels are created, Sendcloud will automatically charge the configured Sendcloud account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:183 +msgid "FAQ" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:186 +msgid "Shipment is too heavy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:188 +msgid "If the shipment is too heavy for the Sendcloud service that is configured, then the weight is split to simulate multiple packages. Products will need to be put in different :guilabel:`Packages` to :guilabel:`Validate` the transfer and generate labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:192 +msgid ":guilabel:`Rules` can also be set up in Sendcloud to use other shipping methods when the weight is too heavy. However, note that these rules will not apply to the shipping price calculation on the calculation on the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:197 +msgid "When using a personal carrier contract" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:199 +msgid "When using a personal carrier contract in Sendcloud, if the the price is not accurately reflected when creating a quotation in Odoo, then the pricing information needs to be updated in Sendcloud." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:203 +msgid "Measuring volumetric weight" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:205 +msgid "Many carriers have several measures for weight. There is the actual weight of the products in the parcel, and there is the *volumetric weight* (:dfn:`Volumetric weight is the volume that a package occupies when in transit. In other words it is the physical size of a package`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:210 +msgid "Check to see if selected carrier(s) already have defined formulas to compute the volumetric weight." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:214 +msgid "`Sendcloud: How to calculate & automate parcel volumetric weight `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:219 +msgid "Unable to calculate shipping rate" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:221 +msgid "First, verify that product being shipped has a weight that is supported by the selected shipping method. If this is set, then verify that the destination country (from the customer address) is supported by the carrier. The country of origin (warehouse address) should also be supported by the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:3 +msgid "How to integrate a third party shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:10 +msgid "Odoo can handle various delivery methods, including third party shippers. Odoo can be linked with the transportation company tracking system. It will allow you to manage the transport company, the real prices and the destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:21 +msgid "In the inventory module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:31 +msgid "If you want to integrate delivery methods in your e-commerce, you'll have to install the **eCommerce Delivery** module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:40 +msgid "The delivery methods for the chosen shippers have been automatically created. Most of the time, there will be **2** delivery methods for the same provider: one for **international** shipping and the other for **domestic** shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:45 +msgid "You can create other methods with the same provider with other configuration, for example the **Packaging Type**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:48 +msgid "You can change the **Name** of the delivery method. This is the name that will appear on your ecommerce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:51 +msgid "Flag **Shipping enabled** when you are ready to use it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:56 +msgid "In the pricing tab, the name of the provider chosen under the **Price computation** means that the pricing will be computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:59 +msgid "The configuration of the shipper is split into two columns:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:61 +msgid "The first one is linked to **your account** (developer key, password,...). For more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:69 +msgid "Finally you can limit the delivery method to a few destinations. You can limit it to some countries, states or even zip codes. This feature limits the list of countries on your e-commerce. It is useful for the domestic providers. For example, USPS US only delivers from the United States to the United States." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:97 +msgid "Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:104 +msgid "The weight on the product form is expressed in kilograms. Don't forget to make the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:109 +msgid "Sale process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:112 +msgid "Sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:117 +msgid "You can now choose the carrier on your sale order. Click on **Delivery method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:120 +msgid "The price is computed when you save the sale order or when you click on **Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:123 +msgid "If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:127 +msgid "Otherwise, the real price (computed when the delivery is validated) will automatically be added to the invoice. For more information, please read the document :doc:`../advanced_operations_shipping/invoicing`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:132 +msgid "Delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:134 +msgid "The delivery created from the sale order will take the shipping information from it. You can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:143 +msgid "The weight is computed based on the products weights. The shipping cost will be computed once the transfer is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:146 +msgid "Click on **Validate** to receive the tracking number. The **Carrier Tracking ref** field will automatically be filled. Click on the **Tracking** button to check your delivery on the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:160 +msgid ":doc:`../advanced_operations_shipping/invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:161 +msgid ":doc:`../advanced_operations_shipping/labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:3 +msgid "How to get UPS credentials for integration with Odoo?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:5 +msgid "In order to use the Odoo UPS API, you will need:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:7 +msgid "A UPS.com user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:9 +msgid "A UPS account number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:11 +msgid "An Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:13 +msgid "An Access Key is a 16 character alphanumeric code that allows access to the UPS Developer Kit API Development and Production servers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:17 +msgid "Create a UPS Account" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:19 +msgid "Note that only customers located in the US can open a UPS account online. If you are located outside the US, you will need to contact UPS Customer Service in order to to open an account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:23 +msgid "You can read additional information about opening a UPS account on the their website, on the page, `How to Open a UPS Account Online `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:27 +msgid "If you don't already have a UPS account, you can create one along with your online profile by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:30 +msgid "1. Access the UPS.com web site at `www.ups.com `__, and click the **New User** link at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:34 +msgid "2. Click the **Register for MyUPS** button, and follow the prompts to complete the registration process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:37 +msgid "If you already have a UPS account, you can add it to your online profile as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:39 +msgid "Log in to the `UPS.com website `_) using your UPS.com User ID and Password." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:41 +msgid "Click the **My UPS** tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:43 +msgid "Click the **Account Summary** link." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:45 +msgid "4. Click the **Add an Existing UPS Account** link in the **UPS Account Details** section of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:48 +msgid "5. In the **Add New Account** screen, enter the **UPS Account Number**, **Account Name**, and **Postal Code** fields. The country defaults to United States.q" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:52 +msgid "Click the **Next** button to continue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:55 +msgid "Get an Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:57 +msgid "After you have added your UPS account number to your user profile you can request an Access Key from UPS using the steps below:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:60 +msgid "Go to the `UPS Developer Kit web page `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:61 +msgid "Log into UPS.com with your user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:62 +msgid "Click on the link **Request an access key**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:63 +msgid "Verify your contact information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:64 +msgid "Click the **Request Access Key** button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:66 +msgid "The **Access Key** will be provided to you on the web page, and an email with the Access Key will be sent to the email address of the primary contact." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage.rst:5 +msgid "Warehouses and storage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:3 +msgid "Batch picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:7 +msgid "*Batch picking* enables a single picker to handle multiple orders at once, reducing the time needed to navigate to the same location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:10 +msgid "When picking in batches, orders are grouped and consolidated into a picking list. After the picking, the batch is taken to an output location, where the products are sorted into their respective delivery packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:15 +msgid ":ref:`Use Barcode app for pickings `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:17 +msgid "Since orders *must* be sorted at the output location after being picked, this picking method suits businesses with a few products that are ordered often. Storing high-demand items in easily accessible locations can increase the number of orders that are fulfilled efficiently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:24 +msgid "To activate the batch picking option, begin by going to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` section, check the :guilabel:`Batch Transfers` box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +msgid "Enable the *Batch Transfers* in Inventory > Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:32 +msgid "Since batch picking is a method to optimize the *pick* operation in Odoo, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options under the :guilabel:`Warehouse` heading must also be checked on this settings page. When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:-1 +msgid "Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:40 +msgid "Lastly, enable the warehouse picking feature, by navigating to the warehouse settings page, which is accessible from :menuselection:`Inventory app --> Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:43 +msgid "From here, select the desired warehouse from the list. Then, from the radio options available for :guilabel:`Outgoing Shipments`, select either the :guilabel:`Send goods in output and then deliver (2 steps)` or :guilabel:`Pack goods, send goods in output and then deliver (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:131 +msgid ":ref:`Delivery in two steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:132 +msgid ":ref:`Delivery in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +msgid "Set up 2-step or 3-step outgoing shipments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:56 +msgid "Create batch transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:58 +msgid "Manually create batch transfers directly from the :menuselection:`Inventory app --> Operations --> Batch Transfers` page. Click the :guilabel:`New` button to begin creating a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:61 +msgid "On the batch transfer form, fill the following fields out accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:63 +msgid ":guilabel:`Responsible`: employee assigned to the picking. Leave this field blank if *any* worker can fulfill this picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:65 +msgid ":guilabel:`Operation Type`: from the drop-down menu, select the operation type under which the picking is categorized." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:67 +msgid ":guilabel:`Scheduled Date`: specifies the date by which the :guilabel:`Responsible` person should complete the transfer to the output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:70 +msgid "Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to open the :guilabel:`Add: Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:73 +msgid "If the :guilabel:`Operation Type` field was filled, the list will filter transfer records matching the selected :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:76 +msgid "Click the :guilabel:`New` button to create a new transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:78 +msgid "Once the transfer records are selected, click :guilabel:`Confirm` to confirm the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:81 +msgid "A new batch transfer assigned to the :guilabel:`Responsible`, `Joel Willis`, for the `Pick` :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` is set to `August 11`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "View of *Batch Transfers* form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:88 +msgid "Clicking the :guilabel:`Add a line` button opens the :guilabel:`Add:Transfers` window, displaying only pickings. This is because the :guilabel:`Operation Type` was set to `Pick` on the batch transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:92 +msgid "Click the checkbox to the left of the transfers, `WH/PICK/00001` and `WH/PICK/00002`, to include them in the new transfer. Then, click the :guilabel:`Select` button to close the :guilabel:`Add:Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Select multiple transfers from the *Add:Transfers* window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:101 +msgid "Add batch from transfers list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:103 +msgid "Another method of creating batch transfers is available using the :guilabel:`Add to batch` option in a list. Navigate to the :menuselection:`Inventory app --> Operations` drop-down menu, and select any of the :guilabel:`Transfers` to open a filtered list of transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +msgid "Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,\n" +"Manufacturings, Batch Transfers, Dropships." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:112 +msgid "On the transfers list, select the checkbox to the left of the selected transfers to add in a batch. Next, navigate to the :guilabel:`Actions āš™ļø (gear)` button, and click :guilabel:`Add to batch` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Use *Add to batch* button, from the *Action* button's list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:151 +msgid "Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the employee :guilabel:`Responsible` for the picking can be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:123 +msgid "Choose from the two radio options to add to :guilabel:`an existing batch transfer` or create :guilabel:`a new batch transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:126 +msgid "To begin with a draft, select the :guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:160 +msgid "Conclude the process by clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:-1 +msgid "Show *Add to batch* window to create a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:135 +msgid "Process batch transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:137 +msgid "Handle batch transfers in the :menuselection:`Inventory app --> Operations --> Batch Transfers` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:140 +msgid "From here, select the intended transfer from the list. Then, on the batch transfer form, input the :guilabel:`Done` quantities for each product, under the :guilabel:`Detailed Operations` tab. Finally, select :guilabel:`Validate` to complete the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:145 +msgid "Be certain the batch transfer is complete when the :guilabel:`Validate` button is highlighted in purple. If the :guilabel:`Check Availability` button is highlighted instead, that means there are items in the batch that are currently *not* available in-stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:152 +msgid "In a batch transfer involving products from pickings, `WH/PICK/00001` and `WH/PICK/00002`, the :guilabel:`Detailed Operations` tab shows that the product, `Cabinet with Doors`, has been picked because the :guilabel:`Done` column matches the value in the :guilabel:`Reserved` column. However, `0.00` quantities have been picked for the other product, `Cable Management Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Show batch transfer of products from two pickings in the *Detailed Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:161 +msgid "Only in-stock products are visible in the :guilabel:`Detailed Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:163 +msgid "To view the complete product list, switch to the :guilabel:`Operations` tab. On this list, the :guilabel:`Demand` column indicates the required quantity for the order. The :guilabel:`Reserved` column shows the available stock to fulfill the order. Lastly, the :guilabel:`Done` column specifies the products that have been picked, and are ready for the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:169 +msgid "The product, `Desk Pad`, from the same batch as the :ref:`example above `, is only visible in the :guilabel:`Operations` tab because there are no :guilabel:`Reserved` quantities in-stock to fulfill the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:173 +msgid "Click the :guilabel:`Check Availability` button to search the stock again for available products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Show unavailable reserved quantities in the *Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:180 +msgid "Create backorder" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:182 +msgid "On the batch transfer form, if the :guilabel:`Done` quantity of the product is *less* than the :guilabel:`Reserved` quantity, a pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:185 +msgid "This pop-up window provides the option: :guilabel:`Create Backorder?`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:187 +msgid "Clicking the :guilabel:`Create Backorder` button automatically creates a new batch transfer, containing the remaining products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:190 +msgid "Click :guilabel:`No Backorder` to finish the picking *without* creating another batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:192 +msgid "Click :guilabel:`Discard` to cancel the validation, and return to the batch transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +msgid "Show the *Create Backorder* pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:201 +msgid "Process batch transfer: Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:203 +msgid "Created batch transfers are also listed in the :menuselection:`Barcode` app, accessible by selecting the :guilabel:`Batch Transfers` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:206 +msgid "By default, confirmed batch pickings appear on the :guilabel:`Batch Transfers` page. On that page, click on the desired batch transfer to open the detailed list of products for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 +msgid "Show list of to-do batch transfers in *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:213 +msgid "For the chosen batch transfer, follow the instructions at the top of the page in the black background. Begin by scanning the product's barcode to record a single product for picking. To record multiple quantities, click the :guilabel:`āœļø (pencil)` icon, and enter the required quantities for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:219 +msgid "Products from the same order are labeled with the same color on the left. Completed pickings are highlighted in green." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:223 +msgid "In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, and 4 `Four Person Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate that the last two product pickings are complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:227 +msgid "`1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the unique serial number for :ref:`product tracking `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Display products to be picked in barcode view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:235 +msgid "Once all the products have been picked, click on :guilabel:`Validate` to mark the batch transfer as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:3 +msgid "Cluster picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:10 +msgid "Cluster picking is an advanced order fulfillment approach derived from :ref:`batch picking `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:13 +msgid "In this strategy, pickers load a cart with multiple packages, each designated for a specific *sales order* (SO). Then, the picker travels to each storage location, and places the products directly in the package of the associated order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:17 +msgid "This method is most efficient for medium-sized companies, with high order volumes, and relatively few unique products, since the method eliminates the need for sorting products into packages for customers after picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:21 +msgid "However, cluster picking does have some disadvantages. For instance, urgent orders cannot be prioritized, and optimized batches must be manually created beforehand. As a result, the picking process can lead to bottlenecks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:28 +msgid "|SO| 1 calls for one apple and orange" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:29 +msgid "|SO| 2 calls for one apple and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:30 +msgid "|SO| 3 calls for one apple, orange, and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:32 +msgid "Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:34 +msgid "To pick products for three orders at once, the cart is loaded with three empty packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:36 +msgid "Starting at Shelf A, the picker places apples into each package. Next, the picker navigates to Shelf B, and places oranges in the packages designated for |SO| 1 and |SO| 3. Finally, the picker pushes the cart to Shelf C, and loads packages for |SO| 2 and |SO| 3 with a banana, each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:40 +msgid "With the packages for all three |SOS| packed, the picker pushes the cart to the output location, where the packages are sealed and prepared for shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Show example of fulfilling sales orders 2 and 3 at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:50 +msgid "To enable cluster picking, begin by navigating to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` heading, activate the :guilabel:`Packages` and :guilabel:`Batch Transfers` options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:-1 +msgid "Activate *Packages* and *Batch Transfers* features in the settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:58 +msgid "Since batch picking is used to optimize the *pick* operation in Odoo, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options, under the :guilabel:`Warehouse` heading, must also be checked on this settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:62 +msgid "*Storage locations* allow products to be stored in specific locations they can be picked from, while *multi-step routes* enable the picking operation itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:65 +msgid "When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:74 +msgid "Packages setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:76 +msgid "After the :guilabel:`Packages` feature is enabled, navigate to :menuselection:`Inventory app --> Products --> Packages`, and click the :guilabel:`New` button to create a new package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:79 +msgid "On the new package form, the :guilabel:`Package Reference` is pre-filled with the next available `PACK` number in the system. :guilabel:`Pack Date` is automatically set to the creation date of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:83 +msgid "For the :guilabel:`Package Use` field, the :guilabel:`Disposable Box` option should be selected if the package is used for a shipping. Alternatively, the :guilabel:`Reusable Box` option should be selected if the package is simply used as a method of grouping products from the same |SO| together before they are moved to the intended shipping box at the output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:89 +msgid ":ref:`Packages `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:92 +msgid "A package intended for cluster picking is named `CLUSTER-PACK-3` for easy identification. For this workflow, the products are directly packed using their intended shipping boxes, so :guilabel:`Package Use` is set to :guilabel:`Disposable Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Create new package form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:101 +msgid "Create cluster batch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:103 +msgid "To see how cluster picking works in Odoo, navigate to the :menuselection:`Sales` app, and create |SOS| that will be fulfilled together in the same batch. After confirming an |SO|, the :guilabel:`Delivery` smart button becomes visible. Displayed inside the icon is a number representing the amount of steps in the outgoing shipment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:109 +msgid "Begin by creating three |SOS| for the apples, oranges, and bananas, as shown in the :ref:`example above `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:112 +msgid "After confirming the |SO|, the :guilabel:`Delivery` smart button displays the number `2`, indicating there are two operations to complete: `Pick` and `Delivery`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example sales order for an apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:119 +msgid "With the |SOS| created, orders now must be grouped into batches. To do so, navigate to the *Inventory* dashboard and select the operation type card, :guilabel:`Delivery Orders` or :guilabel:`Pick` (whichever is the first operation in the delivery flow)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:123 +msgid "Doing so displays a filtered list of outgoing operations with the :guilabel:`Ready` status, indicating that all the products in the |SO| are in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:127 +msgid "Cluster pick batches can be created for outgoing shipments in one, two, or three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:130 +msgid ":ref:`Delivery in one step `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:134 +msgid "Click the checkbox to the left of the corresponding outgoing operation to add them to the batch. With the desired pickings selected, click the :guilabel:`āš™ļø Actions (gear)` button, and select the :guilabel:`Add to batch` option from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:139 +msgid "To create a cluster batch, as shown in the :ref:`example above `, in a warehouse configured with two-step outgoing shipments, the following pick operations are selected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:143 +msgid "`WH/PICK/00007`: linked to |SO| 88 for one apple and orange." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:144 +msgid "`WH/PICK/00008`: linked to |SO| 89 for one apple and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:145 +msgid "`WH/PICK/00009`: linked to |SO| 90 for one apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:154 +msgid "Choose from the two options in the :guilabel:`Add to` field to either: add to :guilabel:`an existing batch transfer`, or create :guilabel:`a new batch transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:157 +msgid "To create draft batch pickings to be confirmed at a later date, select the :guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:167 +msgid "Process batches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:169 +msgid "To process batches, navigate to :menuselection:`Inventory app --> Operations --> Batch Transfers`. Click on a batch to select it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:172 +msgid "In the :guilabel:`Detailed Operations` tab, products that are to be picked are grouped by location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:174 +msgid "Under the :guilabel:`Source Package` or :guilabel:`Destination Package` field, enter the package used for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:178 +msgid "Use the :guilabel:`Source Package` field when the picking package is configured as *reusable* on the :ref:`package form `. This means the products are temporarily placed in a container during picking, before getting transferred to their final shipping box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:182 +msgid "Alternatively, use the :guilabel:`Destination Package` field when the product is directly placed in its *disposable* shipping box during picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:186 +msgid "Process the cluster batch for the three orders of apples, oranges, and bananas :ref:`example ` by assigning each picking to a dedicated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:189 +msgid "At the storage location for apples, `WH/Stock/Shelf A`, assign the apples in all three pickings to one of the three disposable packages, `CLUSTER-PACK-1`, `CLUSTER-PACK-2`, or `CLUSTER-PACK-3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:192 +msgid "Record this in Odoo using the :guilabel:`Destination Package` field in the :guilabel:`Detailed Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example of processing cluster pickings in *Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:200 +msgid "In Barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:202 +msgid "To process cluster pickings directly from the *Barcode* app, select the :guilabel:`Batch Transfers` button from the *Barcode* dashboard. Then, select the desired batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:205 +msgid "On the batch transfer screen, the products in the picking are grouped by location, and each line is color-coded to associate products in the same picking together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:208 +msgid "Then, follow the prompt to :guilabel:`Scan the source location` barcode for the storage location of the first product. Then, scan the barcode for the product and package to process the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:211 +msgid "Repeat this for all products, and click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:214 +msgid "To find the package barcode, navigate to :menuselection:`Inventory app --> Products --> Packages`, select the desired package, click the :guilabel:`āš™ļø (gear)` icon at the top of the package form, and select the :guilabel:`Print` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:218 +msgid "Next, select one of the three print options to generate the package barcode from the :guilabel:`Package Reference` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Display where the package barcode can be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:226 +msgid "Begin processing the cluster picking by going to the first storage location, `Shelf A`, and scanning the :ref:`location barcode `. Doing so highlights all the pickings that need products from this particular location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:230 +msgid "Scan the barcode for the apple, which highlights the picking (labeled in red) for the product `Apple`, for the picking, `WH/PICK/00007`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:233 +msgid "Then, scan the `CLUSTER-PACK-1` package barcode, and place the product in the designated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example of cluster batch from the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:240 +msgid "After creating a batch transfer and assigning a package to a picking, Odoo suggests the specified package by displaying the name *in italics* under the product name, ensuring pickers place products into the correct boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:3 msgid "Organize a cross-dock in a warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:5 msgid "Cross-docking is the process of sending products that are received directly to the customers, without making them enter the stock. The trucks are simply unloaded in a *Cross-Dock* area in order to reorganize products and load another truck." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:13 msgid "For more information on how to organize your warehouse, read our blog: `What is cross-docking and is it for me? `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:20 msgid "In the *Inventory* app, open :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:27 msgid "Doing so will also enable the *Storage Locations* feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:29 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:29 msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit your warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:36 msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in :menuselection:`Inventory --> Configuration --> Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:43 msgid "Configure products with Cross-Dock Route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:45 msgid "Create the product that uses the *Cross-Dock Route* and then, in the inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the purchase tab, specify the vendor to who you buy the product and set a price for it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:55 msgid "Once done, create a sale order for the product and confirm it. Odoo will automatically create two transfers which will be linked to the sale order. The first one is the transfer from the *Input Location* to the *Output Location*, corresponding to the move of the product in the *Cross-Dock* area. The second one is the delivery order from the *Output Location* to your *Customer Location. Both are in state *Waiting Another Operation* because we still need to order the product to our supplier." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:68 msgid "Now, go to the *Purchase* app. There, you will find the purchase order that has been automatically triggered by the system. Validate it and receive the products in the *Input Location*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:77 msgid "When the products have been received from the supplier, you can go back to your initial sale order and validate the internal transfer from *Input* to *Output*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:86 msgid "The delivery order is now ready to be processed and can be validated too." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:3 +msgid "Cycle counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:5 +msgid "For most companies, warehouse stock only needs to be counted once a year. This is why, by default, after making an *inventory adjustment* in Odoo, the scheduled date for the next inventory count is set for the 31st of December of the current year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:9 +msgid "However, for some businesses, it's crucial to have an accurate inventory count at all times. These companies use *cycle counts* to keep critical stock levels accurate. Cycle counting is a method by which companies count their inventory more often in certain *locations*, to ensure that their physical inventory counts match their inventory records." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:15 +msgid "Activate storage locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:17 +msgid "In Odoo, cycle counts are location-based. Therefore, the *storage locations* feature needs to be enabled before performing a cycle count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:20 +msgid "To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Then, click the checkbox next to :guilabel:`Storage Locations`. Click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Enabled storage locations setting in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:29 +msgid "Change inventory count frequency by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:31 +msgid "Now that the storage locations setting is enabled, the inventory count frequency can be changed for specific locations created in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:34 +msgid "To view and edit locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. This reveals a :guilabel:`Locations` page containing every location currently created and listed in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:38 +msgid "From this page, click into a location to reveal the settings and configuration page for that location. Click :guilabel:`Edit` to edit the location settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:41 +msgid "Under the :guilabel:`Cyclic Inventory` section, locate the :guilabel:`Inventory Frequency (Days)` field, which should be set to `0` (if this location has not been edited previously). In this field, change the value to whichever number of days is desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Location frequency setting on location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:50 +msgid "A location that needs an inventory count every 30 days should have the :guilabel:`Inventory Frequency (Days)` value set to `30`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:53 +msgid "Once the frequency has been changed to the desired number of days, click :guilabel:`Save` to save changes. Now, once an inventory adjustment is applied to this location, the next scheduled count date is automatically set, based on the value entered into the :guilabel:`Inventory Frequency (Days)` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:59 +msgid "Count inventory by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:61 +msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in stock, with each product listed on its own line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:66 +msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at the top of the page, under the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:74 +msgid "To select a specific location and view all products within that location, click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to reveal a new drop-down menu to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:77 +msgid "Click :guilabel:`Location` from the drop-down menu, then click :guilabel:`Apply`. The page now displays condensed drop-down menus of each location in the warehouse that has products in stock, and a cycle count can be performed for all products in that location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:82 +msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right. Click this menu to reveal three drop-downs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:87 +msgid "For the first field, click and select :guilabel:`Location` from the drop-down. For the second field, leave the :guilabel:`contains` value as is. For the third field, type in the name of the location that is being searched for. Click :guilabel:`Apply` for that location to appear on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Applied filters and group by on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:97 +msgid "Change full inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:99 +msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of everything in-stock in the warehouse can also be manually changed to push the date up sooner than the date listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:103 +msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down that is set to `31` :guilabel:`December` by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 +msgid "Frequency field in inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:112 +msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:196 +msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:118 +msgid "Once all changes have been made, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:121 +msgid ":doc:`../inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:3 +msgid "Consignment: buy and sell stock without owning it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:5 +msgid "Most of the time, products stored in a company's warehouse are either purchased from suppliers, or are manufactured in-house. However, suppliers will sometimes let companies store and sell products in the company's warehouse, without having to buy those items up-front. This is called *consignment*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:10 +msgid "Consignment is a useful method for suppliers to launch new products, and easily deliver to their customers. It's also a great way for the company storing the products (the consignee) to earn something back for their efforts. Consignees can even charge a fee for the convenience of storing products they don't actually own." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:16 +msgid "Enable the consignment setting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:18 +msgid "To receive, store, and sell consignment stock, the feature needs to be enabled in the settings. To do this, go to :menuselection:`Inventory --> Configuration --> Settings`, and under the :guilabel:`Traceability` section, check the box next to :guilabel:`Consignment`, and then click :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 +msgid "Enabled Consignment setting in Inventory configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:28 +msgid "Receive (and store) consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:30 +msgid "With the feature enabled in Odoo, consignment stock can now be received into a warehouse. From the main :menuselection:`Inventory` dashboard, click into the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:35 +msgid "Consignment stock is not actually purchased from the vendor; it is simply received and stored. Because of this, there are no quotations or purchase orders involved in receiving consignment stock. So, *every* receipt of consignment stock will start by creating manual receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:39 +msgid "Choose a vendor to enter in the :guilabel:`Receive From` field, and then choose the same vendor to enter in the :guilabel:`Assign Owner` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:43 +msgid "Since the products received from the vendor will be owned by the same vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields must match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:46 +msgid "Once the vendor-related fields are set, enter products into the :guilabel:`Product` lines, and set the quantities to be received into the warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be changed, as well. Once all the consignment stock has been received, :guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 +msgid "Matching vendor fields in consignment Receipt creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:56 +msgid "Sell and deliver consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:58 +msgid "Once consignment stock has been received into the warehouse, it can be sold the same as any other in-stock product that has the :guilabel:`Can Be Sold` option enabled on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:61 +msgid "To create a sales order, navigate to the :menuselection:`Sales` app, and from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, choose a customer to enter into the :guilabel:`Customer` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:66 +msgid "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` that supplied the consignment stock received (and stored) in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:69 +msgid "Add the consignment product under the :guilabel:`Product` column in the order lines, set the :guilabel:`Quantity`, and fill out any other pertinent product details on the form. Once the quotation is complete, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 +msgid "Sales order of consignment stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:77 +msgid "Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will become a sales order. From here, the products can be delivered by clicking on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate` to validate the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:82 +msgid "Traceability and reporting of consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:84 +msgid "Although consignment stock is owned by the vendor who supplied it, and not by the company storing it in their warehouse, consignment products will *still* appear in certain inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:87 +msgid "To find inventory reports, go to :menuselection:`Inventory --> Reporting`, and choose a report to view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:91 +msgid "Since the consignee does not actually own consigment stock, these products are *not* reflected in the :guilabel:`Stock Valuation` report, and have no impact on the consignee's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:96 +msgid "Product moves report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:98 +msgid "To view all information about on-hand stock moves, navigate to the the :guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory --> Reporting --> Product Moves`. For consignment products, the information in this report is the same as any other product: the history of its product moves can be reviewed; the :guilabel:`Quantity Done` and :guilabel:`Reference` document are available; and its :guilabel:`Locations` are available, as well. The consignment stock will originate from :guilabel:`Partner Location/Vendors`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:106 +msgid "To view a consignment product's moves by ownership, select the :guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 +msgid "Consignment stock moves history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:115 +msgid "To see forecasted units of consignment stock, go to :menuselection:`Inventory --> Reporting --> Forecasted Inventory`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:119 +msgid "Stock on hand report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:121 +msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consigment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:3 +msgid "Putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:6 +msgid "What is a Putaway Rule?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:8 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:13 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:20 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:-1 +msgid "Activate Multi-Step Routes in Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:29 +msgid "Setting up a putaway rule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:31 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:35 +msgid "In this example, suppose there is one warehouse location, **WH/Stock**, with the following sub-locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:38 +msgid "WH/Stock/Pallets" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:40 +msgid "WH/Stock/Pallets/PAL1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:41 +msgid "WH/Stock/Pallets/PAL2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:42 +msgid "WH/Stock/Pallets/PAL3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:44 +msgid "WH/Stock/Shelf 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:46 +msgid "WH/Stock/Shelf 2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:48 +msgid "WH/Stock/Shelf 2/Small Refrigerator" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:50 +msgid "WH/Stock/Shelf 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:52 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:58 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:62 +msgid "Take the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:64 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:66 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:68 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:70 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:-1 +msgid "Some examples of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:77 +msgid "Using Storage Categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:79 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:86 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:91 +msgid "Create a Storage Category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:93 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:-1 +msgid "Create Storage Categories inside Odoo Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:102 +msgid "First, click :guilabel:`Create` and type a name for the storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:104 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:108 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:109 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:111 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:114 +msgid "Once the storage category settings are saved, the storage category can be linked to a location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:-1 +msgid "When a Storage Category is created, it can be linked to a warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:121 +msgid "Storage categories in putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:123 +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/warehouses_storage/advanced_operations_warehouse/putaway.rst:126 +msgid "Assume one pallet of lemonade cans is received:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:128 +msgid "If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:129 +msgid "If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:130 +msgid "If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:-1 +msgid "Storage Categories used in a variety of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:3 +msgid "Removal strategies (FIFO, LIFO, FEFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:7 +msgid "For companies with warehouses, **removal strategies** determine which products are taken from the warehouse, and when. Removal strategies are typically defined for specific picking operations. This helps companies to select the best products, optimize the distance workers need to travel when picking items for orders, and account for quality control, such as moving products with expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:13 +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." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:17 +msgid "When a product needs to be moved, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the :guilabel:`Removal Strategy` defined in either the :guilabel:`Product Category` or the :guilabel:`Location` dashboards." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:21 +msgid "To change the :guilabel:`Removal Strategy`, go to :menuselection:`Inventory app --> Configuration --> Locations` or :menuselection:`Product Categories`. Click on a :guilabel:`Location` or :guilabel:`Product Category`, and then click :guilabel:`Edit`. Change the product category :guilabel:`Force Removal Strategy` or the location :guilabel:`Removal Strategy` by clicking on the drop-down menu and selecting the desired removal strategy. After selecting the new removal strategy, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Change the Force Removal Strategy for either the Product Categories or Locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:33 +msgid "What happens inside the warehouse?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:35 +msgid "Most warehouses share the same important areas: receiving docks and sorting areas, storage locations, picking and packing areas, and shipping/loading docks. While all products entering or leaving the warehouse might go through each of these locations at some point, removal strategies can have an effect on which products are taken, from where, and when." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:40 +msgid "In this example below, vendor trucks unload pallets of goods at the receiving docks. Then, operators scan the products in the receiving area, with the reception date and expiration date. After that, products are stored in their respective storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:45 +msgid "Not all products have expiration dates, but in this example, expiration dates apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Products entering stock via the receiving area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:51 +msgid "In Odoo, receive products by navigating to the :menuselection:`Inventory` application, and in the kanban view, click on either the :guilabel:`Receipts` heading or :guilabel:`# TO PROCESS` button. On the :guilabel:`Receipts` dashboard, find and click on the individual receipt which will open the warehouse intake form. Click :guilabel:`Edit`, and then enter the received quantity in the :guilabel:`Done` column. To finish, :guilabel:`Validate` to receive the products and register them in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:59 +msgid "Receiving products can also be done within the Odoo *Barcode* application. If using the *Barcode* app, scan the product(s), update the quantity, and finally, click :guilabel:`Validate`. After products are received in Odoo, the products can then be moved to their respective storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:64 +msgid "Continuing with the same example, below, imagine several sales orders are made for the products received earlier, that use expiration dates. In this example, the products weren't received on the same day, and they don't have the same expiration date. In this situation, logically, sending products with the closest expiration date is preferred, instead of products received first or last. Using the chosen removal strategy configured for those products (in this example, :ref:`FEFO `), Odoo generates a transfer for the products with the soonest expiration date to the picking area, then the packing area, and finally, to the shipping docks for delivery to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Products being packed at the packing area for delivery, taking the expiration dates into\n" +"account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:79 +msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form. To learn more about picking and shipping, refer to either the :ref:`Two-step delivery ` or :ref:`Three-step delivery ` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:85 +msgid "How each removal strategy works" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:87 +msgid "Removal strategies determine which products are taken from the warehouse when orders are confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:90 +msgid "First In, First Out (FIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:92 +msgid "When using a :guilabel:`First In, First Out (FIFO)` strategy, demand for a product triggers a removal rule, which requests a transfer for the lot/serial number that entered the stock first (and therefore, has been in stock for the longest time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:96 +msgid "For example, imagine there are three lots of nails in the warehouse, and have the corresponding lot numbers: `00001`, `00002`, `00003`. Each lot has five boxes of nails in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:99 +msgid "Lot `00001` entered the stock on May 23, lot `00002` on May 25, and lot `00003` on June 1. A customer orders six boxes on June 11." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:102 +msgid "Using the :abbr:`FIFO (First In, First Out)` removal strategy, a transfer request will pick the five boxes from lot `00001` first, and then from the boxes in lot `00002`, since lot `00001` entered the stock first. The box from lot `00002` is taken next because it has the oldest receipt date after lot `00001`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "The detailed operations for the transfer shows the nail lots to be removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:112 +msgid "Last In, First Out (LIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:114 +msgid "Similar to the :abbr:`FIFO (First In, First Out)` method, the :guilabel:`Last In, First Out (LIFO)` removal strategy moves products based on the date they entered a warehouse's stock. Instead of removing the oldest stock on-hand, however, it targets the **newest** stock on-hand for removal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:118 +msgid "Every time an order for products with the :abbr:`LIFO (Last In, First Out)` method is placed, a transfer is created for the lot/serial number that has most recently entered the stock (the **last** lot/serial number that entered the warehouse's inventory)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:123 +msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy in banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:126 +msgid "For example, imagine there are three lots of boxes of screws in the warehouse, and have the corresponding lot numbers: `10001`, `10002`, and `10003`, each with 10 boxes of screws per lot." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:129 +msgid "Lot `10001` entered the stock on June 1, lot `10002` on June 3, and lot `10003` on June 6. A customer orders seven boxes on June 8." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:132 +msgid "Using the :abbr:`LIFO (Last In, First Out)` removal strategy, a transfer is requested for seven boxes of screws from lot `10003` because that lot is the last one to have entered the stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "The detailed operations shows which lots are being selected for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:140 +msgid "First Expired, First Out (FEFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:142 +msgid "While the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` methods target products for removal based on date of entry into the warehouse, the :guilabel:`First Expired, First Out (FEFO)` method targets products for removal based on their assigned expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:146 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy, every sales order that includes products with this removal strategy assigned ensures that transfers are requested for products with the expiration date soonest to the order date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:150 +msgid "As an example, imagine there are three lots of six-egg boxes. Those three lots have the following lot numbers: `20001`, `20002`, and `20003`, each with five boxes in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:153 +msgid "Lot `20001` entered the stock on July 1 and expires on July 15, lot `20002` entered on July 2 and expires on July 14, and lot `20003` entered on July 3 and expires on July 21. A customer orders six boxes on July 5." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:157 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` method, a transfer is requested for the five boxes from lot `20002` and one from lot `20001`. All the boxes in lot `20002` are transferred because they have the earliest expiration date. The transfer also requests one box from lot `20001` because it has the next closest expiration date after lot `20002`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "The detailed operations for the transfer shows the lots to be removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:167 +msgid "Using removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:169 +msgid "To differentiate some units of products from others, the units need to be tracked, either by :guilabel:`Lot` or by :guilabel:`Serial Number`. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Locations`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings. Click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid ":alt: Traceability settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid ":alt: Warehouse settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:183 +msgid "To use the :abbr:`FEFO (First Expired, First Out)` removal strategy, the :guilabel:`Expiration Dates` setting needs to be activated as well. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the checkbox next to :guilabel:`Expiration Dates`. Remember to click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:189 +msgid "Now, specific removal strategies can be defined on product categories. To do this, go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and choose a product category to define the removal strategy on. In the :guilabel:`Force Removal Strategy` field, choose a removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:194 +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/warehouses_storage/advanced_operations_warehouse/removal.rst:198 +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 `). 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/warehouses_storage/advanced_operations_warehouse/removal.rst:204 +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/warehouses_storage/advanced_operations_warehouse/removal.rst:213 +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/warehouses_storage/advanced_operations_warehouse/removal.rst:218 +msgid "Closest Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:220 +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/warehouses_storage/advanced_operations_warehouse/removal.rst:224 +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/warehouses_storage/advanced_operations_warehouse/removal.rst:230 +msgid "Use removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:232 +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/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Removal strategy on a product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:241 +msgid "To view all products with lots/serial numbers assigned to them, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. This reveals a page with drop-down menus of all products assigned lots or serial numbers, filtered by *product* by default. To change the category these products are filtered by, click :guilabel:`Product` (in the search bar, in the top right of the page) to remove the default filter, and select a new filter if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Click on Products, then Lots/Serial Numbers to display all the products with lots or serial\n" +"numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:252 +msgid "To view the serial numbers being selected for a sales order, go to the :guilabel:`Sales app` and select the sales order in question. In the sales order, click the :guilabel:`Delivery` smart button in the top right. In the :guilabel:`Operations` tab, click the :guilabel:`ā¦™ā‰£ (Detailed Operations)` icon in the far right for the product in question. The :guilabel:`Detailed Operations` window appears, and displays the lot or serial numbers selected for that specific product for the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:260 +msgid "FIFO (First In, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:262 +msgid "The :abbr:`FIFO (First In, First Out)` removal strategy implies that products which enter a warehouse's stock first are removed first. Companies should use this method if they are selling products with short demand cycles, such as clothes, to ensure they are not stuck with outdated styles in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:267 +msgid "In this example, there are three lots of white shirts. The shirts are from the *All/Clothes* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "View of the lots of white shirts in the inventory valuation report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:275 +msgid "Lot `000001` contains five shirts, lot `000002` contains three shirts, and lot `000003` contains two shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:278 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`White Shirt`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `6.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:285 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the oldest lot numbers will be reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy. All five shirts from lot `000001` and one shirt from lot `000002` will be selected to be sent to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Two lots being reserved for a sales order with the FIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:295 +msgid "LIFO (Last In, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:297 +msgid "The :abbr:`LIFO (Last In, First Out)` removal strategy works in the **opposite** manner from the :abbr:`FIFO (First In, First Out)` strategy. With this method, the products that are received **last** are moved out first. This method is mostly used for products without a shelf life, and no time-sensitive factors, such as expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:302 +msgid "In this example, there are three lots of cinder blocks. The blocks are from the *All/Building Materials* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "View of the lots of cinder blocks in the inventory valuation report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:310 +msgid "Lot `000020` contains three cinder blocks, lot `000030` contains five cinder blocks, and lot `0000400` contains four cinder blocks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:313 +msgid "To see how the :abbr:`LIFO (Last In, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (for this example, the :guilabel:`All/Building Materials` category) to edit. This reveals a product category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:318 +msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :guilabel:`Last In First Out (LIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Last in first out (LIFO) strategy set up as forced removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:325 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Cinder Block`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `5.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:332 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the newest lot numbers will be reserved thanks to the :abbr:`LIFO (Last In, First Out)` strategy. All four cinder blocks from lot `0000400` and one cinder block from lot `000030` will be selected to be sent to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Two lots being reserved for sale with the LIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:344 +msgid "FEFO (First Expired, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:346 +msgid "The :abbr:`FEFO (First Expired, First Out)` removal strategy differs from the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` strategies, because it targets products for removal based on **expiration dates** instead of their warehouse receipt dates. With this method, the products that are going to expire first are moved out first. This method is used for perishable products, such as medicine, food, and beauty products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:352 +msgid "Lots are picked based on their **removal date** from earliest to latest. Removal dates indicate how many days *before* the expiration date the product needs to be removed from stock. The removal date is set on the product form. Lots without a removal date defined are picked after lots with removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:358 +msgid "If products are not removed from stock when they should be, lots that are past the expiration date may still be picked for delivery orders!" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:362 +msgid "For more information about expiration dates, reference the :doc:`Expiration dates <../../product_management/product_tracking/expiration_dates>` document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:365 +msgid "First, go to :menuselection:`Inventory app --> Configuration --> Settings` and ensure :guilabel:`Expiration Dates` is enabled. Once the :guilabel:`Expiration Dates` setting is enabled, it's possible to define different expiration dates for individual serialized products, as well as for lot numbers containing many products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:370 +msgid "In this example, there are three lots of hand cream. The creams are from the *All/Health & Beauty* category, where *FEFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:374 +msgid "Lot `0000001` contains twenty tubes of hand cream, expiring on Sept 30, lot `0000002` contains ten tubes of hand cream, expiring on November 30, and lot `0000003` contains ten tubes of hand cream, expiring on October 31." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "View the hand cream lot numbers and expiration dates in the inventory report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:382 +msgid "Expiration dates can be entered when validating the received products, or set on products by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Click :guilabel:`Create`, enter the serial number, and select the product from the drop-down menu. Next, select the expiration date in the :guilabel:`Dates` tab. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "View of the removal date for 0000001." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:391 +msgid "To see how the :abbr:`FEFO (First Expired, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (in this example, the :guilabel:`All/Health & Beauty` category) to edit. This reveals a product category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:396 +msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :abbr:`FEFO (First Expired, First Out)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "FEFO forced removal strategy set on the product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:403 +msgid "Next, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Hand Cream`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (in this example, `25.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:410 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the lot numbers expiring first will be reserved thanks to the :abbr:`FEFO (First Expired, First Out)` strategy. All twenty tubes of hand cream from lot `0000001` and five from lot `0000003` will be selected to be sent to the customer, detailed in the :guilabel:`Detailed Operations` tab in the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 +msgid "Hand cream lot numbers selected for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:3 msgid "Sell stock from multiple warehouses using virtual locations" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:5 msgid "While keeping stock and selling inventory from one warehouse might work for smaller companies, bigger companies might need to keep stock in, or sell from, multiple warehouses in multiple locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:9 msgid "In Odoo, sometimes products included in a single sales order might take stock from two (or more) warehouses. In Odoo, pulling products from multiple warehouses to satisfy sales demands can be done by using *virtual locations*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:14 msgid "In order to create virtual locations in warehouses and proceed to the following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features will need to be enabled in the :menuselection:`Settings` app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:18 msgid "To do so, go to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` section, and click the checkboxes next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`. Then, :guilabel:`Save` the changes to finish." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:23 msgid "Create and configure a virtual parent location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:25 msgid "Before creating any virtual stock locations, a new warehouse will need to be created. This new warehouse will act as a *virtual* warehouse, and will be the *parent* location of other physical warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:31 msgid "Virtual warehouses are great for companies with multiple physical warehouses. This is because a situation might arise when one warehouse runs out of stock of a particular product, but another warehouse still has stock on-hand. In this case, stock from these two (or more) warehouses could be used to fulfill a single sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:36 msgid "The \"virtual\" warehouse acts as a single aggregator of all the inventory stored in a company's physical warehouses, and is used (for traceability purposes) to create a hierarchy of locations in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:58 +msgid "Create a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:43 msgid "To create a new warehouse, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse :guilabel:`Name` and :guilabel:`Short Name` can be changed, and other warehouse details can be changed under the :guilabel:`Warehouse Configuration` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:48 msgid "Under the :guilabel:`Shipments` heading, set the number of steps used to process :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` by selecting between the :guilabel:`1 step`, :guilabel:`2 steps`, and :guilabel:`3 steps` radio buttons. The desired option for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` will depend on the warehouse's procurement process, and might differ for individual products or product categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:55 -msgid ":doc:`How to choose the right flow to handle receipts and deliveries? `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:55 +msgid ":doc:`How to choose the right flow to handle receipts and deliveries? `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:58 msgid "Under the :guilabel:`Resupply` heading, configure the method(s) for how the warehouse resupplies its inventory:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:61 msgid ":guilabel:`Resupply Subcontractors`: resupply subcontractors with components from this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:62 msgid ":guilabel:`Manufacture to Resupply`: when products are manufactured, they can be manufactured in this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:64 msgid ":guilabel:`Manufacture`: to produce right away, move the components to the production location directly and start the manufacturing process; to pick first and then produce, unload the components from the stock to input location first, and then transfer it to the production location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:68 msgid ":guilabel:`Buy to Resupply`: when products are bought, they can be delivered to this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:69 msgid ":guilabel:`Resupply From`: automatically create routes to resupply this warehouse from another chosen warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:73 msgid "*Routes* can be set and configured directly from the :guilabel:`Warehouse` form, by clicking on the :guilabel:`Routes` smart button. Once the warehouse is configured, virtual *Locations* can be created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 msgid "The edit screen for creating a new warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:81 msgid "In order to apply this virtual warehouse as the *parent* location of two *child* location warehouses, there need to be two warehouses configured with physical stock locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid "**Parent Warehouse**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Location`: `VWH`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid "**Child Warehouses**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Locations`: `WHA/Stock` and `WHB/Stock`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:95 msgid "Create a virtual parent location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:98 msgid "In order to take stock from multiple warehouses to fulfill a sales order, there need to be at least **two** warehouses acting as *child locations* of the *virtual parent location* warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:101 msgid "To create and edit *Locations*, go to :menuselection:`Inventory --> Configuration --> Locations`. All :guilabel:`Locations` are listed here, including the *Stock* :guilabel:`Location` of the virtual warehouse that was created. Click into the *Stock* :guilabel:`Location` for the virtual warehouse that was previously created (:dfn:`Warehouse Name/Stock`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:106 msgid "Then, under the :guilabel:`Additional Information` section, change the :guilabel:`Location Type` from :guilabel:`Internal Location` to :guilabel:`View`. :guilabel:`Save` the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:109 msgid "This identifies this :guilabel:`Location` as a *virtual location*, which is used to create a hierarchical structure for a warehouse and aggregate its *child locations*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:113 msgid "Products can *not* be stored in a :guilabel:`View` :guilabel:`Location Type`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 msgid "Warehouse location types in location creation screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:120 msgid "Configure physical warehouse locations" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:122 msgid "Navigate back to the :guilabel:`Locations` overview (via the breadcrumbs), and remove any filters in the :guilabel:`Search Bar`. Then, click into the first physical warehouse :guilabel:`Location` that was previously created to be a *child location*, and click :guilabel:`Edit`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:126 msgid "Under :guilabel:`Parent Location`, select the virtual warehouse from the drop-down menu, and :guilabel:`Save` changes. Then, navigate back to the :guilabel:`Locations` overview, and repeat this step for the second physical warehouse stock location. Be sure to :guilabel:`Save` changes again." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:130 msgid "Both locations are now *child locations* of the virtual warehouse *parent location*. This allows stock to be taken from multiple locations to fulfill a single sales order, if there is not enough stock in any one location (provided they are both tied to the same virtual warehouse *parent location*)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:136 msgid "Example flow: Sell a product from a virtual warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:139 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:139 msgid "To sell products from multiple warehouses using a virtual *parent* location in this flow, there must be at least **two** products and at least **two** warehouses configured - with at least **one** product with quantity on-hand in each warehouse, respectively." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:143 msgid "To create a new request for quotation, or RFQ, navigate to the :menuselection:`Sales` app, and click :guilabel:`Create` from the :guilabel:`Quotations` overview. Fill out the information on the new quotation by adding a :guilabel:`Customer`, and click :guilabel:`Add a product` to add the two products stored in the two warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:148 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:148 msgid "Then, click the :guilabel:`Other Info` tab on the sales order form. Under the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field value listed to the virtual warehouse that was previously created. Once the warehouse has been changed, click :guilabel:`Confirm` to convert the quotation into a sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:153 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:153 msgid "Now that the quotation has been confirmed as a sales order, click the :guilabel:`Delivery` smart button. From the warehouse delivery form, confirm that the :guilabel:`Source Location` value matches the :guilabel:`Warehouse` field value from the sales order. Both should list the virtual warehouse location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:159 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:159 msgid "The :guilabel:`Source Location` on the warehouse delivery form and the :guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales order form *must* match in order for the products included in the sales order to be pulled from different warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:163 msgid "If the virtual warehouse is not the value in the :guilabel:`Source Location` field on the warehouse delivery form, then click :guilabel:`Edit`, make the change, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:166 msgid "If the virtual warehouse is not the value in the :guilabel:`Warehouse` field on the sales order, then a new quotation may need to be generated." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:168 msgid "If the :guilabel:`Warehouse` field is missing on the sales order form, then the virtual warehouse (and its children warehouses) may not have been set up correctly, in which case, review the documentation above again to make sure all settings/configuration were done properly." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 msgid "Delivery order with matching source and child locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:176 msgid "Finally, on the warehouse delivery form, under the :guilabel:`Detailed Operations` tab, confirm that the *Locations* values under the :guilabel:`From` column for each product matches to the *child locations* that are tied to the virtual *parent location*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:181 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:181 msgid "To view which *Locations* the products are coming from on the drop-down menus, click the :guilabel:`internal link (arrow)` icon to expand the *Location* information. If needed, it can be changed from here (granted there is quantity on hand for the product in that location)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:185 msgid "Once everything has been properly set, click :guilabel:`Validate` and then :guilabel:`Apply` to validate the delivery. Then, navigate back to the sales order form (via the breadcrumbs), and click :guilabel:`Create Invoice` to invoice for the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:190 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:190 msgid "To use a virtual *parent* location as the default warehouse for sales orders, each salesperson can have the virtual warehouse assigned to them from the drop-down menu next to :guilabel:`Default Warehouse` on their employee form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 msgid "Default warehouse location on employee form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:3 +msgid "Units of measure, packages, and packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:5 +msgid "In Odoo, there are a variety of ways to specify the amount of products being bought, stocked, and sold. *Units of measure*, *packages*, and *packagings* are all available to streamline inventory flows, allowing for a variety of configurations for products as they enter and leave the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:12 +msgid "Units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:14 +msgid "A *unit of measure (UoM)* refers to any of the different standards used to measure and handle a quantifiable amount of products, such a units, weight, time, or size. Different :abbr:`UoMs (Units of Measure)` for weight, for example, can be kilos, pounds, ounces, grams, and so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:18 +msgid "In Odoo, stock management and purchasing from suppliers are streamlined by specifying different :abbr:`UoMs (Units of Measure)` for both buying and selling products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:-1 +msgid "Specify unit of measure for selling a product vs purchasing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:25 +msgid "Once a product has a default :guilabel:`Unit of Measure` and :guilabel:`Purchase Unit of Measure` set on the product form, Odoo automatically converts the different units in the product's purchase/sales orders and the corresponding delivery orders/receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:29 +msgid "The only condition is that all of the units have to be in the *same category* (unit, weight, volume, length, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:33 +msgid "On the product form for `Rope`, the following fields are set as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:35 +msgid ":guilabel:`Unit of Measure` in `ft` (feet), and" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:36 +msgid ":guilabel:`Purchase Unit of Measure` in `cm` (centimeters)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:38 +msgid "Because the vendor sells rope in `cm`, the purchase :guilabel:`UoM` is used to represent the quantity on the :abbr:`PO (Purchase Order)`, which is also in centimeters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Display purchase order for the product, rope, in centimeters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:45 +msgid "After confirming the :abbr:`PO (Purchase Order)`, the quantity of product (found under the now visible :guilabel:`Demand` column) is converted from the purchase :abbr:`UoM (Unit of Measure)` to the :guilabel:`Unit of Measure`. Then, when the product is received by clicking the :guilabel:`Validate` button, the quantity in :guilabel:`Done` is automatically adjusted to match the :guilabel:`Demand` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:52 +msgid "On the *receipt* for `Rope`, the quantities are automatically converted from `500 cm` that was requested on the purchase order, to `16.40 ft` to match the internal/stock :guilabel:`Unit of Measure` value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Rope quantity is converted from cm to ft during warehouse reception." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:61 +msgid ":ref:`Use Different Units of Measure `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:66 +msgid "Packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:68 +msgid "Packages are a physical container that holds one or several products from a picking, typically used for outgoing deliveries or internal transfers. Packages can be a reusable or disposable (shipping) box, and are **not** specific to a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:72 +msgid "Reusable boxes temporarily hold products during a picking to be brought to either a packing or shipping area. Disposable boxes are the actual shipping containers (e.g. cardboard boxes, envelopes, shipping bags, etc). These are used to ship the products out to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:76 +msgid "Multiple items in a sales order (SO) can be separated into different packages to accommodate the products. For example, an :abbr:`SO (Sales Order)` that has 20 boxes of pencils and 4 boxes of erasers can be separated into two separate packages, each containing 10 boxes of pencils and 2 boxes of erasers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:82 +msgid "Products do *not* have to be divided equally. Products can be divided into as many packages that are needed to accommodate the :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:85 +msgid "In Odoo, the quantity of products in each package needs to be recorded, so there is a full history for each product, including which package each item is shipped out in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:88 +msgid "To use this method, ensure the :guilabel:`Packages` option is enabled, by navigating to :menuselection:`Inventory app --> Configuration --> Settings --> Operations`. Click the :guilabel:`Packages` check box, and then :guilabel:`Save` to activate the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:92 +msgid "On a delivery order, assign which package to use by clicking on the :guilabel:`ā‰£ (Detailed Operations)` icon to the right of each product in the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:-1 +msgid "Find detailed operations icon to the right on the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:99 +msgid "Clicking the :guilabel:`ā‰£ (Detailed Operations)` icon of a product reveals a pop-up window. In this window, the :guilabel:`Product` name, :guilabel:`Demand`, and :guilabel:`Quantity Done` are clearly displayed above the customizable product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:103 +msgid "Here, the warehouse location the product is coming from can be modified, in addition to the :guilabel:`Source Package` and :guilabel:`Destination Package`, which represents what package(s) the product(s) will be packaged into." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:107 +msgid "Click :guilabel:`Add a line` to include each additional package used. Enter the desired amount in the :guilabel:`Done` field to specify the amount of products that will go into the :guilabel:`Destination Package`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:112 +msgid "Multiple packages in a single delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:114 +msgid "Although a :abbr:`DO (Delivery Order)` is typically associated with a single package, orders can be split by clicking the :guilabel:`ā‰£ (Detailed Operations)` icon next to the products on an :abbr:`SO (Sales Order)` line. This opens the :guilabel:`Detailed Operations` window with an editable table to specify which products are intended for which package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:120 +msgid "To package 10 boxes of pencils with 2 boxes of erasers from the same :abbr:`SO (Sales Order)`, begin by navigating to the :abbr:`DO (Delivery Order)`. Then, select the :guilabel:`ā‰£ (four horizontal lines)` icon to the right of the product, `Box of Pencils`. Clicking the icon opens the :guilabel:`Detailed Operations` window that is used to detail how products, like the 20 `Box of Pencils`, are packaged." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:126 +msgid "Type in `10` under the :guilabel:`Done` field to package 10 products into the :guilabel:`Destination Package`. To specify the destination package, type the name of an existing package (such as `PACK0000006`) under the field, :guilabel:`Destination Package`. If the package does not exist, Odoo displays the :guilabel:`Create` button to create a new package. Click :guilabel:`Add a line` to assign the remaining products in another package, `PACK0000007`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Detailed operations pop-up where the amount of product going in a pack can be specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:136 +msgid "Select :guilabel:`Detailed Operations` on the product line for `Box of Erasers` and similarly set 2 :guilabel:`Done` products to `PACK0000006` and `PACK0000007` each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Put in pack button to match the done amount matches the demand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:143 +msgid "Once all the products for each line have been entered, click :guilabel:`Confirm` to return to the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:146 +msgid "The :guilabel:`Done` quantity on the :abbr:`DO (Delivery Order)` updates as products are selected for each package. When the :guilabel:`Done` amount matches the :guilabel:`Demand` amount, click the :guilabel:`Validate` button to complete the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:151 +msgid "The :guilabel:`Put In Pack` button is intended to quickly package all products in the :abbr:`DO (Delivery Order)` into one new package. The option to rename the package, or modify its contents, is available in the :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:155 +msgid "Clicking on the :guilabel:`Packages` smart button in the upper-right corner of the delivery order reveals a separate page, showing all the packages used in that :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:159 +msgid "Packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:161 +msgid "*Packaging* is product specific, and refers to a disposable container that holds several units of a specific product. Unlike packages, packagings cannot be reusable, and each specific packaging must be defined on the individual product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:165 +msgid "For example, different packages for cans of soda can be configured as a 6-pack, a 12-pack, or a case of 36. Each flavor of soda would need a `6`, `12`, and `36` can packaging configured on the individual product since packagings are product specific, not generic." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:170 +msgid "Set up packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:172 +msgid "To use packagings, ensure the :guilabel:`Product Packagings` feature is enabled. To do that, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Then, under the :guilabel:`Products` heading, check the box next to :guilabel:`Product Packagings`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:177 +msgid "In Odoo, product packagings are used on sales/purchase orders and inventory transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:179 +msgid "Next, to create packagings, navigate to :menuselection:`Inventory app --> Products --> Products` and click on the desired product, then click :guilabel:`Edit` on the product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:182 +msgid "Under the :guilabel:`Inventory` tab, scroll down to the :guilabel:`Packaging` section, and click :guilabel:`Add a line`. Then, a pop-up window appears, in which the following information for each packaging should be entered:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:186 +msgid ":guilabel:`Packaging`: name of packaging that appears on sales/purchase orders as a packaging option for the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:188 +msgid ":guilabel:`Contained quantity`: amount of product in the packaging" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:189 +msgid ":guilabel:`Barcode`: identifier used with the :ref:`Barcode app ` to trace the packaging of a product during stock moves or pickings. Leave blank if not in use" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:191 +msgid ":guilabel:`Company`: indicates the packaging is only available at the selected company. Leave blank to make the packaging available across all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:195 +msgid "Create a packaging type for 6 cans of the product, `Grape Soda`, by naming the :guilabel:`Packaging` to `6-pack` and setting the :guilabel:`Contained quantity` to `6` in the pop-up window that appears after clicking on :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Create 6-pack case for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:203 +msgid "When all the necessary information has been entered, either click :guilabel:`Save & Close` to save the packaging and return to the product detail form, or :guilabel:`Save & New` to save the packaging and create another one in a fresh pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:208 +msgid "View all product packagings in the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Show packaging and contained quantities, specified on the product page form in the\n" +"Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:216 +msgid "View all packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:218 +msgid "To view all packagings that have been created, go to :menuselection:`Inventory app --> Configuration --> Product Packagings`. Doing so reveals the :guilabel:`Product Packagings` page with a complete list of all packagings that have been created for all products. Create new packagings by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:224 +msgid "Two soda products, `Grape Soda` and `Diet Coke`, have three types of packaging configured. On the :guilabel:`Product Packagings` page, each product can sold as a `6-Pack` that contains 6 products, `12-Pack` of 12 products, or a `Case` of 32 products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "List of different packagings for products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:233 +msgid "Apply packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:235 +msgid "When creating a sales order in the :menuselection:`Sales` app, specify the packagings that should be used for the product(s). The chosen packaging is displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Package` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:240 +msgid "18 cans of the product, `Grape Soda`, is packed using three 6-pack packagings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Assign packagings on the Sales Order Line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:247 +msgid "Packaging can be used in conjunction with Odoo :ref:`Barcode `. When receiving products from suppliers, scanning the packaging barcode automatically adds the number of units in the packaging to the internal count of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:3 +msgid "Process wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:-1 +msgid "View of Odoo Inventory app settings to enable the wave transfers option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:30 +msgid "Add products to a wave" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:-1 +msgid "How to get an operation type's list of operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:-1 +msgid "Select lines to add to the wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:54 +msgid "After that, a pop-up box appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:64 +msgid "View wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/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/warehouses_storage/inventory_management.rst:5 +msgid "Inventory management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:3 +msgid "Inventory adjustments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:7 +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 damages, human errors, theft, 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/warehouses_storage/inventory_management/count_products.rst:14 +msgid "Inventory Adjustments page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:16 +msgid "To view the *Inventory Adjustments* page, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 +msgid "In stock products listed on the Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:23 +msgid "On the :guilabel:`Inventory Adjustments` page, all products that are currently in stock are listed, with each product line containing the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:26 +msgid ":guilabel:`Location`: the specific location in the warehouse where a product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:27 +msgid ":guilabel:`Product`: the product whose quantity is listed on the inventory adjustment line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:28 +msgid ":guilabel:`Lot/Serial Number`: the tracking identifier assigned to the specific product listed. It can contain letters, numbers, or a combination of both." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:32 +msgid "If a specific product has a quantity of more than `1.00` in stock, and more than one serial number (or lot number) assigned to it, each uniquely-identified product is displayed on its own product line with its own lot/serial number, displayed under the :guilabel:`Lot/Serial Number` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:37 +msgid ":guilabel:`On Hand Quantity`: the quantity of the product currently recorded in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:38 +msgid ":guilabel:`UoM`: the *unit of measure* in which the product is measured. Unless otherwise specified (i.e., in :guilabel:`Pounds` or :guilabel:`Ounces`), the default :abbr:`UoM (Unit of Measure)` is :guilabel:`Units`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:41 +msgid ":guilabel:`Counted Quantity`: the real quantity counted during an inventory count. This field is left blank by default, but can be changed, depending on if it matches the :guilabel:`On Hand Quantity` or not." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:44 +msgid ":guilabel:`Difference`: the difference between the :guilabel:`On Hand Quantity` and :guilabel:`Counted Quantity`, once an inventory adjustment is made. The difference is automatically calculated after every inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:47 +msgid ":guilabel:`Scheduled Date`: the date at which a count should be made. If not otherwise specified, this date will default to the 31st of December of the current year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:49 +msgid ":guilabel:`User`: the person assigned to the count in the database. This can either be the person physically counting the inventory, or applying the count in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:51 +msgid ":guilabel:`Product Category`: the category assigned internally to a specific product. Unless otherwise specified (i.e., as :guilabel:`Consumable` or :guilabel:`Rental`), the default *Product Category* is set to :guilabel:`All`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:54 +msgid ":guilabel:`Available Quantity`: the quantity of a specific product that is currently available, based on any outstanding/uncompleted sales orders, purchase orders, or manufacturing orders that might change the available quantity once fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:57 +msgid ":guilabel:`Accounting Date`: the date on which the adjustments will be accounted in the Odoo *Accounting* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:59 +msgid ":guilabel:`Company`: the company whose database these inventory adjustments are being made on. The company is listed in the top right corner of the database, next to the user currently logged in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:63 +msgid "Some columns are hidden by default. To reveal these columns, click the :guilabel:`additional options` button (three dots icon) to the far right of the form's top row, and select any desired column to reveal by clicking the checkbox next to that option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:68 +msgid "Create an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:70 +msgid "To create a new inventory adjustment from the :menuselection:`Inventory Adjustments` page, click :guilabel:`Create`. Doing so creates a new, blank inventory adjustment line at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:74 +msgid "On this blank inventory adjustment line, click the drop-down menu under the :guilabel:`Product` column, and select a product. If the selected product is tracked using either lots or serial numbers, the desired lot or serial number can also be chosen from the drop-down menu under the :guilabel:`Lot/Serial Number` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:79 +msgid "Next, set the value in the :guilabel:`Counted Quantity` column to the quantity counted for that product during the inventory adjustment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:83 +msgid "The :guilabel:`Counted Quantity` for new inventory adjustments is set to `0.00` by default. An inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the product's inventory adjustment history, so it should be set to reflect the actual quantity counted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:87 +msgid "To the right of the :guilabel:`Counted Quantity` column, the :guilabel:`Scheduled Date` and :guilabel:`User` can also be changed via their respective drop-down menus. Changing the :guilabel:`Scheduled Date` changes the date that the inventory adjustment should be processed on, and selecting a responsible :guilabel:`User` assigns a user to the specific inventory adjustment (for traceability purposes)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:93 +msgid "Once all changes have been made to the new inventory adjustment line, click away from the line. Doing so saves the adjustment, and moves the line to the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:158 +msgid "If the :guilabel:`Counted Quantity` is greater than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **green**. If the :guilabel:`Counted Quantity` is less than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **red**. If the quantities match, and haven't been changed at all, no value appears in the :guilabel:`Difference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 +msgid "Difference column on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:106 +msgid "At this stage, the count (:dfn:`inventory adjustment`) is recorded, but not yet applied. This means that the quantity on hand before the adjustment has not yet been updated to match the new, real counted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:110 +msgid "There are two ways to apply the new inventory adjustment. The first way is to click the :guilabel:`Apply` button on the line at the far right of the page. The second way is to click the checkbox on the far left of the line. Doing so reveals new button options at the top of the page, one of which is an :guilabel:`Apply` button. Clicking this button instead causes an :guilabel:`Inventory Adjustment Reference / Reason` pop-up window to appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:116 +msgid "From this pop-up menu, a reference or reason can be assigned to the inventory adjustment. By default, the :guilabel:`Inventory Reference / Reason` field is pre-populated with the date the adjustment is being made on, but can be changed to reflect whatever reference or reason is desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:120 +msgid "Once ready, click :guilabel:`Apply` to apply the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 +msgid "Apply all option applies the inventory adjustment once a reason is specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:127 +msgid "Count products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:129 +msgid "Counting products is a recurring activity in a warehouse. Once a count is complete, go to :menuselection:`Inventory app --> Operations --> Inventory Adjustments` to update the :guilabel:`Counted Quantity` column for each product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:133 +msgid "On each product line, identify whether the value in the :guilabel:`On Hand Quantity` column recorded in the database matches the newly-counted value. If the recorded value and the counted value do match, click the :guilabel:`Set` button (target icon) at the far right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:137 +msgid "Doing so copies the value from the :guilabel:`On Hand Quantity` column over to the :guilabel:`Counted Quantity` column, and sets the value of the :guilabel:`Difference` column to `0.00`. Subsequently, once applied, an inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 +msgid "Zero count inventory adjustment move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:146 +msgid "If the newly-counted value for a given product does **not** match the value in the :guilabel:`On Hand Quantity` recorded in the database, instead of clicking the :guilabel:`Set` button, record the real value in the field in the :guilabel:`Counted Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:150 +msgid "To do so, click the field in the :guilabel:`Counted Quantity` column on the specific inventory adjustment line for the product whose count is being changed. This automatically assigns a :guilabel:`Counted Quantity` of `0.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:154 +msgid "To change this value, type in a new value that matches the real, newly-counted value. Then, click away from the line. Doing so saves the adjustment, and automatically adjusts the value in the :guilabel:`Difference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:164 +msgid "Subsequently, once applied, a move with the difference between the :guilabel:`On Hand Quantity` and the :guilabel:`Counted Quantity` is recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 +msgid "Inventory Adjustments History dashboard detailing a list of prior product moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:172 +msgid "Sometimes a count occurs, but cannot 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 on-hand quantity in the database can change and no longer be consistent with the counted quantity. As an extra precaution, Odoo asks for confirmation before applying the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:179 +msgid "Change inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:181 +msgid "By default, the *scheduled date* for inventory adjustments are always scheduled for the 31st of December of the current year. However, for some companies, it is crucial that they have an accurate inventory count at all times. In such cases, the default scheduled date can be modified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:185 +msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting, which includes a drop-down menu that is set to `31 December` by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 +msgid "Adjust the next inventory count date with the Annual Inventory Day and Month setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:193 +msgid "To change the day, click the :guilabel:`31`, and change it to a day within the range `1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:199 +msgid "Once all desired changes have been made, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:202 +msgid "Plan big inventory counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:204 +msgid "To plan big inventory counts, such as a full count of everything currently in stock, first navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:207 +msgid "Then, select the desired products to be counted by clicking the checkbox on the far left of each product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:211 +msgid "To request a count of **all** products currently in stock, click the checkbox at the very top of the table, in the header row next to the :guilabel:`Location` label. This selects **all** product lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 +msgid "Request a count popup on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:219 +msgid "Once all desired products have been selected, click the :guilabel:`Request a Count` button at the top of the page. This causes a :guilabel:`Request a Count` pop-up window to appear. From this pop-up, fill in the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:223 +msgid ":guilabel:`Inventory Date`: the planned date of the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:224 +msgid ":guilabel:`User`: the user responsible for the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:225 +msgid ":guilabel:`Accounting Date`: the date at which the inventory adjustment will be accounted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:226 +msgid ":guilabel:`Count`: to leave the on-hand quantity of each product line blank, select :guilabel:`Leave Empty`. To prefill the 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/warehouses_storage/inventory_management/count_products.rst:230 +msgid "Finally, once ready, click :guilabel:`Confirm` to request the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:233 +msgid "In the Odoo *Barcode* app, users can only view inventory counts that are assigned to **them**, and are scheduled for **today** or **earlier**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:237 +msgid ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:3 +msgid "Create a second warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:5 +msgid "A *warehouse* is a physical building or space where items are stored. In Odoo, it is possible to set up multiple warehouses and transfer stored items between them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:8 +msgid "By default, the Odoo platform has one warehouse that is already configured, with the address set as the company's address. To create a second warehouse, select :menuselection:`Configuration --> Warehouses`, then click :guilabel:`Create` and configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:12 +msgid ":guilabel:`Warehouse`: the full name of the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:13 +msgid ":guilabel:`Short Name`: the abbreviated code by which the warehouse is referred to; the short name for the default warehouse in Odoo is **WH**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:15 +msgid ":guilabel:`Company`: the company that owns the warehouse; this can be set as the company that owns the Odoo database or the company of a customer or vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:17 +msgid ":guilabel:`Address`: the address where the warehouse is located" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:20 +msgid "The options below will only appear if the :guilabel:`Multi-Step Routes` checkbox is enabled in :menuselection:`Configuration --> Settings` under the :guilabel:`Warehouse` heading. For more information about routes and how they work in Odoo, see :ref:`Using Routes and Pull/Push Rules `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:25 +msgid ":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and outgoing shipments should follow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:27 +msgid ":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied from this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:28 +msgid ":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:29 +msgid ":guilabel:`Manufacture`: select the route that should be followed when manufacturing goods inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:31 +msgid ":guilabel:`Buy to Resupply`: check the box to allow for purchased products to be delivered to the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:33 +msgid ":guilabel:`Resupply From`: select warehouses that can be used to resupply the warehouse being created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 +msgid "A filled out form for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:41 +msgid "Creating a second warehouse will automatically enable the *Storage Locations* setting, which allows location tracking of products within a warehouse. To toggle this setting, navigate to :menuselection:`Configuration --> Settings` and click the checkbox under the :guilabel:`Warehouse` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:46 +msgid "After filling out the form, click :guilabel:`Save` and the new warehouse will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:49 +msgid "Add inventory to a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:51 +msgid "If a new warehouse is created that has existing inventory in it, the inventory counts should be added to Odoo so that the stock listed in the Odoo database reflects what is in the physical warehouse. To add inventory to a new warehouse, navigate to :menuselection:`Inventory --> Operations --> Inventory Adjustments`, and then click :guilabel:`Create`. The inventory adjustment form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:57 +msgid ":guilabel:`Inventory Reference`: the name or code that the inventory adjustment can be referred to by" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:59 +msgid ":guilabel:`Locations`: the location(s) where the inventory is stored; include the new warehouse and any locations within it that inventory will be added to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:61 +msgid ":guilabel:`Products`: include all products that will be added to inventory or leave blank to select any product during the next step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:63 +msgid ":guilabel:`Include Exhausted Products`: include products with a quantity of zero; does not affect inventory adjustments for new warehouses since they have no existing inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:65 +msgid ":guilabel:`Accounting Date`: the date used by accounting teams for bookkeeping related to the inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:67 +msgid ":guilabel:`Company`: the company that owns the inventory; can be set as the user's company or as a customer or vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:69 +msgid ":guilabel:`Counted Quantities`: choose whether the counted quantities for products being added should default to stock on hand or zero; does not affect inventory adjustments for new warehouses since they have no existing inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 +msgid "A filled out form for an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:77 +msgid "Once the form is properly configured, click on :guilabel:`Start Inventory` to be taken to the next page where products can be added to the inventory adjustment. Add a new product by clicking on :guilabel:`Create` and then fill out the product line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:81 +msgid ":guilabel:`Product`: the product being added to inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:82 +msgid ":guilabel:`Location`: the location where the product is currently stored in the new warehouse; this can be set as the overall warehouse or a location within the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:84 +msgid ":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the serial number used to identify it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:86 +msgid ":guilabel:`On Hand`: the total quantity of the product stored in the location for which inventory is being adjusted; this should be zero for a new location or warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:88 +msgid ":guilabel:`Counted`: the amount of the product that is being added to inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:89 +msgid ":guilabel:`Difference`: the difference between the *On Hand* and *Counted* values; this will automatically update to reflect the value entered in the :guilabel:`Counted` column" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:91 +msgid ":guilabel:`UoM`: the unit of measure used for counting the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 +msgid "Include a line for each product being added to inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:97 +msgid "After adding all the products already stored in the new warehouse, click :guilabel:`Validate Inventory` to complete the inventory adjustment. The values in the :guilabel:`On Hand` column will update to reflect those in the :guilabel:`Counted` column and the products added will appear in the inventory of the new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:3 +msgid "Resupply from another warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/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/warehouses_storage/inventory_management/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/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 +msgid "Enable Multi-Step Routes in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:21 +msgid "View all the configured warehouses by going to :menuselection:`Inventory --> Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/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/warehouses_storage/inventory_management/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/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 +msgid "Supply one warehouse with another in the Warehouse Configuration tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:39 +msgid "Set route on a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/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/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 +msgid "Route setting which enables a product to resupplied from a second warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/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/warehouses_storage/inventory_management/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/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 +msgid "A reordering rule automatically creates two receipts for stock between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 +msgid "A warehouse order for resupplying one warehouse's stock with another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 +msgid "A receipt for stock received to one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 +msgid "Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:5 +msgid "A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc. There are three types of locations in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 +msgid "*Physical locations* are spaces within a warehouse owned by the user's company. These can be a an area where items are stored like an aisle or shelf, or an area where operations take place, like loading and unloading bays." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:11 +msgid "*Partner locations* are the same as physical locations except that they exist within the warehouse of a customer or vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:13 +msgid "*Virtual locations* are locations that do not exist physically, but where items that are not in inventory can be placed. These can be items that have not yet entered inventory, like products that are on the way to a warehouse, or items that are no longer in inventory due to loss or other factors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:19 +msgid "In order to use locations, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` heading, and enable the :guilabel:`Storage Locations` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:24 +msgid "Create a new location inside a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 +msgid "Starting from the :menuselection:`Inventory` app, select :menuselection:`Configuration --> Locations --> Create`. The new location form can then be configured as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:29 +msgid ":guilabel:`Location Name`: the name that will be used to reference the location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:30 +msgid ":guilabel:`Parent Location`: the location or warehouse that the new location exists within" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:31 +msgid ":guilabel:`Location Type`: choose the category that the location belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:32 +msgid ":guilabel:`Company`: the company that owns the warehouse that the location is inside of" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 +msgid ":guilabel:`Is a Scrap Location?`: check this box to allow for scrapped/damaged goods to be stored in this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 +msgid ":guilabel:`Is a Return Location?`: check this box to allow products to be returned to this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:37 +msgid ":guilabel:`Barcode`: the barcode number assigned to the location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:38 +msgid ":guilabel:`Removal Strategy`: the :ref:`strategy ` for how items should be taken from inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 +msgid "The form for creating a new location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:46 +msgid "Create location hierarchies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 +msgid "The *Parent Location* setting on the new location form allows for a location to exist within a warehouse or another location. Every location can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a virtually infinite hierarchical structure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:54 +msgid "Location hierarchy could be organized so that a shelf is located within an aisle, which is located within a room, which is located within the overall warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:57 +msgid "To create the location hierarchy in the example above, set the warehouse as the parent of the room, the room as the parent of the aisle, and the aisle as the parent of the shelf. This can be adapted to a hierarchy of any magnitude." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 msgid "Routes and Pull/Push Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:7 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:11 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:11 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/warehouses_storage/inventory_management/use_routes.rst:16 msgid "Inside the warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:18 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a generic warehouse with stock and quality control area." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:27 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a generic push to rule when receiving products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:36 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a generic pull from rule when preparing deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:47 msgid "Pull rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:49 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:52 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:52 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:56 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:56 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:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:59 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:65 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:65 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:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:71 msgid "Push rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:73 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:77 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:77 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:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:81 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:85 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:85 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:89 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:89 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:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:97 msgid "Use routes and rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:99 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:102 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:102 msgid "Manage product manufacturing chains." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:103 msgid "Manage default locations per product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:104 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:106 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:106 msgid "Help rental management by generating automated return moves for rented products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:108 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "Activate the Multi-Step Routes feature in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:117 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:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:120 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:124 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:124 msgid "Pre-configured routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:126 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "A preconfigured warehouse in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:135 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of all the preconfigured routes Odoo offers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:144 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a route example applicable on product categories and warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:154 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "An example of rules with push & pull actions in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:163 msgid "Custom Routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:165 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a pick-pack-ship route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:173 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:176 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:176 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:181 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:181 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a route applied to the \"all\" product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:189 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 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:197 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:197 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:201 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:201 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of the menu allowing to add new lines to sales orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:208 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:208 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:211 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:211 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a product form, where the route must be selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:220 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:220 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:223 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:223 msgid "Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:225 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of the rules menu, where it is possible to add new rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:233 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:233 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:236 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:236 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:240 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:240 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:243 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:243 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:248 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:248 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:250 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:250 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 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:258 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:258 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:261 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:261 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:265 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:265 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:267 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:267 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:269 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:269 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:273 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:273 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:277 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:277 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:281 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:281 msgid "Sample full route flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:283 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:283 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:286 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:286 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:289 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:289 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:292 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:292 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:295 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:295 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "Overview of all the transfers created by the pick - pack - ship route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:303 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:303 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of the operations created by a pull from transfer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:311 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:311 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 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:319 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:319 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of the detailed operations for a transfer between the packing and output zones." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:326 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:326 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of the detailed operations for a transfer between the stock and packing zones." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:333 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:333 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:338 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:338 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:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of the transfers' statuses when the route is completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies.rst:5 -msgid "Putaway & Removal Strategies" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:3 +msgid "Transfer products between warehouses using replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:3 -msgid "Putaway rules" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:5 +msgid "For companies that use multiple warehouses, it is often necessary to transfer items between them. This is referred to as an *inter-warehouse transfer*. Odoo *Inventory* handles the administrative process of inter-warehouse transfers to ensure that inventory counts remain accurate during and after the transfer. This document will detail the method for conducting an inter-warehouse transfer using replenishment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:6 -msgid "What is a Putaway Rule?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:12 +msgid "Configure warehouses for inter-warehouse replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:8 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:14 +msgid "First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by navigating to :menuselection:`Inventory --> Configuration --> Settings`, and then check the box under the :guilabel:`Warehouse` tab. This will provide additional configuration options when creating a second warehouse that are needed for inter-warehouse replenishment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:13 -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/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:19 +msgid "By default, Odoo comes with a main warehouse already configured. If an additional warehouse has not already been created, do so now from the :guilabel:`Inventory` module by selecting :menuselection:`Configuration --> Warehouses --> Create`. Otherwise, select the warehouse that products will be transferred to from the :guilabel:`Warehouses` page and then click :guilabel:`Edit` to change its settings. Configure the warehouse as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:20 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:25 +msgid ":guilabel:`Warehouse`: choose a name that is not already being used for another warehouse (e.g. `Alternative Warehouse`)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 -msgid "Activate Multi-Step Routes in Inventory configuration settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:27 +msgid ":guilabel:`Short Name`: choose a short name by which the warehouse will be identified (e.g. `ALT_WH`)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:29 -msgid "Setting up a putaway rule" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:30 +msgid "Click :guilabel:`Save` and the new warehouse will be created. In addition, a new :guilabel:`Resupply From` field will appear on the warehouse's form. Click :guilabel:`Edit` and then check the box next to the warehouse that will be used to resupply the warehouse that is currently being configured." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:31 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 +msgid "A warehouse settings form configured to allow resupplying between warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:35 -msgid "In this example, suppose there is one warehouse location, **WH/Stock**, with the following sub-locations:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:39 +msgid "For the purposes of this demonstration, the warehouse that products are transferred from (outgoing) will be titled \"San Francisco\", and the warehouse that products are transferred to (incoming) will be titled \"San Francisco 2\"." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:38 -msgid "WH/Stock/Pallets" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:44 +msgid "Configure products for inter-warehouse replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:40 -msgid "WH/Stock/Pallets/PAL1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:46 +msgid "Products must also be configured properly in order for them to be transferred between warehouses. Navigate to :menuselection:`Inventory --> Products --> Products` and select an existing product or :guilabel:`Create` a new one, if necessary." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:41 -msgid "WH/Stock/Pallets/PAL2" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:50 +msgid "Then, on the product form, go to the :guilabel:`Inventory` tab and enable the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the warehouse receiving the transferred products and *Y* being the warehouse that products are transferred from." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:42 -msgid "WH/Stock/Pallets/PAL3" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 +msgid "Enable the checkbox to resupply one warehouse from another." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:44 -msgid "WH/Stock/Shelf 1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:59 +msgid "Replenish one warehouse from another" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:46 -msgid "WH/Stock/Shelf 2" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:61 +msgid "Starting in the :menuselection:`Inventory` module, select :menuselection:`Products --> Products` and then choose the product that will be replenished. Click the :guilabel:`Replenish` button on the top left of the product page and fill out the pop-up form as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:48 -msgid "WH/Stock/Shelf 2/Small Refrigerator" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:65 +msgid ":guilabel:`Quantity`: the number of units that will be sent to the warehouse being replenished" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:50 -msgid "WH/Stock/Shelf 3" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:66 +msgid ":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to take place" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:52 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:67 +msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:58 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:68 +msgid ":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* being the warehouse to be replenished and *Y* being the warehouse that the product will be transferred from" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:62 -msgid "Take the following example:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 +msgid "The form for replenishing a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:64 -msgid "If water (category All/drinks) is received, whatever the package, it will be redirected to WH/Stock/Shelf 2/Small Refrigerator." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:75 +msgid "Click :guilabel:`Confirm` and a delivery order will be created for the outgoing warehouse along with a receipt for the warehouse that will receive the product. Depending on the configuration settings for the outgoing and incoming warehouses, processing delivery orders and receipts will require between one and three steps. This document will detail how to process one-step deliveries and receipts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:66 -msgid "If orange juice cans, packaged in boxes, are received, they will be redirected to WH/Stock/Shelf 2." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:82 +msgid "Process the delivery order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:68 -msgid "If water or apple juice bottles, packaged in boxes, are received, they will be redirected to WH/Stock/Shelf 3." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:84 +msgid "The first stage of a replenishment order is processing the delivery from the warehouse that the product is being transferred from. On the :menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, then the delivery order created for the replenishment. On the delivery order page, click the :guilabel:`Check Availability` button in the top left to reserve the quantity of the product to be transferred. Once the delivery has been dispatched, click the :guilabel:`Validate` button to register the quantities shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:70 -msgid "If a pallet of lemonade cans are receieved, it will be redirected to WH/Stock/Pallets/PAL1." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 +msgid "The delivery orders card for the outgoing warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 -msgid "Some examples of putaway rules." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:99 +msgid "Once the goods arrive at the incoming warehouse, the receipt created for that warehouse must be processed as well. Return to the :menuselection:`Inventory` dashboard and select the :guilabel:`X to Process` button on the :guilabel:`Receipts` card for the incoming warehouse, then the receipt created for the replenishment. On the receipt page, click the :guilabel:`Validate` button in the top left of the page to register the quantities received." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:77 -msgid "Using Storage Categories" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:109 +msgid "After processing the receipt, the products transferred will now appear in the inventory of the incoming warehouse. The stock numbers for both warehouses can be viewed by returning to the product page and selecting the :guilabel:`X Units On Hand` button at the top of the screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:79 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:114 +msgid "Automate inter-warehouse replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:86 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:116 +msgid "Using reordering rules, it is possible to automate the process of replenishing one warehouse from another." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:91 -msgid "Create a Storage Category" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:119 +msgid "To get started, navigate to :menuselection:`Inventory --> Products --> Products`, and then choose the product that will be replenished. From the product page, select the :guilabel:`Reordering Rules` smart button at the top of the form, and then on the next page, click :guilabel:`Create` to configure the form as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:93 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:124 +msgid ":guilabel:`Location`: the location that the reordering rule will replenish when triggered, in this case, the incoming warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 -msgid "Create Storage Categories inside Odoo Inventory configuration settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:126 +msgid ":guilabel:`Min Quantity`: when the quantity on hand at the incoming warehouse falls below this number, the reordering rule will be triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:102 -msgid "First, click :guilabel:`Create` and type a name for the storage category." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:128 +msgid ":guilabel:`Max Quantity`: when the reordering rule is triggered, the product will be replenished at the incoming warehouse up to this quantity" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:104 -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:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:130 +msgid ":guilabel:`Multiple Quantity`: specify if the product should be replenished in batches of a certain quantity; for example, a product could be replenished in batches of 20" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:108 -msgid ":guilabel:`If location is empty`: a product can be added there only if the location is empty." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:132 +msgid ":guilabel:`UoM`: the unit of measure used for reordering the product; this value can simply be `Units`, or a specific unit of measurement for weight, length, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:109 -msgid ":guilabel:`If products are the same`: a product can be added there only if the same product is already there." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 +msgid "A fully configured reordering rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:111 -msgid ":guilabel:`Allow mixed products`: several different products can be stored in this location at the same time." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:139 +msgid "Finish by clicking :guilabel:`Save` and the reordering rule will be created. Now, when the scheduler runs automatically each day, a transfer will be created for each reordering rule that has been triggered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:114 -msgid "Once the storage category settings are saved, the storage category can be linked to a location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:144 +msgid "To manually trigger reordering rules, start from the :menuselection:`Inventory` module and select :menuselection:`Operation --> Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the pop-up that appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 -msgid "When a Storage Category is created, it can be linked to a warehouse location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:148 +msgid "After the scheduler runs, a delivery order and receipt will be created for the outgoing and incoming warehouses, respectively. Both the delivery order and receipt should be processed using the same method as detailed above." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:121 -msgid "Storage categories in putaway rules" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:3 +msgid "Manage Warehouses and Locations" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:123 -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:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:9 +msgid "Warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:126 -msgid "Assume one pallet of lemonade cans is received:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/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/routes/strategies/putaway.rst:128 -msgid "If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:19 +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/routes/strategies/putaway.rst:129 -msgid "If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:24 +msgid "There are three types of locations:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:130 -msgid "If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:26 +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/routes/strategies/putaway.rst:-1 -msgid "Storage Categories used in a variety of putaway rules." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:30 +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/routes/strategies/removal.rst:3 -msgid "What is a Removal Strategy (FIFO, LIFO, FEFO, Closest location)?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:34 +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/routes/strategies/removal.rst:5 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:39 +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/routes/strategies/removal.rst:9 -msgid "When a product movement needs to be done, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the *Removal Strategy* defined in the *Product Category* or on the *Location*." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:46 +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/routes/strategies/removal.rst:14 -msgid "What happens inside the warehouse?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 +msgid "Enable the storage location feature in Odoo Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:16 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:54 +msgid "To manage several routes within the warehouses, also enable :guilabel:`Multi-Step Routes` and check :doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Empty stock waiting for deliveries at the docks." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:60 +msgid "To create a warehouse, go to :menuselection:`Configuration --> Warehouse Management --> Warehouses` and click on :guilabel:`Create`." 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 reception date and, if the product has an expiration date, the expiration date. After that, products are stored in their respective locations." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:63 +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/routes/strategies/removal.rst:-1 -msgid "Products entering stock via the receiving area." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 +msgid "Short name field of a warehouse on Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:32 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:71 +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/routes/strategies/removal.rst:-1 -msgid ":alt: Products being packed at the packing area for delivery, taking expiration dates into\n" -"account." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:74 +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/routes/strategies/removal.rst:43 -msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 +msgid "Inventory app dashboard displaying new transfer types for the recently created warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:46 -msgid "How does it work?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:82 +msgid "Adding a second warehouse will automatically activate the :guilabel:`Locations` setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:49 -msgid "First In, First Out (FIFO)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:85 +msgid "Create a new location" msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:87 +msgid "To create a location, go to :menuselection:`Configuration --> Warehouse Management --> Locations` and click on :guilabel:`Create`." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:90 +msgid "Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location` and click :guilabel:`Save`." msgstr "" -#: ../../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`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 +msgid "Create a new warehouse location in Odoo Inventory." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation.rst:5 +msgid "Inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:69 -msgid "Last In, First Out (LIFO)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:3 +msgid "Integrating additional costs to products (landed costs)" msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:7 +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/routes/strategies/removal.rst:76 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:13 +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/routes/strategies/removal.rst:80 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 +msgid "Activate the landed cost feature in Inventory settings." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:22 +msgid "Add costs to products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:89 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:25 +msgid "Receive the vendor bill" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:93 -msgid "First Expire, First Out (FEFO)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:27 +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/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 +msgid "Enable Landed Costs option on vendor bill line." msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:35 +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/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`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:39 +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/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:45 +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/routes/strategies/removal.rst:117 -msgid "Closest Location" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 +msgid "Option to define a product as a landed cost." 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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:52 +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/routes/strategies/removal.rst:123 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 +msgid "Use a warehouse transfer to cover a landed cost in the accounting journal." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:129 -msgid "Use removal strategies" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:64 +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/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:68 +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/routes/strategies/removal.rst:-1 -msgid "Features to enable in order to properly use removal strategies." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:72 +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/routes/strategies/removal.rst:141 -msgid "To work with the :abbr:`FEFO (First Expired, First Out)` strategy, also activate the :guilabel:`Expiration Dates` feature." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 +msgid "Landed cost journal entry" msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:80 +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/routes/strategies/removal.rst:-1 -msgid "Force removal strategy set up as first in first out." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:3 +msgid "Inventory valuation configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:152 -msgid "FIFO (First In, First Out)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:7 +msgid "All of a company's stock on-hand contributes to the valuation of its inventory. That value should be reflected in the company's accounting records to accurately show the value of the company and all of its assets." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:154 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:11 +msgid "By default, Odoo uses a periodic inventory valuation (also known as manual inventory valuation). This method implies that the accounting team posts journal entries based on the physical inventory of the company, and that warehouse employees take the time to count the stock. In Odoo, this method is reflected inside each product category, where the :guilabel:`Costing Method` field will be set to `Standard Price` by default, and the :guilabel:`Inventory Valuation` field will be set to `Manual`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 +msgid "The Inventory Valuation fields are located on the Product Categories form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "View of the white shirt lots inventory valuation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:22 +msgid "Alternatively, automated inventory valuation is an integrated valuation method that updates the inventory value in real-time by creating journal entries whenever there are stock moves initiated between locations in a company's inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:166 -msgid "Lot :guilabel:`000001` contains five shirts, :guilabel:`000002` contains three shirts, and :guilabel:`000003` contains two shirts." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:27 +msgid "Automated inventory valuation is a method recommended for expert accountants, given the extra steps involved in journal entry configuration. Even after the initial setup, the method will need to be periodically checked to ensure accuracy, and adjustments may be needed on an ongoing basis depending on the needs and priorities of the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:35 +msgid "Types of accounting" msgstr "" -#: ../../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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:37 +msgid "Accounting entries will depend on the accounting mode: *Continental* or *Anglo-Saxon*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Two lots being reserved for a sales order with the FIFO strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:40 +msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:180 -msgid "LIFO (Last In, First Out)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:43 +msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. *Interim Stock Accounts* are used for the input and output accounts, and are both *Asset Accounts* in the balance sheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:182 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:48 +msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Additionally, a single *Expense* account is used for both input and output accounts in the balance sheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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)`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:55 +msgid "Costing methods" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Last in first out strategy set up as forced removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:57 +msgid "Below are the three costing methods that can be used in Odoo for inventory valuation." msgstr "" -#: ../../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`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:59 +msgid "**Standard Price**: is the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Two lots being reserved for sale with the LIFO strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:63 +msgid "**Average Cost (AVCO)**: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:201 -msgid "Don't forget that the :abbr:`LIFO (Last In, First Out)` strategy is banned in many countries!" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:66 +msgid "**First In First Out (FIFO)**: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it's highly sensitive to input data and human error." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:204 -msgid "FEFO (First Expired, First Out)" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:74 +msgid "Changing the costing method greatly impacts inventory valuation. It's highly recommended to consult an accountant first before making any adjustments here." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:78 +msgid "Configure automated inventory valuation in Odoo" 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>`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:80 +msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory --> Configuration --> Product Categories`, and choose the category/categories where the automated valuation method should apply." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:85 +msgid "It is possible to use different valuation settings for different product categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "View of the removal date for 0000001." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:87 +msgid "Under the :guilabel:`Inventory Valuation` heading are two labels: :guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the desired :guilabel:`Costing Method` using the drop-down menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to :guilabel:`Automated`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:93 +msgid ":ref:`Using the inventory valuation`" 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!" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:96 +msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:102 +msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "View of the FEFO strategy being set up as forced removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 +msgid "On the same screen, the :guilabel:`Account Stock Properties` fields will appear, as they are now required fields given the change to automated inventory valuation. These accounts are defined as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:238 -msgid "For this particular case, the stock has hand cream. There are three lots of them." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:112 +msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 -msgid "**Lot / Serial No**" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 +msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 -msgid "**Product**" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:118 +msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 -msgid "**Expiration Date**" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:124 +msgid "Access reporting data generated by inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 -msgid "0000001" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:126 +msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:131 +msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 -msgid "09/30/2019" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:135 +msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 -msgid "0000002" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 +msgid "See the full inventory valuation breakdown in Odoo Accounting app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 -msgid "11/30/2019" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:3 +msgid "Using inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 -msgid "0000003" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:7 +msgid "*Inventory valuation* is a quintessential accounting procedure that calculates the value of on-hand stock. Once determined, the inventory valuation amount is then incorporated into a company's overall value." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 -msgid "10/31/2019" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:11 +msgid "In Odoo, this process can be conducted manuallyā€” by warehouse employees physically counting the productsā€” or automatically through the database." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/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`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:15 +msgid "Automatic inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Two hand cream lots reserved for sell with the FEFO strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:17 +msgid "To use Odoo to automatically generate a trail of inventory valuation entries, first navigate to the :menuselection:`Product Categories` list by going to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category. On the form, set the :guilabel:`Inventory Valuation` as :guilabel:`Automated` and the :guilabel:`Costing Method` to any of the three options." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping.rst:5 -msgid "Shipping" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:24 +msgid ":ref:`Set up inventory valuation `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation.rst:5 -msgid "Shipping Operations" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:26 +msgid "In order to understand how moving products in and out of stock affects the company's overall value, consider the following product and stock moves scenario below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:3 -msgid "How to cancel a shipping request to a shipper?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:30 +msgid "Receive a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:8 -msgid "Odoo can handle various delivery methods, including third party shippers. Odoo will be linked with the transportation company tracking system." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:32 +msgid "To track the value of incoming products, such as a simple *table*, configure the product category on the the product itself. To get there, navigate to :menuselection:`Inventory app --> Products --> Products` and click the desired product. On the product form, click the :guilabel:`āž”ļø (right arrow)` icon beside the :guilabel:`Product Category` field, which opens an internal link to edit the product category. Next, set the :guilabel:`Costing Method` as :guilabel:`First In First Out (FIFO)` and :guilabel:`Inventory Valuation` as :guilabel:`Automated`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:12 -msgid "It will allow you to manage the transport company, the real prices and the destination." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:40 +msgid "Alternatively access the :guilabel:`Product Categories` dashboard by navigating to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:15 -msgid "You can easily cancel the request made to the carrier system." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:44 +msgid "Next, assume 10 tables are purchased at a price of $10.00, each. The :abbr:`PO (Purchase Order)` for those tables will show the subtotal of the purchase as $100, plus any additional costs or taxes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:18 -msgid "How to cancel a shipping request?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:-1 +msgid "Purchase order with 10 tables products valued at $10.00 each." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:20 -msgid "If the delivery order is not **Validated**, then the request hasn't been made. You can choose to cancel the delivery or to change the carrier." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:51 +msgid "After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, the :guilabel:`Valuation` smart button is enabled. Clicking on this button displays a report showing how the inventory valuation for the table was affected by this purchase." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:24 -msgid "If you have clicked on **Validate**, the request has been made and you should have received the tracking number and the label. You can still cancel the request. Simply click on the **Cancel** button next to the **Carrier Tracking Ref**:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:56 +msgid ":ref:`Developer mode ` **must** be turned on to see the :guilabel:`Valuation` smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:32 -msgid "You will now see that the shipment has been cancelled." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:60 +msgid "The :doc:`consignment ` feature allows ownership to items in stock. Thus, products owned by other companies are not accounted for in the host company's inventory valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:37 -msgid "You can now change the carrier if you wish." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:-1 +msgid "See Valuation smart button on a receipt, with Developer mode enabled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:40 -msgid "How to send a shipping request after cancelling one?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:68 +msgid "For a comprehensive dashboard that includes the inventory valuation of all product shipments, inventory adjustments, and warehouse operations, refer to the :ref:`stock valuation report `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:42 -msgid "After cancelling the shipping request, you can change the carrier you want to use. Confirm it by clicking on the **Send to shipper** button. You will get a new tracking number and a new label." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:73 +msgid "Deliver a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:50 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:115 -msgid ":doc:`invoicing`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:75 +msgid "In the same logic, when a table is shipped to a customer and leaves the warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock valuation record as it does on a :abbr:`PO (Purchase Order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:51 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:116 -msgid ":doc:`multipack`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:-1 +msgid "Decreased stock valuation after a product is shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:3 -msgid "Use dropshipping to ship directly from suppliers to customers" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:86 +msgid "Inventory valuation report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:5 -msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:88 +msgid "To view the current value of all products in the warehouse, first turn on :ref:`Developer mode ` and navigate to :menuselection:`Inventory app --> Reporting --> Valuation`. The :guilabel:`Stock Valuation` dashboard displays detailed records of products with the :guilabel:`Date`, :guilabel:`Quantity`, :guilabel:`Unit Value`, and :guilabel:`Total Value` of the inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:12 -msgid "Configure products to be dropshipped" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:95 +msgid ":ref:`Developer mode ` **must** be enabled to see the :guilabel:`Valuation` option under :guilabel:`Reporting`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:14 -msgid "To use dropshipping as a fulfillment strategy, navigate to the :menuselection:`Purchase` app and select :menuselection:`Configuration --> Settings`. Under the :guilabel:`Logistics` heading, click the :guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:-1 +msgid "Inventory valuation report showing multiple products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:18 -msgid "Next, go to the :menuselection:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the :guilabel:`Product` page, make sure that the :guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are enabled." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:102 +msgid "The :guilabel:`Valuation At Date` button, located in the top-left corner of the :guilabel:`Stock Valuation` page, reveals a pop-up window. In this pop-up, the inventory valuation of products available during a prior specified date can be seen and selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 -msgid "Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:107 +msgid "View a detailed record of a product's inventory value, stock move, and on-hand stock by selecting the teal :guilabel:`āž”ļø (right arrow)` button to the right of the :guilabel:`Reference` column value." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:27 -msgid "Click on the :guilabel:`Purchase` tab and specify a vendor and the price that they sell the product for. Multiple vendors can be added, but the vendor at the top of the list will be the one automatically selected for purchase orders." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:112 +msgid "Update product unit price" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 -msgid "The product form with a vendor specified." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:114 +msgid "For any company: lead times, supply chain failures, and other risk factors can contribute to invisible costs. Although Odoo attempts to accurately represent the stock value, *manual valuation* serves as an additional tool to update the unit price of products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:35 -msgid "Finally, select the :guilabel:`Inventory` tab and enable the :guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:119 +msgid "Manual valuation is intended for products that can be purchased and received for a cost greater than 0, or have product categories set with :guilabel:`Costing Method` set as either :guilabel:`Average Cost (AVCO)` or :guilabel:`First In First Out (FIFO)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 -msgid "Enable the Dropship option in the product inventory tab." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:-1 +msgid "Add manual valuation of stock value to a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:43 -msgid "Fulfill orders using dropshipping" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:127 +msgid "Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard by first navigating to :menuselection:`Inventory app --> Reporting --> Valuation`. Next, to enable the *product revaluation* feature, select :menuselection:`Group by --> Product` to organize all the records by product. Click on the gray :guilabel:`ā–¶ļø (drop-down triangle)` icon to reveal stock valuation line items below, as well as a teal :guilabel:`āž• (plus)` button on the right." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:45 -msgid "When a customer completes an online purchase for a dropshipped product, a sales order will be automatically created with an associated request for quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:133 +msgid "Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product Revaluation` form. Here, the inventory valuation for a product can be recalculated, by increasing or decreasing the unit price of each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:52 -msgid "Dropship sales orders can also be created manually through the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for dropshipping." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:138 +msgid "The :guilabel:`ā–¶ļø (drop-down triangle)` and :guilabel:`āž• (plus)` buttons are only visible after grouping entries by product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 -msgid "A dropship sales order with the Purchase smart button in the top right corner." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:-1 +msgid "Product revaluation form adding a value of $1.00 with the reason being inflation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:60 -msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Receipt` smart button in the top right corner of the purchase order form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:146 +msgid "Inventory valuation journal entries" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 -msgid "A dropship purchase order with the Receipt smart button in the top right corner." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:148 +msgid "In Odoo, automatic inventory valuation records are also recorded in the :menuselection:`Accounting app --> Accounting --> Journal Entries` dashboard. On this comprehensive list of accounting entries, inventory valuation records are identified by checking values in the :guilabel:`Journal` column, or looking for the :guilabel:`Reference` column value which matches the warehouse operation reference (e.g. `WH/IN/00014` for receipts)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:68 -msgid "The dropship receipt will list the supplier in the :guilabel:`Receive From` section and the customer in the :guilabel:`Destination Location` section. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top left of the dropship receipt to confirm the delivered quantity." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:154 +msgid "Clicking on an inventory valuation journal entry opens a *double-entry accounting* record. These records are generated by Odoo to track the change of value in inventory valuation as products are moved in and out of the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 -msgid "Validate the dropship receipt after delivery." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:159 +msgid "To view the inventory valuation of 10 *tables*, costing $10.00 each, upon reception from the vendor, go to the :menuselection:`Journal Entries` page found in :menuselection:`Accounting app --> Accounting --> Journal Entries`. Here, click the journal line where the :guilabel:`Reference` column value matches the reference on the receipt, `WH/IN/00014`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:77 -msgid "To view all dropship orders, simply navigate to the :menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:0 +msgid "Stock valuation page depicting the products within a shipment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:-1 -msgid "Click the green button on the Dropship card to view all dropship orders." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:168 +msgid "`Stock interim` is a holding account for money intended to pay vendors for the product. The `stock valuation` account stores the value of all on-hand stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:3 -msgid "How to invoice the shipping cost to the customer?" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:0 +msgid "Accounting entry for the inventory valuation of 10 tables." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:8 -msgid "There are two ways to invoice the shipping costs:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:10 -msgid "Agree with the customer over a cost and seal it down in the sale order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:13 -msgid "Invoice the real cost of the shipping." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:18 -msgid "To configure the price of your delivery methods, go to the **Inventory** app, click on :menuselection:`Configuration --> Delivery --> Delivery Methods`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:21 -msgid "You can manually set a price for the shipping: It can be fixed or based on rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:24 -msgid "Or you can use the transportation company computation system. Read the document :doc:`../setup/third_party_shipper`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:28 -msgid "How to invoice the shipping costs to the customer?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:31 -msgid "Invoice the price set on the sale order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:33 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:55 -msgid "On your sale order, choose the carrier that will be used. Click on **Delivery Method** to choose the right one." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:39 -msgid "The price is computed when you **save** the sale order or when you click on **Set price**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:42 -msgid "To invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:46 -msgid "When you create the invoice, it will take the price set on the sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:53 -msgid "Invoice the real shipping costs" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:61 -msgid "The price is computed when you **save** the sale order. Confirm the sale order and proceed to deliver the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:64 -msgid "The real shipping cost is computed when the delivery order is validated, you can see the real cost in the chatter of the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:70 -msgid "Go back to the sale order, the real cost is now added to the sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:76 -msgid "When you create the invoice, it will take the price computed by the carrier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:83 -msgid "If you split the delivery and make several ones, each delivery order will add a line to the sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:87 -msgid ":doc:`../setup/third_party_shipper`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:88 -msgid ":doc:`labels`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:3 -msgid "Change shipping label size" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:8 -msgid "In Odoo, there are a variety of different types of shipping labels that can be selected for delivery orders. Depending on the types of shipping packages used, different label sizes may be more appropriate, and can be configured to fit the package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:15 -msgid "In the :menuselection:`Inventory` module, go to :menuselection:`Configuration --> Delivery --> Shipping Methods.` Click on a delivery method to choose it. For the following example, *FedEx International* will be used." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 -msgid "Different shipping methods." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:23 -msgid "In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose one of the label types available. The availability varies depending on the carrier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 -msgid "Select a label type." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:30 -msgid "When a sales order with the corresponding shipping company is confirmed and a delivery order is validated, the shipping label will be automatically created as a PDF and appear in the :guilabel:`Chatter`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:37 -msgid "In the :menuselection:`Sales` application, click :guilabel:`Create` and select an international customer. Click :guilabel:`Add A Product` and select an item. Click :guilabel:`Add Shipping`, select a shipping method, then click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 -msgid "Add a shipping method and rate to a sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:45 -msgid "Once the quotation is confirmed by clicking :guilabel:`Confirm`, a :guilabel:`Delivery` smart button will appear." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 -msgid "Delivery order smart button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:52 -msgid "Once the delivery order is validated by clicking :guilabel:`Validate` in the delivery order, the shipping documents appear in the :guilabel:`Chatter`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 -msgid "Shipping PDF documents." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:60 -msgid "Example labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:62 -msgid "The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example of a FedEx letter sized label is:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 -msgid "Full page letter size FedEx shipping label." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:69 -msgid "For comparison, an example of a FedEx bottom-half label is:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:-1 -msgid "Half page letter size FedEx shipping label." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:85 -msgid "How to print shipping labels?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:8 -msgid "Odoo can handle various delivery methods, including third party shippers linked with the transportation company tracking system. It allows you to manage the transport company, the real prices and the destination. And finally, you will be able to print the shipping labels directly from Odoo." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:17 -msgid "Install the shipper company connector module" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:20 -msgid "In the **Inventory** module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:27 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:26 -msgid "Then click on **Apply**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:30 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:34 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:33 -msgid "Configure the delivery method" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:32 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:36 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:35 -msgid "To configure your delivery methods, go to the **Inventory** module, click on :menuselection:`Configuration --> Delivery Methods`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:35 -msgid "The delivery methods for the chosen shippers have been automatically created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:41 -msgid "In the **Pricing** tab, the name of the provider means that the delivery will be handled and computed by the shipper system." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:44 -msgid "The configuration of the shipper is split into two columns :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:46 -msgid "The first one is linked to **your account** (develop key, password,...). For more information, please refer to the provider website." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:49 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:62 -msgid "The second column varies according to the **provider**. You can choose the packaging type, the service type, the weight unit..." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:52 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:65 -msgid "Uncheck **Test Mode** when you are done with the testings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:55 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:77 -msgid "Company configuration" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:57 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:79 -msgid "In order to compute the right price, the provider needs your company information. Be sure your address and phone number are correctly encoded." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:64 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:86 -msgid "To check your information, go to the **Settings** application and click on **General Settings**. Click on the first link **Configure your company data**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:68 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:90 -msgid "Product configuration" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:70 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:92 -msgid "The shipper companies need the weight of your product, otherwise the price computation cannot be done." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:73 -msgid "Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open the products you want to ship and set a weight on it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:80 -msgid "The weight on the product form is expressed in kilograms. Don't forget to do the conversion if you are used to the imperial measurement system." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:87 -msgid "The delivery order created from the sale order will take the shipping information from it, but you can change the carrier if you want to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:90 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:135 -msgid "If you create a delivery transfer from the inventory module, you can add the third party shipper in the additional info tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:96 -msgid "Click on **Validate** to receive the tracking number and **the label(s)**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:98 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:151 -msgid "The label to stick on your package is available in the history underneath :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:104 -msgid "Click on it to open the document and print it :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:110 -msgid "If you are doing multi-packages shippings, most of the time, there will be one label per package. Each label will appear in the delivery history." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:3 -msgid "Multi-package shipments" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:5 -msgid "In some cases, a delivery order with multiple items may need to be shipped in more than one package. This may be necessary if the items are too large to ship in a single package, or if certain items cannot be packaged together. Shipping a single delivery order in multiple packages provides flexibility for how each item is packaged, without the need to create multiple delivery orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:13 -msgid "In order to split a delivery order across multiple packages, the *Packages* setting must be enabled. To do so, navigate to :menuselection:`Inventory --> Configuration --> Settings`, then enable the checkbox next to :guilabel:`Packages`. Click :guilabel:`Save` to confirm the change." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:-1 -msgid "The Packages setting on the Inventory app settings page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:24 -msgid "Ship items in multiple packages" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:26 -msgid "To split items in the same delivery order across multiple packages, begin by navigating to :menuselection:`Inventory --> Delivery Orders`, then select a delivery order that has multiple items, a multiple quantity of the same item, or both." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:30 -msgid "On the :guilabel:`Operations` tab, select the :guilabel:`āžā‰£ (menu)` icon in the line of the product that will be shipped in the first package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:-1 -msgid "The menu icon for a product in a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:37 -msgid "This makes a :guilabel:`Detailed Operations` pop-up window appear. In the table at the bottom of the pop-up window, the :guilabel:`Reserved` column shows the total quantity of the product included in the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:41 -msgid "If the full quantity will be shipped in the first package, enter the number from the :guilabel:`Done` column in the :guilabel:`Reserved` column. If less than the full quantity will be shipped in the first package, enter a smaller number than the one that appears in the :guilabel:`Reserved` column. Click :guilabel:`Confirm` to confirm the :guilabel:`Done` quantities and close the pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:-1 -msgid "The Detailed Operations pop-up for a product in a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:51 -msgid "Repeat the same steps for every item quantity that is included in the first package. Then, click :guilabel:`Put In Pack` to create a package with all of the selected items." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:-1 -msgid "The Put In Pack button on a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:58 -msgid "For the next package, follow the same steps as detailed above, marking the quantity of each item to be included in the package as :guilabel:`Done` before clicking :guilabel:`Put In Pack` on the delivery order. Continue doing so until the full quantity of all items are added to a package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:62 -msgid "Finally, after all of the packages have been shipped, click :guilabel:`Validate` to confirm that the delivery order has been completed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:66 -msgid "After one or more packages are created, a :guilabel:`Packages` smart button appears in the top-right corner of the delivery order. Click the :guilabel:`Packages` smart button to go to the :guilabel:`Packages` page for the delivery order, where each package can be selected to view all of the items included in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:0 -msgid "The Packages smart button on a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:76 -msgid "Create a backorder for items to be shipped later" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:78 -msgid "If some items will be shipped at a later date than others, there is no need to put them in a package until they are ready to be shipped. Instead, create a backorder for the items being shipped later." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:81 -msgid "Begin by shipping the items that will be shipped immediately. If they will be shipped in multiple packages, follow the :ref:`steps above ` to package them as required. If they will be shipped in a single package, simply mark in the :guilabel:`Done` column the quantity of each item being shipped, but **do not** click the :guilabel:`Put In Pack` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:86 -msgid "After all quantities being shipped immediately are marked as :guilabel:`Done`, click the :guilabel:`Validate` button, and a :guilabel:`Create Backorder?` pop-up window appears. Then, click the :guilabel:`Create Backorder` button. Doing so confirms the items being shipped immediately and creates a new delivery order for the items that will be shipped later." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:-1 -msgid "The Create Backorder? pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:95 -msgid "The backorder delivery order will be listed in the chatter of the original delivery order in a message that reads :guilabel:`The backorder WH/OUT/XXXXX has been created.`. Click on :guilabel:`WH/OUT/XXXXX` in the message to view the backorder delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:-1 -msgid "The backorder delivery order listed in the chatter of the original delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:103 -msgid "The backorder delivery order can also be accessed by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# Back Orders` button on the :guilabel:`Delivery Orders` card, and selecting the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:-1 -msgid "The Back Orders button on the Delivery Orders card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:111 -msgid "Once the remaining items are ready to be shipped, navigate to the backorder delivery order. The items can be shipped in a single package by clicking :guilabel:`Validate` and selecting :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears, or shipped in multiple packages by following the steps detailed in the section above." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:116 -msgid "It is also possible to ship out some of the items while creating another backorder for the rest. To do so, simply follow the same steps used to create the first backorder." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup.rst:5 -msgid "Shipping Setup" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:3 -msgid "How to setup a delivery method?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:8 -msgid "Odoo can handle various delivery methods, but it is not activated by default. Delivery methods can be used for your sale orders, your deliveries but also on your e-commerce." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:12 -msgid "Delivery methods allow you to manage the transport company, the price and the destination. You can even integrate Odoo with external shippers to compute the real price and the packagings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:20 -msgid "Install the inventory module" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:22 -msgid "Delivery methods are handled by the **Delivery costs** module. Go to **Apps** and search for the module. You should remove the **Apps** filter in order to see it :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:30 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:29 -msgid "If you want to integrate delivery methods in your e-commerce, you'll have to install the **eCommerce Delivery** module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:39 -msgid "First set a name and a transporter company." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:44 -msgid "Then you'll have to set the pricing. It can be fixed or based on rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:46 -msgid "If the price is fixed, tick **Fixed price**. You'll just have to define the price. If you want the delivery to be free above a certain amount, tick the option **Free if Order total is more than** and set a price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:54 -msgid "If the price varies according to rules, tick **Based on Rules**. Click on **add an item to a pricing rule**. Choose a condition based on either the weight, the volume, the price or the quantity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:61 -msgid "Finally you can limit the delivery method to a few destinations. The limit can be applied to some countries, states or even zip codes. This feature limits the list of countries on your e-commerce." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:69 -msgid "You can integrate Odoo with external shippers in order to compute the real price and packagings, and handle the printing the shipping labels. See :doc:`third_party_shipper`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:74 -msgid "Delivery process" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:77 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:110 -msgid "Sale order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:82 -msgid "You can now choose the **Delivery Method** on your sale order. If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:88 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:130 -msgid "Delivery" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:90 -msgid "You can add or change the delivery method on the delivery itself." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:95 -msgid "On the delivery, check the **Carrier Information**. The carrier is the chosen delivery method." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:99 -msgid ":doc:`third_party_shipper`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:100 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:158 -msgid ":doc:`../operation/invoicing`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:3 -msgid "How to get DHL credentials for integration with Odoo?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:5 -msgid "In order to use the Odoo DHL API, you will need:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:7 -msgid "A DHL.com SiteID" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:9 -msgid "A DHL Password" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:11 -msgid "A DHL Account Number" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:15 -msgid "Getting SiteID and password for countries other than United States (UK and Rest of the world)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:17 -msgid "You should contact DHL account manager and request integration for XML Express API. The presales should provide you live credentials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:20 -msgid "Getting SiteID and Password for United States" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:22 -msgid "You need to write to xmlrequests@dhl.com along with your full Account details like account number, region, address, etc. to get API Access." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:3 -msgid "Set up Sendcloud shipping services in Odoo" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:5 -msgid "Sendcloud is a shipping service aggregator that facilitates the integration of European shipping carriers with Odoo. Once integrated, users can select shipping carriers on inventory operations in their Odoo database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:10 -msgid "`Sendcloud integration documentation `_" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:14 -msgid "Setup in Sendcloud" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:17 -msgid "Create an account and activate carriers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:19 -msgid "To get started, go to `Sendcloud's platform `_ to configure the account and generate the connector credentials. Log in with the Sendcloud account, or create a new one if needed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:24 -msgid "For new account creation, Sendcloud will ask for a :abbr:`VAT (Value-Added Tax Identification)` number or :abbr:`EORI (Economic Operators' Registration and Identification)` number. After completing the account setup, activate (or deactivate) the shipping carriers that will be used in the Odoo database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:30 -msgid "Odoo integration of Sendcloud works on free Sendcloud plans *only* if a bank account is linked, since Sendcloud won't ship for free. To use shipping rules or individual custom carrier contacts, a paid plan of Sendcloud is required." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:35 -msgid "Warehouse configuration" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:37 -msgid "Once logged into the Sendcloud account, navigate to :menuselection:`Settings --> Shipping --> Addresses`, and fill in the field for :guilabel:`Warehouse address`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:-1 -msgid "Adding addresses in the Sendcloud settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:44 -msgid "To allow Sendcloud to process returns as well, a :guilabel:`Return Address` is required. Under the :guilabel:`Miscellaneous section`, there is a field called :guilabel:`Address Name (optional)`. The Odoo warehouse name should be entered here, and the characters should be exactly the same." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid "**SendClould configuration**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Miscellaneous`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Address Name (optional)`: `Warehouse #1`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Brand`: `Default`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid "**Odoo warehouse configuration**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Warehouse`: `Warehouse #1`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Short Name`: `WH`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Company`: `My company (San Francisco)`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Address`: `My Company (San Francisco)`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:61 -msgid "Notice how the inputs for the :guilabel:`Warehouse` field, for both the Odoo configuration and the Sendcloud configuration, are the exact same." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:65 -msgid "Generate Sendcloud credentials" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:67 -msgid "In the Sendcloud account, navigate to :menuselection:`Settings --> Integrations` in the menu on the right. Next, search for :guilabel:`Odoo Native`. Then, click on :guilabel:`Connect`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:70 -msgid "After clicking on :guilabel:`Connect`, the page redirects to the :guilabel:`Sendcloud API` settings page, where the :guilabel:`Public and Secret Keys` are produced. The next step is to name the :guilabel:`Integration`. The naming convention is as follows: `Odoo CompanyName`, with the user's company name replacing `CompanyName` (e.g. `Odoo StealthyWood`)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:75 -msgid "Then, check the box next to :guilabel:`Service Points` and select the shipping services for this integration. After saving, the :guilabel:`Public and Secret Keys` are generated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:-1 -msgid "Configuring the Sendcloud integration and receiving the credentials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:83 -msgid "Setup in Odoo" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:86 -msgid "Install the Sendcloud shipping module" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:88 -msgid "After the Sendcloud account is set up and configured, it's time to configure the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, search for the :guilabel:`Sendcloud Shipping` integration, and install it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:-1 -msgid "Sendcloud Shipping module in the Odoo Apps module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:97 -msgid "Sendcloud shipping connector configuration" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:99 -msgid "Once installed, activate the :guilabel:`Sendcloud Shipping` module in :menuselection:`Inventory --> Configuration --> Settings`. The :guilabel:`Sendcloud Connector` setting is found under the :guilabel:`Shipping Connectors` section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:103 -msgid "After activating the :guilabel:`Sendcloud Connector`, click on the :guilabel:`Sendcloud Shipping Methods` link below the listed connector. Once on the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:108 -msgid ":guilabel:`Shipping Methods` can also be accessed by going to :menuselection:`Inventory --> Configuration --> Delivery --> Shipping Methods`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:111 -msgid "Fill out the following fields in the :guilabel:`New Shipping Method` form:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:113 -msgid ":guilabel:`Shipping Method`: type `Sendcloud DPD`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:114 -msgid ":guilabel:`Provider`: select :guilabel:`Sendcloud` from the drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:115 -msgid ":guilabel:`Delivery Product`: set the product that was configured for this shipping method or create a new product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:117 -msgid "In the :guilabel:`SendCloud Configuration` tab, enter the :guilabel:`Sendcloud Public Key`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:118 -msgid "In the :guilabel:`SendCloud Configuration` tab, enter the :guilabel:`Sendcloud Secret Key`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:119 -msgid "Manually :guilabel:`Save` the form by clicking the cloud icon next to the :guilabel:`Shipping Methods / New` breadcrumbs." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:122 -msgid "After configuring and saving the form, follow these steps to load the shipping products:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:124 -msgid "In the :guilabel:`SendCloud Configuration` tab of the :guilabel:`New Shipping Method` form, click on the :guilabel:`Load your SendCloud shipping products` link." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:126 -msgid "Select the shipping products the company would like to use for deliveries and returns." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:127 -msgid "Click :guilabel:`Select`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:130 -msgid "Sample Sendcloud shipping products configured in Odoo:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`DELIVERY`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Shipping Product`: `DPD Home 0-31.5kg`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Carrier`: `DPD`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Minimum Weight`: `0.00`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Maximum Weight`: `31.50`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:138 -msgid ":guilabel:`Countries`: `Austria` `Belgium` `Bosnia` `Herzegovina` `Bulgaria` `Croatia` `Czech` `Republic` `Denmark` `Estonia` `Finland` `France` `Germany` `Greece` `Hungary` `Iceland` `Ireland` `Italy` `Latvia` `Liechtenstein` `Lithuania` `Luxembourg` `Monaco` `Netherlands` `Norway` `Poland` `Portugal` `Romania` `Serbia` `Slovakia` `Slovenia` `Spain` `Sweden` `Switzerland`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`RETURN`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Return Shipping Product`: `DPD Return 0-20kg`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Return Carrier`: `DPD`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Return Minimum Weight`: `0.00`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Return Maximum Weight`: `20.00`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:0 -msgid ":guilabel:`Return Countries`: `Belgium` `Netherlands`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:-1 -msgid "Example of shipping products configured in Odoo." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:156 -msgid "Sendcloud does not provide test keys when a company tests the sending of a package in Odoo. This means if a package is created, the configured Sendcloud account will be charged, unless the associated package is canceled within 24 hours of creation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:160 -msgid "Odoo has a built-in layer of protection against unwanted charges when using test environments. Within a test environment, if a shipping method is used to create labels, then those labels are immediately canceled after the creation ā€” this occurs automatically. The test and production environment settings can be toggled back and forth from the :guilabel:`Smart Buttons`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:166 -msgid "Generate a label with Sendcloud" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:168 -msgid "When creating a quotation in Odoo, add shipping and a :guilabel:`Sendcloud shipping product`. Then, :guilabel:`Validate` the delivery. Shipping label documents are automatically generated in the chatter, which include the following:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:172 -msgid ":guilabel:`Shipping label(s)` depending on the number of packages." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:173 -msgid ":guilabel:`Return label(s)` if the Sendcloud connector is configured for returns." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:174 -msgid ":guilabel:`Customs document(s)` should the destination country require them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:176 -msgid "Additionally, the tracking number is now available." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:179 -msgid "When return labels are created, Sendcloud will automatically charge the configured Sendcloud account." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:183 -msgid "FAQ" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:186 -msgid "Shipment is too heavy" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:188 -msgid "If the shipment is too heavy for the Sendcloud service that is configured, then the weight is split to simulate multiple packages. Products will need to be put in different :guilabel:`Packages` to :guilabel:`Validate` the transfer and generate labels." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:192 -msgid ":guilabel:`Rules` can also be set up in Sendcloud to use other shipping methods when the weight is too heavy. However, note that these rules will not apply to the shipping price calculation on the calculation on the sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:197 -msgid "When using a personal carrier contract" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:199 -msgid "When using a personal carrier contract in Sendcloud, if the the price is not accurately reflected when creating a quotation in Odoo, then the pricing information needs to be updated in Sendcloud." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:203 -msgid "Measuring volumetric weight" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:205 -msgid "Many carriers have several measures for weight. There is the actual weight of the products in the parcel, and there is the *volumetric weight* (:dfn:`Volumetric weight is the volume that a package occupies when in transit. In other words it is the physical size of a package`)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:210 -msgid "Check to see if selected carrier(s) already have defined formulas to compute the volumetric weight." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:214 -msgid "`Sendcloud: How to calculate & automate parcel volumetric weight `_" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:219 -msgid "Unable to calculate shipping rate" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/sendcloud_shipping.rst:221 -msgid "First, verify that product being shipped has a weight that is supported by the selected shipping method. If this is set, then verify that the destination country (from the customer address) is supported by the carrier. The country of origin (warehouse address) should also be supported by the carrier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:3 -msgid "How to integrate a third party shipper?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:8 -msgid "Odoo can handle various delivery methods, including third party shippers. Odoo can be linked with the transportation company tracking system. It will allow you to manage the transport company, the real prices and the destination." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:19 -msgid "In the inventory module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:38 -msgid "The delivery methods for the chosen shippers have been automatically created. Most of the time, there will be **2** delivery methods for the same provider: one for **international** shipping and the other for **domestic** shipping." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:43 -msgid "You can create other methods with the same provider with other configuration, for example the **Packaging Type**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:46 -msgid "You can change the **Name** of the delivery method. This is the name that will appear on your ecommerce." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:49 -msgid "Flag **Shipping enabled** when you are ready to use it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:54 -msgid "In the pricing tab, the name of the provider chosen under the **Price computation** means that the pricing will be computed by the shipper system." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:57 -msgid "The configuration of the shipper is split into two columns:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:59 -msgid "The first one is linked to **your account** (developer key, password,...). For more information, please refer to the provider website." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:67 -msgid "Finally you can limit the delivery method to a few destinations. You can limit it to some countries, states or even zip codes. This feature limits the list of countries on your e-commerce. It is useful for the domestic providers. For example, USPS US only delivers from the United States to the United States." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:95 -msgid "Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products you want to ship and set a weight on it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:102 -msgid "The weight on the product form is expressed in kilograms. Don't forget to make the conversion if you are used to the imperial measurement system." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:107 -msgid "Sale process" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:115 -msgid "You can now choose the carrier on your sale order. Click on **Delivery method** to choose the right one." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:118 -msgid "The price is computed when you save the sale order or when you click on **Set price**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:121 -msgid "If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:125 -msgid "Otherwise, the real price (computed when the delivery is validated) will automatically be added to the invoice. For more information, please read the document :doc:`../operation/invoicing`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:132 -msgid "The delivery created from the sale order will take the shipping information from it. You can change the carrier if you want to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:141 -msgid "The weight is computed based on the products weights. The shipping cost will be computed once the transfer is validated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:144 -msgid "Click on **Validate** to receive the tracking number. The **Carrier Tracking ref** field will automatically be filled. Click on the **Tracking** button to check your delivery on the provider website." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:159 -msgid ":doc:`../operation/labels`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:3 -msgid "How to get UPS credentials for integration with Odoo?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:5 -msgid "In order to use the Odoo UPS API, you will need:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:7 -msgid "A UPS.com user ID and password" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:9 -msgid "A UPS account number" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:11 -msgid "An Access Key" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:13 -msgid "An Access Key is a 16 character alphanumeric code that allows access to the UPS Developer Kit API Development and Production servers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:17 -msgid "Create a UPS Account" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:19 -msgid "Note that only customers located in the US can open a UPS account online. If you are located outside the US, you will need to contact UPS Customer Service in order to to open an account." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:23 -msgid "You can read additional information about opening a UPS account on the their website, on the page, `How to Open a UPS Account Online `_" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:27 -msgid "If you don't already have a UPS account, you can create one along with your online profile by following these steps:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:30 -msgid "1. Access the UPS.com web site at `www.ups.com `__, and click the **New User** link at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:34 -msgid "2. Click the **Register for MyUPS** button, and follow the prompts to complete the registration process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:37 -msgid "If you already have a UPS account, you can add it to your online profile as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:39 -msgid "Log in to the `UPS.com website `_) using your UPS.com User ID and Password." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:41 -msgid "Click the **My UPS** tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:43 -msgid "Click the **Account Summary** link." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:45 -msgid "4. Click the **Add an Existing UPS Account** link in the **UPS Account Details** section of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:48 -msgid "5. In the **Add New Account** screen, enter the **UPS Account Number**, **Account Name**, and **Postal Code** fields. The country defaults to United States.q" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:52 -msgid "Click the **Next** button to continue." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:55 -msgid "Get an Access Key" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:57 -msgid "After you have added your UPS account number to your user profile you can request an Access Key from UPS using the steps below:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:60 -msgid "Go to the `UPS Developer Kit web page `_" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:61 -msgid "Log into UPS.com with your user ID and password" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:62 -msgid "Click on the link **Request an access key**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:63 -msgid "Verify your contact information" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:64 -msgid "Click the **Request Access Key** button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:66 -msgid "The **Access Key** will be provided to you on the web page, and an email with the Access Key will be sent to the email address of the primary contact." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:176 +msgid "`Odoo Tutorial: Inventory Valuation `_" msgstr "" #: ../../content/applications/inventory_and_mrp/maintenance.rst:8 @@ -7941,43 +8943,43 @@ msgstr "" msgid "Add new equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:5 -msgid "In Odoo, **equipment** refers to any item that is used in everyday operations, including the manufacturing of products. This can mean a piece of machinery on a production line, a tool that is used in different locations, or a computer in an office space. Equipment registered in Odoo can be owned by the company that uses the Odoo database, or by a third party, such as a vendor in the case of equipment rentals." +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:7 +msgid "In Odoo, *equipment* refers to any item that is used in everyday operations, including the manufacturing of products. This can mean a piece of machinery on a production line, a tool that is used in different locations, or a computer in an office space. Equipment registered in Odoo can be owned by the company that uses the Odoo database, or by a third party, such as a vendor in the case of equipment rentals." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:11 -msgid "Using Odoo **Maintenance**, it is possible to track individual pieces of equipment, along with information about their maintenance requirements. To add a new piece of equipment, navigate to the :guilabel:`Maintenance` module, select :menuselection:`Equipments --> Machines & Tools --> Create`, and configure the equipment as follows:" +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:13 +msgid "Using Odoo *Maintenance*, it is possible to track individual pieces of equipment, along with information about their maintenance requirements. To add a new piece of equipment, navigate to the :guilabel:`Maintenance` module, select :menuselection:`Equipments --> Machines & Tools --> Create`, and configure the equipment as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:16 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:18 msgid ":guilabel:`Equipment Name`: the product name of the piece of equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:17 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:19 msgid ":guilabel:`Equipment Category`: the category that the equipment belongs to; for example, computers, machinery, tools, etc.; new categories can be created by navigating to :menuselection:`Configuration --> Equipment Categories` and clicking :guilabel:`Create`" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:20 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:22 msgid ":guilabel:`Company`: the company that owns the equipment; again, this can be the company that uses the Odoo database, or a third-party company" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:22 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:24 msgid ":guilabel:`Used By`: specify if the equipment is used by a specific employee, department, or both; select :guilabel:`Other` to specify both an employee and a department" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:24 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:26 msgid ":guilabel:`Maintenance Team`: the team responsible for servicing the equipment; new teams can be created by navigating to :menuselection:`Configuration --> Maintenance Teams` and selecting :guilabel:`Create`; the members of each team can also be assigned from this page" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:27 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:29 msgid ":guilabel:`Technician`: the person responsible for servicing the equipment; this can be used to assign a specific individual in the event that no maintenance team is assigned or when a specific member of the assigned team should always be responsible for the equipment; any person added to Odoo as a user can be assigned as a technician" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:31 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:33 msgid ":guilabel:`Used in location`: the location where the equipment is used; this is a simple text field that can be used to specify locations that are not work centers, like an office, for example" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:34 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:36 msgid ":guilabel:`Work Center`: if the equipment is used at a work center, specify it here; equipment can also be assigned to a work center by navigating to :menuselection:`Maintenance --> Equipments --> Work Centers`, selecting a work center or creating a new one using the :guilabel:`Create` button, and clicking the :guilabel:`Equipment` tab on the work center form" msgstr "" @@ -7985,39 +8987,39 @@ msgstr "" msgid "An example of a fully configured new equipment form." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:44 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:46 msgid "Include additional product information" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:46 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:48 msgid "The :guilabel:`Product Information` tab at the bottom of the form can be used to provide further details about the piece of equipment:" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:49 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:51 msgid ":guilabel:`Vendor`: the vendor that the equipment was purchased from" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:50 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:52 msgid ":guilabel:`Vendor Reference`: the reference code assigned to the vendor" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:51 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:53 msgid ":guilabel:`Model`: the specific model of the piece of equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:52 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:54 msgid ":guilabel:`Serial Number`: the unique serial number of the equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:53 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:55 msgid ":guilabel:`Effective Date`: the date that the equipment became available for use; this is used to calculate the :abbr:`MTBF (Mean Time Between Failures)`" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:55 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:57 msgid ":guilabel:`Cost`: the amount the equipment was purchased for" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:56 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:58 msgid ":guilabel:`Warranty Expiration Date`: the date on which the equipment's warranty will expire" msgstr "" @@ -8025,23 +9027,23 @@ msgstr "" msgid "The product information tab for the new piece of equipment." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:63 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:65 msgid "Add maintenance details" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:65 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:67 msgid "The :guilabel:`Maintenance` tab includes information that can be useful to maintenance teams:" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:67 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:69 msgid ":guilabel:`Preventive Maintenance Frequency`: specifies how often maintenance should be performed to prevent equipment failure" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:69 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:71 msgid ":guilabel:`Maintenance Duration`: the amount of time required to fix the equipment when it fails" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:70 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:72 msgid ":guilabel:`Expected Mean Time Between Failure`: the average amount of time that the equipment is expected to operate before failing" msgstr "" @@ -8049,11 +9051,11 @@ msgstr "" msgid "The maintenance tab for the new piece of equipment." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:78 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:80 msgid "The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated automatically based on maintenance requests if any exist." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:84 +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:86 msgid "To see the maintenance requests for a piece of equipment, go to the page for the equipment and select :guilabel:`Maintenance` in the top right corner of the form." msgstr "" @@ -8082,15 +9084,15 @@ msgid "Manufacturing workflows" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3 -msgid "Create a bill of materials" +msgid "Bill of materials" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:7 -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." +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:11 -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)`." +msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:14 @@ -8181,19 +9183,19 @@ msgstr "" msgid "Manufacturing product configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:7 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:8 msgid "In order to manufacture a product in Odoo *Manufacturing*, the product must be properly configured. Doing so consists of enabling the *Manufacturing* route and configuring a bill of materials (BoM) for the product. Once these steps are completed, the product is selectable when creating a new manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:13 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:14 msgid "Activate the Manufacture route" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:16 msgid "The Manufacture route is activated for each product on its own product page. To do so, begin by navigating to :menuselection:`Manufacturing --> Products --> Products`. Then, select an existing product, or create a new one by clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:19 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:20 msgid "On the product page, select the :guilabel:`Inventory` tab, then enable the :guilabel:`Manufacture` checkbox in the :guilabel:`Routes` section. This tells Odoo the product can be manufactured." msgstr "" @@ -8201,15 +9203,15 @@ msgstr "" msgid "The Manufacturing route on the Inventory tab of a product page." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:27 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:28 msgid "Configure a bill of materials (BoM)" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:29 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:30 msgid "Next, a |BOM| must be configured for the product so Odoo knows how it is manufactured. A |BOM| is a list of the components and operations required to manufacture a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:32 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:33 msgid "To create a |BOM| for a specific product, navigate to :menuselection:`Manufacturing --> Products --> Products`, then select the product. On the product page, click the :guilabel:`Bill of Materials` smart button at the top of the page, then select :guilabel:`New` to configure a new |BOM|." msgstr "" @@ -8217,11 +9219,11 @@ msgstr "" msgid "The Bill of Materials smart button on a product page." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:41 msgid "On the |BOM|, the :guilabel:`Product` field auto-populates with the product. In the :guilabel:`Quantity` field, specify the number of units that the BoM produces." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:43 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:44 msgid "Add a component to the |BOM| by selecting the :guilabel:`Components` tab and clicking :guilabel:`Add a line`. Select a component from the :guilabel:`Component` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. Continue adding components on new lines until all components have been added." msgstr "" @@ -8229,11 +9231,11 @@ msgstr "" msgid "The Components tab on a bill of materials." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:52 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:53 msgid "Next, select the :guilabel:`Operations` tab. Click :guilabel:`Add a line` and a :guilabel:`Create Operations` pop-up window appears. In the :guilabel:`Operation` field, specify the name of the operation being added (e.g. Assemble, Cut, etc.). Select the work center where the operation will be carried out from the :guilabel:`Work Center` drop-down menu. Finally, click :guilabel:`Save & Close` to finish adding operations, or :guilabel:`Save & New` to add more." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:59 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:60 msgid "The :guilabel:`Operations` tab only appears if the :guilabel:`Work Orders` setting is enabled. To do so, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`, then enable the :guilabel:`Work Orders` checkbox." msgstr "" @@ -8241,11 +9243,7 @@ msgstr "" msgid "The Operations tab on a bill of materials." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:67 -msgid "Learn more" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:69 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:70 msgid "The section above provides instructions for creating a basic |BOM| that allows a product to be manufactured in Odoo. However, it is by no means an exhaustive summary of all the options available when configuring a |BOM|. For more information about bills of materials, see the documentation on how to :ref:`create a bill of materials `." msgstr "" @@ -8459,6 +9457,9 @@ msgid "After confirming the manufacturing order, select the :guilabel:`Work Orde msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 msgid "The tablet view button for a work order on a manufacturing order." msgstr "" @@ -8554,6 +9555,150 @@ msgstr "" msgid "Once more screws are available, the manufacturing employee assembles the remaining chairs and clicks :guilabel:`Mark As Done And Close MO` to complete the *Assemble* work order and close the backorder manufacturing order." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:3 +msgid "One-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:9 +msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using one-step manufacturing, Odoo creates a manufacturing order (MO), but does not generate transfers for the movement of components out of inventory or finished products into stock. Inventory counts still update based on the number of components used and products manufactured, but the act of transferring them to and from inventory is not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:16 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:16 +msgid "The number of steps used in manufacturing is set at the warehouse level, allowing for each warehouse to use a different number of steps. To change the number of steps used for a specific warehouse, begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, and then select a warehouse from the :guilabel:`Warehouses` screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:20 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:21 +msgid "On the :guilabel:`Warehouse Configuration` tab, find the :guilabel:`Manufacture` radio input field, and select one of the three options: :guilabel:`Manufacture (1 step)`, :guilabel:`Pick components and then manufacture (2 steps)`, or :guilabel:`Pick components, manufacture and then store products (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:0 +msgid "The Manufacture radio input field on a warehouse configuration page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:31 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:31 +msgid "Products must be properly configured before they can be manufactured in Odoo. For details on how to do so, see the documentation on how to :ref:`configure a product for manufacturing `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:36 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:36 +msgid "Create manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:38 +msgid "To manufacture a product in Odoo *Manufacturing*, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then click :guilabel:`New` to create a new |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:42 +msgid "On the new |MO|, select the product to be produced from the :guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field auto-populates with the associated bill of materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:44 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:45 +msgid "If a product has more than one |BOM| configured for it, the specific |BOM| can be selected in the :guilabel:`Bill of Material` field, and the :guilabel:`Product` field auto-populates with the associated product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:49 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:49 +msgid "After a |BOM| has been selected, the :guilabel:`Components` and :guilabel:`Work Orders` tabs auto-populate with the components and operations specified on the |BOM|. If additional components or operations are required for the |MO| being configured, add them to the :guilabel:`Components` and :guilabel:`Work Orders` tabs by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:55 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:80 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:77 +msgid "Process manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:79 +msgid "An |MO| is processed by completing all of the work orders listed under its :guilabel:`Work Orders` tab. This can be done on the |MO| itself, or from the work order tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:83 +msgid "Basic workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:85 +msgid "To complete work orders from the |MO| itself, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:91 +msgid "On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins on the first work order that needs to be completed, click the :guilabel:`Start` button for that work order. Odoo *Manufacturing* then starts a timer that keeps track of how long the work order takes to complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:-1 +msgid "The Start button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:74 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:99 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:96 +msgid "When the work order is completed, click the :guilabel:`Done` button for that work order. Repeat the same process for each work order listed on the :guilabel:`Work Orders` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:-1 +msgid "The Done button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:81 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:103 +msgid "After completing all of the work orders, click :guilabel:`Produce All` at the top of the screen to mark the |MO| as :guilabel:`Done`, and register the manufactured product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:107 +msgid "Tablet view workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:87 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:112 +msgid "To complete the work orders for an |MO| using the tablet view, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:91 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:116 +msgid "Next, click on the :guilabel:`Work Orders` tab, and then select the :guilabel:`šŸ“± (tablet)` button on the line of the first work order to be processed. This opens the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:98 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:119 +msgid "After opening the tablet view, Odoo *Manufacturing* automatically starts a timer that keeps track of how long the work order takes to complete. After completing the work order, click the :guilabel:`Mark as Done` button in the top-right corner of the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:102 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:127 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:123 +msgid "Clicking :guilabel:`Mark as Done` while there is at least one more work order left to complete opens a page that lists the next work order. Click on that work order to open it in the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:105 +msgid "Once the final work order for the |MO| has been reached, a :guilabel:`Mark as Done and Close MO` button appears on the tablet view in addition to the :guilabel:`Mark as Done` button. Click :guilabel:`Mark as Done and Close MO` to mark the |MO| as :guilabel:`Done` and register the manufactured product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:110 +msgid "It is also possible to complete the final operation while keeping the |MO| open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be closed later by clicking the :guilabel:`Produce All` button on the order." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3 msgid "Managing BoMs for product variants" msgstr "" @@ -8614,10 +9759,6 @@ msgstr "" msgid "Odoo *Manufacturing* allows for both components and finished products to be scrapped within a manufacturing order. The specific type of item that can be scrapped during a manufacturing order depends on the stage of the manufacturing process." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:19 -msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:23 msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`, then remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display all virtual locations. From the list, select the :guilabel:`Virtual Locations/Scrap` location." msgstr "" @@ -8702,6 +9843,86 @@ msgstr "" msgid "If five units of a chair were manufactured, but two units were scrapped after manufacturing was completed, then the on-hand inventory of the chair will increase by three: five units manufactured minus two units scrapped." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:3 +msgid "Split and merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:5 +msgid "In Odoo *Manufacturing*, it is possible to create manufacturing orders for a single unit of an item, or multiple units of the same item. In some cases, it may be necessary to split a manufacturing order that contains multiple units into two or more orders, or to merge two or more orders into a single order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:11 +msgid "A manufacturing order can only contain one unit of a product, or multiple units of a single product that all use the same Bill of Materials (BoM). As a result, it is only possible to merge manufacturing orders when every order contains the same product being manufactured with the same BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:17 +msgid "Split manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:19 +msgid "To split a manufacturing order into multiple orders, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select a manufacturing order. At the top of the page, next to the :guilabel:`New` button, the manufacturing order's reference number appears with a :guilabel:`āš™ļø (settings)` button next to it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:24 +msgid "Click the :guilabel:`āš™ļø (settings)` button to open the general settings for the manufacturing order, then select :guilabel:`Split`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 +msgid "The Settings and Split buttons on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:31 +msgid "After selecting :guilabel:`Split`, a :guilabel:`Split production` pop-up window appears. In the :guilabel:`Split #` field, enter the number of manufacturing orders that the original order should be split into, then click outside of the field. A table appears below, with a line for each new manufacturing order that will be created by the split. In the :guilabel:`Quantity To Produce` column, enter the number of units that will be assigned to each new manufacturing order. Finally, click :guilabel:`Split` to split the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 +msgid "The Split production pop-up window for a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:42 +msgid "After clicking :guilabel:`Split`, the original manufacturing order is split into the number of orders that was specified in the :guilabel:`Split #` field. The reference numbers for the new manufacturing orders are the reference number for the original order with *-###* tags added to the end." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:48 +msgid "Manufacturing order *WH/MO/00012* is split into three separate orders. The reference numbers for the new orders are *WH/MO/00012-001*, *WH/MO/00012-002*, and *WH/MO/00012-003*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:52 +msgid "Merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:54 +msgid "To merge two or more manufacturing orders into a single order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select the manufacturing orders that will be merged by activating the checkbox to the left of the name of each order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 +msgid "Select manufacturing orders that will be merged by clicking the checkbox for each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:62 +msgid "Once all manufacturing orders have been selected, click the :guilabel:`Actions` button at the top of the page, then select :guilabel:`Merge` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 +msgid "The Actions and Merge buttons on the Manufacturing Orders page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:69 +msgid "The selected manufacturing orders are merged into a single order. The reference number for the new manufacturing order is the next sequential number that has *not* already been assigned to an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:73 +msgid "The last reference number used for a manufacturing order was *WH/MO/00012*. Two manufacturing orders, *WH/MO/00008* and *WH/MO/00009*, are merged into a single order. The reference number for the manufacturing order created by the merger is *WH/MO/00013*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:77 +msgid "In the :guilabel:`Source` field for the manufacturing order created by the merger, the reference numbers of the manufacturing orders that were merged are listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:81 +msgid "Manufacturing orders *WH/MO/00009* and *WH/MO/00010* are merged to create *WH/MO/00011*. The source field for *WH/MO/00011* lists both *WH/MO/00009* and *WH/MO/00010*." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:3 msgid "Manage semi-finished products" msgstr "" @@ -8974,99 +10195,214 @@ msgstr "" msgid "Alternatively, you can also manually ask your vendor to resupply your subcontractor by creating a dropship type PO, with your subcontractor set as the delivery address." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:3 +msgid "Three-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:9 +msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using three-step manufacturing, Odoo creates a pick components transfer, a manufacturing order (MO), and a store finished products transfer, and updates inventory counts based on the number of components removed, and finished products created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:42 +msgid "On the new |MO|, select the product to be produced from the :guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field auto-populates with the associated Bill of Materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:53 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:54 +msgid "Finally, click :guilabel:`Confirm` to confirm the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:56 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:57 +msgid "Process pick components transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:58 +msgid "After confirming a three-step |MO|, a :guilabel:`Transfers` smart button appears at the top of the page. Click it to be taken to the :guilabel:`Transfers` page for the |MO|. The page lists two transfers: *WH/PC/XXXXX* (the pick components transfer), and *WH/SFP/XXXXX* (the store finished products transfer)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:63 +msgid "Select :guilabel:`WH/PC/XXXXX` to open the pick components transfer for the |MO|. This transfer is used to track the movement of components from the locations where they are stored to the location where they are used to manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:64 +msgid "After transferring the components out of their storage location, click :guilabel:`Validate` at the top of the transfer, followed by :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears. Doing so marks the transfer as :guilabel:`Done`, and updates inventory counts to reflect the quantity of components transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:72 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:69 +msgid "Finally, return to the |MO| by clicking the :guilabel:`WH/MO/XXXXX` breadcrumb at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 +msgid "The manufacturing order bread crumb on a pick components transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:88 +msgid "To complete work orders from the |MO| itself, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 +msgid "The Start button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 +msgid "The Done button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:130 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:126 +msgid "Once the final work order for the |MO| has been reached, a :guilabel:`Mark as Done and Close MO` button appears on the tablet view in addition to the :guilabel:`Mark as Done` button. Click :guilabel:`Mark as Done and Close MO` to mark the |MO| as :guilabel:`Done`, and register the manufactured product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:135 +msgid "It is also possible to complete the final work order while keeping the |MO| open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be closed at a later time by clicking the :guilabel:`Produce All` button on the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:140 +msgid "Process finished product transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:142 +msgid "After completing the |MO|, return to the order's :guilabel:`Transfers` page by clicking the :guilabel:`Transfers` button at the top of the order. This time, select :guilabel:`WH/SFP/XXXXX` to open the store finished products transfer. This transfer is used to track the movement of finished products from the location where they were manufactured to the location where they are stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:147 +msgid "After transferring the finished products to their storage location, click :guilabel:`Validate` at the top of the transfer, followed by :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears. Doing so marks the transfer as :guilabel:`Done`, and updates inventory counts to reflect the quantity of finished products transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:3 +msgid "Two-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:9 +msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using two-step manufacturing, Odoo creates a manufacturing order (MO) and a pick components transfer, but does not generate a transfer for the movement of finished products into stock. Inventory counts still update based on the number of products manufactured, but the act of transferring them to and from inventory is not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:59 +msgid "After confirming a two-step |MO|, a :guilabel:`Transfers` smart button appears at the top of the page. Click it to open the pick components transfer for the |MO|. This transfer is used to track the movement of components from the locations where they are stored to the location where they are used to manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:88 +msgid "On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins on the first work order that needs to be completed, click the :guilabel:`Start` button for that operation. Odoo *Manufacturing* then starts a timer that keeps track of how long the work order takes to complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 +msgid "The Start button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 +msgid "The Done button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:109 +msgid "To complete the work orders for an |MO| using the tablet view, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:112 +msgid "Next, click on the :guilabel:`Work Orders` tab, then select the :guilabel:`šŸ“± (tablet)` button on the line of the first work order to be processed. This opens the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:131 +msgid "It is also possible to complete the final operation while keeping the |MO| open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be closed at a later time by clicking the :guilabel:`Produce All` button on the order." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:3 msgid "Use the Master Production Schedule" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:7 msgid "The Master Production Schedule (MPS) is a valuable tool to plan your production based on your demand forecast." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:13 msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:17 msgid "In the MPS settings, you can define the time range of your MPS (month/week/day) and the number of periods you want to display at all times." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:18 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:20 msgid "Now, go to :menuselection:`Planning --> Master Production Schedule` and click on *add a product*. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities that must or can be replenished in each period." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:26 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:28 msgid "In the MPS view, you can decide which information you would like to display by clicking on *rows*. For instance, the *Actual demand* will show you which quantity of products has already been ordered for the period, or *Available to Promise*, what can still be sold during that same period (what you plan to replenish - what is already sold during the period). You can also decide to hide rows if you like." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:36 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 msgid "Estimate your demand and launch replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:40 msgid "The next step is to estimate the demand for the chosen period. This is done in the *Forecasted Demand* Row. You can easily, at any time, compare the demand forecast with the actual demand (= confirmed sales). The demand forecast for a finished product will impact the indirect demand for its components." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:46 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:48 msgid "Once the forecasted demand has been set, the quantity to replenish for the different periods will automatically be computed. The replenishments you are supposed to launch based on your lead times (vendor lead time or manufacturing lead time) are then displayed in green. You can now launch the replenishment by clicking on the replenish button." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:52 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:54 msgid "Depending on the configuration of the product (buy vs. manufacture), requests for quotations or manufacturing orders will be created. You can easily access those by clicking on the *Actual Replenishment* cell." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:59 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:61 msgid "In case you manually edit the *Suggested Replenishment* quantity, a small cross will appear on the left hand side of the cell. In case you want to go back to the automatically computed value given by Odoo, simply click the cross." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:65 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 msgid "Cells color signification" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:69 msgid "The cells, which are part of the *Suggested Replenishment* line, can take different colors depending on the situation:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:70 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 msgid "**Green**: quantity of products which should be replenished to reach the expected safety stock considering the demand forecast and the indirect demand forecast." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 msgid "**Grey**: replenishment order has already been generated, and its quantity still matches current data." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 msgid "**Red**: replenishment order has already been generated, and its quantity was too high considering current data." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 msgid "**Orange**: replenishment order has already been generated, and its quantity was too low considering current data." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:80 msgid "The *Forecasted stock* line can also contain red cells, which means the stock will be negative during the period in question." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 msgid "What if I have underestimated the demand?" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:86 msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and youā€™ll be able to launch a new replenishment." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:89 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 msgid "What if I have overestimated the demand?" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:93 msgid "You can decrease the demand forecast. The cell will become red to inform you that youā€™ve ordered more than planned. If youā€™re still able to do it, you can cancel some RFQ or MO manually." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:96 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 msgid "What if I wrongly added a product to the MPS?" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:100 msgid "You can easily remove a product from the MPS by clicking the small bin on the right of its name." msgstr "" @@ -9114,39 +10450,39 @@ msgstr "" msgid "An example of a fully configured work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 msgid "Set standards for work center productivity" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:39 msgid "The :guilabel:`General Information` tab on the work center form allows for productivity goals to be assigned to a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:42 msgid ":guilabel:`Time Efficiency`: used to calculate the expected duration of a work order at the work center; for example, if a work order normally takes one hour and the efficiency is set to 200%, the work order will take 30 minutes" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:43 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 msgid ":guilabel:`Capacity`: the number of operations that can be performed at the work center simultaneously" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 msgid ":guilabel:`OEE Target`: the target for efficiency at the work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:46 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 msgid ":guilabel:`Time before prod.`: setup time required before work can commence" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 msgid ":guilabel:`Time after prod.`: breakdown or cleanup time required after work is finished" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:50 msgid ":guilabel:`Cost per hour`: the cost of operating the work center for one hour" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:51 msgid ":guilabel:`Analytic Account`: the account where the cost of the work center should be recorded" msgstr "" @@ -9154,35 +10490,35 @@ msgstr "" msgid "The general information tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:56 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 msgid "Assign equipment to a work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:60 msgid "Using the :guilabel:`Equipment` tab, it is possible for specific pieces of equipment to be assigned to a work center. The following information will be displayed for each piece of equipment added:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 msgid ":guilabel:`Equipment Name`: the name of the piece of equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:62 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 msgid ":guilabel:`Technician`: the technician responsible for servicing the equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:65 msgid ":guilabel:`Equipment Category`: the category the equipment belongs to" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 msgid ":guilabel:`MTBF`: mean time between failures; the average time that the piece of equipment will operate before failing" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 msgid ":guilabel:`MTTR`: mean time to recovery; the average time it takes for the equipment to become fully operational again" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:70 msgid ":guilabel:`Est. Next Failure`: an estimate of when the next equipment failure will occur" msgstr "" @@ -9190,27 +10526,27 @@ msgstr "" msgid "The equipment tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:75 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:77 msgid ":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are all calculated automatically based on past failure data, if any exists." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:81 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 msgid "Integrate IoT devices" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:85 msgid "The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT (Internet of Things)` devices with a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 msgid ":guilabel:`Device`: specifies the IoT device to be triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:87 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:89 msgid ":guilabel:`Key`: the security key for the device" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:90 msgid ":guilabel:`Action`: the IoT device action triggered" msgstr "" @@ -9218,19 +10554,19 @@ msgstr "" msgid "The IoT Triggers tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:95 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 msgid "Use case: configure an alternative work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:99 msgid "When a work center is at capacity, it cannot accept any new work orders. Instead of waiting for the work center to become available, it is possible to specify an alternative work center where surplus work orders should be carried out." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:101 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:103 msgid "Begin by creating a new work center. Configure the :guilabel:`Equipment` tab so that it has all of the same equipment as the main work center. This will ensure that the same tasks can be carried out at both work centers. Navigate to the main work center and include the new work center in the :guilabel:`Alternative Workcenters` selection field." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:108 msgid "Now, create a new manufacturing order that uses the main work center for one of its operations. The main work center will automatically be selected for the operation in the :guilabel:`Work Orders` tab. After confirming the manufacturing order, click the :guilabel:`Plan` button that appears at the top left of the form." msgstr "" @@ -9238,7 +10574,7 @@ msgstr "" msgid "Click the plan button to automatically select an available work center." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:115 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:117 msgid "If the main work center is at capacity, the work center selected for the operation will be automatically changed to the alternative work center." msgstr "" @@ -9246,27 +10582,27 @@ msgstr "" msgid "The alternative work center is automatically selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 msgid "Monitor work center performance" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:127 msgid "Performance for an individual work center can be viewed by selecting :menuselection:`Configuration --> Work Centers`, and clicking on a work center. A variety of metrics showing work center performance can be viewed at the top right of the form:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:129 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 msgid ":guilabel:`OEE`: overall effective efficiency, the percentage of time that the work center has been fully productive" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:132 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:134 msgid ":guilabel:`Load`: the amount of time it will take to complete the current workload" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:135 msgid ":guilabel:`Performance`: the real duration of work time, shown as a percentage of the expected duration" msgstr "" @@ -9386,6 +10722,1304 @@ msgstr "" msgid "Once the time-off period for the unavailable work center ends, Odoo recognizes that the work center is available again. At this point, clicking the :guilabel:`Plan` button does not route work orders to an alternative work center unless the first one is at capacity." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:3 +msgid "Work order dependencies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:7 +msgid "When manufacturing certain products, specific operations may need to be completed before others can begin. In order to ensure operations are carried out in the correct order, Odoo *Manufacturing* features a *work order dependencies* setting. Enabling this setting allows for operations on a Bill of Materials (BoM) to be *blocked* by other operations that should occur first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:15 +msgid "The *work order dependencies* setting is not enabled by default. To enable it, begin by navigating to :menuselection:`Manufacturing --> Configuration --> Settings`. Then, enable the :guilabel:`Work Orders` setting, if it is not already active." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:19 +msgid "After enabling the :guilabel:`Work Orders` setting, the :guilabel:`Work Order Dependencies` setting appears below it. Enable :guilabel:`Work Order Dependencies`, then click :guilabel:`Save` to confirm the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:24 +msgid "Add dependencies to BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:26 +msgid "Work order dependencies are configured on a product's |BOM|. To do so, navigate to :menuselection:`Manufacturing --> Products --> Bills of Materials`, then select a |BOM|, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:32 +msgid "For a complete guide on how to properly configure a new |BOM|, see the documentation on :ref:`creating a bill of materials `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:35 +msgid "On the |BOM|, click on the :guilabel:`Miscellaneous` tab, then enable the :guilabel:`Operation Dependencies` checkbox. This makes a new :guilabel:`Blocked By` option available in the settings of the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +msgid "The Operation Dependencies checkbox on the Miscellaneous tab of a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:43 +msgid "Next, click on the :guilabel:`Operations` tab. On the top-right of the tab, click on the tab's :guilabel:`settings` button, then enable the :guilabel:`Blocked By` checkbox. This makes a :guilabel:`Blocked By` field appear for each operation on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +msgid "The settings for the Operations tab on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:51 +msgid "In the line of the operation that should be blocked by another operation, click the :guilabel:`Blocked By` field, and an :guilabel:`Open: Operations` pop-up window appears. In the :guilabel:`Blocked By` drop-down field on the pop-up window, select the blocking operation that must be completed *before* the operation that is blocked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +msgid "The Blocked By drop-down field for an operation on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:60 +msgid "Finally, save the |BOM| by clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:63 +msgid "Plan work orders using dependencies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:65 +msgid "Once work order dependencies have been configured on a |BOM|, Odoo *Manufacturing* is able to plan when work orders are scheduled, based on their dependencies. To plan the work orders for a manufacturing order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:70 +msgid "Next, select a manufacturing order for a product with work order dependencies set on its |BOM|, or create a new manufacturing order by clicking :guilabel:`New`. If a new manufacturing order is created, select a |BOM| configured with work order dependencies from the :guilabel:`Bill of Material` drop-down field, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:75 +msgid "After confirming the manufacturing order, select the :guilabel:`Work Orders` tab to view the work orders required to complete it. Any work orders that are *not* blocked by a different work order display a `Ready` tag in the :guilabel:`Status` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:79 +msgid "Work orders that are blocked by one or more work orders display a `Waiting for another WO` tag instead. Once the blocking work order(s) are completed, the tag updates to `Ready`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +msgid "The status tags for work orders on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:86 +msgid "To schedule the manufacturing order's work orders, click the :guilabel:`Plan` button at the top of the page. After doing so, the :guilabel:`Scheduled Start Date` field for each work order on the :guilabel:`Work Orders` tab auto-fills with the scheduled start date and time. A blocked work order is scheduled at the end of the time period specified in the :guilabel:`Expected Duration` field of the work order that precedes it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +msgid "The Scheduled Start Date field for work orders on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:97 +msgid "A manufacturing order is created for Product A. The manufacturing order has two operations: Cut and Assemble. Each operation has an expected duration of 60 minutes, and the Assemble operation is blocked by the Cut operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:101 +msgid "The :guilabel:`Plan` button for the manufacturing order is clicked at 1:30 pm, and the Cut operation is scheduled to begin immediately. Since the Cut operation has an expected duration of 60 minutes, the Assemble operation is scheduled to begin at 2:30 pm." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:106 +msgid "Planning by workcenter" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:108 +msgid "To see a visual representation of how work orders are planned, navigate to the :guilabel:`Work Orders Planning` page by going to :menuselection:`Manufacturing --> Planning --> Planning by Workcenter`. This page shows a timeline of all the work orders scheduled for each operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:112 +msgid "If one work order is blocked by the completion of another, the work order that is blocked is shown as scheduled to start after the work order blocking it. In addition, an arrow connects the two work orders, leading from the blocking operation to the blocked operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +msgid "The arrow connecting a blocked work order to the work order blocking it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor.rst:5 +msgid "Shop Floor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:3 +msgid "Shop Floor overview" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:9 +msgid "The *Shop Floor* module is a companion module to the *Manufacturing* app. *Shop Floor* provides a visual interface for processing manufacturing orders (MOs) and work orders. It also allows manufacturing employees to track the amount of time spent working on manufacturing and work orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:13 +msgid "The *Shop Floor* module is installed alongside the *Manufacturing* app. It cannot be installed by itself. To install the *Manufacturing* app, navigate to :menuselection:`Apps`, search for `manufacturing` in the :guilabel:`Search...` bar, and then click :guilabel:`Install` on the :guilabel:`Manufacturing` app card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:19 +msgid "The *Shop Floor* module replaces the tablet view functionality of the *Manufacturing* app, and is only available in Odoo versions 16.4 and later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:22 +msgid "To check the version number of an Odoo database, navigate to :menuselection:`Settings` and scroll down to the :guilabel:`About` section at the bottom of the page. The version number is displayed there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:26 +msgid "To switch to a newer version of Odoo, see the documentation on :ref:`upgrading a database `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:30 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:32 +msgid "*Shop Floor* is broken down into three main views, which can be selected from the navigation bar at the top of the module:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:35 +msgid "The :guilabel:`All` page serves as the main dashboard for the module, and displays information cards for |MOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:37 +msgid "Each work center also has a dedicated page, which shows information cards for work orders assigned to that work center. Work center pages can be toggled on or off by clicking the :guilabel:`+ (plus)` button in the navigation bar, selecting or deselecting them on the pop-up window that appears, and then clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:41 +msgid "The :guilabel:`My` page shows information cards for all work orders assigned to the employee whose profile is currently active in the operator panel on the left side of the module. Other than only showing work orders assigned to the active employee, this page functions the same as the pages for each work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:47 +msgid "To isolate an |MO| or work order, so that no other orders appear, simply search the reference number of the |MO| in the :guilabel:`Search...` bar at the top of the module. This search filter remains active while switching between the different module views." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:51 +msgid "On the left side of the module is the operator panel, which shows all of the employees currently signed in to *Shop Floor*, and allows new employees to sign in. The operator panel is always available in the module, regardless of which view is selected. It can be toggled on or off by clicking the :guilabel:`sidebar` button at the extreme left of the navigation bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:-1 +msgid "The \"sidebar\" button, which is used to toggle the operator panel on or off." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:61 +msgid "All page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:63 +msgid "By default, the :guilabel:`All` page shows an information card for every |MO| that is *ready to start*. An |MO| is considered ready to start once it has been confirmed, and all required components are available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:67 +msgid "To view every confirmed |MO| regardless of readiness, click the :guilabel:`x` button on the :guilabel:`Ready to Start` filter to remove it from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:71 +msgid "MO information card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:73 +msgid "An |MO| information card on the :guilabel:`All` page shows all of the relevant details of the associated |MO|, and also provides employees with options for processing the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:76 +msgid "The header for an |MO| card shows the |MO| number, the product and number of units being produced, and the status of the |MO|. If work has not yet begun on the |MO|, the status appears as :guilabel:`Confirmed`. Once work has begun, the status updates to :guilabel:`In Progress`. If all work orders for an |MO| have been completed and the |MO| is ready to close, the status updates to :guilabel:`To Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:82 +msgid "The main body of an |MO| card shows a line for each completed work order, if any, followed by the current work order that needs to be completed. Completed work orders are indicated by a green check mark to the right of title of the work order. The current work order is indicated by a button that opens the page for the work center to which the order is assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:87 +msgid "Below the current work order is a line titled :guilabel:`Register Production`, which is used to record the number of product units produced. To manually enter the number of units produced, click on the :guilabel:`Register Production` line, enter a value in the :guilabel:`Units` field of the resulting pop-up window, then click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:92 +msgid "Alternatively, click the :guilabel:`# Units` button on the right side of the line, which automatically records the number of units the |MO| was created for as the number of units produced. For example, if an |MO| is created for 10 units of a dining table, clicking the :guilabel:`10 units` button records that 10 units were produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:97 +msgid "The footer of the |MO| card displays a :guilabel:`Close Production` button. This is used to close the |MO| once production is completed. However, if there are any quality checks required for the |MO| as a whole (not the work orders within it), a :guilabel:`Quality Checks` button appears instead. Clicking :guilabel:`Quality Checks` opens a pop-up window, from which any required quality checks can be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:103 +msgid "After clicking :guilabel:`Close Production`, the |MO| card begins to fade away, and an :guilabel:`Undo` button appears on the footer. Clicking :guilabel:`Undo` causes the |MO| to remain open. Once the |MO| card disappears completely, the work order is closed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:107 +msgid "On the right side of the footer is an :guilabel:`ā‹® (options)` button, which opens a pop-up window with additional options for the |MO|:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:171 +msgid ":guilabel:`Scrap` is used to send components to a scrap location when they are found to be defective." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:112 +msgid ":guilabel:`Add Work Order` is used to add an additional work order to the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:113 +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:173 +msgid ":guilabel:`Add Component` is used to add an additional component to the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:114 +msgid ":guilabel:`Open Backend MO` opens the |MO| in the Manufacturing app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:-1 +msgid "An information card for an MO on the \"All\" page of the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:121 +msgid "Work center pages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:123 +msgid "By default, the page for each work center shows an information card for every work order assigned to it that is *ready to start*. A work order is considered ready to start once the |MO| it is a part of is ready to start, and any preceding work orders have been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:127 +msgid "To view every confirmed work order assigned to a work center regardless of readiness, click the :guilabel:`x` button on the :guilabel:`Ready to Start` filter to remove it from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:132 +msgid "Work order information card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:134 +msgid "A work order information card on a work center's page shows all of the relevant details of the associated work order, and also provides employees with options for processing the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:137 +msgid "The header for a work order card shows the reference number of the |MO| that the work order is a part of, the product and number of units being produced, and the status of the work order. If work has not yet begun on the work order, the status appears as :guilabel:`To Do`. Once work has begun, the status updates to display a timer showing the total time the work order has been worked on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:142 +msgid "The main body of a work order card shows a line for each step required to complete the work order. Work order steps can be completed by clicking on the line, then following the instructions on the pop-up window that appears. Alternatively, clicking the checkbox on the right side of each line automatically marks the step as completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:147 +msgid "Below the final step of the work order is a line titled :guilabel:`Register Production`, which functions the same as the :guilabel:`Register Production` line on an |MO| card. Registering the number of units produced using the :guilabel:`Register Production` line on a work order card also completes the step for the associated |MO| card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:152 +msgid "If the work order being processed is the final work order for the |MO|, a :guilabel:`Close Production` button appears on the footer of the work order card. Clicking :guilabel:`Close Production` closes both the work order and the |MO|, unless a quality check is required for the |MO|. In this case, the quality check must be completed from the |MO| card before the |MO| can be closed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:158 +msgid "Alternatively, if the |MO| requires the completion of additional work orders, a :guilabel:`Mark as Done` button appears instead. Clicking :guilabel:`Mark as Done` marks the current work order as completed, and causes the next work order to appear on the page for the work center it is assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:163 +msgid "After clicking :guilabel:`Close Production` or :guilabel:`Mark as Done`, the work order card begins to fade away, and an :guilabel:`Undo` button appears on the footer. Clicking :guilabel:`Undo` causes the work order to remain open. Once the work order card disappears completely, the work order is marked as :guilabel:`Finished` on the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:168 +msgid "On the right side of the footer is an :guilabel:`ā‹® (options)` button, which opens a pop-up window with additional options for the work order:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:174 +msgid ":guilabel:`Move to work center` is used to transfer the work order to a different work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:175 +msgid ":guilabel:`Suggest a Worksheet improvement` allows the user to propose a change to the work order's instructions or steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:177 +msgid ":guilabel:`Create a Quality Alert` opens a quality alert form that can be filled out to alert a quality team about a potential issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:-1 +msgid "An information card for a work order in the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:185 +msgid "Operator panel" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:187 +msgid "The operator panel is used to manage the employees that are signed in to the *Shop Floor* module. The panel shows the name and profile picture of every employee that is currently signed in across all instances of the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:191 +msgid "To interact with *Shop Floor* as a specific employee, click the employee's name to activate their profile. Profiles that are not active appear with their names and profile pictures greyed-out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:194 +msgid "When an employee is selected in the operator panel, they can begin working on a work order by clicking the work order's heading. If an employee is working on one or more work orders, the work order title(s) appear under their name, along with a timer showing how long they've been working on each order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:199 +msgid "To add a new employee to the operator panel, click the :guilabel:`+ Add Operator` button at the bottom of the panel. Then, select an employee from the :guilabel:`Select Employee` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:202 +msgid "To remove an employee from the operator panel, simply click the :guilabel:`x` button next to their name in the panel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:-1 +msgid "The operator panel of the Shop Floor module, showing three employees signed in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:8 +msgid "Product lifecycle management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:10 +msgid "Odoo *Product Lifecycle Management* (*PLM*) offers a systematic approach for testing, collaboration, and iteration of products across concept development, design, manufacturing, marketing, and post-launch support stages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:14 +msgid "With approvals, key stakeholders can review changes before implementation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes.rst:3 +msgid "Change management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:10 +msgid "ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:12 +msgid "An *ECO type* is assigned to *engineering change orders* (ECOs) to organize and track changes to products and bills of materials (BoMs). Each |ECO| type separates |ECOs| into a project in Gantt view, ensuring collaborators and stakeholders **only** view and assist with relevant |BOM| improvements." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:17 +msgid "For example, an electronic chip manufacturer might use 'New Product Introduction', 'Product Improvement', 'Component Change', and 'Firmware Update' |ECO| types. Then, designers and engineers can focus on |ECOs| in the 'New Product Introduction' and 'Product Improvement' projects, avoiding unrelated supplier change or firmware update |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:23 +msgid "Create ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:25 +msgid "To access and manage ECO types, navigate to :menuselection:`PLM app --> Configuration --> ECO Types`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:28 +msgid "Create a new ECO type by clicking :guilabel:`New`. On the new :guilabel:`ECO Types` form, fill in the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:31 +msgid ":guilabel:`Name`: the name of the |ECO| type, which will organize all of the |ECOs| of this *type* in a project." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:33 +msgid ":guilabel:`Email Alias`: if this optional field is filled, emails submitted to this email address automatically generate |ECOs| in the left-most stage of this |ECO| type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:37 +msgid "The `Formulation change` |ECO| type is used to organize and track related |ECOs| in a single project. Configuring the :guilabel:`Email Alias` field generates |ECOs| in the `Formulation change` project sent to the email address, `pawlish-change@pawlished-glam.odoo.com`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Example of an ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:46 +msgid "Edit ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:48 +msgid "Modify existing |ECO| type names and email aliases by navigating to the :menuselection:`PLM app --> Configuration --> ECO Types` page. There, click on the desired |ECO| type from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:51 +msgid "On the form for each |ECO| type, proceed to edit the :guilabel:`Name` and :guilabel:`Email Alias` fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:57 +msgid "Stages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:59 +msgid "Within an |ECO| type project, *stages* are like milestones and are used to identify the progress of the |ECO| before the changes are ready to be applied. (e.g. 'Feedback', 'In Progress', 'Approved', 'Complete')" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:63 +msgid "Additionally, required approvers can be added to each stage, ensuring that changes to the production |BOM| cannot proceed until the approver reviews and approves the |ECO|. Doing so prevents errors on the production |BOM| by enforcing at least one review of suggested changes before they're applied on a production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:68 +msgid "For best practice, there should be at least one *verification* stage, which is a stage with a required approver, and one *closing* stage, which stores |ECOs| that have been either canceled or approved for use as the next production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:73 +msgid "Create stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:75 +msgid "To add a stage, go to the :menuselection:`PLM` app and select the intended project for an |ECO| type from the :guilabel:`PLM Overview` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:78 +msgid "Then, on the :guilabel:`Engineering Change Orders` project pipeline for the |ECO| type, click the :guilabel:`+ Stage` button. Doing so reveals a text box to fill in the name of the stage. After filling it in, click the :guilabel:`Add` button to finish adding the stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:83 +msgid "A new `Assigned` stage separates assigned |ECOs| from the unassigned ones in the `New` stage. Adding another stage helps the product manager track unassigned tasks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Create a new stage in a project for an ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:91 +msgid "Verification stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:93 +msgid "Click an ECO type from :menuselection:`PLM app --> Overview` to open a kanban view of |ECOs| of this type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:96 +msgid "To configure a verification stage, hover over the intended stage, and select the :guilabel:`āš™ļø (gear)` icon. Then, click :guilabel:`Edit` to open a pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:99 +msgid "Configure the verification stage in the edit stage pop-up window, by checking the box for :guilabel:`Allow to apply changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:102 +msgid "Then, add an approver in the :guilabel:`Approvers` section, by clicking :guilabel:`Add a line`, and specifying the :guilabel:`Role` of the reviewer, their :guilabel:`User`, and :guilabel:`Approval Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:106 +msgid "Make sure at least one approver is configured with the :guilabel:`Approval Type`: :guilabel:`Is required to approve`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:109 +msgid "The approver listed is automatically notified when |ECOs| are dropped in the stage specified in the pop-up window. Once finished, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:113 +msgid "In the |ECO| type `New Product Introduction`, the verification stage `Validated` is configured by clicking the :guilabel:`āš™ļø (gear)` icon, and selecting :guilabel:`Edit`. Doing so opens the :guilabel:`Edit: Validated` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:117 +msgid "By adding the `Engineering manager` as an approver, only |ECOs| approved by this user can proceed to the next stage, and have the changes applied on the production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:120 +msgid "Additionally, check the :guilabel:`Allow to apply changes` option to ensure proper behavior." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Show \"Allow to apply changes\" option is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:127 +msgid "Closing stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:129 +msgid "Configure a closing stage by opening the :guilabel:`Edit: [stage]` pop-up window. To do so, hover over the intended stage and click the :guilabel:`āš™ļø (gear)` icon that appears in the top-right corner. Then, click :guilabel:`Edit` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:133 +msgid "On the :guilabel:`Edit: [stage]` pop-up window, select the check boxes for :guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes` and :guilabel:`Final Stage`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:137 +msgid "The closing stage, `Effective` is configured by checking the :guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes`, and :guilabel:`Final Stage` options" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:-1 +msgid "Show configurations of the closing stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:3 +msgid "Engineering change orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:12 +msgid "Utilize *engineering change orders* (*ECOs*) to track, implement, and revert change versions made to products, and :ref:`bills of materials `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:15 +msgid "Engineering change orders can be created:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:17 +msgid ":ref:`directly in the ECO type `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:18 +msgid "by an operator in the :ref:`tablet view ` of an operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:19 +msgid "automatically from feedback submitted to the :ref:`ECO type's email alias `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:24 +msgid "Create ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:26 +msgid "To create a new |ECO|, begin by navigating to the *PLM* app. Then, select the |ECO| type card that will be used to track the progress of the change. On the :guilabel:`Engineering Change Orders` page, click the :guilabel:`New` button in the top-left corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:31 +msgid "Learn how to create new :ref:`ECO types ` to categorize and organize change orders. Doing so ensures employees only view the |ECOs| related to their responsibilities, whether it involves new product introductions, targeted product line updates, or regulatory compliance fulfillment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:36 +msgid "On the |ECO| form, fill in the following fields accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:38 +msgid ":guilabel:`Description` is a brief summary of the improvement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:39 +msgid ":guilabel:`Type`: specifies the |ECO| type project for organizing the |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:40 +msgid ":guilabel:`Apply on` determines if the |ECO| changes the :guilabel:`Bill of Materials` or the :guilabel:`Product Only`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:42 +msgid ":guilabel:`Product` indicates the product being improved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:43 +msgid ":guilabel:`Bill of Materials` specifies the changed |BOM|. It auto-populates if the product in :guilabel:`Product` field has an existing |BOM|. If multiple |BOMs| exist, select the intended radio options from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:46 +msgid ":guilabel:`Company` field is used in multi-company databases. Specify if the change applies to products in a specific company, or leave blank if the change applies to all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:48 +msgid ":guilabel:`Responsible` represents the assignee in charge of this |ECO|. (Optional)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:49 +msgid ":guilabel:`Effective` specifies when the |ECO| becomes live. Choosing :guilabel:`As soon as possible` means the |ECO| applies to the production |BOM| as soon as an authorized user :ref:`applies the changes `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:53 +msgid "On the other hand, choosing :guilabel:`At Date`, and setting a specific date, leaves a date that makes it easier to track the version history of the |BOM|, and the specific date |BOMs|, used for production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:56 +msgid ":guilabel:`Tags` are assigned to |ECOs| for prioritization and organization. Create a new tag by typing the name in the field and selecting :guilabel:`Create` from the drop-down menu. (Optional)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:59 +msgid "After filling out the |ECO| form, click the :guilabel:`Start Revision` button to begin implementing the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:62 +msgid "By pressing :guilabel:`Start Revision`, three actions occur:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:64 +msgid "The :guilabel:`Documents` smart button appears, storing relevant files of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:65 +msgid "A copy of the production |BOM| is stored in the newly-appeared :guilabel:`Revision` smart button of the |ECO|. The next available version number (e.g., `V2`, `V3`, ...) is also assigned to keep track of all |BOM| versions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:68 +msgid "The stages of the |ECO| :guilabel:`Type` are displayed in the top-right corner of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:71 +msgid "The :guilabel:`Revision` smart button is available **only** when the :guilabel:`Bill of Materials` radio button is selected in the :guilabel:`Apply on` field, and the :guilabel:`Start Revision` button has been pressed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:-1 +msgid "ECO with overview of stages in the top-right corner, and *Revision* smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:80 +msgid "Change components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:82 +msgid "To modify the components in a |BOM|, click the :guilabel:`Revision` smart button on an |ECO| to access the new version of the |BOM|. Odoo distinguishes the non-production version of the |BOM| from the current version, by flagging the test |BOM| with a large :guilabel:`Archived` tag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:87 +msgid "After clicking the :guilabel:`Start Revision` button for an |ECO| for the product, `[D_0045 Stool]`, make changes to the product's |BOM| by clicking the :guilabel:`Revision` smart button. Doing so opens the archived |BOM|, marked with a large red :guilabel:`Archived` flag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Show the archived Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:95 +msgid "On the new |BOM|, in the :guilabel:`Components` tab, proceed to modify the components list, by changing the :guilabel:`Quantity` of existing components, adding new components using the :guilabel:`Add a line` button, and removing components with the :guilabel:`šŸ—‘ļø (trash)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:102 +msgid "In version two of the |BOM| for a keyboard, the component quantities are reduced, and an additional component, `Stabilizers`, is added." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Make changes to components by going to the new BoM with the *Revision* smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:110 +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:153 +msgid "Compare changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:112 +msgid "Once the changes are complete, navigate back to the |ECO|, by clicking `ECO00X` in the breadcrumbs located in the top-left corner. On the |ECO| form, a new :guilabel:`BoM Changes` tab displays the differences between the current |BOM| and the new version." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:116 +msgid "Blue text indicates new components added to the revised |BOM| that are not in the production |BOM|. Black text represents updates shared by both |BOMs|, while red text indicates components removed in the revised |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:120 +msgid "Changes and tests are encapsulated in the revised |BOM|, and do **not** affect the |BOM| currently used in production. That is, until the :ref:`changes are applied `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:124 +msgid "View the summary of the differences between the current and revised keyboard |BOMs| in the :guilabel:`BoM Changes` tab of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "View summary of component changes in the *BoM Changes* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:132 +msgid "Change operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:134 +msgid "To modify the operations in a |BOM|, click the :guilabel:`Revision` smart button on an |ECO| to access the archived, new version of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:137 +msgid "In the new |BOM| version, switch to the :guilabel:`Operations` tab to view and edit |BOM| operations. To make changes, select each operation, which opens the corresponding :guilabel:`Open: Operations` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:142 +msgid "The :guilabel:`Operations` tab is *not* available by default. To enable it, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and check the :guilabel:`Work Orders` box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:146 +msgid "Make changes to any of the fields in the :guilabel:`Open: Operations` pop-up window, then click :guilabel:`Save` once completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:149 +msgid "Create new operations by clicking the :guilabel:`Add a line` button, and remove new operations by clicking the :guilabel:`Archive Operation` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:155 +msgid "Once the changes are complete, navigate back to the |ECO|, by clicking `ECO00X` in the breadcrumbs located in the top-left corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:158 +msgid "On the |ECO| form, a new :guilabel:`Operation Changes` tab displays the differences between the current production |BOM| and the new version." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:161 +msgid "Blue text indicates new operations added to the revised |BOM| that do not yet exist in the production |BOM|. Black text represents updates shared by both |BOMs|, while red text indicates operations removed in the revised |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:165 +msgid "Modifications to the |BOM| in an |ECO| will **not** affect the |BOM| used in production. That is, until the :ref:`changes are applied `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:168 +msgid "In the :guilabel:`Operation Changes` tab, each row of details, beneath the columns in the table, reflect the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:171 +msgid ":guilabel:`Operation`: Name of the operation that was modified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:172 +msgid ":guilabel:`Step`: specifies the quality control point, visible when the operation includes detailed instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:176 +msgid "To check for instructions, click the operation line item in the :guilabel:`Operations` tab of a |BOM|. Then, in the :guilabel:`Open: Operations` pop-up window, look for the :guilabel:`Instructions` smart button displayed at the top." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:181 +msgid "The `Assembly` :guilabel:`Operation` includes `10` detailed :guilabel:`Instructions` to complete it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Show *Instructions* smart button to check whether an operation has additional\n" +"instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:189 +msgid ":guilabel:`Step Type` details the type of quality control for further instructions in the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:191 +msgid ":guilabel:`Type` corresponds with the colored text to specify how the revised |BOM| differs from the production |BOM|. Operation change types can be :guilabel:`Add`, :guilabel:`Remove`, or :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:194 +msgid ":guilabel:`Work Center` specifies the work center at which the operation is performed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:195 +msgid ":guilabel:`Manual Duration Change` refers to the change in the :guilabel:`Default Duration` field in the :guilabel:`Open: Operations` pop-up window, which specifies the expected time for completing the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:200 +msgid "The :guilabel:`Operation Changes` tab compares the production |BOM| with the revised |BOM| in the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:203 +msgid "In the revised |BOM|, a new `Assembly` :guilabel:`Operation` at the :guilabel:`Work Center` `Assembly Line 1` is added. In addition, the expected duration of the operation is `20.00` minutes, as specified by the :guilabel:`Manual Duration Change`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:207 +msgid "To supplement the `Assembly` operation, two quality control point instructions are added:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:209 +msgid "The first is the :guilabel:`Step` `QCP00039`, a :guilabel:`Step Type` to :guilabel:`Register Production` of components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:211 +msgid "The second :guilabel:`Step` is `QCP00034`, an `Instructions` :guilabel:`Step Type` that provides additional assembly details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Show *Operation Changes* tab in an |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:221 +msgid "Apply changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:223 +msgid "After verifying the changes, move the |ECO| to a :ref:`verification stage `, which are stages that require approval before the revised changes can be applied to the production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:227 +msgid "Once the approvers accept the changes, the :guilabel:`Apply Changes` button becomes available. Click this button, and the |ECO| is automatically moved to a closing stage. The changes are applied, which archives the original production |BOM|, and the revised |BOM| becomes the new production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:232 +msgid "Verify changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:234 +msgid "To ensure the changes are live, from the |ECO| where the :guilabel:`Apply Changes` button was just pressed, return to the revised |BOM| by clicking the :guilabel:`Revision` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:237 +msgid "On the revised |BOM|, the large red :guilabel:`Archived` flag is removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:239 +msgid "To further verify the changes, check the production |BOM| by going to :menuselection:`Manufacturing app --> Products --> Products` and select the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:242 +msgid "Then, on the product form, click the :guilabel:`Bill of Materials` smart button, and select the |BOM| from the list. In the :guilabel:`Miscellaneous` tab of the |BOM|, the :guilabel:`Version` field is updated to match the version number shown on the :guilabel:`Revision` smart button of the latest |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:248 +msgid "After applying the changes of the |ECO| for the :ref:`keyboard `, view the version of the current keyboard |BOM| in the :guilabel:`Miscellaneous` tab. Here, the :guilabel:`Version` number has been updated to `2`, matching the `V2` that appears in the :guilabel:`Revision` smart button of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "View current *BOM* version in the Miscellaneous tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:260 +msgid "Create ECO from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:262 +msgid "Operators can directly suggest clearer operation instructions, while performing manufacturing orders (MOs) in the *Manufacturing* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:265 +msgid "To create |ECOs| in this manner, begin by navigating to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`. Then, select the desired :abbr:`MO (Manufacturing Order)` and switch to the :guilabel:`Work Orders` tab. Then, click the :guilabel:`šŸ“± (mobile phone)` icon for the desired work order to open the *tablet view* of the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:271 +msgid "The :guilabel:`šŸ“± (mobile phone)` icon is **only** available for :abbr:`MOs (Manufacturing Orders)` with a :guilabel:`Confirmed` or :guilabel:`In Progress` status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:-1 +msgid "Find the tablet icon for each operation, second from the far right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:278 +msgid "Next, add an instructional step, by clicking the :guilabel:`ā˜° (three horizontal lines)` icon in the tablet view of an operation. Doing so opens the :guilabel:`Menu` of action items for a :abbr:`MO (Manufacturing Order)`. Then, click the :guilabel:`Add a step` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:-1 +msgid "Open the *Add a Step* pop-up by clicking the three horizontal lines icon in tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:286 +msgid "Clicking the button reveals an :guilabel:`Add a step` pop-up window, where the proposed changes are submitted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:289 +msgid "In the :guilabel:`Title` field, enter a short step description. Next, in the :guilabel:`Instruction` text field, type the instructions of the step in greater detail. Optionally, add an image to the :guilabel:`Document` field. Once completed, finish by clicking the :guilabel:`Propose Change` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:295 +msgid "To propose an additional check for broken components, enter the details in the :guilabel:`Add a Step` pop-up window. Doing so creates an instructional quality control point that will be reviewed in the following section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Fill out the *Add a Step* form to suggest an additional quality control point." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:303 +msgid "Based on the inputs from the :guilabel:`Add a Step` pop-up window, an |ECO| is created with the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:306 +msgid ":guilabel:`Description` is the name of the operation, followed by the :abbr:`MO (Manufacturing Order)` number for reference." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:308 +msgid "The |ECO| :guilabel:`Type` is automatically assigned to `BOM Changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:309 +msgid ":guilabel:`Product` and :guilabel:`Bill of Materials` fields are automatically populated, based on the |BOM| used in the :abbr:`MO (Manufacturing Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:311 +msgid ":guilabel:`Responsible` is the operator who submitted the feedback." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:314 +msgid "View ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:316 +msgid "To review the proposed changes, navigate to the :menuselection:`PLM app --> Overview`. In the `BOM Updates` |ECO| type card, the :guilabel:`X Engineering Changes` button represents the amount of operational changes created from the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:320 +msgid "Click on the :guilabel:`X Engineering Changes` button to open the kanban view of the |ECO| type. To view the suggestion, select an |ECO| in the `New` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:323 +msgid "On the |ECO|, view a summary of the proposed changes in the :guilabel:`Operation Changes` tab. Click the :guilabel:`Revision` smart button to navigate to the revised |BOM| and look into the proposed changes in greater detail." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:328 +msgid "An operator suggested another check for broken components by adding a step from the tablet view, while performing the `Assemble switches` operation for the :abbr:`MO (Manufacturing Order)` `WH/MO/00010` for the product, `Keyboard`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:332 +msgid "Then, this created |ECO| can be viewed by navigating to the `BOM Changes` ECO type found in :menuselection:`PLM app --> Overview`. By default, |ECOs| created from tablet view are set to spawn in the `New` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:336 +msgid "The :guilabel:`Responsible` field is assigned to the operator who made the suggestion, allowing the employee revising the |BOM| to seek further clarification from the person who proposed the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Find the new ECO in the \"BOM Changes\" ECO type, in the *New* stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:344 +msgid "On the revised |BOM|, switch to the :guilabel:`Operations` tab, and select the :guilabel:`ā˜° (three horizontal lines)` icon. Doing so opens a list of :guilabel:`Steps` to perform the operation, with the newest instruction titled `New Step Suggestion:`, followed by the user-entered title. Click the line item to view the suggested changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:-1 +msgid "\"Show Instructions\" icon in the *Operations* tab of a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:353 +msgid "On the :ref:`quality control point ` form, ensure the following form fields are accurately filled out to give detailed instructions for operators:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:356 +msgid ":guilabel:`Title`: rename to give a concise description of the new instruction." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:357 +msgid ":guilabel:`Control per`: using the drop-down menu, determine whether this instruction applies broadly for the :guilabel:`Product`, specifically for this :guilabel:`Operation` *only*, or a particular :guilabel:`Quantity` of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:360 +msgid ":guilabel:`Type`: categorizes the control point type. From the drop-down menu, select :guilabel:`Instructions` to detail an instruction for the worker. To receive input from the workers, select the :guilabel:`Take a Picture`, :guilabel:`Register Consumed Materials`, :guilabel:`Print Label`, or other :ref:`quality check options `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:367 +msgid ":ref:`Configure quality control points `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:369 +msgid "Once the quality control point is configured, return to the :guilabel:`Steps` list using the breadcrumbs. Finally, drag the last quality control line item to its intended order of instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:373 +msgid "Drag and reorder the `Check for broken switches` instruction, by clicking and dragging its \"6 dots\" icon to move it from the bottom to the second position." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Drag and reorder instructions by selecting the \"6 dots\" icon on the far left." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:3 +msgid "Version control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:10 +msgid "Use Odoo's *Product Lifecycle Management (PLM)* to manage previous versions of bills of materials (BoMs). Store former assembly instructions, component details, and past product design files while keeping the past details out of the production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:14 +msgid "Easily revert to previous |BOM| versions, when needed. Additionally, use *PLM* to trace which |BOM| version was active on specific dates for recalls or customer complaints." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:17 +msgid "Every |BOM| version is stored in an *engineering change order* (ECO) for organized testing and improvements without disrupting normal manufacturing operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:21 +msgid ":ref:`Engineering change order `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:24 +msgid "Current BoM version" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:26 +msgid "To see the current version of the |BOM| used in production, go to :menuselection:`PLM app --> Master Data --> Bill of Materials`, and select the desired |BOM| from the list. Then, switch to the :guilabel:`Miscellaneous` tab, where the currently live :guilabel:`Version` of the |BOM| is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:32 +msgid "|BOMs| can also be accessed from :menuselection:`Manufacturing app --> Products --> Bill of Materials`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:-1 +msgid "Show the current version BOM in the Misc tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:40 +msgid "Version history" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:42 +msgid "To manage all former, current, and future versions of a |BOM|, begin by navigating to :menuselection:`Manufacturing app --> Products --> Bills of Materials` and click the desired |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:45 +msgid "From the |BOM| page, click the :guilabel:`ECO` smart button, and switch to list view by selecting the :guilabel:`ā‰£ (four horizontal lines)` icon on the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:49 +msgid "The :guilabel:`ECO` smart button is visible on the |BOM| **only** if the *PLM* app is installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:-1 +msgid "Show ECO smart button on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:55 +msgid "In the list of |ECOs| for the product, navigate to the search bar at the top, and click the :guilabel:`ā–¼ (down arrow)` icon on the right to access a drop-down menu of :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:58 +msgid "Next, filter by :guilabel:`Done` |ECOs| to view: the revision history of the |BOM|, the :guilabel:`Responsible` user who applied the change, and the :guilabel:`Effective Date` of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:62 +msgid "Click each |ECO| to view the past components, operations, and design files associated with the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:-1 +msgid "Display ECO revision history for a BoM for a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:70 +msgid "If the :guilabel:`Effective Date` field is empty, the :guilabel:`Effective` date of the |ECO| is automatically set to :guilabel:`As soon as possible` and no dates are recorded in the revision history of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "List of BOM effective dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:79 +msgid "A workaround for checking when the |BOM| went live is by navigating to the chatter, and hovering over the time the |ECO| was moved to the :ref:`closing stage `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:83 +msgid "Design files" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:85 +msgid "Attach computer-aided design (CAD) files, PDFs, images, or other design material to the |BOM| itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:88 +msgid "To do so, navigate to :menuselection:`PLM app --> Master Data --> Bill of Materials`, and select the desired |BOM|. On the |BOM|, navigate to the *chatter*, and click the :guilabel:`šŸ“Ž (paperclip)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:92 +msgid "The files associated with the |BOM| are displayed in the :guilabel:`Files` section. To add more design files, select the :guilabel:`Attach files` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:-1 +msgid "Show paperclip icon in the chatter to attach files to a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:100 +msgid "Manage design files in an ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:102 +msgid "Add, modify, and remove files in an |ECO|. Once the |ECO| is approved and applied, the new files are automatically linked to the production |BOM|. Archived files are removed from the |BOM|, but are still accessible in the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:106 +msgid "To manage the design files in the |ECO|, begin by navigating to :menuselection:`PLM app --> Changes` and choose the desired |ECO|. Next, open the :guilabel:`Attachments` page by clicking the :guilabel:`Documents` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:110 +msgid "Hover over each attachment to reveal the :guilabel:`ļø™ (three vertical dots)` icon. From there, choose whether to :guilabel:`Edit`, :guilabel:`Remove`, or :guilabel:`Download` the file. Any changes made to these files are contained within the |ECO|, and will only apply to the production |BOM| once the :ref:`changes are applied `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:116 +msgid "In the `Create 60% keyboard` |ECO|, the design files are from the original `100% keyboard` |BOM|. To replace the keyboard PDF, begin by selecting the :guilabel:`Documents` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "Show *Documents* smart button from an active ECO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:123 +msgid "On the :guilabel:`Attachments` page, hover over the `100% keyboard manual.pdf` design file, and click the :guilabel:`ļø™ (three vertical dots)` icon. Then, click the :guilabel:`Remove` option to archive the file." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:127 +msgid "Next, on the same :guilabel:`Attachments` page, click the :guilabel:`Upload` button to upload the new design file, named `60% keyboard manual`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "View of *Attachments* page from the *Documents* smart button. Displays one archived and\n" +"one newly added attachment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:136 +msgid "Archived files are **not** permanently deleted ā€” they can still be accessed in the previous |ECO|, or as an archived file in the latest |ECO|, where the archival occurred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:140 +msgid "Apply rebase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:142 +msgid "Odoo simplifies merge conflict resolution for concurrent |ECOs| on the same product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:144 +msgid "Conflicts can occur when the production |BOM| is updated while other |ECOs| are modifying the previous version. Differences between the new and previous production |BOMs| are displayed in the :guilabel:`Previous Eco Bom Changes` tab, visible only in this scenario." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:148 +msgid "To resolve conflicts and retain |ECO| changes, click the :guilabel:`Apply Rebase` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:151 +msgid "Two |ECOs|, `ECO0011` and `ECO0012`, are created when the current |BOM| version is `5`. In `ECO0011`, a new component, `Space stabilizer`, is added, and the changes are applied. This means the current |BOM| version has become `6`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "Apply changes to an ECO to update the production BOM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:159 +msgid "This means `ECO0012` is modifying an outdated |BOM|. As shown in the :guilabel:`Previous Eco Bom Changes` tab, the |BOM| is missing the `Space stabilizer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:162 +msgid "To ensure the changes applied by `ECO0011` are kept when the changes occur in `ECO0012`, click the :guilabel:`Apply Rebase` button to apply the previous |ECO| changes, without affecting the changes already made to `ECO0012`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "Click the *Apply Rebase* button to update the BOM to match the production BOM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management.rst:3 +msgid "Project management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:3 +msgid "Approvals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:10 +msgid "Notify stakeholders and managers automatically by assigning approvers to stages of :ref:`engineering change orders ` (ECOs) under review. Changes can only be applied after the assigned approver accepts them. Approvals ensure reviews by team members, which prevents mistakes and premature actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:16 +msgid ":ref:`Stage configuration `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:19 +msgid "Add approver" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:21 +msgid "To add an approver, first go to the :menuselection:`PLM app`, and click on the project card of an ECO type to open the Gantt view of the |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:24 +msgid "On the :guilabel:`Engineering Change Orders` page, hover over the intended stage, and select the :guilabel:`āš™ļø (gear)` icon. Then, click :guilabel:`Edit` to open a pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:28 +msgid "Approvers can be added to any stage, but it's strongly recommended to assign them to the *verification* stage, which comes before the *closing* stage, where |ECOs| are applied, and the :abbr:`BoM (Bill of Materials)` version is updated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:32 +msgid "See the documentation about :ref:`stage types ` for more information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:36 +msgid "In the :guilabel:`Edit` stage pop-up window, click the :guilabel:`Add a line` button, located under :guilabel:`Approvals`. Then, type in the approver's position (or title) under :guilabel:`Role` (e.g. `Engineering Manager`, `Quality Team`, etc.), and select the relevant :guilabel:`User` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:41 +msgid "Next, set the :guilabel:`Approval Type` to :guilabel:`Is required to approve`, :guilabel:`Approves, but the approval is optional`, or :guilabel:`Comments only`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:45 +msgid "Assign the `CTO`, \"Mitchell Admin,\" as a required approver for |ECOs| in the `Validated` stage in the `New Product Introduction` ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:48 +msgid "Approvals from the quality and marketing teams are **not** required to apply changes to the |ECO| because their :guilabel:`Approval Type` is set to :guilabel:`Approves, but the approval is optional` and :guilabel:`Comments only`, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "Set an approver that \"Is required to approve\" ECOs in the \"Validated\" stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:57 +msgid "Manage approvals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:59 +msgid "Approvers can easily track their to-do approvals by navigating to the :menuselection:`PLM app`, and looking at the card for an ECO type, which shows the count of open tasks assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:62 +msgid "Here's what each button on an ECO project card does:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:64 +msgid "The :guilabel:`# Engineering Changes` button displays a count of in-progress |ECOs| of this ECO type. Clicking the button opens the Gantt view of the :guilabel:`Engineering Change Orders` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:66 +msgid ":guilabel:`My Validations` displays a count of |ECOs| the approver must accept or reject. Clicking on this button displays |ECOs| pending approval or rejected (marked with the red :guilabel:`Blocked` state)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:69 +msgid "The :guilabel:`All Validations` button shows the count of |ECOs| awaiting approval or rejected by any approver. Clicking it reveals these pending |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:71 +msgid ":guilabel:`To Apply` displays a count of |ECOs| to which the user needs to apply changes. Clicking on the button displays all the |ECOs| to approve, and apply changes to, in the verification stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:75 +msgid "|ECOs| marked with the green :guilabel:`Done` stage have already been approved, and the user just needs to click on the |ECO| to enter the form view, and click the :guilabel:`Apply Changes` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:-1 +msgid "Display count of validations to-do and buttons to open filtered list of ECOs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:84 +msgid "Approve ECOs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:86 +msgid "Navigate to an |ECO| in a verification stage, while logged in as the assigned approver, to see the :guilabel:`Approve`, :guilabel:`Reject`, and :guilabel:`Apply Changes` buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:89 +msgid "To approve the |ECO|, and apply the changes onto the production :abbr:`BoM (Bill of Materials)`, click :guilabel:`Approve`, and then :guilabel:`Apply Changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:92 +msgid "Note that the :guilabel:`Apply Changes` button will **not** work unless the :guilabel:`Approve` button was clicked first. Additionally, the chatter logs the history of the clicked buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:96 +msgid "When the :guilabel:`Approval Type` is **not** set to :guilabel:`Is required to approve`, approval from the associated user is not needed before applying changes with the :guilabel:`Apply Changes` button. Thus, the :guilabel:`Apply Changes` button **will work** without requiring the :guilabel:`Approve` button to be clicked first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:102 +msgid "Automated activities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:104 +msgid "When an |ECO| is moved to a verification stage, a planned activity is automatically created for assigned approvers to review the |ECO|. Approvers receive a notification in their activities inbox, accessible through the :guilabel:`šŸ•˜ (clock)` icon at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:108 +msgid "In the to-do task list, the :guilabel:`Engineering Change Order (ECO)` notification displays the number of activities marked :guilabel:`Late`, :guilabel:`Today`, and :guilabel:`Future`. Clicking on each of these buttons shows a filtered Gantt view of the respective |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:113 +msgid "Scheduled activities are shown as a number on the :guilabel:`šŸ•˜ (clock)` icon, with `5` |ECOs| pending approval :guilabel:`Today`. Currently, there are `0` :guilabel:`Late` or :guilabel:`Future` |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "Show scheduled approvals notifications for the user." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:121 +msgid "By clicking a pending |ECO|, a *planned activity* for :guilabel:`ECO Approval` is recorded in the chatter. Click on the :guilabel:`i (Info)` icon to view additional information, including the approval's :guilabel:`Created` date, the approver :guilabel:`Assigned to` it, and the due date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:-1 +msgid "Show additional details of the planned ECO approval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:130 +msgid "Follow-up activities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:132 +msgid "When |ECOs| are rejected, tasks need to be assigned to project members for required modifications before |ECO| approval. To create tasks with deadlines, navigate to the rejected |ECO| form, and go to the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:136 +msgid "Select the :guilabel:`Mark Done` button in the :guilabel:`Planned Activities` section of the chatter to close the activity, and open a pop-up window for creating tasks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:-1 +msgid "Show *Mark Done* window to show *Done & Schedule Next*, *Done*, and *Discard* buttons to\n" +"close the planned activity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:144 +msgid "In the :guilabel:`Mark Done` window, click :guilabel:`Done & Schedule Next` to open a new :guilabel:`Schedule an Activity` window. Next, set the :guilabel:`Assigned to` team member and the :guilabel:`Due Date` for completing the changes. Provide task details in the :guilabel:`Summary` field and the text box. Click the :guilabel:`Schedule` button to close the window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:149 +msgid "After closing the window, on the |ECO| form, move the |ECO| back one stage. Doing so ensures that when the team member completes the changes, and returns the |ECO| to the verification stage, a new :guilabel:`ECO Approval` task is created for the approver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:154 +msgid "The approver creates an activity for the :guilabel:`Responsible` of the |ECO|, `Laurie Poiret`, that details the changes required for the approver to :guilabel:`Accept` the |ECO|. Clicking the :guilabel:`Schedule` button creates a planned activity for Laurie due on `08/15/2023`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "Create a scheduled activity for follow-up changes to a rejected ECO." +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase.rst:8 msgid "Purchase" msgstr "" @@ -10376,6 +13010,10 @@ msgstr "" msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/control_bills`" msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/products.rst:5 +msgid "Products" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:3 msgid "Configure reordering rules" msgstr "" @@ -10616,6 +13254,534 @@ msgstr "" msgid "`Odoo Tutorials: Managing Quality Checks `_" msgstr "" +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types.rst:5 +msgid "Quality check types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:3 +msgid "Instructions quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:7 +msgid "In Odoo *Quality*, an *Instructions* check is one of the quality check types that can be selected when creating a new quality check or quality control point (QCP). *Instructions* checks consist of a text entry field that allows the creator to provide instructions for how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:11 +msgid "For a full overview of how to configure a quality check or a |QCP|, see the documentation on :ref:`quality checks ` and :ref:`quality control points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:16 +msgid "Process an Instructions quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:18 +msgid "There are multiple ways that *Instructions* quality checks can be processed. If a quality check is assigned to a specific manufacturing, inventory, or work order, the check can be processed on the order itself. Alternatively, a check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:23 +msgid "Process from the quality check's page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:25 +msgid "To process an *Instructions* quality check from the check's page, begin by navigating to :menuselection:`Quality --> Quality Control --> Quality Checks`, and select a quality check. Follow the :guilabel:`Instructions` for how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:29 +msgid "If the product passes the check, click the :guilabel:`Pass` button above the quality check form. If the product does not pass the check, click the :guilabel:`Fail` button, instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:33 +msgid "Process quality check on an order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:35 +msgid "To process an *Instructions* quality check on an order, select a manufacturing order or inventory order (receipt, delivery, return, etc.) for which a check is required. Manufacturing orders can be selected by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and clicking on an order. Inventory orders can be selected by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:42 +msgid "On the selected manufacturing or inventory order, a purple :guilabel:`Quality Checks` button appears above the order. Click the button to open the :guilabel:`Quality Check` pop-up window, from which any quality checks created for the order can be processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:-1 +msgid "The Quality Check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:50 +msgid "To complete an *Instructions* quality check, follow the instructions detailed in the :guilabel:`Quality Check` pop-up window. Finally, click :guilabel:`Validate` to confirm that the check has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:54 +msgid "If an issue or defect is found during the quality check, a quality alert may need to be created to notify a quality team. To do so, click the :guilabel:`Quality Alert` button that appears at the top of the manufacturing or inventory order after the check is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:58 +msgid "Clicking :guilabel:`Quality Alert` opens a quality alert form on a new page. For a complete guide on how to fill out quality alert forms, view the documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:63 +msgid "Process work order quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:65 +msgid "When configuring a |QCP| that is triggered by a manufacturing order, a specific work order can also be specified in the :guilabel:`Work Order Operation` field on the |QCP| form. If a work order is specified, an *Instructions* quality check is created for that specific work order, rather than the manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:70 +msgid "Quality checks configured for work orders must be completed from the tablet view. To do so, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order that includes a work order for which a quality check is required. Open the tablet view for that work order by clicking the :guilabel:`šŸ“± (tablet)` button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:75 +msgid "With tablet view open, complete the steps listed on the left side of the screen until the *Instructions* quality check step is reached. Upon reaching the check, the instructions for how to complete it will appear at the top of the screen. Follow the instructions, then click :guilabel:`Next` to move on to the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:-1 +msgid "An Instructions check for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:84 +msgid "If an issue or defect is found during the quality check, a quality alert may need to be created to notify a quality team. To do so, click the :guilabel:`ā˜° (menu)` button in the tablet view, and then select :guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:88 +msgid "Clicking :guilabel:`Quality Alert` opens a :guilabel:`Quality Alerts` pop-up window, from which a quality alert can be created. For a complete guide to quality alert creation, view the documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:3 +msgid "Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:8 +msgid "In Odoo *Quality*, a *Measure* check is one of the quality check types that can be selected when creating a new quality check or quality control point (QCP). *Measure* checks prompt users to measure a certain aspect of a product and record the measurement in Odoo. For the quality check to pass, the recorded measurement must be within a certain *tolerance* of a *norm* value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:14 +msgid "Create a Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:16 +msgid "There are two distinct ways that *Measure* quality checks can be created. A single check can be manually created. Alternatively, a |QCP| can be configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:20 +msgid "This documentation only details the configuration options that are unique to *Measure* quality checks and |QCPs|. For a full overview of all the configuration options available when creating a single check or a |QCP|, see the documentation on :ref:`quality checks ` and :ref:`quality control points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:27 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:27 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:26 +msgid "Quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:29 +msgid "To create a single *Measure* quality check, navigate to :menuselection:`Quality --> Quality Control --> Quality Checks`, and click :guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:32 +msgid "In the :guilabel:`Type` drop-down field, select the :guilabel:`Measure` quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:34 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:33 +msgid "In the :guilabel:`Team` drop-down field, select the quality team responsible for managing the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:35 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:35 +msgid "In the :guilabel:`Instructions` text field of the :guilabel:`Notes` tab, enter instructions for how the picture should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:-1 +msgid "A quality check form configured for a Measure quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:43 +msgid "Quality control point (QCP)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:45 +msgid "To create a |QCP| that generates *Measure* quality checks automatically, navigate to :menuselection:`Quality --> Quality Control --> Control Points`, and click :guilabel:`New`. Fill out the new |QCP| form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:49 +msgid "In the :guilabel:`Type` drop-down field, select the :guilabel:`Measure` quality check type. Doing so causes two new fields to appear: :guilabel:`Norm` and :guilabel:`Tolerance`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:52 +msgid "Use the first text-entry field of the :guilabel:`Norm` field to record the ideal measurement that the product should conform to. Use the second text-entry field to specify the unit of measurement that should be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:55 +msgid "The :guilabel:`Tolerance` field features two sub-fields: :guilabel:`from` and :guilabel:`to`. Use the :guilabel:`from` field to specify the minimum acceptable measurement, and the :guilabel:`to` field to specify the maximum acceptable measurement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:59 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:51 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:54 +msgid "In the :guilabel:`Team` drop-down field, select the quality team responsible for managing the checks created by the |QCP|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:61 +msgid "In the :guilabel:`Instructions` text field, enter instructions for how the measurement should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:-1 +msgid "A QCP form configured to create Measure quality checks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:69 +msgid "Process a Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:71 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:63 +msgid "Once created, there are multiple ways that *Measure* quality checks can be processed. If a quality check is assigned to a specific inventory, manufacturing, or work order, the check can be processed on the order itself. Alternatively, a check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:76 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:68 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:71 +msgid "From the check's page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:78 +msgid "To process a *Measure* quality check from the check's page, begin by navigating to :menuselection:`Quality --> Quality Control --> Quality Checks`, and select a quality check. Follow the :guilabel:`Instructions` for how to take the measurement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:82 +msgid "After taking the measurement, record the value in the :guilabel:`Measure` field on the quality check form. To manually pass or fail the check, click :guilabel:`Pass` or :guilabel:`Fail` at the top-left corner of the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:86 +msgid "Alternatively, if the quality check is assigned to a |QCP| for which *norm* and *tolerance* values have been specified, click :guilabel:`Measure` at the top-left corner of the check instead. Doing so automatically marks the check as *Passed* if the recorded value is within the specified *tolerance*, or *Failed* if the value is outside of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:92 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:78 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:87 +msgid "On an order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:94 +msgid "To process a *Measure* quality check on an order, select a manufacturing order or inventory order (receipt, delivery, return, etc.), for which a check is required. Manufacturing orders can be selected by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and clicking on an order. Inventory orders can be selected by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:101 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:96 +msgid "On the selected manufacturing or inventory order, a purple :guilabel:`Quality Checks` button appears at the top of the page. Click the button to open the :guilabel:`Quality Check` pop-up window, which shows all of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:105 +msgid "To process a *Measure* quality check, measure the product as instructed, then enter the value in the :guilabel:`Measure` field on the pop-up window. Finally, click :guilabel:`Validate` to register the recorded value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:-1 +msgid "A Measure quality check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:113 +msgid "If the value entered is within the range specified in the :guilabel:`Tolerance` section of the |QCP|, the quality check passes and the pop-up window closes. The rest of the manufacturing or inventory order can then be processed as usual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:117 +msgid "However, if the value entered is outside of the specified range, a new pop-up window appears, titled :guilabel:`Quality Check Failed`. The body of the pop-up shows a warning message that states, :guilabel:`You measured # units and it should be between # units and # units.`, as well as the instructions entered in the :guilabel:`Message If Failure` tab of the |QCP|. At the bottom of the pop-up, two buttons appear: :guilabel:`Correct Measure` and :guilabel:`Confirm Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:-1 +msgid "The \"Quality Check Failed\" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:127 +msgid "If the measurement was not entered correctly and should be changed, select :guilabel:`Correct Measure`. Doing so re-opens the :guilabel:`Quality Check` pop-up window. Enter the corrected measurement in the :guilabel:`Measure` field, and then click :guilabel:`Validate` to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:132 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:185 +msgid "If the measurement was entered correctly, click :guilabel:`Confirm Measure` instead, and the quality check fails. Follow any instructions that were listed on the :guilabel:`Quality Check Failed` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:136 +msgid "If a quality alert must be created, click the :guilabel:`Quality Alert` button that appears at the top of the manufacturing or inventory order after the check fails. Clicking :guilabel:`Quality Alert` opens a quality alert form on a new page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:140 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:193 +msgid "For a complete guide on how to fill out the quality alert form, view the documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:144 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:106 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:120 +msgid "On a work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:146 +msgid "When configuring a |QCP| that is triggered during manufacturing, a specific work order can also be specified in the :guilabel:`Work Order Operation` field on the |QCP| form. If a work order is specified, a *Measure* quality check is created for that specific work order, rather than the manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:151 +msgid "*Measure* quality checks created for work orders must be processed from the tablet view. To do so, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order that includes a work order for which a quality check is required. Open the tablet view for that work order by selecting the :guilabel:`Work Orders` tab, and then clicking the :guilabel:`šŸ“± (tablet)` button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:157 +msgid "With tablet view open, complete the steps listed on the left side of the screen until the *Measure* quality check step is reached. Upon reaching the check, the instructions for how to take the measurement appear at the top of the screen. Enter the measured value in the :guilabel:`Measure` field above the instructions, and then click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:-1 +msgid "A Measure quality check in the Manufacturing tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:166 +msgid "If the measurement entered is within the range specified in the :guilabel:`Tolerance` section of the |QCP|, the quality check passes and the tablet view moves on to the next step of the work order. However, if the measurement entered is outside of the specified range, a pop-up window appears, titled :guilabel:`Quality Check Failed`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:171 +msgid "The body of the :guilabel:`Quality Check Failed` pop-up window shows a warning message that states, :guilabel:`You measured # units and it should be between # units and # units.`, as well as the instructions entered in the :guilabel:`Message If Failure` tab of the |QCP|. At the bottom of the pop-up, two buttons appear: :guilabel:`Correct Measure` and :guilabel:`Confirm Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:180 +msgid "If the measurement was not entered correctly, and should be changed, select :guilabel:`Correct Measure`. Doing so opens a new pop-up window, titled :guilabel:`Quality Check`. Enter the corrected measurement in the :guilabel:`Measure` field, then click :guilabel:`Validate` to complete the check, and move on to the next step of the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:189 +msgid "If a quality alert must be created, do so by clicking the :guilabel:`ā˜° (three horizontal lines)` button, and selecting :guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window. A :guilabel:`Quality Alerts` pop-up window appears, from which a quality alert can be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:3 +msgid "Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:8 +msgid "In Odoo *Quality*, a *Pass - Fail* check is one of the quality check types that can be selected when creating a new quality check or quality control point (QCP). *Pass - Fail* checks consist of a text field that allows the creator to specify a certain criteria that a product must meet to pass the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:14 +msgid "Create a Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:16 +msgid "There are two distinct ways that *Pass - Fail* quality checks can be created. A single check can be manually created. Alternatively, a |QCP| can be configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:20 +msgid "This documentation only details the configuration options that are unique to *Pass - Fail* quality checks and |QCPs|. For a full overview of all the configuration options available when creating a single check or a |QCP|, see the documentation on :ref:`quality checks ` and :ref:`quality control points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:29 +msgid "To create a single *Pass - Fail* quality check, navigate to :menuselection:`Quality --> Quality Control --> Quality Checks`, and click :guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:50 +msgid "In the :guilabel:`Type` drop-down field, select the :guilabel:`Pass - Fail` quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:36 +msgid "In the :guilabel:`Instructions` text field of the :guilabel:`Notes` tab, enter instructions for how to complete the quality check and the criteria that must be met for the check to pass." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:-1 +msgid "A quality check form configured for a Pass - Fail quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:44 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:43 +msgid "Quality Control Point (QCP)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:46 +msgid "To create a |QCP| that generates *Pass - Fail* quality checks automatically, begin by navigating to :menuselection:`Quality --> Quality Control --> Control Points`, and click :guilabel:`New`. Fill out the new |QCP| form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:53 +msgid "In the :guilabel:`Instructions` text field, enter instructions for how to complete the quality check and the criteria that must be met for the check to pass." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:-1 +msgid "A Quality Control Point (QCP) form configured to create a Pass - Fail quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:61 +msgid "Process a Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:70 +msgid "To process a *Measure* quality check from the check's page, begin by navigating to :menuselection:`Quality --> Quality Control --> Quality Checks`, and select a quality check. Follow the :guilabel:`Instructions` for how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:74 +msgid "If the criteria for the check is met, click the :guilabel:`Pass` button at the top-left corner of the page. If the criteria is not met, click the :guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:80 +msgid "To process a *Pass - Fail* quality check on an order, select a manufacturing order or inventory order (receipt, delivery, return, etc.), for which a check is required. Manufacturing orders can be selected by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and clicking on an order. Inventory orders can be selected by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:87 +msgid "On the selected manufacturing or inventory order, a purple :guilabel:`Quality Checks` button appears at the top of the order. Click the button to open the :guilabel:`Quality Check` pop-up window, which shows all of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:91 +msgid "To process a *Pass - Fail* quality check, follow the instructions shown on the :guilabel:`Quality Check` pop-up window. If the criteria for the check is met, click the :guilabel:`Pass` button at the bottom of the window. If the criteria is not met, click the :guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:-1 +msgid "A Pass - Fail quality check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:99 +msgid "If a quality alert must be created, click the :guilabel:`Quality Alert` button that appears at the top of the manufacturing or inventory order after the check fails. Clicking :guilabel:`Quality Alert` opens a quality alert form on a new page. For a complete guide on how to fill out quality alert forms, view the documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:108 +msgid "When configuring a |QCP| that is triggered during manufacturing, a specific work order can also be specified in the :guilabel:`Work Order Operation` field on the |QCP| form. If a work order is specified, a *Pass - Fail* quality check is created for that specific work order, rather than the manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:113 +msgid "*Pass - Fail* quality checks configured for work orders must be processed from the tablet view. To do so, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order that includes a work order for which a quality check is required. Open the tablet view for that work order by selecting the :guilabel:`Work Orders` tab, and then clicking the :guilabel:`šŸ“± (tablet)` button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:119 +msgid "With tablet view open, complete the steps listed on the left side of the screen until the *Pass - Fail* quality check step is reached. Upon reaching the check, follow the instructions that appear at the top of the screen. If the criteria for the check is met, click the :guilabel:`Pass` button at the top-right of the screen. If the criteria is not met, click the :guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:-1 +msgid "A Pass - Fail check for a manufacturing work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:128 +msgid "If a quality alert must be created, do so by clicking the :guilabel:`ā˜° (menu)` button in the tablet view, and selecting :guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window. A :guilabel:`Quality Alerts` pop-up window appears, from which a quality alert can be created. For a complete guide on how to fill out quality alert forms, view the documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:3 +msgid "Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:8 +msgid "In Odoo *Quality*, a *Take a Picture* check is one of the quality check types that can be selected when creating a new quality check or quality control point (QCP). *Take a Picture* checks require a picture to be attached to the check, which can then be reviewed by a quality team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:13 +msgid "Create a Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:15 +msgid "There are two distinct ways that *Take a Picture* quality checks can be created. A single check can be manually created. Alternatively, a |QCP| can be configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:19 +msgid "This documentation only details the configuration options that are unique to *Take a Picture* quality checks and |QCPs|. For a full overview of all the configuration options available when creating a single check or a |QCP|, see the documentation on :ref:`quality checks ` and :ref:`quality control points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:28 +msgid "To create a single *Take a Picture* quality check, navigate to :menuselection:`Quality --> Quality Control --> Quality Checks`, and click :guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:32 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:49 +msgid "In the :guilabel:`Type` drop-down field, select the :guilabel:`Take a Picture` quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:-1 +msgid "A quality check form configured for a Take a Picture quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:45 +msgid "To create a |QCP| that will generate *Take a Picture* quality checks automatically, navigate to :menuselection:`Quality --> Quality Control --> Control Points`, and click :guilabel:`New`. Fill out the new |QCP| form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:50 +msgid "If the *Maintenance* app is installed, a :guilabel:`Device` field appears after selecting the *Take a Picture* check type. Use this field to specify a device that should be used to take quality check pictures. For information about managing devices in the *Maintenance* app, see the documentation on :ref:`adding new equipment `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:56 +msgid "In the :guilabel:`Instructions` text field, enter instructions for how the picture should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:-1 +msgid "A Quality Control Point (QCP) form configured to create a Take a Picture quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:64 +msgid "Process a Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:66 +msgid "Once created, there are multiple ways that *Take a Picture* quality checks can be processed. If a quality check is assigned to a specific inventory, manufacturing, or work order, the check can be processed on the order itself. Alternatively, a check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:73 +msgid "To process a *Take a Picture* quality check from the check's page, begin by navigating to :menuselection:`Quality --> Quality Control --> Quality Checks`, and then select a quality check. Follow the :guilabel:`Instructions` for how to take the picture." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:77 +msgid "After taking the picture, make sure it is stored on the device being used to process the quality check (computer, tablet, etc.). Then, click the :guilabel:`āœļø (pencil)` button in the :guilabel:`Picture` section to open the device's file manager. In the file manager, navigate to the picture, select it, and click :guilabel:`Open` to attach it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:-1 +msgid "The edit button (pencil) on a Take a Picture quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:89 +msgid "To process a *Take a Picture* quality check on an order, select a manufacturing order or inventory order (receipt, delivery, return, etc.), for which a check is required. Manufacturing orders can be selected by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and clicking on an order. Inventory orders can be selected by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:100 +msgid "Follow the instructions detailing how to take the picture, which are shown on the :guilabel:`Quality Check` pop-up window. After taking the picture, make sure it is stored on the device being used to process the quality check (computer, tablet, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:104 +msgid "Then, click the :guilabel:`Take a Picture` button in the :guilabel:`Picture` section to open the device's file manager. In the file manager, navigate to the picture, select it, and click :guilabel:`Open` to attach it. Finally, click :guilabel:`Validate` on the :guilabel:`Quality Check` pop-up window to complete the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:-1 +msgid "A Take a Picture quality check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:113 +msgid "If a quality alert must be created, click the :guilabel:`Quality Alert` button that appears at the top of the manufacturing or inventory order after the check is validated. Clicking :guilabel:`Quality Alert` opens a quality alert form on a new page. For a complete guide on how to fill out quality alert forms, view the documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:122 +msgid "When configuring a |QCP| that is triggered during manufacturing, a specific work order can also be specified in the :guilabel:`Work Order Operation` field on the |QCP| form. If a work order is specified, a *Take a Picture* quality check is created for that specific work order, rather than the manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:127 +msgid "*Take a Picture* quality checks created for work orders must be completed from the tablet view. To do so, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order that includes a work order for which a quality check is required. Open the tablet view for that work order by selecting the :guilabel:`Work Orders` tab, and then clicking the :guilabel:`šŸ“± (tablet)` button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:133 +msgid "With tablet view open, complete the steps listed on the left side of the screen until the *Take a Picture* quality check step is reached. Upon reaching the check, follow the instructions for how to take the picture, which appear at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:137 +msgid "After taking the picture, make sure it is stored on the device being used to process the work order (computer, tablet, etc.). Then, click the :guilabel:`Take a Picture` button to open the device's file manager. In the file manager, navigate to the picture, select it, and click :guilabel:`Open` to attach it. Finally, click :guilabel:`Validate` to complete the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:-1 +msgid "A Take a Picture check for a manufacturing work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:146 +msgid "If a quality alert must be created, do so by clicking the :guilabel:`ā˜° (three horizontal lines)` button in the tablet view, and selecting :guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window. A :guilabel:`Quality Alerts` pop-up window appears, from which a quality alert can be created. For a complete guide on how to fill out quality alert forms, view the documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:153 +msgid "Review a picture attached to a check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:155 +msgid "After a picture has been attached to a check, it can then be reviewed by quality team members or other users. To do so, navigate to :menuselection:`Quality --> Quality Control --> Quality Checks`, and select a quality check to review." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:159 +msgid "The attached picture appears in the :guilabel:`Picture` section of the quality check form. After reviewing the picture, click the :guilabel:`Pass` button if the check passes, or the :guilabel:`Fail` button if the check fails." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:-1 +msgid "A Take a Picture check with a picture attached." +msgstr "" + #: ../../content/applications/inventory_and_mrp/quality/quality_management.rst:5 msgid "Quality control basics" msgstr "" @@ -10624,92 +13790,92 @@ msgstr "" msgid "Create quality alerts" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:5 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:7 msgid "Configuring quality control points is a great way to ensure that quality checks are performed at routine stages during specific operations. However, quality issues can often appear outside of these scheduled checks. Using Odoo *Quality*, users can create quality alerts for issues that are not detected by automated processes." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:11 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:13 msgid ":doc:`Add quality control points `" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:14 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:16 msgid "Find and fill out the quality alerts form" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:16 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:18 msgid "In some situations, it is necessary to manually create quality alerts within the *Quality* module." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:19 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:21 msgid "A helpdesk user who is notified of a product defect by a customer ticket can create an alert that brings the issue to the attention of the relevant quality team." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:22 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:24 msgid "To create a new quality alert, start from the :menuselection:`Quality` module and select :menuselection:`Quality Control --> Quality Alerts --> Create`. The quality alert form can then be filled out as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:26 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:28 msgid ":guilabel:`Title`: choose a concise, yet descriptive title for the quality alert" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:27 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:29 msgid ":guilabel:`Product`: the product about which the quality alert is being created" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:28 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:30 msgid ":guilabel:`Product Variant`: the specific variant of the product that has the quality issue, if applicable" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:30 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:32 msgid ":guilabel:`Lot`: the lot number assigned to the product" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:31 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:33 msgid ":guilabel:`Work Center`: the work center where the quality issue originated" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:32 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:34 msgid ":guilabel:`Picking`: the picking operation during which the quality issue originated" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:35 msgid ":guilabel:`Team`: the quality team that will be notified by the quality alert" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:34 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:36 msgid ":guilabel:`Responsible`: the individual responsible for managing the quality alert" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:35 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:37 msgid ":guilabel:`Tags`: classify the quality alert based on user-created tags" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:36 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:38 msgid ":guilabel:`Root Cause`: the cause of the quality issue, if known" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:37 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:39 msgid ":guilabel:`Priority`: assign a priority between one and three stars to ensure more urgent issues are prioritized" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:40 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:42 #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:42 msgid "The tabs at the bottom of the form can be used to provide additional information to quality teams:" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:42 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:44 msgid ":guilabel:`Description`: provide additional details about the quality issue" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:43 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:45 msgid ":guilabel:`Corrective Actions`: the method for fixing affected products" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:44 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:46 msgid ":guilabel:`Preventive Actions`: procedures for preventing the issue from occurring in the future" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:46 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:48 msgid ":guilabel:`Miscellaneous`: the product vendor (if applicable), the company that produces the product, and the date assigned" msgstr "" @@ -10717,11 +13883,11 @@ msgstr "" msgid "An example of a completed quality alert form." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:54 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:56 msgid "Add quality alerts during the manufacturing process" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:56 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:58 msgid "Odoo enables manufacturing employees to create quality alerts within a work order without accessing the *Quality* module. From the work order tablet view, click the :guilabel:` ā˜° ` hamburger menu icon in the top left corner and select :guilabel:`Quality Alert`." msgstr "" @@ -10729,19 +13895,19 @@ msgstr "" msgid "Access the work order menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:64 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:66 msgid "The quality alert form can then be filled out as detailed in the previous section. After saving the form, a new alert will appear on the :guilabel:`Quality Alerts` dashboard that can be found through the :menuselection:`Quality --> Quality Control` menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:69 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:71 msgid "Manage existing quality alerts" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:71 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:73 msgid "By default, quality alerts are organized in a kanban board view. The stages of the kanban board are fully configurable and alerts can be moved from one stage to the next by dragging and dropping or from within each alert. Additional options are available for viewing alerts, including graph, calendar, and pivot table views." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:77 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:79 msgid "Filter alerts based on diverse criteria like date assigned or date closed. Alerts can also be grouped by quality team, root cause, or other parameters found under the :guilabel:`Filters` button menu." msgstr "" @@ -10749,79 +13915,79 @@ msgstr "" msgid "Quality checks" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:7 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:8 msgid "Quality checks are manual inspections conducted by employees, and are used to ensure the quality of products. In Odoo, a quality check can be conducted for a single product, or multiple products within the same inventory operation or manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:11 -msgid "Using a Quality Control Point (QCP), it is possible to create quality checks automatically at regular intervals. When quality checks are created by a |QCP|, they appear on a manufacturing or inventory order, where the employee processing the order will be prompted to complete them. For a full explanation of how to create and configure a |QCP|, see the documentation on :ref:`quality control points `." +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:12 +msgid "Using a Quality Control Point (QCP), it is possible to create quality checks automatically at regular intervals. When quality checks are created by a |QCP|, they appear on a manufacturing or inventory order, where the employee processing the order will be prompted to complete them. For a full explanation of how to create and configure a |QCP|, see the documentation on :ref:`quality control points `." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:17 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:18 msgid "While quality checks are most commonly created automatically by a |QCP|, it is also possible to manually create a single quality check. Creating a check manually is useful when an employee wants to schedule a quality check that will only occur once, or register a quality check that they conduct unprompted." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:23 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:24 msgid "Manual quality check" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:25 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:26 msgid "To manually create a single quality check, navigate to :menuselection:`Quality --> Quality Control --> Quality Checks`, and click :guilabel:`New`. On the quality check form, begin by selecting an option from the :guilabel:`Control per` drop-down menu:" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:29 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:30 msgid ":guilabel:`Operation` requests a check for an entire operation (ex. delivery order) and all products within it." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:31 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:32 msgid ":guilabel:`Product` requests a check for every unit of a product that is part of an operation (ex. every unit of a product within a delivery order)." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:34 msgid ":guilabel:`Quantity` requests a check for every quantity of a product that is part of an operation (ex. one check for five units of a product within a delivery order). Selecting :guilabel:`Quantity` also causes a :guilabel:`Lot/Serial` drop-down field to appear, from which can be selected a specific lot or serial number that the quality check should be conducted for." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:38 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:39 msgid "Next, select an inventory operation from the :guilabel:`Picking` drop-down menu or a manufacturing order from the :guilabel:`Production Order` drop-down menu. This is necessary because Odoo needs to know for which operation the quality check is being conducted." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:42 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:43 msgid "If the quality check should be assigned to a specific |QCP|, select it from the :guilabel:`Control Point` drop-down menu. This is useful if the quality check is being created manually, but should still be recognized as belonging to a specific |QCP|." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:46 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:47 msgid "Select a quality check type from the :guilabel:`Type` drop-down field:" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:48 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:49 msgid ":guilabel:`Instructions` provides specific instructions for how to conduct the quality check." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:49 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:50 msgid ":guilabel:`Take a Picture` requires a picture to be attached to the check before the check can be completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:51 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:52 msgid ":guilabel:`Pass - Fail` is used when the product being checked must meet a certain criteria to pass the check." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:53 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:54 msgid "Selecting :guilabel:`Measure` causes a :guilabel:`Measure` input field to appear, in which a measurement must be entered before the check can be completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:55 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:56 msgid "Selecting :guilabel:`Worksheet` causes a :guilabel:`Quality Template` drop-down field to appear. Use it to select a quality worksheet that must be filled out to complete the check." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:58 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:59 msgid "In the :guilabel:`Team` field, select the quality team that is responsible for the quality check. In the :guilabel:`Company` field, select the company that owns the product being inspected." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:61 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:62 msgid "On the :guilabel:`Notes` tab at the bottom of the form, enter any relevant instructions in the :guilabel:`Instructions` text entry box (ex. 'Attach a picture of the product'). In the :guilabel:`Notes` text entry box, enter any relevant information about the quality check (who created it, why it was created, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:66 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:67 msgid "Finally, if the check is being processed immediately, click the :guilabel:`Pass` button at the top left of the screen if the check passes, or the :guilabel:`Fail` button if the check fails." msgstr "" @@ -10829,43 +13995,43 @@ msgstr "" msgid "A quality check form filled out for a Pass - Fail check." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:74 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:75 msgid "Process quality check" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:76 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:77 msgid "Quality checks can be processed directly on the quality check's page, or from a manufacturing or inventory order for which a check is required. Alternatively, if a quality check is created for a specific work order operation, the check is processed in the tablet view for the work order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:81 -msgid "It is not possible to manually create a single quality check that is assigned to a specific work order operation. Quality checks for work order operations can only be created by a |QCP|. See the documentation on :ref:`Quality Control Points ` for information about how to configure a |QCP| that will create quality checks for a specific work order operation." +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:82 +msgid "It is not possible to manually create a single quality check that is assigned to a specific work order operation. Quality checks for work order operations can only be created by a |QCP|. See the documentation on :ref:`Quality Control Points ` for information about how to configure a |QCP| that will create quality checks for a specific work order operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:88 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:89 msgid "Quality check page" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:90 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:91 msgid "To process a quality check from the check's page, begin by navigating to :menuselection:`Quality --> Quality Control --> Quality Checks`, then select the check to process. Follow the instructions for how to complete the check, listed in the :guilabel:`Instructions` field of the :guilabel:`Notes` tab at the bottom of the page." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:95 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:96 msgid "If the quality check passes, click the :guilabel:`Pass` button at the top of the page. If the check fails, click the :guilabel:`Fail` button, instead." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:99 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:100 msgid "Quality check on order" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:101 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:102 msgid "To process a quality check on an order, select a manufacturing or inventory order (receipt, delivery, return, etc.), for which a check is required. Manufacturing orders can be selected by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and clicking on an order. Inventory orders can be selected by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on an operation card, and selecting an order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:107 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:108 msgid "On the selected inventory or manufacturing order, a purple :guilabel:`Quality Checks` button appears at the top of the order. Click the button to open the :guilabel:`Quality Check` pop-up window, which shows all of the quality checks required for that order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:111 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:112 msgid "Follow the instructions that appear on the :guilabel:`Quality Check` pop-up window. If a Pass - Fail check is being processed, complete the check by clicking :guilabel:`Pass` or :guilabel:`Fail` at the bottom of the pop-up window. For all other quality check types, a :guilabel:`Validate` button appears instead. Click it to complete the check." msgstr "" @@ -10873,15 +14039,15 @@ msgstr "" msgid "The \"Quality Check\" pop-up window on a manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:121 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:122 msgid "Quality check on work order" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:123 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:124 msgid "To process a quality check for a work order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select a manufacturing order. Select the :guilabel:`Work Orders` tab, then click the :guilabel:`šŸ“± (tablet)` tablet view button for the work order that requires the quality check." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:128 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:129 msgid "With tablet view open, complete the steps listed on the left side of the screen until the quality check step is reached, then follow the instructions at the top of the screen. If a Pass - Fail check is being processed, complete the check by clicking :guilabel:`Pass` or :guilabel:`Fail` at the top of the screen. For all other quality check types, a :guilabel:`Next` button appears instead. Click it to complete the check and move on to the next step of the work order." msgstr "" @@ -10894,7 +14060,7 @@ msgid "Add quality controls" msgstr "" #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:7 -msgid "Use *Odoo Quality* to control the quality of products before they are registered into stock, during picking operations, and when leaving the warehouse for a delivery order. By creating *quality control points*, manufacturers can set up quality checks that automatically trigger at specific points during production." +msgid "Use Odoo *Quality* to control the quality of products before they are registered into stock, during picking operations, and when leaving the warehouse for a delivery order. By creating *quality control points*, manufacturers can set up quality checks that automatically trigger at specific points during production." msgstr "" #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:13 diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 9d2cd7799..9da988748 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -334,42 +334,38 @@ msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Out msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:106 -msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees." -msgstr "" - -#: ../../content/applications/productivity/calendar/outlook.rst:113 msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:115 +#: ../../content/applications/productivity/calendar/outlook.rst:108 msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:116 +#: ../../content/applications/productivity/calendar/outlook.rst:109 msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:117 +#: ../../content/applications/productivity/calendar/outlook.rst:110 msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:118 +#: ../../content/applications/productivity/calendar/outlook.rst:111 msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:119 +#: ../../content/applications/productivity/calendar/outlook.rst:112 msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:120 +#: ../../content/applications/productivity/calendar/outlook.rst:113 msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:123 +#: ../../content/applications/productivity/calendar/outlook.rst:116 msgid "Sync Odoo Calendar and Outlook" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:125 +#: ../../content/applications/productivity/calendar/outlook.rst:118 msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions." msgstr "" @@ -377,19 +373,19 @@ msgstr "" msgid "The \"Outlook\" sync button in Odoo Calendar." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:133 +#: ../../content/applications/productivity/calendar/outlook.rst:126 msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:137 +#: ../../content/applications/productivity/calendar/outlook.rst:130 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 Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:144 +#: ../../content/applications/productivity/calendar/outlook.rst:137 msgid ":doc:`../mail_plugins/outlook`" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:145 +#: ../../content/applications/productivity/calendar/outlook.rst:138 msgid ":doc:`google`" msgstr "" @@ -623,7 +619,7 @@ 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 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250 msgid ":doc:`team_communication`" msgstr "" @@ -632,76 +628,302 @@ msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 -msgid "Get Organized by Planning Activities" +msgid "Activities" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5 -msgid "When you plan activities you minimize the risk of uncertainties, as you provide clear directions for the course of your next action. In addition to that, you do not leave space for wasteful activities and reduce the chance of having overlapping actions between team members." +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any page of the database that contains a chatter thread, kanban view, list view, or activities view of an application." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 -msgid "Where do I see my schedule activities?" +msgid "Schedule activities" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12 -msgid "Access and manage your activities wherever you are in Odoo by the *Activities* menu." +msgid "One way that activities are created is by clicking the :guilabel:`Schedule Activity` button, located at the top of the *chatter* on any record. On the pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17 +msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21 +msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24 +msgid "To assign the activity to a different user, select a name from the :guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the activity is automatically assigned." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27 +msgid "Lastly, feel free to add any additional information in the optional :guilabel:`Log a note...` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30 +msgid "The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up window auto-populates based on the configuration settings for the selected :guilabel:`Activity Type`. However, this date can be changed by selecting a day on the calendar in the :guilabel:`Due Date` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34 +msgid "Lastly, click one of the following buttons:" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36 +msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37 +msgid ":guilabel:`Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, it is automatically marked as completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39 +msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41 +msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -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 "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:22 -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:-1 -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 "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:33 -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:-1 -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 "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:46 -msgid "Recommend next activities" +msgid "View of CRM leads and the option to schedule an activity." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48 -msgid "Odoo helps you to plan a flow of activities by allowing you to set *Recommended Next Activities*." +msgid "Depending on the activity type, the :guilabel:`Schedule` button may be replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51 +msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:57 +msgid "Activities can also be scheduled from the kanban, list, or activities view of an application." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63 +msgid "Select a record on which to schedule an activity. Click on the :guilabel:`šŸ•˜ (clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill out the pop-up form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70 +msgid "List view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:72 +msgid "Select a record on which to schedule an activity. Click on the :guilabel:`šŸ•˜ (clock)` icon, then :guilabel:`Schedule An Activity`. If the record already has an activity scheduled, the clock icon may be replaced by a :guilabel:`šŸ“ž (phone)` or an :guilabel:`āœ‰ļø (envelope)` icon." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:82 +msgid "To open the activity view for an application, select the :guilabel:`šŸ•˜ (clock)` icon from the menu bar anywhere in the database. Select any application from the drop-down menu, and click the :guilabel:`šŸ•˜ (clock)` icon for the desired app." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "Activity menu drop down with focus on where to open activity view for CRM." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:90 +msgid "Select a record on which to schedule an activity. Move across the row to find the desired activity type, then click the :guilabel:`ļ¼‹ (plus sign)`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:98 +msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101 +msgid "Activities that appear in **green** indicate a due date sometime in the future." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102 +msgid "**Yellow** indicates that the activity's due date is today." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103 +msgid "**Red** indicates that the activity is overdue and the due date has passed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105 +msgid "For example, if an activity is created for a phone call, and the due date passes, the activity appears with a red phone in list view, and a red clock on the kanban view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109 +msgid "View scheduled activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111 +msgid "To view scheduled activities, open either the :menuselection:`Sales app` or :menuselection:`CRM app` and click the :guilabel:`šŸ•˜ (clock)` icon, located to the far-right side of the other view options." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:114 +msgid "Doing so opens the activities menu, showcasing all the scheduled activities for the user, by default. To show all activities for every user, remove the :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:118 +msgid "To view a consolidated list of activities separated by the application where they were created, and by deadline, click the :guilabel:`šŸ•˜ (clock)` icon on the header menu to see the activities for that specific application in a drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:122 +msgid "The possibility to :guilabel:`Add new note` and :guilabel:`Request a Document` appear at the bottom of this drop-down menu, when the :guilabel:`šŸ•˜ (clock)` icon on the header menu is clicked." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of an activity type form emphasizing the field recommended next activities for Odoo\n" -"Discuss" +msgid "View of CRM leads page emphasizing the activities menu." 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." +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130 +msgid "Configure activity types" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132 +msgid "To configure the types of activities in the database, go to :menuselection:`Settings app --> Discuss --> Activities --> Activity Types`." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of an activity being schedule emphasizing the recommended activities field being\n" -"shown for Odoo Discuss" +msgid "View of the settings page emphasizing the menu activity types." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139 +msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141 +msgid "To edit an existing activity type, select it from the list, then click :guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144 +msgid "At the top of a blank activity type form, start by choosing a :guilabel:`Name` for the new activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152 +msgid "Activity settings" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155 +#: ../../content/applications/productivity/studio/automated_actions.rst:134 +msgid "Action" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:157 +msgid "The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors after an activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:160 +msgid "If :guilabel:`Upload Document` is selected, a link to upload a document is added directly to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:162 +msgid "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open their calendar to schedule a time for this activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164 +msgid "If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the chatter that opens a signature request pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168 +msgid "The actions available to select on an activity type vary, depending on the applications currently installed in the database." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172 +msgid "Default user" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:174 +msgid "To automatically assign this activity to a specific user when this activity type is scheduled, choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the activity is assigned to the user who creates the activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:179 +msgid "Default summary" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:181 +msgid "To include notes whenever this activity type is created, enter them into the :guilabel:`Default Summary` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:185 +msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:190 +msgid "Next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:192 +msgid "To automatically suggest, or trigger, a new activity after an activity has been marked complete, the :guilabel:`Chaining Type` must be set." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:196 +msgid "Suggest next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:198 +msgid "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to select any activities to recommend as follow-up tasks to this activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:202 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:230 +msgid "In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so, configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity deadline`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235 +msgid "This :guilabel:`Schedule` field information can be altered before the activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237 +msgid "When all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 +msgid "Schedule activity popup with emphasis on recommended activities." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216 +msgid "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations for activities as next steps." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221 +msgid "Trigger next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223 +msgid "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the next activity once the previous one is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:226 +msgid "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select the activity that should be launched once this activity is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 +msgid "Schedule new activity popup with emphasis on Done and launch next button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:244 +msgid "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`, marking the activity as `Done` immediately launches the next activity listed in the :guilabel:`Trigger` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:249 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:113 msgid ":doc:`get_started`" msgstr "" @@ -822,8 +1044,12 @@ msgstr "" msgid "Internet of Things (IoT)" msgstr "" +#: ../../content/applications/productivity/iot.rst:17 +msgid "The Open Platform Communications (OPC) Unified Architecture (UA) protocol is now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` is an open standard that specifies information exchange for industrial communication on devices, between machines and between systems. This includes communication between information technology and operational technology. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` can be used with any software platform, on a wide variety of devices, and deployed securely. The :abbr:`IoT (Internet of Things)` box has entered the world of the Industry 4.0 standard and can be utilized in a wide variety of industries, and for things like building automation, packaging, utilities, etc." +msgstr "" + #: ../../content/applications/productivity/iot/config.rst:5 -#: ../../content/applications/productivity/mail_plugins/outlook.rst:6 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:10 msgid "Configuration" msgstr "" @@ -2325,7 +2551,7 @@ msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:82 #: ../../content/applications/productivity/iot/devices/footswitch.rst:52 -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:90 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:92 #: ../../content/applications/productivity/iot/devices/printer.rst:95 msgid ":ref:`workcenter_iot`" msgstr "" @@ -2378,19 +2604,19 @@ msgstr "" msgid "Connect a measurement tool" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:5 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:7 msgid "With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect measurement tools to the Odoo database for use in the *Quality app* on a quality control point/quality check, or for use in a work center during the manufacturing process." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:9 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:11 msgid "Find the list of supported devices here: `Supported devices `_." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:13 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 msgid "Connect with universal serial bus (USB)" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:17 msgid "To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the :abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of Things)` box, and the device appears in the Odoo database." msgstr "" @@ -2398,11 +2624,11 @@ msgstr "" msgid "Measurement tool recognized on the IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:24 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 msgid "Connect with bluetooth" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:28 msgid "Activate the Bluetooth functionality on the device (see the device manual for further explanation), and the :abbr:`IoT (Internet of Things)` box automatically connects to the device." msgstr "" @@ -2410,23 +2636,23 @@ msgstr "" msgid "Bluetooth indicator on measurement tool." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:35 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 msgid "Link a measurement tool to a quality control point in the manufacturing process" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:39 msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the measurement tool should be linked." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:41 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:43 msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, where the attached device can be selected." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:45 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 msgid "Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. :guilabel:`Save` the changes, if required." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:48 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:50 msgid "At this point, the measurement tool is linked to the chosen quality control point. The value, which usually needs to be changed manually, is automatically updated while the tool is being used." msgstr "" @@ -2434,40 +2660,40 @@ msgstr "" msgid "Measurement tool input in the Odoo database." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:56 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:58 #: ../../content/applications/productivity/iot/devices/printer.rst:60 msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:61 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:63 msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:68 msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:69 msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:70 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 msgid "Link a measurement tool to a work center in the Manufacturing app" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:74 msgid "To link a measurement tool to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Then, select the desired work center in which the measurement tool will be used." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:76 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:78 msgid "On the work center page, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Then, the measurement tool can be linked to the :guilabel:`Action` drop-down menu option labeled :guilabel:`Take Measure`. A key can be added to trigger the action." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:82 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:84 msgid "It should be noted that the first listed trigger is chosen first. The order matters, and these triggers can be dragged into any order." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:86 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:88 msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the measurement tool." msgstr "" @@ -3747,160 +3973,160 @@ msgstr "" msgid "Outlook Plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:8 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:5 +msgid "Outlook allows for third-party applications to connect in order to execute database actions from emails. Odoo has a plugin for Outlook that allows for the creation of an opportunity from the email panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:12 msgid "The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Outlook." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:13 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:17 msgid "Enable Mail Plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:15 -msgid "First, you need to enable the *Mail Plugin* feature in your database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable *Mail Plugin*, and *Save* the configuration." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:21 -msgid "Install the Outlook Plugin" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:23 -msgid "Open your Outlook mailbox and select any email." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:19 +msgid "First, enable the *Mail Plugin* feature in the database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable :guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration." msgstr "" #: ../../content/applications/productivity/mail_plugins/outlook.rst:25 -msgid "Click on the *More actions* button and select *Get Add-ins*." +msgid "Install the Outlook Plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 -msgid "More actions button in Outlook" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:27 +msgid "Download (:menuselection:`Save Page As --> Web Page XML only`) the following XML file to upload later: `https://download.odoocdn.com/plugins/outlook/manifest.xml `_." msgstr "" #: ../../content/applications/productivity/mail_plugins/outlook.rst:31 -msgid "Select the *My add-ins* tab." +msgid "Next, open the Outlook mailbox, and select any email. After completing this, click on the :guilabel:`More actions` button in the upper right-side and select :guilabel:`Get Add-ins`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 +msgid "More actions button in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:38 +msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 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...*" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:44 +msgid "Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ Add a custom add-in`, and then on :guilabel:`Add from file...`" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Custom add-ins in Outlook" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:43 -msgid "Enter the following URL `https://download.odoocdn.com/plugins/v15/outlook/manifest.xml` and press *OK*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:51 +msgid "For the next step, attach the `manifest.xml` file downloaded above, and press :guilabel:`OK`. Next, read the warning and click on :guilabel:`Install`." 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 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Custom add-in installation warning in Outlook" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:59 -msgid "Connect your database" -msgstr "" - #: ../../content/applications/productivity/mail_plugins/outlook.rst:61 -msgid "Open any email in your Outlook mailbox, click on the *More actions* button, and select *Odoo for Outlook*." +msgid "Connect the database" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:63 +msgid "Now, Outlook will be connected to the Odoo database. First, open any email in the Outlook mailbox, click on the :guilabel:`More actions` button in the upper right-side, and select :guilabel:`Odoo for Outlook`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Odoo for Outlook add-in button" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:68 -msgid "The right-side panel can now display **Company Insights**. At the bottom, click on *Login*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:71 +msgid "The right-side panel can now display **Company Insights**. At the bottom, click on :guilabel:`Login`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 -msgid "Logging in your Odoo database" -msgstr "" - -#: ../../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 `." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 +msgid "Logging in the Odoo database" 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." +msgid "Only a limited amount of **Company Insights** (*Lead Enrichment*) requests are available as a trial database. This feature requires :ref:`prepaid credits `." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:84 -msgid "To fix this issue, configure your browser to always allow cookies on Odoo's plugin page." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:83 +msgid "If, after a short while, the panel is still empty, it is possible that the browser cookie settings prevented it from loading. Note that these settings also change if the browser is in \"Incognito\" mode." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:86 -msgid "For Google Chrome, you can do so by following the guide at: `https://support.google.com/chrome/answer/95647 `_ and adding `download.odoo.com` to the list of `Sites that can always use cookies`." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:87 +msgid "To fix this issue, configure the browser to always allow cookies on Odoo's plugin page." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:90 -msgid "Once done, the Outlook panel needs to be opened again." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:89 +msgid "For Google Chrome, change the browser cookie settings by following the guide at: `https://support.google.com/chrome/answer/95647 `_ and adding `download.odoo.com` to the list of :guilabel:`Sites that can always use cookies`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:93 -msgid "Enter your Odoo database URL and click on *Login*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:94 +msgid "Once this is complete, the Outlook panel needs to be opened again." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 -msgid "Entering your Odoo database URL" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:96 +msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:99 -msgid "Click on *Allow* to open the pop-up window." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 +msgid "Entering the Odoo database URL" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:102 +msgid "Next, click on :guilabel:`Allow` to open the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "New window pop-up warning" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:105 -msgid "If you aren't logged into your database, enter your credentials." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:108 +msgid "If the user isn't logged into the database, enter the credentials. Click on :guilabel:`Allow` to let the Outlook Plugin connect to the database." 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 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Allowing the Outlook Plugin to connect to a database" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:116 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 msgid "Add a shortcut to the plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:120 msgid "By default, the Outlook Plugin can be opened from the *More actions* menu. However, to save time, it's possible to add it next to the other default actions." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:121 -msgid "In your Outlook mailbox, click on *Settings*, then on *View all Outlook settings*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:123 +msgid "In the Outlook mailbox, click on :guilabel:`Settings`, then on :guilabel:`View all Outlook settings`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 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*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:130 +msgid "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on :guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Odoo for Outlook customized action" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:133 -msgid "Open any email; the shortcut should be displayed." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:137 +msgid "Following this step, open any email; the shortcut should be displayed." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:144 +msgid "Using the plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:146 +msgid "Now that the plug-in is installed and operational, all that needs to be done to create a lead is to click on the `O` [Odoo icon] or navigate to :guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side panel will appear on the right-side, and under :guilabel:`Opportunities` click on :guilabel:`New`. A new window with the created opportunity in the Odoo database will populate." msgstr "" #: ../../content/applications/productivity/studio.rst:6 @@ -4083,10 +4309,6 @@ msgstr "" msgid "Define on which records of the model the automated action should be applied. It works the same way as when you apply filters on a model." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:134 -msgid "Action" -msgstr "" - #: ../../content/applications/productivity/studio/automated_actions.rst:136 msgid "Determine what the automated action should do (server action). There are eight types of action to choose from." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 9019dfb8e..748184f40 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 08:06+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -53,7 +53,6 @@ msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 #: ../../content/applications/sales/crm/optimize/gamification.rst:11 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9 -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:10 #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 #: ../../content/applications/sales/point_of_sale/configuration.rst:6 @@ -61,24 +60,25 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:11 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:12 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:12 #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:12 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:52 #: ../../content/applications/sales/point_of_sale/restaurant.rst:20 #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11 #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 #: ../../content/applications/sales/rental.rst:20 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:14 #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:13 #: ../../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:13 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:14 #: ../../content/applications/sales/subscriptions/closing.rst:31 #: ../../content/applications/sales/subscriptions/upselling.rst:25 msgid "Configuration" @@ -577,134 +577,6 @@ msgstr "" msgid "Analyze performance" msgstr "" -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:3 -msgid "How to use Google Spreadsheet in Addition to my Data?" -msgstr "" - -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:5 -msgid "Create custom dashboards in Google Spreadsheet that retrieves data directly from Odoo using spreadsheet formula. You can use it to create sales commission plans, budgets, project forecasts, etc. Formulas are written in Python but programming skills are not required." -msgstr "" - -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:12 -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:-1 -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 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: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:-1 -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: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:43 -msgid "Link a Spreadsheet with Odoo" -msgstr "" - -#: ../../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:46 -msgid "Go to :menuselection:`Odoo --> Server Settings --> Database Name --> Username --> Password`." -msgstr "" - -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1 -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: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: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:66 -msgid "Retrieve Data" -msgstr "" - -#: ../../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:71 -msgid "Find some the arguments in the table below." -msgstr "" - -#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1 -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:-1 -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:91 -msgid "Mix Odoo data with spreadsheet data, add traditional formulas, and create Dynamic Tabled and Graphs." -msgstr "" - #: ../../content/applications/sales/crm/performance/win_loss.rst:3 msgid "Check your Win/Loss Ratio" msgstr "" @@ -738,7 +610,7 @@ msgid "Manage lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 -msgid "While working with your opportunities, you might lose some of them. You will want to keep track of the reasons you lost them and also which ways Odoo can help you recover them in the future." +msgid "Not all opportunities result in successful sales. In order to keep the pipeline up to date, lost opportunities need to be identified. Specifying the reason why an opportunity was lost provides additional insight that can prove useful for future opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 @@ -746,66 +618,126 @@ msgid "Mark a lead as lost" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 -msgid "While in your pipeline, select any opportunity you want and you will see a *Mark Lost* button." +msgid "To mark a lead as lost, open the :menuselection:`CRM` application, and select a lead from the pipeline, by clicking on its corresponding kanban card. Doing so reveals that lead's detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 -msgid "You can then select an existing *Lost Reason* or create a new one right there." +msgid "Then, click :guilabel:`Lost`, located at the top of the lead's detail form." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:22 -msgid "Manage & create lost reasons" +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Buttons from the top of an opportunity record with the lost button emphasized." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:24 -msgid "You will find your *Lost Reasons* under :menuselection:`Configuration --> Lost Reasons`." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:21 +msgid "This opens the :guilabel:`Lost Reason` popup. From the drop-down, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:26 -msgid "You can select & rename any of them as well as create a new one from there." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:25 +msgid "Additional notes and comments can be added below the lost reason designated in the :guilabel:`Lost Reason` field." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:30 -msgid "Retrieve lost opportunities" +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:28 +msgid "When all the desired information has been entered in the :guilabel:`Lost Reason` pop-up window, click :guilabel:`Submit`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:32 -msgid "To retrieve lost opportunities and do actions on them (send an email, make a feedback call, etc.), select the *Lost* filter in the search bar." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Lost reasons popup with sample reasons." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:35 +msgid "Upon clicking :guilabel:`Submit`, the pop-up window disappears, and Odoo returns to the lead detail form, where a new red :guilabel:`Lost` banner is now present in the upper-right corner of the lead." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 -msgid "You will then see all your lost opportunities." +msgid "Create/edit lost reasons" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 -msgid "If you want to refine them further, you can add a filter on the *Lost Reason*." +msgid "To create a new lost reason, or edit an existing one, navigate to :menuselection:`CRM app --> Configuration --> Lost Reasons`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 -msgid "For Example, *Too Expensive*." +msgid "To edit an existing reason, click on the reason that should be modified. When clicked, that reason becomes highlighted. Once highlighted, change the description of the selected lost reason by editing the :guilabel:`Description` field. When done, click :guilabel:`Save` in the upper-left corner." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:50 -msgid "Restore lost opportunities" +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:48 +msgid "To create a new lost reason, click :guilabel:`Create` in the upper-left corner of the :guilabel:`Lost Reasons` page. Doing so reveals a new blank line in the :guilabel:`Description` field. Then, proceed to type in the new lost reason in that new line. Once ready, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:52 -msgid "From the Kanban view with the filter(s) in place, you can select any opportunity you wish and work on it as usual. You can also restore it by clicking on *Archived*." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:54 +msgid "Retrieve lost opportunities" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:59 -msgid "You can also restore items in batch from the Kanban view when they belong to the same stage. Select *Restore Records* in the column options. You can also archive the same way." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56 +msgid "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM app` to the main :guilabel:`Pipeline` dashboard. Then, click the :guilabel:`Filters` drop-down menu, located beneath the search bar." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 -msgid "To select specific opportunities, you should switch to the list view." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Search bar with lost filter emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 +msgid "From the :guilabel:`Filters` drop-down menu, select the :guilabel:`Lost` option. Upon selecting :guilabel:`Lost`, only the leads that have been marked as `Lost` appear on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 +msgid "To filter leads by a specific lost reason, select :menuselection:`Filters --> Add Custom Filter`. Doing so reveals another drop-down menu with three fields." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 -msgid "Then you can select as many or all opportunities and select the actions you want to take." +msgid "In the top field drop-down menu, select :guilabel:`Lost Reason`. In the second field drop-down menu, select :guilabel:`Contains`. Then, in the third field of the :guilabel:`Add Custom Field` sub menu, type in the specific keyword(s). Lastly, click :guilabel:`Apply`. Upon clicking :guilabel:`Apply`, Odoo reveals all the lost leads with a reason that contains that specified keyword(s)." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:78 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Search bar with custom filter added for lost reason." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:81 +msgid "Restore lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 +msgid "To restore a lost opportunity, navigate to the main :guilabel:`Pipeline` dashboard on the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option. Doing so reveals all the lost opportunities on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:87 +msgid "Then, click on the kanban card of the desired lost opportunity to restore, which opens that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 +msgid "From the lost lead's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the lead form, signifying the lead has been restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Lost opportunity with emphasis on the Restore button." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:98 +msgid "Restore multiple opportunities at once" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:100 +msgid "To restore multiple opportunities at once, navigate to the main :guilabel:`Pipeline` dashboard in the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:103 +msgid "Next, select the list view option, which is represented by the three-line :guilabel:`ā˜° (list)` icon in the upper-right corner. Doing so places all the leads from the :guilabel:`Pipeline` page in a list form. With the list form chosen, select the checkbox to the left of each desired opportunity/lead to be restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108 +msgid "Once the desired opportunities/leads have been selected, click the :guilabel:`āš™ļø Action (gear)` drop-down menu at the top of the :guilabel:`Pipeline` page. From the :guilabel:`āš™ļø Action (gear)` drop-down menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:112 +msgid "Doing so removes those selected lost opportunities from the :guilabel:`Pipeline` page because they no longer fit into the `Lost` filter criteria. To reveal these newly-restored leads, delete the `Lost` filter from the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Action button from list view with the Unarchive option emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:121 msgid ":doc:`../performance/win_loss`" msgstr "" @@ -1202,26 +1134,30 @@ msgid "Set customers" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:54 -msgid "You can create and set customers from an :ref:`open POS session `. Registering your customer is necessary to :doc:`collect their loyalty points and grant them rewards `, automatically apply the :doc:`attributed pricelist `, or :ref:`generate and print an invoice `." +msgid "Registering your customer is necessary to :doc:`collect their loyalty points and grant them rewards `, automatically apply the :doc:`attributed pricelist `, or :ref:`generate and print an invoice `." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:60 -msgid "To access the list of customers, click :guilabel:`Customer` on the POS interface. Then, select a customer or create a new one by clicking :guilabel:`Create`, completing the form, and saving." +#: ../../content/applications/sales/point_of_sale.rst:59 +msgid "You can create customers from an :ref:`open POS session ` by clicking :menuselection:`Customer --> Create`, and filling in the contact information. You can also create customers from the backend by going to :menuselection:`Point of Sale --> Orders --> Customers` and clicking :guilabel:`New`. Then, fill in the information and save." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:66 +#: ../../content/applications/sales/point_of_sale.rst:64 +msgid "To set a customer during an order, access the list of customers by clicking :guilabel:`Customer` on the POS interface. You can also set a customer at the payment screen by clicking :guilabel:`Customer`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:71 msgid "Customer notes" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:68 +#: ../../content/applications/sales/point_of_sale.rst:73 msgid "You can add **customer notes** about specific products directly from an open :ref:`POS session `. For instance, to provide cleaning and maintenance tips. They can also be used to track a customer's particular request, such as not wanting the product to be assembled for them." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:72 +#: ../../content/applications/sales/point_of_sale.rst:77 msgid "To do so, select a product and click :guilabel:`Customer Note` on the pad. Doing so opens a pop-up window in which you can add or modify content for the note." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:76 +#: ../../content/applications/sales/point_of_sale.rst:81 msgid "Product notes from an :doc:`imported SO ` are displayed identically in the cart." msgstr "" @@ -1229,7 +1165,7 @@ msgstr "" msgid "Customer note button and notes (SO and POS session) on products in the cart" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:82 +#: ../../content/applications/sales/point_of_sale.rst:87 msgid "Customer notes appear on customers' receipts and invoices similarly to how they appear in the cart, under the related product." msgstr "" @@ -1237,35 +1173,35 @@ msgstr "" msgid "Customer receipt with notes from an SO and from the customer note feature" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:91 +#: ../../content/applications/sales/point_of_sale.rst:96 msgid "Return and refund products" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:93 +#: ../../content/applications/sales/point_of_sale.rst:98 msgid "To return and refund a product," msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:95 +#: ../../content/applications/sales/point_of_sale.rst:100 msgid ":ref:`start a session ` from the **POS dashboard**;" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:96 +#: ../../content/applications/sales/point_of_sale.rst:101 msgid "click :guilabel:`Refund` and select the corresponding order;" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:97 +#: ../../content/applications/sales/point_of_sale.rst:102 msgid "select the product and the quantity to refund using the keypad;" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:98 +#: ../../content/applications/sales/point_of_sale.rst:103 msgid "click :guilabel:`Refund` to go back to the previous screen;" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:99 +#: ../../content/applications/sales/point_of_sale.rst:104 msgid "once the order is completed, click :guilabel:`Payment` to proceed to the refund;" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:100 +#: ../../content/applications/sales/point_of_sale.rst:105 msgid "click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next customer." msgstr "" @@ -1273,31 +1209,31 @@ msgstr "" msgid "refund view from a POS" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:106 +#: ../../content/applications/sales/point_of_sale.rst:111 msgid "You can filter the **orders list** by :guilabel:`Receipt Number`, :guilabel:`Date` or :guilabel:`Customer` using the search bar." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:108 +#: ../../content/applications/sales/point_of_sale.rst:113 msgid "You can also refund a product by selecting the returned product from an open session, and setting a negative quantity that equals the number of returned products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by the quantity of returned products." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:115 +#: ../../content/applications/sales/point_of_sale.rst:120 msgid "Close the POS session" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:117 +#: ../../content/applications/sales/point_of_sale.rst:122 msgid "To close your session, click :guilabel:`Close` in the upper right corner of your screen; doing so opens the :guilabel:`Closing Control` pop-up screen. From this screen, you can retrieve various information:" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:121 +#: ../../content/applications/sales/point_of_sale.rst:126 msgid "the number of orders made and the total amount made during the session;" msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:122 +#: ../../content/applications/sales/point_of_sale.rst:127 msgid "the expected amounts grouped by payment method." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:124 +#: ../../content/applications/sales/point_of_sale.rst:129 msgid "Before closing this window, count your cash using the calculator icon. Doing so opens a pop-up window that computes the total amount in the cash drawer depending on the coins and bills counted and added manually. Then, click :guilabel:`Confirm` or :guilabel:`Discard` to close the window. The computed amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money Details` are specified in the **Notes** section." msgstr "" @@ -1305,23 +1241,23 @@ msgstr "" msgid "How to close a POS session." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:133 +#: ../../content/applications/sales/point_of_sale.rst:138 msgid "Once you are done controlling the amounts, click :guilabel:`Close Session` to close and go back to the **POS dashboard**." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:137 +#: ../../content/applications/sales/point_of_sale.rst:142 msgid "You can let the session open by clicking :guilabel:`Backend` or abort and keep selling by clicking :guilabel:`Discard`." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:139 +#: ../../content/applications/sales/point_of_sale.rst:144 msgid "Depending on your setup, you might only be allowed to close a session if the expected cash revenue equals the counted cash. To close it anyway, click :guilabel:`Ok` on the :guilabel:`Payments Difference` screen." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:144 +#: ../../content/applications/sales/point_of_sale.rst:149 msgid "It is strongly advised to close your POS session at the end of each day." msgstr "" -#: ../../content/applications/sales/point_of_sale.rst:145 +#: ../../content/applications/sales/point_of_sale.rst:150 msgid "To look at all your previous sessions, go to :menuselection:`Point of Sale --> Orders --> Sessions`." msgstr "" @@ -2011,6 +1947,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:23 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63 msgid "Configure the payment method" @@ -2102,6 +2039,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:65 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:86 msgid "Pay with a payment terminal" @@ -2193,61 +2131,84 @@ msgid "SIX" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5 -msgid "Connecting a SIX payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." +msgid "Connecting a **SIX payment terminal** allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9 -msgid "Starting in July 2022, it will **not** be possible anymore to connect and use a Six payment terminal in PoS." +msgid "Even though Worldline has acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are, therefore, not compatible with this integration." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:11 -msgid "Even though Worldline has recently acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are therefore not compatible with this integration." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:17 +msgid "Install the POS IoT Six module" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:16 -msgid "Configure the Payment Method" +msgid "To activate the POS IoT Six module, go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds the necessary driver and interface to your database to detect Six terminals." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:21 -msgid "First, make sure that the :guilabel:`POS Six` module is installed. For this, go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for *POS Six*." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:24 +msgid "This module replaces the **POS Six** module." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:27 +msgid "Connect an IoT box" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29 +msgid "Connecting a Six payment terminal to Odoo is requires :doc:`using a Raspberry Pi or virtual (for Windows OS only) IoT box `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33 +msgid "Configure the terminal ID" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35 +msgid "Navigate to your IoT Box homepage, where you can find the :guilabel:`Six payment terminal` field once your database server is connected to the IoT box. Click :guilabel:`Configure`, fill in the :guilabel:`Terminal ID` field with the ID received from Six, and click :guilabel:`Connect`. Your Six terminal ID should appear in the :guilabel:`Current Terminal Id` section." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 -msgid "The POS Six module." +msgid "Setting the Six terminal ID" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/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." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:43 +msgid "Odoo automatically restarts the IoT box when the Six terminal ID is configured. If your Six terminal is online, it will be automatically detected and connected to the database. Check the IoT box homepage under the :guilabel:`Payments` section to confirm the connection." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 -msgid "Create a new payment method for the SIX payment terminal." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:40 -msgid "Pay with a Payment Terminal" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:39 -msgid "In the :abbr:`PoS (Point of Sale)` interface, at the moment of the payment, select a payment method using a payment terminal. Verify that the amount in the tendered column is the one that has to be sent to the payment terminal and click on :guilabel:`Send`. To cancel the payment request, click on :guilabel:`Cancel`." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 -msgid "The PoS interface." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:48 -msgid "When the payment is done, the status will change to :guilabel:`Payment Successful`. If needed, reverse the last transaction by clicking on :guilabel:`Reverse`." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 -msgid "The Reverse button on the PoS interface." +msgid "Confirming the connection to the Six payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55 -msgid "If there is any issue with the payment terminal, you can still force the payment using the :guilabel:`Force Done` button. This will allow you to validate the order in Odoo even if there are connection issues between the payment terminal and Odoo." +msgid "From your database, go to :menuselection:`Point of Sale --> Configuration --> Payment Methods` to create a new payment method specifically for Six. Click :guilabel:`New`, enter a :guilabel:`Name`, set the :guilabel:`Journal` field as :guilabel:`Bank`, the :guilabel:`Use a Payment Terminal` field as :guilabel:`SIX IOT`, and select the corresponding device in the :guilabel:`Payment Terminal Device` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 +msgid "Creating a new payment method for the SIX payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:67 +msgid "When processing a payment, select :ref:`your Six payment method ` in the :guilabel:`Payment Method` section and click :guilabel:`Send`. To cancel the payment request, click :guilabel:`Cancel`. Once the payment is successful, the status switches to :guilabel:`Payment Successful`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1 +msgid "Paying with Six" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:76 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 +msgid "Once your payment is processed, the type of card used and the transaction ID appear on the payment record." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:78 +msgid "The language used for error messages is the same as the Six terminal. Configure the terminal to change the language or contact Six." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:80 +msgid "By default, the port used by the Six terminal is `7784`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:83 +msgid "If there are connection issues between the payment terminal and Odoo, you can still force the payment validation in Odoo using the :guilabel:`Force Done` button." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:3 @@ -2402,19 +2363,31 @@ msgstr "" msgid "Please note MercuryPay only operates with US and Canadian banks, making this procedure only suitable for North American businesses." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:18 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +msgid "Vantiv card readers should be purchased exclusively from Vantiv, as certain Vantiv terminals bought on Amazon do not include the correct encryption needed to be used with an Odoo database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 +msgid "Configure the Payment Method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22 msgid "First, go in the general settings of the POS app, and activate the Vantiv setting." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:24 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28 msgid "Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:32 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36 msgid "To create new Vantiv credentials, fill in your merchant ID and password, then save. Make sure the credentials you just created are selected, then save the payment method." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:42 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44 +msgid "Pay with a Payment Terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46 msgid "In your PoS interface, at the moment of the payment, select your Vantiv payment method andā€¦ thatā€™s all." msgstr "" @@ -2514,10 +2487,6 @@ msgstr "" msgid "When processing a payment, select *Worldline* as payment method. Check the amount and click on *Send*. Once the payment is successful, the status changes to *Payment Successful*." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 -msgid "Once your payment is processed, the type of card used and the transaction ID appear on the payment record." -msgstr "" - #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98 msgid "In case of connexion issues between Odoo and the payment terminal, force the payment by clicking on *Force Done*, which allows you to validate the order. This option is only available after receiving an error message informing you that the connection failed." msgstr "" @@ -2824,7 +2793,8 @@ msgid "If you select a customer with a default pricelist, it will be applied. Yo msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 -#: ../../content/applications/sales/subscriptions/products.rst:80 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 +#: ../../content/applications/sales/subscriptions/products.rst:108 msgid "Pricelists" msgstr "" @@ -2857,6 +2827,7 @@ msgid "Go to :menuselection:`Point of Sale --> Products --> Pricelists` and clic msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234 msgid "Multiple prices per product" msgstr "" @@ -2889,6 +2860,7 @@ msgid "Setup form of a multiple prices pricelist" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:312 msgid "Advanced price rules" msgstr "" @@ -3045,62 +3017,50 @@ msgid "Invoices" msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42 -msgid "In Point of Sale, you can issue and print invoices upon payment at the cash register or retrieve all the past invoiced orders." +msgid "Point of Sale allows you to issue and print invoices for :ref:`registered customers ` upon payment and retrieve all past invoiced orders." msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46 -msgid "Set a customer" +msgid "An invoice created in a POS creates an entry into the corresponding :ref:`accounting journal `, previously :ref:`set up `." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:48 -msgid "First, you need to open a session and set your customer. Open the **POS interface** by going to :menuselection:`Point of Sale --> New session --> Open session`. Then, click :guilabel:`Customer` to access the list of **customers**." +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:54 +msgid "To define what journals will be used for a specific POS, go to the :ref:`POS' settings ` and scroll down to the accounting section. Then, you can determine the accounting journals used by default for orders and invoices in the :guilabel:`Default Journals` section." msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:-1 -msgid "customer selection and creation button" +msgid "accounting section in the POS settings" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:55 -msgid "From there, you can either set an existing customer by clicking their name or create a new one by clicking :guilabel:`Create`. Doing so opens a customer creation form to fill in with their information. Click :guilabel:`Save` to validate and set this new customer." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:60 -msgid "You can also **edit** a customer's information by clicking :guilabel:`Details`." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:61 -msgid "If you did not set your customer during the order, you can do so at the payment screen by clicking :guilabel:`Customer`." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:63 msgid "Invoice a customer" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:67 -msgid "Once an order is done, click :guilabel:`Payment` to move to the **payment screen**. Click :guilabel:`Invoice` underneath the customer's name to enable issuing and printing invoices upon payment." +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 +msgid "Upon processing a payment, click :guilabel:`Invoice` underneath the customer's name to issue an invoice for that order." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:-1 -msgid "button to generate an invoice in POS" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:74 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:68 msgid "Select the payment method and click :guilabel:`Validate`. The **invoice** is automatically issued and ready to be downloaded and/or printed." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:78 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:72 +msgid "To be able to issue an invoice, a :ref:`customer ` must be selected." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:75 msgid "Retrieve invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:80 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:77 msgid "To retrieve invoices from the **POS dashboard**," msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:82 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79 msgid "access all orders made through your POS by going to :menuselection:`Point of Sale --> Orders --> Orders`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:84 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81 msgid "to access an order's invoice, open the **order form** by selecting the order, then click :guilabel:`Invoice`." msgstr "" @@ -3108,19 +3068,19 @@ msgstr "" msgid "invoice smart button from an order form" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:91 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:88 msgid "**Invoiced orders** can be identified by the :guilabel:`Invoiced` status in the :guilabel:`Status` column." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:93 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:90 msgid "You can filter the list of orders to invoiced orders by clicking :guilabel:`Filters` and :guilabel:`Invoiced`." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:97 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:94 msgid "QR codes to generate invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:99 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:96 msgid "Customers can also request an invoice by scanning the **QR code** printed on their receipt. Upon scanning, they must fill in a form with their billing information and click :guilabel:`Get my invoice`. On the one hand, doing so generates an invoice available for download. On the other hand, the order status goes from :guilabel:`Paid` or :guilabel:`Posted` to :guilabel:`Invoiced` in the Odoo backend." msgstr "" @@ -3128,7 +3088,7 @@ msgstr "" msgid "order status change" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:108 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:105 msgid "To use this feature, you have to enable QR codes on receipts by going to :menuselection:`Point of Sale --> Configuration --> Settings`. Then, select the POS in the :guilabel:`Point of Sale` field, scroll down to the :guilabel:`Bills & Receipts` section and enable :guilabel:`Use QR code on ticket`." msgstr "" @@ -3708,11 +3668,11 @@ msgid ":guilabel:`Lot & Serial Number(s)` are :guilabel:`required` on tracked pr msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:59 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:60 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" msgstr "" #: ../../content/applications/sales/rental.rst:3 @@ -3982,7 +3942,7 @@ msgid ":doc:`setup`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:64 -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:105 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:155 msgid ":doc:`manage`" msgstr "" @@ -4039,7 +3999,7 @@ msgid "Keep in mind that the customer is notified by email about the delivery, a msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:54 -msgid ":doc:`../../../inventory_and_mrp/inventory/shipping/setup/third_party_shipper`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:57 @@ -4111,105 +4071,181 @@ msgid "It is also possible to perform reporting on a per-marketplace basis in a msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:131 -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:104 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:154 msgid ":doc:`features`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:3 -msgid "Configure Amazon Connector in Odoo" +msgid "Amazon Connector configuration" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:6 -msgid "Register your Amazon account in Odoo" +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:5 +msgid "Odoo allows users to register an Amazon seller account in the database, but the user **must** have a paid Amazon Seller account prior to completing the configuration." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:10 -msgid "To register your seller account in Odoo, navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts` and click on :guilabel:`CREATE`." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:8 +msgid "Set up a paid Seller account on Amazon by first logging into the Amazon platform, and navigating to :menuselection:`Account \\& Lists --> Start a Selling Account` from the drop-down menu located in the header section." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:13 -msgid "Choose a meaningful name for your account (e.g. `Europe`), and select your :guilabel:`Sign-up Marketplace`. This is the original sign-up marketplace of your seller account (e.g. if you created your account on Amazon Germany, your sign-up marketplace will be `amazon.de`)" +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:12 +msgid "Then on the :guilabel:`Sell with Amazon` page, follow the sign-up process and finally proceed to follow the instructions below to register and link that Amazon Seller account in Odoo." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:17 -msgid "Upon saving, a button to :guilabel:`link with Amazon` appears. Click on it to be redirected to the Amazon login page, or directly to the consent page if you are already logged in. There, confirm that you want Amazon to give Odoo access to your account and related data." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:16 +msgid "`Sell with Amazon `_" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:21 -msgid "Amazon redirects you to Odoo, with your account registered." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:19 +msgid "Connect Amazon Seller account to Odoo" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:23 -msgid "Once the account is registered, the marketplaces available to this account are synchronized and listed under the :guilabel:`Marketplaces` tab. If you wish, you can remove some items from the list of synchronized marketplaces to disable their synchronization." +msgid "To connect an Amazon Seller account in Odoo, navigate to :menuselection:`Sales app --> Configuration --> Settings --> Connectors section`, activate the :guilabel:`Amazon Sync` feature, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:28 -msgid "Match database products in Amazon" +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:27 +msgid "Then, return to :menuselection:`Sales app --> Configuration --> Settings --> Connectors section`, and click on the :guilabel:`Amazon Accounts` link under the :guilabel:`Amazon Sync` setting." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:30 -msgid "When an Amazon order is synchronized, up to three sales order items are created in Odoo for each product sold on Amazon: one for the marketplace product, one for the shipping charges (if any) and one for the gift wrapping charges (if any)." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:-1 +msgid "The Amazon Accounts link beneath the Amazon Sync settings in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:36 -msgid "The selection of a database product for a sales order item is done by matching its **internal reference** with the **SKU** for marketplace items, the **shipping code** for delivery charges, and the **gift wrapping** code for gift wrapping charges." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:34 +msgid "Doing so reveals a separate :guilabel:`Amazon Accounts` page. From here, click :guilabel:`New` to create and link a new Amazon account." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:40 -msgid "For marketplace products, pairings are saved as **Amazon Offers** which are listed under the **Offers** stat button on the account form. Offers are automatically created when the pairing is established and are used for subsequent orders to lookup SKUs. If no offer with a matching SKU is found, :ref:`the internal reference is used instead `." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:37 +msgid "On the blank :guilabel:`Amazon Account` form page, start by choosing a name for the account (e.g. `American Marketplace`). Then, in the :guilabel:`Credentials` tab, select the marketplace on which the seller account was initially created from the :guilabel:`Home Marketplace` drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:46 -msgid "It is possible to force the pairing of a marketplace item with a specific product by changing either the product or the SKU of an offer. The offer can be manually created if it was not automatically done yet. This is useful if you do not use the internal reference as the SKU or if you sell the product under different conditions." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:-1 +msgid "A typical Amazon Account form page in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:51 -msgid "If no database product with a matching internal reference is found for a given SKU or gift wrapping code, a default database product **Amazon Sale** is used. The same is done with the default product **Amazon Shipping** and the shipping code." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:45 +msgid "After saving, the field in the :guilabel:`Credentials` tab is replaced by a :guilabel:`Link with Amazon` button." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:56 -msgid "To modify the default products, activate the :ref:`developer mode ` and navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Default Products`." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:-1 +msgid "A typical Amazon Account form page and Link with Amazon button in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:61 -msgid "Configure taxes of products" +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:52 +msgid "Clicking that button redirects to either the Amazon login page, or directly to the required consent page, if the user is already logged in to Amazon." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:63 -msgid "To allow for tax reporting of Amazon sales with Odoo, the taxes applied to the sales order items are those set on the product or determined by the fiscal position. Make sure to have set the correct taxes on your products in Odoo or to have it done by a fiscal position, to avoid discrepancies in the subtotals between Seller Central and Odoo." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:55 +msgid "On the login page, log in to the desired Amazon seller account." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:69 -msgid "As Amazon does not necessarily apply the same taxes as those configured in Odoo, it may happen that order totals differ by a few cents from that on Seller Central. Those differences can be resolved with a write-off when reconciling the payments in Odoo." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:57 +msgid "On the consent page, confirm that Amazon is allowed to give Odoo access to the account and related data." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:60 +msgid "Upon confirmation, Amazon returns the user to Odoo, and the account has been registered." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:62 +msgid "With the Amazon account successfully registered, the marketplaces available to this specific account are synchronized with Odoo and listed under the :guilabel:`Marketplaces` tab." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:65 +msgid "If desired, remove items from the list of synchronized marketplaces to disable synchronization." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:68 +msgid "Amazon orders in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:70 +msgid "When an Amazon order is synchronized, up to three line items are created on the sales order in Odoo. Each one represents a product sold on Amazon: one for the product that was sold on Amazon Marketplace, one for the shipping charges (if any), and one for the gift wrapping charges (if any)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:76 +msgid "The selection of a database product for a sales order item is done by matching its :guilabel:`Internal Reference` (a customizable product reference idenifier in Odoo, like `FURN001`) with the Amazon *SKU* for marketplace items, the Amazon *Shipping Code* for delivery charges, and the Amazon *Gift Wrapping* code for gift wrapping charges." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:81 +msgid "For marketplace products, pairings are saved as *Amazon Offers*, which are listed under the :guilabel:`Offers` smart button on the account form." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:-1 +msgid "The Amazon Offers smart button on the account form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:88 +msgid "Offers are automatically created when the pairing is established, and they're used for subsequent orders to lookup SKUs. If no offer with a matching SKU is found, :ref:`the internal reference is used instead `." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:93 +msgid "It's possible to force the pairing of a marketplace item with a specific product, by changing either the product or the SKU of an offer to ensure they match. The offer can be manually created if it was not automatically done yet." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:97 +msgid "This is useful if the internal reference is not used as the SKU, or if the product sells under different conditions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:100 +msgid "If no database product with a matching internal reference is found for a given Amazon SKU or gift wrapping code, then a default database product, *Amazon Sale*, is used. The same is done with the default product *Amazon Shipping* if no database product is found for a given Amazon shipping code." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:105 +msgid "To modify default products, activate the :ref:`developer mode `, and navigate to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Default Products`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:110 +msgid "Product tax configuration" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:112 +msgid "To allow for tax reporting of Amazon sales with Odoo, the taxes applied to the sales order items are those set on the product, or determined by the fiscal position." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:115 +msgid "Make sure to have the correct taxes set on your products in Odoo, or have it done by a fiscal position, to avoid discrepancies in the subtotals between *Amazon Seller Central* and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:119 +msgid "As Amazon does not necessarily apply the same taxes as those configured in Odoo, it may happen that order totals differ by a few cents between Odoo and *Amazon Seller Central*. Those differences can be resolved with a write-off when reconciling the payments in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:126 msgid "Add a new marketplace" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:78 -msgid ":ref:`All marketplaces are supported by the Amazon Connector `, but recently created ones might be missing from your database. To add a new marketplace, proceed as follows:" +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:128 +msgid "All marketplaces are supported by the Amazon Connector. To add a new marketplace, proceed as follows:" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:82 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:131 #: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 msgid "Activate the :ref:`developer mode `." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:83 -msgid "Go to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Marketplaces`." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:132 +msgid "Go to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Marketplaces`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:85 -msgid "Create a new marketplace record. Enter the :guilabel:`Marketplace ID` and select the :guilabel:`Amazon Region` for your marketplace as described in the `Amazon Documentation for marketplace IDs and regions `_, and the :guilabel:`Seller Central URL` as described in the `Amazon Documentation for seller central URLs `_." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:134 +msgid "Click :guilabel:`New` to create a new marketplace record." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:91 -msgid "Set the name of the record to `Amazon.` to easily retrieve it (e.g.: **Amazon.se**). The :guilabel:`API Identifier`, the :guilabel:`Region` and the :guilabel:`Seller Central URL` fields should respectively hold the *MarketplaceId*, the selected Amazon region and the *Seller Central URL* values from the Amazon Documentation." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:135 +msgid "Enter the Marketplace ID in the :guilabel:`API Idenifier` field, and select the :guilabel:`Amazon Region` for your marketplace as described in the `Amazon Documentation for marketplace IDs and regions `_, and the :guilabel:`Seller Central URL` as described in the `Amazon Documentation for seller central URLs `_." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/setup.rst:95 -msgid "Once the marketplace is saved, update the Amazon Account configuration by going to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`. Open the account on which you wish to use the new marketplace, go to the :guilabel:`Marketplaces` tab and click on :guilabel:`Update available marketplaces` (an animation should confirm the success of the operation). Newly added marketplaces are automatically added to the list of synchronized marketplaces. If the new marketplace is not added to the list, it means that it is either incompatible or unavailable for your seller account." +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:140 +msgid "Set the :guilabel:`Name` of the record to `Amazon.` to easily retrieve it (e.g. `Amazon.se`). The :guilabel:`API Identifier`, the :guilabel:`Region` and the :guilabel:`Seller Central URL` fields should respectively hold the *Marketplace ID*, the selected Amazon region, and the *Seller Central URL* values from the Amazon Documentation." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:144 +msgid "Once the marketplace is saved, update the Amazon Account configuration by going to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:147 +msgid "Select the account on which to use the new marketplace, go to the :guilabel:`Marketplaces` tab, and click on :guilabel:`Update available marketplaces`. An animation should confirm the success of the operation. Newly added marketplaces are automatically added to the list of synchronized marketplaces. If the new marketplace is not added to the list, it means that it is either incompatible or unavailable for the seller account." msgstr "" #: ../../content/applications/sales/sales/ebay_connector.rst:5 @@ -4437,258 +4473,575 @@ msgid "With a down payment, the buyer pays a portion of the total amount owed wh msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 -msgid "Initial down payment request" +msgid "Create invoices" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 msgid "When a sales order is confirmed, the option to create an invoice becomes available, via the :guilabel:`Create Invoice` button, located in the upper-left corner of the sales order form. When clicked, a :guilabel:`Create invoices` pop-up appears." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:20 -msgid "Invoices are automatically created in drafts, so they can be reviewed before validation." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "Create invoices pop-up form that appears in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:22 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:24 +msgid "Invoices are automatically created as drafts, so they can be reviewed before validation." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:26 msgid "On the :guilabel:`Create invoices` pop-up, there are 3 options to choose from in the :guilabel:`Create Invoice` field:" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 msgid ":guilabel:`Regular invoice`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 -msgid "If :guilabel:`Regular Invoice` is selected the other fields disappear, as they only pertain to down payment configurations." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:42 msgid ":guilabel:`Down payment (percentage)`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:31 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:43 msgid ":guilabel:`Down payment (fixed amount)`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:32 -msgid "In terms of a down payment, it can either be a fixed amount or a percentage of the total amount." -msgstr "" - #: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 -msgid "Once the desired down payment option is selected in the :guilabel:`Create Invoice` field, designate the desired amount (either as a percentage or fixed amount) in the :guilabel:`Down Payment Amount` field." +msgid "If :guilabel:`Regular Invoice` is selected, the other fields disappear, as they only pertain to down payment configurations." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 -msgid "Then, select the appropriate income account for the invoice in the :guilabel:`Income Account` field, and add a tax amount, if necessary, in the :guilabel:`Customer Taxes` field. These settings will be reused for future down payments." +msgid "Initial down payment request" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:40 +msgid "On the :guilabel:`Create invoices` pop-up form, the down payment options are:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:45 +msgid "Once the desired down payment option is selected in the :guilabel:`Create Invoice` field on the pop-up form, designate the desired amount, either as a percentage or a fixed amount, in the :guilabel:`Down Payment Amount` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:49 +msgid "Then, select the appropriate income account for the invoice in the :guilabel:`Income Account` field. Next, select a tax amount, if necessary, in the :guilabel:`Customer Taxes` drop-down field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "How to configure a down payment on Odoo Sales." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:47 -msgid "When a down payment is first requested, a new product called :guilabel:`Down payment` is created. This product is registered as a :guilabel:`Service` product, with an invoicing policy of :guilabel:`Ordered quantities`. This product can be edited and modified at any time." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:52 -msgid "If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an invoice will **not** be able to be created." +msgid "A create invoices pop-up form with down payment fields filled in with information." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 -msgid "Request a 50% down payment" +msgid "Once all fields are filled in with the desired information, click the :guilabel:`Create Draft Invoice` button. Upon clicking this button, Odoo reveals the :guilabel:`Customer Invoice Draft`." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:58 -msgid "For the following example, the flow involves a 50% amount down payment on a product with :guilabel:`Ordered quantities` as the invoicing policy." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:62 -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:184 -msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:64 -msgid "When the order is confirmed (via the :guilabel:`Confirm` button), it's time to create/view the invoice, by clicking :guilabel:`Create Invoice`." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:67 -msgid "Then, on the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down Payment Amount` field. Lastly, click :guilabel:`Create and View Invoice` to create and view the invoice." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:59 +msgid "In the :guilabel:`Invoice Lines` tab of the :guilabel:`Customer Invoice Draft`, the down payment that was just configured in the :guilabel:`Create invoices` pop-up form appears as a :guilabel:`Product`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "Create invoices pop up window in Odoo Sales." +msgid "Down payment as a product in the invoice lines tab of a customer invoice draft in Odoo." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:75 -msgid "Doing so reveals the draft invoice, which mentions the down payment." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:68 +msgid "When the :guilabel:`Down payment` product in the :guilabel:`Invoice Lines` tab is clicked, Odoo reveals the product form for the down payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:71 +msgid "By default, the :guilabel:`Product Type` of down payment products generated for invoices are set as :guilabel:`Service`, with the :guilabel:`Invoicing Policy` set to :guilabel:`Prepaid/Fixed Price`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "Down payment product form with service product type and invoicing policy field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:79 +msgid "This product can be edited/modified at any time." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:82 +msgid "If :guilabel:`Based on Delivered Quantity (Manual)` is chosen as the :guilabel:`Invoicing Policy`, an invoice will **not** be able to be created." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:86 +msgid "Example: request 50% down payment" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:89 +msgid "The following example involves a 50% amount down payment on a product (:guilabel:`Cabinet with Doors`) with :guilabel:`Ordered quantities` as the :guilabel:`Invoicing Policy`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:0 +msgid "Cabinet with doors product form showcasing various details and fields." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:97 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:260 +#: ../../content/applications/sales/sales/invoicing/expense.rst:226 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:238 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:71 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:166 +msgid ":doc:`invoicing_policy`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 +msgid "First, navigate to :menuselection:`Sales app --> New`, and add a :guilabel:`Customer` to the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:102 +msgid "Then, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab, and select the :guilabel:`Cabinet with Doors` product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 +msgid "When the order is confirmed (via the :guilabel:`Confirm` button), the quotation turns into a sales order. Once this occurs, create and view the invoice by clicking :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "Cabinet with doors sales order that's been confirmed in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 +msgid "Next, on the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down Payment Amount` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:116 +msgid "The :guilabel:`Income Account` and :guilabel:`Customer Taxes` fields are *not* required fields, and they will *not* appear if they've already been preconfigured in previous down payment requests." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:120 +msgid "For more information, check out the documentation on :ref:`customer taxes modification on down payments ` and :ref:`income account modification on down payments `." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:124 +msgid "Lastly, click :guilabel:`Create Draft Invoice` to create and view the invoice draft." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 +msgid "Clicking :guilabel:`Create Draft Invoice` reveals the draft invoice, which includes the down payment as a :guilabel:`Product` in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:129 +msgid "From there, the invoice can be confirmed and posted by clicking :guilabel:`Confirm`. Confirming the invoice changes the status from :guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of buttons at the top of the page." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 msgid "A sample draft invoice with down payment mentioned in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:81 -msgid "From there, the invoice can be confirmed/posted, and the payment can be registered. Return to the sales order, via the breadcrumbs." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:84 -msgid "On the sales order, the option to view what the customer will see is available, via the :guilabel:`Customer Preview` smart button, and the :guilabel:`Invoice` button reveals the drafted invoice. In either case, the down payment is mentioned on both the sales order and draft invoice." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:137 +msgid "From those buttons, the payment can be registered by clicking :guilabel:`Register Payment`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "How the down payment is mentioned on the sales order in Odoo Sales." +msgid "Showcase of the Register Payment button on a confirmed customer invoice." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:92 -msgid "To confirm and register the first payment of the down payment, click the :guilabel:`Invoices` smart button to return to the invoice. On the :guilabel:`Customer Invoice` page, click :guilabel:`Confirm`, then :guilabel:`Register Payment` to open a :guilabel:`Register Payment` pop-up form." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:143 +msgid "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-populated with the necessary information. Confirm the information provided is correct and make any necessary adjustments. When ready, click the :guilabel:`Create Payment` button." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "How the register payment pop up looks in Odoo Sales." +msgid "Showcase of the Register Payment pop-up window with create payment button." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:101 -msgid "On this form, select the appropriate :guilabel:`Journal` and confirm that the down payment amount is correct in the :guilabel:`Amount` field. Then, make any other modifications to the other fields, if necessary, before clicking :guilabel:`Create Payment`." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 -msgid "Odoo returns to the invoice, which now has a green :guilabel:`In Payment` banner visible in the upper-right corner." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:151 +msgid "After clicking :guilabel:`Create Payment`, Odoo reveals the customer invoice, now with a green :guilabel:`In Payment` banner in the upper-right corner." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "How the initial down payment invoice has a green paid banner in Odoo Sales." +msgid "Customer Invoice with a green In Payment banner located in the upper-right corner." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 -msgid "Now, when the customer wants to pay the remaining amount of the order, another invoice must be created. To do that, return to the sales order, and click :guilabel:`Create Invoice`." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +msgid "Now, when the customer wants to pay the remaining amount of the order, another invoice must be created. To do that, return to the sales order, via the breadcrumb links." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:115 -msgid "On the :guilabel:`Create invoices` pop-up window, there is now an option to :guilabel:`Deduct down payments`, which is selected by default." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:161 +msgid "Back on the sales order, a new :guilabel:`Down Payments` section is present in the :guilabel:`Order Lines` tab, along with the down payment that was just invoiced and posted." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "The down payments section in the order lines tab of a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:168 +msgid "Next, click the :guilabel:`Create Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 +msgid "On the :guilabel:`Create invoices` pop-up window that appears, there are two new fields: :guilabel:`Already invoiced` and :guilabel:`Amount to invoice`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 msgid "The deduct down payment option on the create invoices pop up in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:122 -msgid "If the remaining amount is ready to be paid, the :guilabel:`Regular Invoice` option should be selected, and the :guilabel:`Deduct down payments` option should *stay* selected. Then, click :guilabel:`Create and View Invoice`." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:177 +msgid "If the remaining amount is ready to be paid, select the :guilabel:`Regular Invoice` option. Odoo will create an invoice for the exact amount needed to complete the total payment, as indicated in the :guilabel:`Amount to invoice` field." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 -msgid "Doing so reveals a separate :guilabel:`Invoices` page, listing all the invoices for that specific sales order. Each invoice line item displays all the necessary information related to each invoice, along with the current :guilabel:`Payment Status`." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:181 +msgid "Once ready, click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:183 +msgid "Doing so reveals another :guilabel:`Customer Invoice Draft` page, listing *all* the invoices for that specific sales order in the :guilabel:`Invoice Lines` tab. Each invoice line item displays all the necessary information related to each invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:187 +msgid "To complete the flow, click :guilabel:`Confirm`, which changes the status of the invoice from :guilabel:`Draft` to :guilabel:`Posted`. Then, click :guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:190 +msgid "Once again, the :guilabel:`Register Payment` appears, with all fields auto-populated with the necessary information, including the remaining amount left to be paid on the order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "The down payment invoices page in Odoo Sales." +msgid "The second register payment pop-up form in Odoo sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:134 -msgid "To complete the flow, select the invoice with the :guilabel:`Not Paid` status, which opens that invoice. On the invoice page, click :guilabel:`Confirm`, then :guilabel:`Register Payment`, and confirm that the remaining :guilabel:`Amount` is correct. Then, click :guilabel:`Create Payment`." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:197 +msgid "After confirming that information, click :guilabel:`Create Payment`. Doing so reveals the final :guilabel:`Customer Invoice` with a green :guilabel:`In Payment` banner in the upper-right corner. Also, both down payments are present in the :guilabel:`Invoice Lines` tab." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:138 -msgid "That pop-up window disappears, and a green :guilabel:`In Payment` banner is now present on the invoice. The line items on the invoice show that the total amount has been paid, including mentions of the down payment, and the flow is complete." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "The second down payment invoice with in payment banner in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:142 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:205 +msgid "At this point, the flow is now complete." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:208 msgid "This flow is also possible with the :guilabel:`Fixed amount` down payment option." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:145 -msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, the down payments will **not** be able to be deducted when it comes time to invoice the customer. This is because, due to the invoicing policy, the product(s) would have to be delivered *before* creating the final invoice." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:211 +msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, the down payments will **not** be able to be deducted when it comes time to invoice the customer." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:150 -msgid "If nothing has been delivered, a :guilabel:`Credit Note` is created, which cancels the draft invoice that was created after the down payment. To utilize the :guilabel:`Credit Note` option, the *Inventory* application must be installed, in order to confirm the delivery. Otherwise, the delivered quantity can be entered manually directly on the sales order." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:215 +msgid "This is because, due to the invoicing policy, the product(s) would have to be delivered *before* creating the final invoice." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:156 -msgid "Income account and customer taxes modifications" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:218 +msgid "If nothing has been delivered, a :guilabel:`Credit Note` is created, which cancels the draft invoice that was created after the down payment." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:221 +msgid "To utilize the :guilabel:`Credit Note` option, the *Inventory* application must be installed, in order to confirm the delivery. Otherwise, the delivered quantity can be entered manually directly on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:228 +msgid "Customer taxes modification on down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:230 msgid "To adjust the income account and customer taxes attached to a down payment, navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> Products --> Products`), search for the `Down Payment` product in the search bar, and select it to reveal the product detail page." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:162 -msgid "On the :guilabel:`Down Payment` product page, click :guilabel:`Edit`, then scroll down to the :guilabel:`General Information` tab. In this tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:234 +msgid "On the :guilabel:`Down Payment` product page, in the :guilabel:`General Information` tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "How to modify the income account link to down payments" +msgid "How to modify the income account link to down payments." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 -msgid "To change or adjust the income account attached to the :guilabel:`Down Payment` product page, the *Accounting* app **must** be installed. With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes available on the product page. That tab will **not** be accessible without the *Accounting* app installed." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:244 +msgid "Income account modification on down payments" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:175 -msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, in the :guilabel:`Receivables` section. Once all desired changes are complete, click :guilabel:`Save`." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:246 +msgid "To change or adjust the income account attached to the :guilabel:`Down Payment` product page, the *Accounting* app **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:249 +msgid "With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes available on the product page. That tab will **not** be accessible without the *Accounting* app installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:252 +msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, located in the :guilabel:`Receivables` section." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:3 -msgid "Re-invoice expenses to customers" +msgid "Reinvoice expenses to customers" msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:5 -msgid "It often happens that your employees have to spend their personal money while working on a project for your client. Let's take the example of a consultant paying for a hotel to work on the site of your client. As a company, you would like to be able to invoice that expense to your client." +msgid "While working on a project for a client, employees often have to spend their own money on various expenses related to the project." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:12 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:64 -msgid "Expenses configuration" +#: ../../content/applications/sales/sales/invoicing/expense.rst:8 +msgid "For example, an employee may need to use their own money to pay for a hotel, while they provide an on-site service for a client. As a company, this expense should be reinvoiced to the customer. With Odoo, these kinds of expenses can quickly be reinvoiced to the customer related to the project." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:14 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:66 -msgid "To track & invoice expenses, you will need the expenses app. Go to :menuselection:`Apps --> Expenses` to install it." +#: ../../content/applications/sales/sales/invoicing/expense.rst:13 +msgid "Expenses application" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:15 +msgid "To be able to reinvoice a customer for an expense, the *Expenses* application **must** be installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:17 -msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Invoicing --> Configuration --> Settings` and activate *Analytic Accounting*." +msgid "To install the *Expenses* application, navigate to :menuselection:`main Odoo dashboard --> Apps`, and click :guilabel:`Install` on the *Expenses* application block. When clicked, Odoo installs the application, refreshes the page, and returns to the main Odoo dashboard." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:22 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:74 -msgid "Add expenses to your sales order" +msgid "Add expenses to sales orders" msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:24 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:76 -msgid "From the expense app, you or your consultant can create a new one, e.g. the hotel for the first week on the site of your customer." +msgid "To begin, have a sales order confirmed in the *Sales* app to which a reinvoiced expense can be added. Or, create a new sales order from scratch. To do that, navigate to the :menuselection:`Sales app --> New`. Doing so reveals a blank quotation form." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:27 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:79 -msgid "You can then enter a relevant description and select an existing product or create a new one from right there." +#: ../../content/applications/sales/sales/invoicing/expense.rst:28 +msgid "Then, add a :guilabel:`Customer`, and add a product to the :guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`. Next, select a product from the drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:33 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:85 -msgid "Here, we are creating a *Hotel* product:" +#: ../../content/applications/sales/sales/invoicing/expense.rst:31 +msgid "Lastly, click :guilabel:`Confirm` to confirm the sales order." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:38 -msgid "Under the invoicing tab, select *Delivered quantities* and either *At cost* or *Sales price* as well depending if you want to invoice the cost of your expense or a previously agreed on sales price." +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "This is how a confirmed sales order looks in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:45 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:97 -msgid "To modify or create more products go to :menuselection:`Expenses --> Configuration --> Expense products`." +#: ../../content/applications/sales/sales/invoicing/expense.rst:37 +msgid "With the sales order confirmed, it's time to create an expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:39 +msgid "To do that, navigate to the *Expenses* application, by going to :menuselection:`main Odoo dashboard --> Expenses`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:42 +msgid "Then, from the *Expenses* dashboard, click :guilabel:`New` to reveal a blank expenses form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "A blank expenses form in the Odoo Expenses application." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:48 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:100 -msgid "Back on the expense, add the original sale order in the expense to submit." +msgid "On the expenses form, add a :guilabel:`Description` to easily reference the expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:50 +msgid "Then, in the :guilabel:`Category` field, select one of the following options from the drop-down menu:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:53 +msgid ":guilabel:`Communication`: any form of communication related to a project/order." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:54 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:106 -msgid "It can then be submitted to the manager, approved and finally posted." +msgid ":guilabel:`Others`: expense that doesn't fit into any other categories." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:65 -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:117 -msgid "It will then be in the sales order and ready to be invoiced." +#: ../../content/applications/sales/sales/invoicing/expense.rst:55 +msgid ":guilabel:`Meals`: any form of meal costs related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:56 +msgid ":guilabel:`Gifts`: any form of gift costs related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:57 +msgid ":guilabel:`Mileage`: any form of mileage (gas) costs related to project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:58 +msgid ":guilabel:`Travel \\& Accommodation`: any travel or accommodation costs related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:61 +msgid "New expense categories can be created from an expense form, by clicking the :guilabel:`Category` field drop-down menu, selecting :guilabel:`View All`, and clicking :guilabel:`New` from the :guilabel:`Search:Category` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:0 +msgid "The Search:Category expenses pop-up window from a blank expenses form in Odoo Expenses." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:69 +msgid "For this sample workflow, which will reinvoice a customer for a brief hotel stay, the :guilabel:`Category` for this example is :guilabel:`[TRANS \\& ACC] Travel \\& Accommodation`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:73 +msgid "The following example requires the *Sales*, *Accounting*, and *Expense* apps to view/modify all the fields mentioned during the workflow." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:76 +msgid "Beneath the :guilabel:`Category` field, enter in the amount to be expensed in the :guilabel:`Total` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:79 +msgid "Next, designate if there are any :guilabel:`Included taxes` in the :guilabel:`Total`. If a preconfigured tax amount is selected from the :guilabel:`Included taxes` field, Odoo auto-calculates the taxed amount, based on the amount entered in the :guilabel:`Total` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:83 +msgid "Then, choose which :guilabel:`Employee` was responsible for the expense, and choose an option in the :guilabel:`Paid By` field: :guilabel:`Employee (to reimburse)` or :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:86 +msgid "In this case, our employee paid for the hotel with their own money, so the :guilabel:`Employee (to reimburse)` option is chosen." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:89 +msgid "On the right-hand side of the expenses form, the option to add a :guilabel:`Bill Reference` is available. Beneath that, the auto-populated :guilabel:`Expense Date` and :guilabel:`Account` fields are available." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:94 +msgid "The :guilabel:`Expense Date` and :guilabel:`Account` field can be modified, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:96 +msgid "Next, in the :guilabel:`Customer to Reinvoice` field, click the blank field to reveal a drop-down menu. From this drop-down menu, select the appropriate sales order to which this expense should be attached. This field **must** be filled, in order to reinvoice a customer for an expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:100 +msgid "Lastly, the option to modify the :guilabel:`Analytic Distribution` and :guilabel:`Company` fields are available. These fields are *not* required to complete a reinvoiced expense to a customer, but are available to modify, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:104 +msgid "Also, at the bottom of the expense form, there is a :guilabel:`Notes...` section, wherein any notes related to this expense can be added, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "A filled out expenses form in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:111 +msgid "At the top of the expense form, there are buttons to :guilabel:`Attach Receipt`, :guilabel:`Create Report`, and :guilabel:`Split Expense`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:114 +msgid "If there is a physical or digital receipt that should be attached to the expense, click :guilabel:`Attach Receipt`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:117 +msgid "If the cost of this expense needs to be split, click :guilabel:`Split Expense`. This feature can be used for a number of reasons (spitting expense with another employee, to accommodate different tax rates, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:121 +msgid "If neither of these options are necessary, click :guilabel:`Create Report` to lock in the expense report that was just configured." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:124 +msgid "Doing so reveals an :guilabel:`Expense Report Summary` for the new expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "An expense report summary in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:130 +msgid "Here, once the details related to the expense have been confirmed, click :guilabel:`Submit to Manager`. This sends the expense report to the approving manager, who will review the expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:133 +msgid "The manager in charge of reviewing and approving the expense will inspect the details related to the expense, and if there are no issues, they will click the :guilabel:`Approve` button ā€” which *only* appears on the manager's view of the :guilabel:`Expense Report Summary` that's been submitted to the manager by the employee." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "An expense report summary that a manager will approve with an Approve button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:142 +msgid "Once approved, the buttons at the top of the :guilabel:`Expense Report Summary` change once again. At this point, the buttons at the top of the :guilabel:`Expense Report Summary` are: :guilabel:`Post Journal Entries`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, and :guilabel:`Reset to Draft`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "An expense report summary with post journal entries button at the top of the form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:151 +msgid "When the manager is satisfied with the :guilabel:`Expense Report Summary`, they'll click :guilabel:`Post Journal Entries`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:154 +msgid "Upon clicking :guilabel:`Post Journal Entries`, that button disappears, and the :guilabel:`Analytic Distribution` column in the :guilabel:`Expense` tab is filled with the sales order that was initially configured to the expense in the :guilabel:`Customer to Reinvoice` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:159 +msgid "Reinvoice expense" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:161 +msgid "With those steps completed, it's time to return to the sales order to complete the reinvoice of the expense to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:164 +msgid "To do that, navigate to :menuselection:`main Odoo dashboard --> Sales app`, and select the appropriate sales order that should be reinvoiced for the expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:167 +msgid "On the sales form, the newly-configured expense is now in the :guilabel:`Order Lines` tab, with its :guilabel:`Delivered` column filled in, and ready to be invoiced." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "A sales order with the configured expense ready to be invoiced in the Order Lines tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:174 +msgid "After confirming the details of the expense, click :guilabel:`Create Invoice` at the top of the sales order. When clicked, a :guilabel:`Create invoices` pop-up window appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "A create invoices pop-up window that appears when the Create Invoice is clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:181 +msgid "From this pop-up window, leave the :guilabel:`Create Invoice` field on the default :guilabel:`Regular invoice` option, and click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:184 +msgid "Doing so reveals a :guilabel:`Customer Invoice Draft` showing *only* the expense in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "A customer invoice draft with the expense in the Invoice Lines tab of the form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:191 +msgid "If all the information related to the expense is correct, click :guilabel:`Confirm` to confirm the invoice. Doing so moves the status of the invoice from :guilabel:`Draft` to :guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:194 +msgid "To send the invoice to the customer, click :guilabel:`Send \\& Print`. Doing so reveals a :guilabel:`Send` pop-up window, with a preconfigured message and PDF invoice in the body of the message. The message can be reviewed and modified, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:198 +msgid "Once ready, click :guilabel:`Send \\& Print` to send the invoice to the customer. When clicked, the pop-up window disappears, and Odoo sends the message/invoice to the customer. Additionally, a PDF of the invoice is automatically downloaded for record-keeping and/or printing purposes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:202 +msgid "Back on the :guilabel:`Customer Invoice`, click the :guilabel:`Register Payment` button when the customer pays for the invoiced expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "A customer invoice with the register payment button ready to be clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:209 +msgid "When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment` pop-up window appears. In this pop-up window, the necessary fields are auto-populated with the correct information. After reviewing the information, click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 +msgid "A register payment pop-up window on a customer invoice in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:217 +msgid "Once :guilabel:`Create Payment` is clicked, the pop-up window disappears, and a green :guilabel:`In Payment` banner is in the upper-right corner of the invoice, signifying this invoice is paid for in full. Thus, completing the workflow." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:227 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:236 +msgid ":doc:`time_materials`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:228 +msgid ":doc:`milestone`" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:3 @@ -4792,31 +5145,275 @@ msgid "Invoice project milestones" msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:5 -msgid "Milestone invoicing can be used for expensive or large-scale projects, with each milestone representing a clear sequence of work that will incrementally build up to the completion of the contract. This invoicing method is comfortable both for the company which is ensured to get a steady cash flow throughout the project lifetime and for the client who can monitor the project's progress and pay in several installments." +msgid "Invoicing based on project milestones can be used for expensive or large-scale projects. The series of milestones in a project represent a clear sequence of work that will inevitably result in the completion of a project and/or contract." msgstr "" -#: ../../content/applications/sales/sales/invoicing/milestone.rst:13 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:9 +msgid "This method of invoicing ensures the company gets a consistent flow of money throughout the lifetime of the project. Customers can closely monitor every phase of the project's development as it happens, in addition to paying a large bill in several installments, instead of all at once." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:14 msgid "Create milestone products" msgstr "" -#: ../../content/applications/sales/sales/invoicing/milestone.rst:15 -msgid "In Odoo, each milestone of your project is considered as a product. To configure products to work this way, go to any product form." +#: ../../content/applications/sales/sales/invoicing/milestone.rst:16 +msgid "In Odoo, each milestone of a project is considered as an individual product." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:18 -msgid "You have to set the product type as *Service* under general information and select *Milestones* in the sales tab." +msgid "To create and/or configure products to work like this, first navigate to :menuselection:`Sales app --> Products --> Products`. Then, click on a product, or create a new one by clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/sales/sales/invoicing/milestone.rst:25 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:22 +msgid "The option to invoice based on milestones is only available for certain product types." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:24 +msgid "On the product form, under the :guilabel:`General Information` tab, the :guilabel:`Product Type` field *must* be set on any of the following options: :guilabel:`Service`, :guilabel:`Event Ticket`, :guilabel:`Event Booth`, or :guilabel:`Course`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The invoicing policy field drop-down menu with options on product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:32 +msgid "With any of those :guilabel:`Product Type` options selected, choose :guilabel:`Based on Milestones` from the :guilabel:`Invoicing Policy` drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:39 +msgid "Beneath that is the :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:41 +msgid "To ensure workflows are as seamless as possible, it is recommended that an option in the :guilabel:`Create on Order` field is selected." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:45 +msgid "Leaving it on the default :guilabel:`Nothing` option won't negatively affect the desired workflow. However, a project *must* then be created directly from a sales order form with that specific product. Once a project is created *then* milestones and tasks can be created and configured." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:50 +msgid "When the :guilabel:`Create on Order` default option of :guilabel:`Nothing` is clicked, a drop-down menu is revealed with the following options:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:53 +msgid ":guilabel:`Task`: Odoo creates a task related to this milestone product in the *Projects* app when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:55 +msgid ":guilabel:`Project \\& Task`: Odoo creates a project and task related to this milestone product in the *Projects* app when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:57 +msgid ":guilabel:`Project`: Odoo creates a project related to this milestone product in the *Projects* app when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:60 +msgid "When :guilabel:`Task` is selected, a :guilabel:`Project` field appears. In this field, select to which existing project in the *Projects* app this created task should be connected." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The Project field appears when the Task option is selected in Create on Order field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:67 +msgid "When :guilabel:`Project \\& Task` or :guilabel:`Project` is selected, two new fields appear: :guilabel:`Project Template` and :guilabel:`Workspace Template`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The Project template and workspace template fields that appear on milestone product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:74 +msgid "The :guilabel:`Project Template` field provides template options to use for the project that will be created when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:77 +msgid "The :guilabel:`Workspace Template` field provides template options to use for the workspace (for the *Documents* app, not the *Projects* app) that will be automatically generated for the project when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:82 +msgid "For organizational purposes, click the :guilabel:`Sales` tab on the product form, and enter a custom 'Milestone' related descriptor in the :guilabel:`Sales Description` field. This information appears in the :guilabel:`Description` column on the :guilabel:`Order Lines` tab of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:87 +msgid "Or, directly edit/modify the :guilabel:`Description` field on the :guilabel:`Order Lines` tab of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:90 +msgid "This is *not* a requirement." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:93 msgid "Invoice milestones" msgstr "" -#: ../../content/applications/sales/sales/invoicing/milestone.rst:27 -msgid "From the sales order, you can manually edit the quantity delivered as you complete a milestone." +#: ../../content/applications/sales/sales/invoicing/milestone.rst:96 +msgid "The following flow features a trio of milestone products that have :guilabel:`Service` set as their :guilabel:`Product Type`, and :guilabel:`Task` set on their :guilabel:`Create on Order` field." msgstr "" -#: ../../content/applications/sales/sales/invoicing/milestone.rst:33 -msgid "You can then invoice that first milestone." +#: ../../content/applications/sales/sales/invoicing/milestone.rst:0 +msgid "Product with Service \"Product Type\" and \"Task\" in the Create on Order field on form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:104 +msgid "Those tasks are then attached to a pre-existing :guilabel:`Project`, which, in this case, is titled, :guilabel:`Rebranding Projects`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:107 +msgid "To invoice milestones, create a sales order with the milestone product(s). To do that, go to :menuselection:`Sales app --> New`. Doing so reveals a blank quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:110 +msgid "From this quotation form, add a :guilabel:`Customer`. Then, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Next, add the milestone product(s) to the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:113 +msgid "Once the corresponding milestone product(s) have been added, click :guilabel:`Confirm` to confirm the order, which turns the quotation into a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:116 +msgid "When the order is confirmed, new smart buttons appear at the top of the sales order based on what was selected in the :guilabel:`Create on Order` field on the product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:119 +msgid "From the sales order, click the :guilabel:`Milestones` smart button. Doing so reveals a blank :guilabel:`Milestones` page. Click :guilabel:`New` to add milestones." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "Adding milestones to a sales order with milestone products." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:126 +msgid "Enter a :guilabel:`Name` for the milestone. Next, apply it to the corresponding :guilabel:`Sales Order Item`. Lastly, assign a :guilabel:`Deadline` to the milestone, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:129 +msgid "Repeat that process for all milestone sales order items." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:131 +msgid "Then, return to the sales order, via the breadcrumbs. From the sales order, click the :guilabel:`Tasks` smart button. Doing so reveals a :guilabel:`Tasks` page with a task for each sales order item with that option designated in the :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "Sample tasks page accessed via the smart button from a sales order with milestone products." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:139 +msgid "To manually assign a configured milestone to a task, click the desired task, which reveals the task form. On the task form, select the appropriate milestone to which this task should be connected, in the :guilabel:`Milestone` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The milestone field on the task form when dealing with milestone products in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:147 +msgid "Repeat this process for all milestone tasks." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:149 +msgid "With those tasks properly configured, employees log in their progress as they work on the task, in addition to adding any notes related to the task." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:152 +msgid "Then, when that task is complete, that means that milestone has been reached. At that point, it is time to invoice that milestone." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:155 +msgid "To invoice a milestone, first return to the sales order ā€” either via the breadcrumb links, or by navigating to :menuselection:`Sales app --> Orders --> Orders` and picking the appropriate sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:159 +msgid "Back on the sales order form, click the :guilabel:`Milestones` smart button, and check the box in the :guilabel:`Reached` column for that particular task." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "What it looks like to mark a milestone as reached via the milestone smart button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:166 +msgid "Next, return to the sales order ā€” either by clicking :guilabel:`View Sales Order` on the :guilabel:`Milestones` page, or via the breadcrumb links." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:169 +msgid "Back on the sales order, the line item for the milestone that's been reached has its :guilabel:`Delivered` column filled. That's because the milestone has been reached, and therefore delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "A milestone product that's been reached marked as delivered on the sales order in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:177 +msgid "Click :guilabel:`Create Invoice` in the upper-left corner. Doing so reveals a :guilabel:`Create invoices` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The create invoices pop-up window that appears when create invoice button is clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:184 +msgid "On the :guilabel:`Create invoices` pop-up window, leave the :guilabel:`Create Invoice` option on the default :guilabel:`Regular Invoice` selection, and click the :guilabel:`Create Draft Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:188 +msgid "Upon clicking :guilabel:`Create Draft Invoice`, Odoo reveals the :guilabel:`Customer Invoice Draft`, *only* showing that reached milestone in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "A customer invoice draft showing only the milestone product that's been reached." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:195 +msgid "From this invoice page, click the :guilabel:`Confirm` button to confirm the invoice. Then, when the customer has paid for this milestone, click :guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:198 +msgid "When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment` pop-up window appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The Register Payment pop-up window that appears when Register Payment is clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:204 +msgid "On this pop-up window, confirm the accuracy of the auto-populated fields, then click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:207 +msgid "When clicked, the pop-up window disappears, and Odoo returns to the invoice for that milestone, which now has a green :guilabel:`In Payment` banner in the upper-right corner. This banner signifies the invoice has been paid." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "An invoice with a milestone product that has been paid with an In Payment banner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:215 +msgid "Then, return to the sales order, via the breadcrumb links. Back on the sales order, in the :guilabel:`Order Lines` tab, the reached milestone that's been invoiced and paid for, now has its :guilabel:`Invoiced` column filled." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The Invoiced column of a milestone product that's been paid for is filled." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:223 +msgid "There is also a new :guilabel:`Invoices` smart button at the top of the sales order. Clicking that reveals all the invoices that are connected to this sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 +msgid "The invoices smart button that appears at the top of a sales order with milestones." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:230 +msgid "Simply repeat the above process for each milestone as it is worked on, and subsequently, completed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:232 +msgid "Continue that process until the entire project has been completed, each milestone has been invoiced, and the entire order has been paid for in full." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:237 +msgid ":doc:`proforma`" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:3 @@ -4828,26 +5425,26 @@ msgid "A *pro-forma invoice* is an abridged or estimated invoice sent in advance msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:9 -msgid "Pro-forma invoices are commonly used as preliminary invoices with a quotation. They are also used for customs purposes during importation. They differ from a normal invoice in that they are not a demand (or request) for payment." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/proforma.rst:14 -msgid "Activate the feature" +msgid "Pro-forma invoices are commonly used as preliminary invoices with a quotation. They are also used during importation for customs purposes. They differ from a normal invoice, in that they are *not* a demand (or request) for payment." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:16 -msgid "In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature **must** be activated. To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Quotations & Orders` section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, click :guilabel:`Save` to save all changes." +msgid "In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature **must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:18 +msgid "To enable this feature, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Quotations \\& Orders` section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, click :guilabel:`Save` to save all changes." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:-1 msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:26 -msgid "Send a pro-forma invoice" +#: ../../content/applications/sales/sales/invoicing/proforma.rst:27 +msgid "Send pro-forma invoice" msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:28 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:29 msgid "With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send a pro-forma invoice is now available on any quotation or sales order, via the :guilabel:`Send Pro-Forma Invoice` button." msgstr "" @@ -4855,11 +5452,31 @@ msgstr "" msgid "The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:35 -msgid "When the :guilabel:`Send Pro-Forma Invoice` button is clicked, an email pop-up appears. The :guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation. Then, if needed, modify the :guilabel:`Subject` field and the body of the email. The pro-forma invoice is automatically added as an attachment to the email." +#: ../../content/applications/sales/sales/invoicing/proforma.rst:37 +msgid "Pro-forma invoices can **not** be sent for a sales order or quotation if an invoice for a down payment has already been sent, or for a recurring subscription." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:40 +msgid "In either case, the :guilabel:`Send Pro-Froma Invoice` button does **not** appear." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:42 +msgid "However, pro-forma invoices **can** be sent for services, event registrations, courses, and/or new subscriptions. Pro-forma invoices are not limited to physical, consumable, or storable goods." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:45 +msgid "When the :guilabel:`Send Pro-Forma Invoice` button is clicked, a pop-up window appears, from which an email can be sent." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:48 +msgid "In the pop-up window, the :guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation. The :guilabel:`Subject` field and the body of the email can be modified, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:52 +msgid "The pro-forma invoice is automatically added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:54 msgid "When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with the attached pro-forma invoice, to the customer." msgstr "" @@ -4867,7 +5484,7 @@ msgstr "" msgid "The email pop-up window that appears with pro-forma invoice attached in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:48 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:62 msgid "To preview what the pro-forma invoice looks like, click on the PDF at the bottom of the email pop-up window *before* clicking :guilabel:`Send`. When clicked, the pro-forma invoice is downloaded instantly. Open that PDF to view (and review) the pro-forma invoice." msgstr "" @@ -4876,87 +5493,392 @@ msgid "Sample pro-forma invoice PDF from Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:3 -msgid "Invoice based on time and materials" +msgid "Invoicing based on time and materials" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:5 -msgid "Time and Materials is generally used in projects in which it is not possible to accurately estimate the size of the project, or when it is expected that the project requirements would most likely change." +msgid "Invoicing based on time and/or materials is typically used when accurately estimating the size of a project isn't possible, or when the requirements of a project may change." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:9 -msgid "This is opposed to a fixed-price contract in which the owner agrees to pay the contractor a lump sum for the fulfillment of the contract no matter what the contractors pay their employees, sub-contractors, and suppliers." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:8 +msgid "This is different from a fixed-price contract, when a customer agrees to pay a specified total for the fulfillment of the contract---no matter what needs to be paid to the employees, sub-contractors, vendors, suppliers, and so on." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:14 -msgid "For this documentation I will use the example of a consultant, you will need to invoice their time, their various expenses (transport, lodging, ...) and purchases." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:12 +msgid "The Odoo *Sales* app can invoice for time and various other expenses (e.g. transport, lodging), as well as purchases needed to fulfill an order." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:19 -msgid "Invoice time configuration" +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:16 +msgid "App and settings configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:18 +msgid "First, in order to accurately keep track of the progress of a project, the Odoo *Project* and *Accounting* apps **must** be installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:21 -msgid "To keep track of progress in the project, you will need the *Project* app. Go to :menuselection:`Apps --> Project` to install it." +msgid "To install the *Project* app, navigate to :menuselection:`Odoo main dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the :guilabel:`Project` app block, and click :guilabel:`Activate`. The page automatically refreshes and returns to the main Odoo dashboard, where the *Project* app is now available to access." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:24 -msgid "In *Project* you will use timesheets, to do so go to :menuselection:`Project --> Configuration --> Settings` and activate the *Timesheets* feature." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:26 +msgid "Repeat the same process to install the *Accounting* application." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:32 -msgid "Invoice your time spent" +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:28 +msgid "After installation, click the :guilabel:`Accounting` app icon from the main Odoo dashboard, and navigate to :menuselection:`Configuration --> Settings`. On the :guilabel:`Settings` page, scroll down to the :guilabel:`Analytics` section, and ensure the box next to :guilabel:`Analytic Accounting` is checked." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:34 -msgid "From a product page set as a service, you will find two options under the invoicing tab, select both *Timesheets on tasks* and *Create a task in a new project*." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:41 -msgid "You could also add the task to an existing project." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "How it looks to activate the Analytic Accounting setting in Odoo Accounting Setting page." msgstr "" +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:37 #: ../../content/applications/sales/sales/invoicing/time_materials.rst:43 -msgid "Once confirming a sales order, you will now see two new buttons, one for the project overview and one for the current task." +msgid "Then, click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:49 -msgid "You will directly be in the task if you click on it, you can also access it from the *Project* app." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:39 +msgid "Then, navigate to :menuselection:`Odoo main dashboard --> Project app --> Configuration --> Settings`. On the :guilabel:`Settings` page, in the :guilabel:`Time Management` section, ensure the box beside the :guilabel:`Timesheets` feature is checked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "What the Timesheets feature looks like on the Odoo Project settings page." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:52 -msgid "Under timesheets, you can assign who works on it. You can or they can add how many hours they worked on the project so far." +msgid "Service product configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:54 +msgid "With the *Timesheets* feature activated in the *Project* app, it is now possible to invoice for time spent on a project, but **only** when the following product configurations have been made." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:58 -msgid "From the sales order, you can then invoice those hours." +msgid "Invoicing for time spent on a project is **only** possible with products that have *Service* set as the *Product Type* on their product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:61 +msgid "To configure a service product, first navigate to :menuselection:`Sales app --> Products --> Products`. On the :guilabel:`Products` page, select the desired service product to be configured, or click :guilabel:`New` to create a new product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:65 +msgid "From the product form, in the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Service`. Then, open the drop-down menu in the :guilabel:`Invoicing Policy` field, and select :guilabel:`Based on Timesheets`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:69 -msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Accounting --> Configuration --> Settings` and activate *Analytic Accounting*." +msgid "Next, from the :guilabel:`Create on Order` drop-down menu, select :guilabel:`Project \\& Task`. That setting indicates that, when a sales order is created with this specific service product, a new project and task is created in the *Project* app." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:90 -msgid "under the invoicing tab, select *Delivered quantities* and either *At cost* or *Sales price* as well depending if you want to invoice the cost of your expense or a previously agreed on sales price." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "The correct settings for Invoicing Policy and Create on Order fields for service product." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:120 -msgid "Invoice purchases" +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:78 +msgid "The option :guilabel:`Task` can be chosen instead from the :guilabel:`Create on Order` drop-down menu. If :guilabel:`Task` is chosen, select an existing project that the task will appear in from :guilabel:`Project` field, which only appears if :guilabel:`Task` is chosen in the :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:84 +msgid "Add time spent to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:86 +msgid "After properly configuring a service product with the correct *Invoicing Policy* and *Create on Order* options, it is possible to add time spent to a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:89 +msgid "To see that in action, navigate to :menuselection:`Sales app --> New` to open a blank quotation form. Then, proceed to add a :guilabel:`Customer`, and in the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select the properly :ref:`configured service product ` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:94 +msgid "Next, click :guilabel:`Confirm` to confirm the order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:96 +msgid "After confirming the sales order, two smart buttons appear at the top of the order form: :guilabel:`Projects` and :guilabel:`Tasks`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "How the Projects and Tasks smart buttons look on a Sales Order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:103 +msgid "If the :guilabel:`Projects` smart button is clicked, it reveals the specific project related to this sales order. If the :guilabel:`Tasks` smart button is clicked, it reveals the specific project task related to this sales order. Both are also accessible in the *Project* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:107 +msgid "In order to add time spent on a sales order, click the :guilabel:`Tasks` smart button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:109 +msgid "On the task form, select the :guilabel:`Timesheets` tab. From the :guilabel:`Timesheets` tab, employees can be assigned to work on the project, and the time they spend working on the task can be added by the employees or by the person who created the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:113 +msgid "To add an employee, and the time spent working on the task, click :guilabel:`Add a line` in the :guilabel:`Timesheets` tab. Then, select the appropriate :guilabel:`Date` and :guilabel:`Employee`. There is also the option to add a brief description of the work done during this time in the :guilabel:`Description` column, but it's not required." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:118 +msgid "Lastly, enter the amount of time worked on the task in the :guilabel:`Hours Spent` column, and click away to complete that line in the :guilabel:`Timesheets` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:122 -msgid "The last thing you might need to add to the sale order is purchases made for it." +msgid "The time entered in the :guilabel:`Hours Spent` column is immediately reflected in the :guilabel:`Allocated Time` field (located near the top of the task form) as a percentage, which reflects how much of the total allocated work hours have been done so far." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:125 -msgid "You will need the *Purchase Analytics* feature, to activate it, go to :menuselection:`Invoicing --> Configuration --> Settings` and select *Purchase Analytics*." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:126 +msgid "That same information is found as numerical hours in the :guilabel:`Hours Spent` and :guilabel:`Remaining Hours` fields, located at the bottom of the :guilabel:`Timesheets` tab." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:129 -msgid "While making the purchase order don't forget to add the right analytic account." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "How the Timesheets tab appears on a task form in Odoo Sales and Odoo Project." msgstr "" -#: ../../content/applications/sales/sales/invoicing/time_materials.rst:135 -msgid "Once the PO is confirmed and received, you can create the vendor bill, this will automatically add it to the SO where you can invoice it." +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:133 +msgid "Repeat this process for however many employees and hours have been worked on the project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:136 +msgid "Invoice time spent" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:138 +msgid "Once all the necessary employees and time spent have been added to the project task, return to the sales order to invoice the customer for those hours. To do that, either click the :guilabel:`Sales Order` smart button at the top of the task form, or return to the sales order via the breadcrumb links, located in the upper-left of the screen." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:143 +msgid "Back on the sales order form, the time that was added to the task is reflected in the :guilabel:`Order Lines` tab (in the :guilabel:`Delivered` column) and in the new :guilabel:`Recorded Hours` smart button at the top of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:147 +msgid "To invoice the customer for time spent on the project, click :guilabel:`Create Invoice`, and select :guilabel:`Regular invoice` from the :guilabel:`Create invoices` pop-up window. Then, click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:151 +msgid "Doing so reveals a :guilabel:`Customer Invoice Draft`, clearly showing all the work that's been done in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:155 +msgid "Pay attention to the :guilabel:`Analytic Distribution` column in the :guilabel:`Customer Invoice`, as that information is necessary to ensure other time/material invoicing tasks are completed properly and accurately." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "Invoice draft showing time spent on sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:163 +msgid "Click :guilabel:`Confirm` to confirm the invoice and continue with the invoicing process." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:169 +msgid "Expenses configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:171 +msgid "In order to track and invoice expenses related to a sales order, the Odoo *Expenses* app **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:174 +msgid "To install the *Expenses* app, navigate to :menuselection:`Odoo main dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the :guilabel:`Expenses` app block, and click :guilabel:`Activate`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:178 +msgid "The page automatically refreshes and returns to the main Odoo dashboard, where the :guilabel:`Expenses` app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:184 +msgid "Add expenses to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:186 +msgid "To add an expense to a sales order, first navigate to the :menuselection:`Expenses` app. Then, from the main *Expenses* dashboard, click :guilabel:`New`, which reveals a blank expense form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:189 +msgid "On the expense form, add a :guilabel:`Description` of the expense (e.g. `Hotel Stay`, `Plane Ticket`). Next, in the :guilabel:`Category` field, select the appropriate option from the drop-down menu (e.g. :guilabel:`Meals`, :guilabel:`Miles`, :guilabel:`Travel \\& Accommodation`)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:194 +msgid "Expense categories can be added and modified by navigating to :menuselection:`Expenses app --> Configuration --> Expense Categories`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:197 +msgid "Then, enter the total amount of the expense in the :guilabel:`Total` field, as well as any :guilabel:`Included Taxes` that may apply. Next, ensure that the correct :guilabel:`Employee` is selected, and designate who paid for the expense in the :guilabel:`Paid By` field: the :guilabel:`Employee (to reimburse)` or the :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:202 +msgid "Next, in the :guilabel:`Customer to Reinvoice` field, select the appropriate sales order from the drop-down menu. Then, select that same sales order information from the :guilabel:`Analytic Distribution` field, as well." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:207 +msgid "The :guilabel:`Analytic Distribution` field will **only** have the corresponding sales order as an option if the sales order contains a service product that is billed based on *Timesheets*, *Milestones*, or *Delivered Quantities*." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "How to properly fill out an expense form that's attached to a sales order in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:215 +msgid "If there are any receipts that should be uploaded and attached to the expense, click the :guilabel:`Attach Receipt` button, and upload the necessary documents to the expense. This is **not** required, but it may affect whether or not an expense is approved." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:219 +msgid "When all the information has been entered, click :guilabel:`Create Report` to create an expense report detailing all the expense information that was just entered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "How an Expense Report Summary looks in Odoo Expenses." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:226 +msgid "Then, there's the option to :guilabel:`Submit to Manager` for approval. Once approved, the :guilabel:`Report in Next Payslip` appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:229 +msgid "To showcase a complete flow in this example, select :guilabel:`Submit to Manager`. Then, the manager would click :guilabel:`Approve` to approve this expense, and click :guilabel:`Post Journal Entries` to post this expense to the accounting journal." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:234 +msgid "Invoice expenses" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:236 +msgid "To invoice a customer for an :ref:`expense on a sales order `, navigate to the related sales order, either from the :menuselection:`Sales` app or from the expense report in the :menuselection:`Expenses` app. From the expense report, click the :guilabel:`Sales Orders` smart button at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:241 +msgid "If the expense report was linked to the sales order, the newly-configured expense now has its own line in the :guilabel:`Order Lines` tab, and can be invoiced to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "An expense appearing on Order Lines tab of a Sales Order in Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:248 +msgid "To invoice the customer for the expense on the sales order, click :guilabel:`Create Invoice`, select :guilabel:`Regular Invoice` from the :guilabel:`Create invoices` pop-up window, then click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:252 +msgid "Doing so reveals a :guilabel:`Customer Invoice Draft` for the expense. Then, the invoicing process can be completed as usual." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "Sample customer invoice for an expense generated from a sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:260 +msgid "Purchase configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:262 +msgid "In order to invoice a customer for purchases made on a sales order, the *Purchase* application **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:265 +msgid "To install the *Purchase* application, navigate to :menuselection:`Odoo main dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the :guilabel:`Purchase` app block, and click :guilabel:`Activate`. The page automatically refreshes and returns to the main Odoo dashboard, where the :guilabel:`Purchase` app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:273 +msgid "Add purchase to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:275 +msgid "To add a purchase to a sales order, a purchase order must first be created. To create a purchase order, navigate to :menuselection:`Purchase app --> New` to reveal a blank purchase order form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:278 +msgid "First, add a :guilabel:`Vendor` to the purchase order. Then, under the :guilabel:`Products` tab, click the :guilabel:`extra column options` drop-down menu, represented by two horizontal lines with dots on them, located to the far-right of the column headers. From that drop-down menu, select :guilabel:`Analytic Distribution`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "How to add analytic distribution column on purchase order form in Odoo Purchase." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:287 +msgid "After adding the :guilabel:`Analytic Distribution` column to the headers on the :guilabel:`Products` tab of the purchase order form, proceed to add the product(s) to the purchase order. To do that, click :guilabel:`Add a product`, and select the desired product from the drop-down menu. Repeat for all the products to add." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:293 +msgid "In order for a purchase to be properly invoiced on a sales order, the product on the purchase order **must** be marked as :guilabel:`Can be Expensed`, have an :guilabel:`Invoicing Policy` set to :guilabel:`Delivered quantities`, and have the :guilabel:`At cost` option selected in the :guilabel:`Re-Invoice Expenses` field on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "Product settings for a purchase order to be invoiced on a sales order in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:302 +msgid "Then, select the appropriate :guilabel:`Analytic Distribution` associated with the sales order to which this purchase order is related. To do that, click the empty :guilabel:`Analytic Distribution` field to reveal an :guilabel:`Analytic` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:306 +msgid "Then, from the :guilabel:`Departments` drop-down menu, select the analytic distribution associated with the desired sales order to be invoiced for the purchase." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "How to select the Analytic Distribution department from a purchase order in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:313 +msgid "Once all the information is entered in the :guilabel:`Products` tab of the purchase order, confirm the order by clicking :guilabel:`Confirm Order`. Then, click :guilabel:`Receive Products` when the products have been received. This creates a receipt form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:318 +msgid "If any serial/lot numbers must be entered before validating the receipt of products, then on the receipt form, click the :guilabel:`details` icon represented by four horizontal lines located to the far-right of the product line." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:322 +msgid "This reveals a :guilabel:`Detailed Operations` tab, in which the necessary :guilabel:`Lot/Serial Number(s)` and :guilabel:`Done` quantity can be added. When ready, click :guilabel:`Confirm` to confirm the data." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:326 +msgid "Then, click :guilabel:`Validate` to validate the purchase order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:328 +msgid "Next, return to the purchase order, via the breadcrumb links at the top of the page, and click :guilabel:`Create Bill` to create a vendor bill that can be invoiced to the customer on the attached sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "Vendor bill draft for a purchase order to be invoiced to a customer in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:337 +msgid "Make sure to enter a :guilabel:`Bill Date` on the :guilabel:`Vendor Bill Draft` before confirming. If a :guilabel:`Bill Date` is *not* entered, an error window appears, requesting that information to be entered before confirmation can occur." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:341 +msgid "Then, click :guilabel:`Confirm` to confirm the vendor bill, which is then automatically added to the sales order, where it can be invoiced directly to the customer attached to it." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:345 +msgid "Invoice purchase" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:347 +msgid "To invoice a customer for a purchase on a sales order, first :ref:`add the purchase to the sales order `, then navigate to the desired sales order in the :menuselection:`Sales` app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:351 +msgid "On the sales order that was attached to the purchase order, the purchased product now has its own product line under the :guilabel:`Order Lines` tab, and it is ready to be invoiced." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "Purchase order product on sales order to be invoiced to customer via Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:358 +msgid "To invoice the customer for the purchase, simply click :guilabel:`Create Invoice`, select :guilabel:`Regular Invoice` from the :guilabel:`Create invoices` pop-up window, then click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:362 +msgid "Doing so reveals a :guilabel:`Customer Invoice Draft` with the newly-added purchase order product in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:-1 +msgid "Customer invoice draft with purchase product attached to sales order in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:369 +msgid "To complete the invoicing process, click :guilabel:`Confirm` to confirm the invoice, and then click :guilabel:`Register Payment` in the :guilabel:`Register Payment` pop-up form." msgstr "" #: ../../content/applications/sales/sales/products_prices.rst:5 @@ -5429,202 +6351,759 @@ msgid "Manage your pricing" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:3 -msgid "How to sell in foreign currencies" +msgid "Foreign currencies" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:5 -msgid "Pricelists can also be used to manage prices in foreign currencies." +msgid "With Odoo, pricelists can be used to manage prices in a number of foreign currencies. Specifically, Odoo has the ability to work with 167 total currencies." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:7 -msgid "Check *Allow multi currencies* in :menuselection:`Invoicing/Accounting --> Settings`. As admin, you need *Adviser* access rights on Invoicing/Accounting apps." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:10 -msgid "Create one pricelist per currency. A new *Currency* field shows up in pricelist setup form." +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:9 +msgid "In order to use multiple currencies in Odoo *Sales*, the *Accounting* application **must** be installed." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 -msgid "To activate a new currency, go to :menuselection:`Accounting --> Configuration --> Currencies`, select it in the list and press *Activate* in the top-right corner. Now it will show up in currencies drop-down lists." +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:17 +msgid "Settings" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:17 -msgid "Prices in foreign currencies can be defined in two fashions." +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:15 +msgid "Once the *Accounting* app has been installed, foreign currencies can be added to the database. Navigate to :menuselection:`Accounting app --> Configuration --> Settings`, scroll to the :guilabel:`Currencies` section, and locate the :guilabel:`Main Currency` setting." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:20 -msgid "Automatic conversion from public price" +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 +msgid "How the main currency feature appears on settings page in Odoo Accounting." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:22 -msgid "The public price is in your company's main currency (see :menuselection:`Accounting --> Settings`) and is set in product detail form." +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:23 +msgid "Odoo automatically sets the main currency as the currency of the country the company is based in." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:28 -msgid "The conversion rates can be found in :menuselection:`Accounting --> Configuration --> Currencies`. They can be updated from Yahoo or the European Central Bank at your convenience: manually, daily, weekly, etc. See :menuselection:`Accounting --> Settings`." +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:25 +msgid "To change the main currency of the company, select the drop-down menu in the :guilabel:`Currency` field, select the desired currency, and be sure to :guilabel:`Save` the changes." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:40 -msgid "Set your own prices" +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:29 +msgid "To ensure currency rates are updated automatically, enable the *automatic currency rates* feature on the *Accounting* settings page (:menuselection:`Accounting app --> Configuration --> Settings --> Currencies section`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:37 +msgid "Click the checkbox beside the :guilabel:`Automatic Currency Rates` feature, choose a designated bank to get the currency rates from in the :guilabel:`Service` field drop-down menu, and select an :guilabel:`Interval` of time for the updates to take place. Then determine when the date of the :guilabel:`Next Run` should be." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:42 -msgid "This is advised if you don't want your pricing to change along with currency rates." +msgid "To instantly update the currency rates, click the :guilabel:`šŸ” (circular arrows)` icon, located to the right of the :guilabel:`Next Run` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:49 -msgid ":doc:`pricing`" +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:45 +msgid "When all configurations are complete, be sure to :guilabel:`Save` all changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:48 +msgid "All payment methods **must** be in the same currency as the sales journal, or the company currency, if the company currency is not set. If it is not the same, a :guilabel:`Validation Error` message appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:53 +msgid "View, edit, and add currencies" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:55 +msgid "To view, edit, and add currencies to the database, making them available on pricelists and on the :guilabel:`Main Currency` drop-down menu, click the :guilabel:`Currencies` link, located beneath the :guilabel:`Currency` field on the :menuselection:`Accounting app --> Settings` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:59 +msgid "When the :guilabel:`Currencies` link is clicked, a separate :guilabel:`Currencies` page is revealed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 +msgid "How the main currencies page appears in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:65 +msgid "On this page, Odoo provides a master list of 167 global currencies. Each row shows the corresponding :guilabel:`Currency`, :guilabel:`Symbol`, :guilabel:`Name`, date of the :guilabel:`Last Update`, and :guilabel:`Current Rate` (compared to the default currency of the country in which the company is based)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:70 +msgid "To the far right, there are two columns, which can be toggled on or off:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:72 +msgid ":guilabel:`Use on eBay`: this currency can be used with the connected eBay account (if applicable)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:74 +msgid ":guilabel:`Active`: this currency is activated, which means it can be added to a pricelist, or used as the main currency of the company, if desired (via :menuselection:`Accounting app --> Configuration --> Settings --> Currencies section`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:79 +msgid "By default, all the :guilabel:`Active` currency options are at the top of the list." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:82 +msgid "It is recommended that *at least* one pricelist is created per :guilabel:`Active` currency. See :doc:`./pricing` to learn more about pricelist configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:85 +msgid "To toggle options on/off, click the toggle switch in the row for the corresponding column. When *on* the color of the switch is green. When *off*, the color of the switch is grey." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:89 +msgid "Currency detail form" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:91 +msgid "To edit any currency on the :guilabel:`Currencies` page, click the desired currency to reveal the detail form for that specific currency, and proceed to make any necessary changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 +msgid "How a currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:98 +msgid "On the currency detail form, the relevant currency code appears in the :guilabel:`Currency` field. Beneath that, the name for the currency is in the :guilabel:`Name` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:101 +msgid "Then, toggle the currency's availability with the :guilabel:`Active` toggle: *on* is indicated with a green switch, and *off* is indicated with a grey switch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:104 +msgid "On the right of the currency detail form, the appropriate :guilabel:`Currency Unit` (e.g. `Dollars`) and :guilabel:`Currency Subunit` (e.g. `Cents`) can be found." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:107 +msgid "If the currency is meant to be used for eBay purposes, toggle the :guilabel:`Use on eBay` option to the desired activation." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:110 +msgid "Next, under the :guilabel:`Rates` tab, the various conversion rates can be viewed, added, or deleted. Each row shows the :guilabel:`Date` of that specific rate, the :guilabel:`Company` to which it is connected, followed by the :guilabel:`Unit per...` and :guilabel:`...per Unit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:115 +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:166 +msgid "The *...* in each of the last two columns represents the main currency set for the company. For example, if the main currency is set to `USD`, the columns are titled :guilabel:`Unit per USD` and :guilabel:`USD per Unit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:119 +msgid "To add a new rate, click :guilabel:`Add a line` in the :guilabel:`Rates` tab, and proceed to fill in the necessary information in the aforementioned columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:123 +msgid "Main currency detail form" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:125 +msgid "If the selected currency is the main currency of the company, a blue banner appears at the top of the currency detail form with the message: :guilabel:`This is your company's currency.`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 +msgid "How a main currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:132 +msgid "All the fields are the same as a typical currency detail form, but there will **not** be a :guilabel:`Rates` tab because all other currency rates are based off the main currency of the company." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:137 +msgid "Create new currency" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:139 +msgid "If a desired currency isn't on the :guilabel:`Currencies` page, click the :guilabel:`New` button to open a blank currency template form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:143 +msgid "The same :guilabel:`New` button is located in the upper-right corner of any currency detail form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 +msgid "How a blank currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:149 +msgid "On the blank currency detail form, proceed to enter the desired currency code in the :guilabel:`Currency` field. Beneath that, enter the name for the currency in the :guilabel:`Name` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:153 +msgid "Then, toggle the currency's availability with the :guilabel:`Active` toggle switch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:155 +msgid "On the right of the currency detail form, enter the appropriate :guilabel:`Currency Unit` (e.g. `Dollars`) and appropriate :guilabel:`Currency Subunit` (e.g. `Cents`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:158 +msgid "If the currency is meant to be used for eBay purposes, toggle the :guilabel:`Use on eBay` to the desired activation." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:161 +msgid "Next, under the :guilabel:`Rates` tab, add a new rate by clicking :guilabel:`Add a line`. Then, proceed to confirm and adjust the :guilabel:`Date`, :guilabel:`Company`, :guilabel:`Unit per...`, and :guilabel:`...per Unit` fields to ensure all the auto-populated information is accurate." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:171 +msgid "Currency-specific pricelists" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:173 +msgid "It is recommended that *at least* one pricelist is created per active currency in the database. To create (or assign) a pricelist to a specific currency, start by navigating to :menuselection:`Sales app --> Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:177 +msgid "From the :guilabel:`Pricelists` page, either select an existing pricelist to edit, or click :guilabel:`New` to create a new pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:180 +msgid "On the pricelist detail form, for either a new or existing pricelist, adjust the :guilabel:`Currency` field as desired." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:184 +msgid ":doc:`./pricing` to learn more about pricelist configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:187 +msgid "Auto-conversion from public price" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:189 +msgid "It should be noted that the public price seen on products is directly related to the main currency the company has set, which is configured by navigating to :menuselection:`Accounting app --> Configuration --> Settings --> Currencies section --> Main Currency --> Currency drop-down menu`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:193 +msgid "The sales price automatically updates if the pricelist is changed to a different pricelist that has a different currency than the company's main currency. The change in price is directly related to the updated conversion rate for that currency." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:198 +msgid "Set product prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:200 +msgid "In order to have product prices set in place to avoid any changes in currency rates, start by navigating to :menuselection:`Sales app --> Products --> Products`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:203 +msgid "From the :guilabel:`Products` page, select the desired product to modify. Or, create a new product by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:206 +msgid "Then, on the product detail form, click the :guilabel:`Extra Prices` smart button, located in the upper-left corner. Doing so reveals a separate :guilabel:`Price Rules` page, specific to that particular product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 +msgid "How to set product prices based on foreign currency pricelists in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:214 +msgid "Click :guilabel:`New`, and select the desired pricelist from the drop-down menu in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:217 +msgid "The :guilabel:`Applied On` field is auto-populated with the product, so proceed to enter in the desired figures in the :guilabel:`Min. Quantity` and :guilabel:`Price` fields." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:221 +msgid "The figure in the :guilabel:`Min. Quantity` field means the :guilabel:`Price` being set will **only** trigger if at least that amount of product is purchased." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:224 +msgid "If necessary, configure a :guilabel:`Start Date` and :guilabel:`End Date` for the set prices. Leaving those columns blank ensures the set price will remain valid, regardless of the date of sale." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:227 +msgid "If working in a multi-company environment, designate to which company this price rule should be applied in the :guilabel:`Company` field. Leaving that field blank ensures the price rule applies to all companies in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:231 +msgid "With those configurations complete, regardless of any changes/updates in conversion, whenever those designated pricelists are applied to a customer trying to purchase this specific product, these pre-determined set prices appear." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:236 +msgid ":doc:`./pricing`" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:3 -msgid "How to adapt your prices to your customers and apply discounts" +msgid "Pricelists, discounts, and formulas" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:5 -msgid "Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business. A pricelist is a list of prices or price rules that Odoo searches to determine the suggested price. You can set several criteria to use a specific price: periods, min. sold quantity (meet a minimum order quantity and get a price break), etc." +msgid "Odoo *Sales* has a useful pricelist feature that can be tailored to fit any unique pricing strategy." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:10 -msgid "As pricelists only suggest prices, they can be overridden by vendors completing sales orders. Choose your pricing strategy from :menuselection:`Sales --> Settings`." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:7 +msgid "A *pricelist* is a list of prices (or price rules) that Odoo uses to determine the appropriate price for a customer. These pricelists can be set with specific criteria (such as time periods, minimum quantity sold, and more) in order to apply certain prices or discounts." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:18 -msgid "*A single sale price per product:* doesn't let you adapt prices, it use default product price ;" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:11 +msgid "Pricelists suggest certain prices, but they can always be overridden on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:14 +msgid "Pricing strategy options" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:16 +msgid "To choose a pricing strategy, first navigate to :menuselection:`Sales app --> Configuration --> Settings`. In the :guilabel:`Pricing` section, click the checkbox next to the :guilabel:`Pricelists` feature." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20 -msgid "*Different prices per customer segment:* you will set several prices per products ;" +msgid "Doing so reveals two additional options beneath it: :guilabel:`Multiple prices per product` and :guilabel:`Advanced price rules (discounts, formulas)`. A link labeled :guilabel:`Pricelists` also appears, which leads to a separate pricelists page, wherein pricelists can be created and/or modified." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:21 -msgid "*Advanced pricing based on formula:* will let you apply discounts, margins and roundings." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:25 +msgid ":guilabel:`Multiple prices per product`: provides the option to set several different prices per product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:24 -msgid "Several prices per product" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:27 +msgid ":guilabel:`Advanced price rules (discounts, formulas)`: provides the option to create detailed price rules and apply discounts, margins, and roundings." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:26 -msgid "To apply several prices per product, select *Different prices per customer segment* in :menuselection:`Sales --> Settings`. Then open the *Sales* tab in the product detail form. You can settle following strategies." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the pricelist feature setting looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:31 -msgid "Prices per customer segment" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:34 +msgid "After clicking the checkbox beside the :guilabel:`Pricelists` feature, select one of those two options, then click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:33 -msgid "Create pricelists for your customer segments: e.g. registered, premium, etc." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:40 +msgid "After activating and saving the :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 -msgid "The default pricelist applied to any new customer is *Public Pricelist*. To segment your customers, open the customer detail form and change the *Sale Pricelist* in the *Sales & Purchases* tab." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:328 +msgid "Either option reveals the :guilabel:`Pricelists` page, in which pricelists can be created and/or modified at any time." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:46 -msgid "Temporary prices" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the pricelists page looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:48 -msgid "Apply deals for bank holidays, etc. Enter start and end dates dates." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:53 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:267 +msgid "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo *Sales* and *eCommerce*." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:54 -msgid "Make sure you have default prices set in the pricelist outside of the deals period. Otherwise you might have issues once the period over." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:55 +msgid "From the :guilabel:`Pricelists` page, either select the desired pricelist to edit, or click :guilabel:`New` to create a new pricelist, which reveals a blank pricelist form that can be configured in a number of different ways." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:58 -msgid "Prices per minimum quantity" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the pricelist detail form looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:64 -msgid "The prices order does not matter. The system is smart and applies first prices that match the order date and/or the minimal quantities." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:63 +msgid "When creating a new pricelist, start by adding a name for the pricelist at the top of the form, in the blank field. Next, select which :guilabel:`Currency` should be used." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:68 -msgid "Discounts, margins, roundings" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:66 +msgid "Then, if working in a multi-company environment, select which company this pricelist should apply to in the :guilabel:`Company` field. If this field is left blank, the pricelist is automatically applied to all companies in the database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:70 -msgid "*Advanced pricing based on formula* allows to set price change rules. Changes can be relative to the product list/catalog price, the product cost price, or to another pricelist. Changes are calculated via discounts or surcharges and can be forced to fit within floor (minimum margin) and ceilings (maximum margins). Prices can be rounded to the nearest cent/dollar or multiple of either (nearest 5 cents, nearest 10 dollars)." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:71 +msgid "Price rules tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:73 +msgid "The :guilabel:`Price Rules` tab functionality on a pricelist form varies depending on the :guilabel:`Pricelists` setting chosen: either :guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules (discounts, formulas)`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:77 -msgid "Once installed go to :menuselection:`Sales --> Configuration --> Pricelists` (or :menuselection:`Website Admin --> Catalog --> Pricelists` if you use e-Commerce)." +msgid "However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` tab are always the same, regardless of the chosen :guilabel:`Pricelists` setting." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:85 -msgid "Each pricelist item can be associated to either all products, to a product internal category (set of products) or to a specific product. Like in second option, you can set dates and minimum quantities." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:81 +msgid "Price rules tab (multiple prices per product)" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:92 -msgid "Once again the system is smart. If a rule is set for a particular item and another one for its category, Odoo will take the rule of the item." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:83 +msgid "With the :guilabel:`Multiple prices per product` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to add specific products, with a specific price, to a pricelist." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:94 -msgid "Make sure at least one pricelist item covers all your products." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:87 +msgid "To add a specific product and price to a pricelist form, click the :guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the :guilabel:`Products` column. Then, select the desired product for which a specific price should be applied." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:96 -msgid "There are 3 modes of computation: fix price, discount & formula." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:91 +msgid "Next, if necessary, select a product variant under the :guilabel:`Variants` column (e.g. a specific product size, color, etc.). If no variants are selected, then this price will apply to all variants of the product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:101 -msgid "Here are different price settings made possible thanks to formulas." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:95 +msgid "If a minimum amount of the product must be purchased in order to apply the specific price, enter the amount under the :guilabel:`Min. Quantity` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:104 -msgid "Discounts with roundings" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:98 +msgid "To configure the price of the product for this specific pricelist, enter the desired amount under the :guilabel:`Price` column. Then, there is the option to add a :guilabel:`Start Date` and :guilabel:`End Date` to the configured product price, if desired." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:106 -msgid "e.g. 20% discounts with prices rounded up to 9.99." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:102 +msgid "To add another product line, click :guilabel:`Add a line` again, and repeat the process. There is no limit to how many products can be added in the :guilabel:`Price Rules` tab of a pricelist form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:112 -msgid "Costs with markups (retail)" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:105 +msgid "For more information, check out the following section: :ref:`Multiple prices per product `." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:114 -msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:109 +msgid "Price rules tab (advanced price rules)" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120 -msgid "Prices per country" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111 +msgid "With the :guilabel:`Advanced price rules (discounts, formulas)` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to configure detailed price rules based on formulas." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:122 -msgid "Pricelists can be set by countries group. Any new customer recorded in Odoo gets a default pricelist, i.e. the first one in the list matching the country. In case no country is set for the customer, Odoo takes the first pricelist without any country group." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:115 +msgid "Check out the :ref:`Advanced price rules (discounts, formulas) ` section for detailed steps on how to add advanced price rules to a pricelist." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:126 -msgid "The default pricelist can be replaced when creating a sales order." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119 +msgid "Time-based rules tab" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128 -msgid "You can change the pricelists sequence by drag & drop in list view." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:121 +msgid "Time-based rules are used specifically with :doc:`subscription products `. Be sure to check out the Odoo *Subscriptions* :doc:`documentation `." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:131 -msgid "Compute and show discount % to customers" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:125 +msgid "Under the :guilabel:`Time-based rules` tab, the same functionality of the :guilabel:`Price Rules` tab is present, with the only difference being that a repeating time period can be applied in the :guilabel:`Period` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:129 +msgid "After a :guilabel:`Product` and potential :guilabel:`Variant` are selected in the :guilabel:`Time-based rules` tab, select the blank field in the :guilabel:`Period` column to reveal a drop-down menu of pre-designated recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133 -msgid "In case of discount, you can show the public price and the computed discount % on printed sales orders and in your eCommerce catalog. To do so:" +msgid "New recurrence periods can also be directly created from this column, by typing in the new name for the :guilabel:`Period` and then selecting :guilabel:`Create` to create the time period, which can be edited later. Or, select :guilabel:`Create and edit...` to reveal a pop-up form, in which the new recurrence period can be directly configured." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:136 -msgid "Check *Allow discounts on sales order lines* in :menuselection:`Sales --> Configuration --> Settings --> Quotations & Sales --> Discounts`." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "Custom time period pop-up form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:138 -msgid "Apply the option in the pricelist setup form." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:142 +msgid "From this :guilabel:`Create Period` pop-up form, add a :guilabel:`Name`, :guilabel:`Duration`, then a :guilabel:`Unit` (e.g. `Days`, `Weeks`, etc.). When finished, click :guilabel:`Save and Close`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145 -msgid ":doc:`currencies`" +msgid "Lastly, add the desired price for this time-based rule in the :guilabel:`Price` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:146 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:148 +msgid ":doc:`/applications/sales/subscriptions`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:151 +msgid "Configuration tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:153 +msgid "Under the :guilabel:`Configuration` tab, there are a few options that can further customize the pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "Configuration tab on pricelist detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:160 +msgid "From here, under the :guilabel:`Availability` section, in the :guilabel:`Country Groups` field, certain country groups can be added to the pricelist. There is no limit to how many country groups can be added in this field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:165 +msgid "If no country is set for a customer, Odoo takes the first pricelist without any country group." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:167 +msgid "Under the :guilabel:`Website` section, there are a few options that can be configured. In the :guilabel:`Website` field, this pricelist can be applied to a specific website, if working in a multi-website environment. If left blank, the pricelist will be applied to all websites in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:172 +msgid "Click the :guilabel:`Selectable` checkbox to have this pricelist as a selectable option for customers to choose as they shop. If the :guilabel:`Selectable` box is left unchecked, customers **cannot** select this pricelist for themselves as they shop." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:176 +msgid "Lastly, there is the option to add an :guilabel:`E-commerce Promotional Code`. To add a code, type in the desired promo code that, when entered during the checkout process, applies the pricelist to the customer, even if the customer does not fall into the previously-specified criteria." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:181 +msgid "Show discount percentage to customers" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:183 +msgid "With Odoo *Sales*, the option to show the public price *and* the computed discount percentage on the product catalog is available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:186 +msgid "To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Pricing` section, click the checkbox next to the :guilabel:`Discounts` feature, and then click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:190 +msgid "After activating the :guilabel:`Discounts` feature, navigate to the pricelists page, either by clicking the :guilabel:`Pricelists` link from the :guilabel:`Settings` page, or by going to :menuselection:`Sales app --> Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:194 +msgid "On the :guilabel:`Pricelists` page, select the desired pricelist to edit. On the pricelist form, click into the :guilabel:`Configuration` tab. In the :guilabel:`Configuration` tab, at the bottom, a :guilabel:`Discounts` section is now available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "What the discount options are on the configuration tab of a pricelist in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:202 +msgid "The options available in this section are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:204 +msgid ":guilabel:`Discount included in the price`: shows the customer only the final price with the discount already included." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:206 +msgid ":guilabel:`Show public price & discount to the customer`: shows the customer the public price *and* the discount they're earning." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:210 +msgid "Customer pricelist application" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:212 +msgid "While the default pricelist applied to any customer is the :guilabel:`Public Pricelist`, Odoo provides the opportunity to directly apply a different pricelist to customers on their contact form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:215 +msgid "To do that, open the desired customer's contact form, either by navigating to :menuselection:`Sales app --> Orders --> Customers` and selecting the customer from the main :guilabel:`Customers` page, or by clicking on the customer's name on a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "Sample customer detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:223 +msgid "On the desired customer's contact form, under the :guilabel:`Sales & Purchase` tab, in the :guilabel:`Sales` section, designate what pricelist should be applied to this specific customer from the drop-down menu in the :guilabel:`Pricelist` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "The pricelist field in a customer detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:236 +msgid "To apply several prices per individual product, select the :guilabel:`Multiple prices per product` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:240 +msgid "Next, apply pricelists to specific products using the product form. Navigate to the :menuselection:`Sales app --> Products --> Products` and select the product for which multiple prices should be applied. Selecting a product from the :guilabel:`Products` page reveals that specific product's product form on a separate page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:245 +msgid "On the product form, click the :guilabel:`Extra Prices` smart button, located at the top of the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the extra prices smart button appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:252 +msgid "Doing so reveals a separate page displaying the :guilabel:`Price Rules` that are specific to that particular product. Here, price rules can be edited or created at any time." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the extra price rules per product page appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:259 +msgid "To create a new price rule for a product from this specific :guilabel:`Price Rules` page, click :guilabel:`New` to add a new, customizable row that has the desired product already populated in the :guilabel:`Applied On` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:263 +msgid "Next, select which :guilabel:`Pricelist` this specific product price rule should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:270 +msgid "To create a new pricelist from this page, type in the desired name of the new pricelist in the :guilabel:`Pricelist` column, then select :guilabel:`Create` from the drop-down menu. All pricelists can be modified at any time, by navigating to :menuselection:`Sales app --> Products --> Pricelists`. Pricelists can also be created on that specific :guilabel:`Pricelists` page, as well." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 +msgid "After the desired pricelist is added to the row, designate a :guilabel:`Min. Quantity` for the price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 +msgid "If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the :guilabel:`Price` column will be applied to orders of 2 or more products. So, in theory, if a single product costs $100, customers can be encouraged to buy more, if the :guilabel:`Price` is set at $85 per product for a :guilabel:`Min. Quantity` of `2` products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 +msgid "Next, enter the desired amount in the :guilabel:`Price` column. Then, if needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the product's price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 +msgid "And lastly, if working in a multi-company environment, select which company this price rule should be applied to in the :guilabel:`Company` field. Leaving this field blank means the price rule applies for all companies in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:292 +msgid "Click away from the row to activate Odoo's auto-save capability, meaning that newly-created price rule is now ready to be used." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:295 +msgid "Proceed to add as many unique price rules per product as desired. There is no limit to how many price rules can be added per product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:298 +msgid "With the price rule(s) in place for a specific product, customers who fall into those corresponding pricelists automatically see those new prices applied. The number of price rules applied to a particular product are also displayed in the :guilabel:`Extra Prices` smart button, located on every product form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 +msgid "When a price rule/pricelist is added to a product via the :guilabel:`Extra Prices` smart button, it is also reflected on the pricelist itself. Similarly, when a price rule for a specific product is added to a pricelist, it is also reflected on the product form via the :guilabel:`Extra Prices` smart button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:314 +msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:318 +msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 +msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:331 +msgid "From the :guilabel:`Pricelists` page, select a desired pricelist to modify, or create a new pricelist by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 +msgid "On the pricelist form, under the :guilabel:`Price Rules` tab, click :guilabel:`Add a line` to add an advanced price rule. Doing so reveals a :guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule is configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 +msgid "Price computation" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:345 +msgid "On this form, first choose one of the three :guilabel:`Computation` options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:347 +msgid ":guilabel:`Fixed Price`: the price computation is based on a fixed price." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:348 +msgid ":guilabel:`Discount`: the price computation is based on a discount." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:349 +msgid ":guilabel:`Formula`: the price computation is based on a formula." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 +msgid "Each :guilabel:`Computation` option reveals its own computation-specific fields on the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 +msgid "If :guilabel:`Fixed Price` is selected, enter the desired price in the :guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, enter the desired discount percentage in the :guilabel:`Discount` field that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 +msgid "If :guilabel:`Formula` is selected, a number of configurable options appear." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "The various formula computation options present in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:364 +msgid "To configure the :guilabel:`Formula` computation option, start by selecting an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the advanced price rule formula will be based on." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:368 +msgid "Next, in the :guilabel:`Discount` field, determine how much of a discount should be applied. It should be noted that a mark-up can be applied by setting a negative discount in this field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:372 +msgid "To formulate a 100% markup (or 2 times the cost of the product), with a $5 minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the :guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is often seen in retail situations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:380 +msgid "Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or subtract) to the amount calculated with the discount. After that, enter a desired figure in the :guilabel:`Rounding Method` field. The rounding method sets the price so that it is a multiple of the value in the field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 +msgid "Rounding is applied *after* the discount and *before* the surcharge." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 +msgid "To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10` and the :guilabel:`Extra Fee` to `-0.01`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:391 +msgid "Lastly, specify the minimum amount of margin over the base price in the :guilabel:`Margins` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:393 +msgid "Once all formula-related configurations are complete, Odoo provides an example of the formula in a blue block to the right of the configurations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 +msgid "To apply 20% discounts, with prices rounded up to 9.99, set the :guilabel:`Based on` field to :guilabel:`Sales Price`, the :guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to `-0.01`, and the :guilabel:`Rounding Method` field to `10`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:408 +msgid "At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the :guilabel:`Conditions` section." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 +msgid "Here, start by selecting one of the options in the :guilabel:`Apply On` field:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:413 +msgid ":guilabel:`All Products`: the advanced pricelist rule will be applied to all products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 +msgid ":guilabel:`Product Category`: the advanced pricelist rule will be applied to a specific category of products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 +msgid ":guilabel:`Product`: the advanced pricelist rule will be applied to a specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 +msgid ":guilabel:`Product Variant`: the advanced pricelist rule will be applied to a specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 +msgid "If any of those options, apart from :guilabel:`All Products`, are selected, a new option-specific field appears, in which the specific :guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product Variant` must be chosen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:424 +msgid "Then, select a minimum quantity to be applied to the advanced pricelist rule in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for the pricelist item validation in the :guilabel:`Validity` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:428 +msgid "Once all configurations are complete, either click :guilabel:`Save & Close` to save the advanced pricelist rule, or click :guilabel:`Save & New` to immediately create another advanced pricelist rule on a fresh form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 +msgid "If a price rule is set for a particular product, and another one for its product category, Odoo takes the rule of the product itself." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 msgid ":doc:`/applications/websites/ecommerce/managing_products/price_management`" msgstr "" @@ -6083,11 +7562,11 @@ msgid "Changes to the product template automatically apply to every variant of t msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:3 -msgid "Process returns and refunds" +msgid "Returns and refunds" msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:5 -msgid "The :guilabel:`Sales` app provides two different ways to process returns based on whether an invoice has been sent or not." +msgid "The Odoo *Sales* app provides two different ways to process returns. The method used depends on whether or not an invoice has been sent." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:9 @@ -6095,67 +7574,131 @@ msgid "Before invoicing" msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:11 -msgid "Returns are completed using *Reverse Transfers* when a customer decides to return a product before an invoice has been sent or validated." +msgid "Returns are completed using *Reverse Transfers* when a customer decides to return a product **before** an invoice has been sent or validated." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:15 -msgid "In order to use Reverse Transfers, the :guilabel:`Inventory` app must also be installed." +msgid "In order to use *Reverse Transfers*, the *Inventory* app **must** be installed." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:17 -msgid "To start a return, open the :guilabel:`Sales` app, navigate to the customer's sales order, and click on the :guilabel:`Delivery` smart button to open the associated delivery order." +msgid "To start a return before invoicing, navigate to the :menuselection:`Sales` app, select the desired sales order, and click on the :guilabel:`Delivery` smart button to open the associated delivery order." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:20 -msgid "On the validated delivery order, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window. By default, the :guilabel:`Quantity` matches the validated quantities from the delivery order. Update the quantities if necessary. Click on the trash icon next to a line item to remove it from the return." +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 +msgid "A typical sales order with a highlighted delivery smart button in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:25 +msgid "On the validated delivery order, click :guilabel:`Return`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 +msgid "A validated delivery order with a highlighted Return button in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:31 +msgid "This opens a :guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:33 +msgid "By default, the :guilabel:`Quantity` matches the validated quantities from the delivery order. Update the quantities, if necessary. Click on the :guilabel:`šŸ—‘ļø (trash)` icon next to a line item to remove it from the return." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:-1 msgid "The \"Reverse Transfer\" pop-up window, to make a return before invoicing the customer." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:29 -msgid "Next, click :guilabel:`Return` to confirm the return. This generates a new warehouse operation for the incoming returned product(s). Upon receiving the return, the warehouse team validates the warehouse operation. Then, on the original sales order, the :guilabel:`Delivered` quantity will reflect the difference between the initial validated quantities and the returned quantities." +#: ../../content/applications/sales/sales/products_prices/returns.rst:41 +msgid "Next, click :guilabel:`Return` to confirm the return. This generates a new warehouse operation for the incoming returned product(s)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 +msgid "Warehouse operation after a return has been confirmed in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:48 +msgid "Upon receiving the return, the warehouse team validates the warehouse operation by clicking :guilabel:`Validate`. Then, on the original sales order, the :guilabel:`Delivered` quantity updates to reflect the difference between the initial validated quantities and the returned quantities." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:-1 msgid "The updated \"Delivered\" quantity on the sales order after the reverse transfer." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:38 -msgid "When an invoice is created, the customer receives an invoice only for the products they are keeping." +#: ../../content/applications/sales/sales/products_prices/returns.rst:56 +msgid "When an invoice is created, the customer receives an invoice **only** for the products they are keeping, if any." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:42 +#: ../../content/applications/sales/sales/products_prices/returns.rst:60 msgid "After invoicing" msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:44 -msgid "Sometimes, customers return an item after they receive and/or pay for their invoice. In these cases, a return using only *Reverse Transfers* is insufficient since validated or sent invoices cannot be changed. However, *Reverse Transfers* can be used in conjunction with *Credit Notes* to complete the customer's return." +#: ../../content/applications/sales/sales/products_prices/returns.rst:62 +msgid "Sometimes, customers return an item after they receive and/or pay for their invoice. In these cases, a return using only *Reverse Transfers* is insufficient since validated, or sent, invoices cannot be changed." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:49 -msgid "To start a return, navigate to the relevant sales order. If there is a payment registered on the sales order, then the payment details will appear in the Chatter, and the invoice (accessible through the :guilabel:`Invoices` smart button) will have a green banner across it." +#: ../../content/applications/sales/sales/products_prices/returns.rst:66 +msgid "However, *Reverse Transfers* can be used in conjunction with *Credit Notes* to complete the customer's return." msgstr "" -#: ../../content/applications/sales/sales/products_prices/returns.rst:53 -msgid "From the sales order, click on the :guilabel:`Delivery` smart button to view the validated delivery order. Then, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window. Next, edit the :guilabel:`Product` or :guilabel:`Quantity` as needed for the return, and then click :guilabel:`Return`. This generates a new warehouse operation for the incoming returned product(s), which is validated by the warehouse team once the return is received. Then, on the sales order, the :guilabel:`Delivered` quantity will reflect the difference between the initial validated quantities and the returned quantities." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/returns.rst:61 -msgid "To process a refund, navigate to the relevant invoice (from the sales order, click on the :guilabel:`Invoices` smart button). Click :guilabel:`Add Credit Note` from the validated invoice." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 -msgid "The \"Credit Note\" pop-up window, to issue a credit to the customer after invoicing." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/returns.rst:68 -msgid "A :guilabel:`Reason` for the credit and a :guilabel:`Specific Journal` to use to process the credit can be specified. If a :guilabel:`Specific Reversal Date` is selected, then a :guilabel:`Refund Date` must also be selected." +#: ../../content/applications/sales/sales/products_prices/returns.rst:69 +msgid "To start a return after invoicing, navigate to the relevant sales order in the :menuselection:`Sales` app." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:72 -msgid "After the information is filled in, click :guilabel:`Reverse`. Then, :guilabel:`Edit` the draft as needed, and finally, click :guilabel:`Confirm` to confirm the credit note." +msgid "If there is a payment registered on the sales order, the payment details appear in the chatter, and the invoice (accessible through the :guilabel:`Invoices` smart button) has a green :guilabel:`In Payment` banner." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 +msgid "Sample of a green in payment banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:80 +msgid "From the sales order, click on the :guilabel:`Delivery` smart button to view the validated delivery order. Then, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:83 +msgid "Next, edit the :guilabel:`Product` and/or :guilabel:`Quantity`, as needed for the return. Then, click :guilabel:`Return`. This generates a new warehouse operation for the incoming returned product(s), which is validated by the warehouse team once the return is received by clicking :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:88 +msgid "Then, on the sales order, the :guilabel:`Delivered` quantity updates to reflect the difference between the initial validated quantities and the returned quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:91 +msgid "To process a refund, navigate to the relevant invoice (from the sales order, click on the :guilabel:`Invoices` smart button). Then, click the :guilabel:`Credit Note` button at the top of the validated invoice." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 +msgid "A typical customer invoice with a Credit Note button highlighted in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:99 +msgid "Doing so reveals a :guilabel:`Credit Note` pop-up form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:-1 +msgid "Typical credit note pop-up form that appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:105 +msgid "Start by entering a :guilabel:`Reason displayed on Credit Note` and a specific :guilabel:`Journal` to process the credit. Then, select a specific :guilabel:`Reversal Date`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:108 +msgid "After the information is filled in, click :guilabel:`Reverse` or :guilabel:`Reverse and Create Invoice`. Then, edit the draft, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:111 +msgid "Lastly, click :guilabel:`Confirm` to confirm the credit note." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:113 +msgid "When complete, a blue banner reading: :guilabel:`You have outstanding credits for this customer. You can allocate them to mark this invoice as paid.` appears at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:117 +msgid ":doc:`../../../finance/accounting/customer_invoices/credit_notes`" msgstr "" #: ../../content/applications/sales/sales/send_quotations.rst:5 @@ -6171,64 +7714,58 @@ msgid "In the Odoo *Sales* application, it is possible to set deadlines on sales msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:11 -msgid "Expiration date deadlines" +msgid "Quotation expiration" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:13 -msgid "On an Odoo *Sales* quotation, add an expiration date in the :guilabel:`Expiration` field located at the top of the quotation or sales order form." +msgid "In Odoo *Sales*, there's the option to add an expiration date to a quotation." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:16 -msgid "To add an expiration date to a quotation, navigate to :menuselection:`Sales app`, and select a desired quotation, or create a new one by clicking :guilabel:`Create`." +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:15 +msgid "To add an expiration date to a quotation, navigate to :menuselection:`Sales app`, and select a desired quotation, or create a new one by clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:19 -msgid "On the quotation form, click :guilabel:`Edit` (if modifying a pre-existing quotation), and click the :guilabel:`Expiration` field. Doing so reveals a drop-down calendar, in which the month and date can be designated as the expiration date of the quotation." +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:18 +msgid "On the quotation form, click the :guilabel:`Expiration` field to reveal a pop-up calendar. From this pop-up calendar, select the desired month and date as the expiration date for the quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:-1 -msgid "How to configure deadlines on Odoo Sales." +msgid "The expiration field on a standard quotation form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:27 -msgid "Once the expiration date is selected, click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:30 -msgid "Deadlines in quotation templates" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:32 -msgid "The Odoo *Sales* application also makes it possible to add a deadline to every quotation template. Whenever a specific quotation template is used in a quote, its associated deadline is automatically applied." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:36 -msgid "To add a deadline to a quotation template, navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates`, and either select the desired quotation template to which a deadline should be added, or click :guilabel:`Create` to build a new quotation template from scratch." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:40 -msgid "On the quotation template detail page, click the :guilabel:`Edit` button to edit the quotation." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:42 -msgid "Then, add a specific number of days to the :guilabel:`Quotation expires after` field, located beneath the quotation template name. The number of days represents how long the quotation will be valid for, before it expires. When done, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:-1 -msgid "How to use deadline in a quotation template on Odoo Sales." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/deadline.rst:51 -msgid "By clicking the :guilabel:`Customer Preview` button on a quotation, Odoo clearly displays when that specific offer expires. As a reminder, the number of days is the same as those mentioned in the quotation template (if a quotation template was used for the initial quotation)." +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:26 +msgid "By clicking the :guilabel:`Preview` button on a quotation, Odoo clearly displays when that specific offer expires." 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:60 -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:52 -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:90 +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:34 +msgid "Quotation template expiration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:36 +msgid "The Odoo *Sales* application also makes it possible to add a deadline expiration date to quotation templates." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:39 +msgid "To add a deadline expiration date to a quotation template, navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates`, and either select the desired quotation template to which a deadline should be added, or click :guilabel:`New` to build a new quotation template from scratch." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:43 +msgid "On the quotation template form, add a specific number of days to the :guilabel:`Quotation expires after` field, located beneath the quotation template name. The number of days represents how long the quotation will be valid for, before it expires." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:-1 +msgid "The quotation expires after field on a quotation template form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:51 +msgid "Then, whenever that specific quotation template is used in a quote, an expiration date is automatically calculated, based on the number of days designated above. However, this date can be overwritten before sending the quotation to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:56 msgid ":doc:`/applications/sales/sales/send_quotations/quote_template`" msgstr "" @@ -6240,10 +7777,6 @@ msgstr "" msgid "People and businesses often use separate addresses for billing (invoicing) and shipping (delivery) purposes. With the Odoo *Sales* app, contacts can have different specified addresses for delivery and invoicing." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 -msgid "Settings" -msgstr "" - #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12 msgid "To properly utilize multiple addresses in Odoo, go to :menuselection:`Sales app --> Configuration --> Settings` and scroll down to the :guilabel:`Quotations & Orders` heading. Then, check the box next to :guilabel:`Customer Addresses`, and click :guilabel:`Save`." msgstr "" @@ -6337,63 +7870,111 @@ msgid "If any changes are made on a form in Odoo, include *Contacts* forms, reme msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 -msgid "Get paid to confirm an order" +msgid "Online payment order confirmation" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:5 -msgid "In general, online payments are considered as a fast and secure alternative to traditional payment methods. It is generally cheaper, easier and faster than other payment methods. It is particularly useful and efficient for international transactions. With Odoo Sales, you can use online payments to get automatic orders confirmation. Online payments are made instantly, so it's very convenient and saves lots of time in a basic sales process." +msgid "The Odoo *Sales* application provides customers with the ability to confirm orders, via an online payment, directly on a sales order. Once the sales order is electronically paid for by the customer, the salesperson attached to the sales order is instantly notified that the order is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:10 +msgid "Activate online payments" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:12 -msgid "Enable online payment" +msgid "In order to have customers confirm orders with an online payment, the *Online Payment* setting **must** be activated." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:14 -msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Online Payment** feature." +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:15 +msgid "To activate the *Online Payment* feature, go to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& Orders` heading, check the box next to the :guilabel:`Online Payment` feature, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 -msgid "How to enable online payment on Odoo Sales?" +msgid "The online payment setting in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:22 -msgid "There, you will have direct access to the **Payment Providers** page. It will allow you to select and configure your providers of choice. Before creating or modifying a payment provider, be sure to check out our documentation about how to be paid with payment providers such as :doc:`/applications/finance/payment_providers/paypal`, :doc:`/applications/finance/payment_providers/authorize`, and others in the :doc:`/applications/finance/payment_providers` documentation." +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:23 +msgid "Beneath the :guilabel:`Online Payment` option on the *Sales* :guilabel:`Settings` page, there's a :guilabel:`Default Quotation Validity` field. In this field, there's the option to add a specific number of days for quotations to remain valid by default." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:30 -msgid "If you are familiar with this documentation: :doc:`quote_template`; you can activate or not the **Online Payment** feature for each template you use, under their confirmation tab." +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:27 +msgid "To enable this feature on a standard quotation, click the checkbox for the :guilabel:`Payment` feature option, located in the :guilabel:`Online confirmation` field, on the :guilabel:`Other Info` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 +msgid "The online payment setting on a standard quotation in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35 -msgid "Register a payment" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:37 -msgid "After opening quotations from their received email, your customers will have different possibilities to make their online payments. For example:" +msgid "To enable this feature on a quotation template, click the checkbox for the :guilabel:`Payment` feature option, located in the :guilabel:`Online confirmation` field of the quotation template form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 -msgid "How to register a payment on Odoo Sales?" +msgid "The online payment setting on quotation template forms in 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." +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:43 +msgid "Payment providers" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:50 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:45 +msgid "After activating the :guilabel:`Online Payment` feature, a link to configure :guilabel:`Payment Providers` appears beneath it." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:48 +msgid "Clicking that link reveals a separate :guilabel:`Payment Providers` page, in which a large variety of payment providers can be enabled, customized, and published." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 +msgid "Payment providers page in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:56 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:91 +msgid ":doc:`../../../finance/payment_providers`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:59 +msgid "Register a payment" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:61 +msgid "After opening quotations in their customer portal, customers can click :guilabel:`Accept \\& Pay` to confirm their order with an online payment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 +msgid "The accept and pay button on an online quotation in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:68 +msgid "After clicking :guilabel:`Accept \\& Pay`, customers are presented with :guilabel:`Validate Order` pop-up window containing different options for them to make online payments, in the :guilabel:`Pay with` section." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 +msgid "How to register a payment on a validate order pop-up window in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:77 +msgid "Odoo will **only** offer payment options on the :guilabel:`Validate Order` pop-up window that have been published and configured on the :guilabel:`Payment Providers` page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:80 +msgid "Once the customer selects their desired method of payment, they will click the :guilabel:`Pay` button on the pop-up window to confirm the order. Odoo instantly notifies the assigned salesperson upon order confirmation with an online payment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 +msgid "Sample of notification that appears in the chatter when an online payment is made." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:89 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:77 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:99 msgid ":doc:`quote_template`" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:51 -msgid ":doc:`/applications/finance/payment_providers`" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:52 -msgid ":doc:`/applications/finance/payment_providers/paypal`" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:53 -msgid ":doc:`/applications/finance/payment_providers/authorize`" +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:272 +msgid ":doc:`get_signature_to_validate`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 @@ -6401,7 +7982,7 @@ msgid "Online signatures for order confirmations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:5 -msgid "The Odoo *Sales* application provides customers with the ability to confirm orders via an online signature directly on the sales order. Once the sales order is electronically signed by the customer, the salesperson attached to the sales order is automatically notified that the order is confirmed." +msgid "The Odoo *Sales* application provides customers with the ability to confirm orders, via an online signature, directly on the sales order. Once the sales order is electronically signed by the customer, the salesperson attached to the sales order is instantly notified that the order is confirmed." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:11 @@ -6409,43 +7990,80 @@ msgid "Activate online signatures" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:13 -msgid "To activate the *online signature* feature, go to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Quotations & Orders` heading, and activate the :guilabel:`Online Signature` feature by checking the box beside it. Then, click the :guilabel:`Save` button in the top-left corner." +msgid "In order to have customers confirm orders with an online signature, the *Online Signature* feature **must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:16 +msgid "To activate the *Online Signature* feature, go to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& Orders` heading, and activate the :guilabel:`Online Signature` feature by checking the box beside it." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:-1 -msgid "How to enable online signature in Odoo Sales settings." +msgid "The Online Signature feature option in the Settings of the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:23 -msgid "On quotation templates, the :guilabel:`Online Signature` feature is located under the :guilabel:`Confirmation` tab." +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:24 +msgid "Then, click the :guilabel:`Save` button in the top-left corner." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:27 +msgid "When making a quotation template, the online signature feature is the :guilabel:`Signature` option, located in the :guilabel:`Online confirmation` field of the quotation template form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 -msgid "How to enable online signature on a quotation template." +msgid "The Online confirmation signature option found on every quotation template in Odoo." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:30 -msgid "On standard quotations, the :guilabel:`Online Signature` feature is located under the :guilabel:`Other Info` tab." +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:34 +msgid "On standard quotations, the online signature feature is the :guilabel:`Signature` option, located under the :guilabel:`Other Info` tab of the quotation form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 -msgid "How to enable online signature on standard quotations." +msgid "The online signature feature option in the Other Info tab of a quotation form in Odoo." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:38 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:42 msgid "Order confirmations with online signatures" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:40 -msgid "When quotations are sent to clients, there's an option for them to :guilabel:`Sign & Pay` directly on the quotation in the online customer portal. When clicked, clients have the option to draw a signature, fill in the field with an automated signature, or load a file from their computer." +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:44 +msgid "When clients access quotations online through their customer portal, there's a :guilabel:`Sign \\& Pay` button directly on the quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:-1 -msgid "How to confirm an order with a signature on Odoo Sales." +msgid "The Sign and Pay button present on online quotations in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:48 -msgid "Once signed, the various payment method options become available. Then, when the quotation is paid and confirmed, a delivery order is automatically created (if the Odoo *Inventory* app is installed)." +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 +msgid "When clicked, a :guilabel:`Validate Order` pop-up window appears. In this pop-up window, the :guilabel:`Full Name` field is auto-populated, based on the contact information in the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:-1 +msgid "The Validate Order pop-up window for online signatures in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:58 +msgid "Then, customers have the option to enter an online signature with any of the following options: :guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:61 +msgid ":guilabel:`Auto` lets Odoo automatically generate an online signature based on the information in the :guilabel:`Full Name` field. :guilabel:`Draw` lets the customer use the cursor to create a custom signature directly on the pop-up window. And :guilabel:`Load` lets the customer upload a previously-created signature file from their computer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:66 +msgid "After the customer has chosen any of the three previously mentioned signature options (:guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`), they will click the :guilabel:`Accept \\& Sign` button." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:70 +msgid "When :guilabel:`Accept \\& Sign` is clicked, the various payment method options become available for them to choose from (if the *online payment* option applies to this quotation)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:73 +msgid "Then, when the quotation is paid and confirmed, a delivery order is automatically created (if the Odoo *Inventory* app is installed)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:273 +msgid ":doc:`get_paid_to_validate`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3 @@ -6457,6 +8075,7 @@ msgid "The use of optional products is a marketing strategy that involves the cr msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:9 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:157 msgid "For instance, if a customer wants to buy a car, they have the choice to order massaging seats, as well, or ignore the offer and simply buy the car. Presenting the choice to purchase optional products enhances the customer experience." msgstr "" @@ -6472,144 +8091,202 @@ msgstr "" msgid "How to add optional products to your quotations on Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:24 -msgid "Click the :guilabel:`Customer Preview` button to reveal a preview of the quotation customers would receive via email, along with the optional products they have a chance of adding to their order." +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:23 +msgid "To add an optional product(s) to a quotation, click :guilabel:`Add a product` in the :guilabel:`Optional Products` tab of a quotation. Doing so reveals a blank field in the :guilabel:`Product` column." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:0 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:27 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:178 +msgid "When clicked, a drop-down menu with products from the database appear. Select the desired product from the drop-down menu to add it as an optional product to the quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:31 +msgid "If the desired product isn't readily visible, type the name of the desired product in the field, and the option appears in the drop-down menu. Then, select that desired product to add it to the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:36 +msgid "When a product is added, the default :guilabel:`Quantity` is `1`, but that can be edited at any time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:39 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:181 +msgid "To delete any line item from the :guilabel:`Optional Products` tab, click the :guilabel:`šŸ—‘ļø (trash can)` icon." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:42 +msgid "Click the :guilabel:`Preview` button, located in the upper-left corner of the quotation, to reveal a preview of the quotation customers would receive, via email, along with the optional products they can potentially add to their order, located in the :guilabel:`Options` section." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 msgid "Preview your quotations on Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:32 -msgid "In practice, customers are able to add different optional products to an order by clicking the :guilabel:`šŸ›’ (shopping cart)` icon, located to the right of the optional product line. If a customer selects all the optional products suggested, these additional items are automatically filled in on the quotation that is managed by the salesperson." +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:50 +msgid "Customers are able to add different optional products to an order by clicking the :guilabel:`šŸ›’ (shopping cart)` icon, located to the right of the optional product line." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 -msgid "How to select optional products on Odoo Sales." +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:53 +msgid "If a customer selects optional products, these are automatically added to the quotation managed by the salesperson." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:41 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:56 msgid "When the customer adds an optional product(s) to an order, the salesperson is instantly notified about the change, along with any other change the customer makes to an order. This allows salespeople to stay up-to-date with everything related to an order in the backend of the *Sales* application." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 -msgid "How to follow each movement made by your customers on Odoo Sales." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:51 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:62 msgid "Optional products on quotation templates" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:54 -msgid "Be sure to review the documentation on how to :doc:`/applications/sales/sales/send_quotations/quote_template` to better understand how quotation templates work before reading the following information." +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 +msgid "Be sure to review the :doc:`quote_template` documentation to better understand how quotation templates work before reading the following information." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:58 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:68 msgid "For quotation templates, just like a typical quotation form, there is also an :guilabel:`Optional Products` tab, wherein related products or services can be added to a quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:61 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:71 msgid "To add optional products to a quotation template, navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates`. Then, either select an existing quotation template to edit, or create a new one by clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 -msgid "On the quotation form, click :guilabel:`Edit`, then click the :guilabel:`Optional Products` tab. Under the :guilabel:`Optional Products` tab, click :guilabel:`Add a line`, and select the desired product to add as an optional product to the quotation template." +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:75 +msgid "On the quotation template form, click the :guilabel:`Optional Products` tab. Under the :guilabel:`Optional Products` tab, click :guilabel:`Add a line`, and select the desired product to add as an optional product to the quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:70 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:83 +msgid "The products added in the :guilabel:`Optional Products` tab are present in the quotation, by default, whenever that particular quotation template is used. These products can be removed, and additional products can be added, before the quotation is sent to a customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:88 msgid "It's best to offer optional products that would encourage a customer to add additional items to their order, or entice them to purchase a more expensive version of their initially selected product." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:74 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:92 msgid "For example, if a customer purchases a wooden chair, some optional products could be: a warranty on that chair and/or a wooden chair with leather seats." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:77 -msgid "When the desired optional product(s) have been added, click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:80 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:96 msgid "There is no limit to how many optional products can be added to a quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:82 -msgid "The products added in the :guilabel:`Optional Products` tab are present in the quotation, by default, whenever that particular quotation template is used." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 -msgid "How to add optional products to your quotation templates on Odoo Sales." -msgstr "" - #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:3 -msgid "Use product variants on quotations and sales orders" +msgid "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." +msgid "Before getting into detail about how to use product variants on quotations and sales orders, it's recommended to learn about :doc:`../products_prices/products/variants` in Odoo." 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." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:8 +msgid "Once familiarized with the basics surrounding product variants, the following covers how product variants can be added to quotations and sales orders using the *product configurator* or *order grid entry*." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:13 +msgid "It should be noted that the setting is titled, *Variant Grid Entry* on the *Sales* app settings page, and titled, *Order Grid Entry* on product forms. So, be sure to keep that in mind." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:19 +msgid "When working with product variants, Odoo uses the product configurator, by default. To add the variant grid entry option, that feature **must** be enabled in the Odoo *Sales* application. The variant grid entry option provides a pop-up window on the quotation/sales order to simplify the variant selection process." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:24 +msgid "To enable that setting, go to :menuselection:`Sales app --> Configuration --> Settings`, and scroll to the :guilabel:`Product Catalog` section. Then, check the box next to the :guilabel:`Variant Grid Entry` option, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 -msgid "Activating entry type settings." +msgid "The variant grid entry setting in the Odoo Sales application." 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:-1 -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." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:33 +msgid "Of course, the :guilabel:`Variants` feature **must** also be activated, in order to use product variants on quotations and sales orders." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 -msgid "Use the Product Configurator" +msgid "Product configuration" 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." +msgid "Once the :guilabel:`Variant Grid Entry` setting is enabled, both options (*Product Configurator* and *Order Grid Entry*) become available on every product form." 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." +msgid "To configure a product form to use either a product configurator or variant grid entry, start by navigating to :menuselection:`Sales app --> Products --> Products` to view all the products in the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:46 +msgid "Then, select the desired product to configure, or click :guilabel:`New`, to create a new product from scratch. Once on the product form, click into the :guilabel:`Attributes \\& Variants` tab, where product variants can be viewed, modified, and added." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:50 +msgid "At the bottom of the :guilabel:`Attributes \\& Variants` tab, there is a :guilabel:`Sales Variant Selection` section with two options: :guilabel:`Product Configurator` and :guilabel:`Order Grid Entry`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:55 +msgid "It should be noted that these options **only** appear if at least two values of an attribute have been added to the record." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 -msgid "Product Configurator and Price Extras." +msgid "Sales variant selection options on the attributes and variants tab on product form." 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)." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:62 +msgid "These options determine which method is used when adding product variants to quotations or sales orders." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:57 -msgid "Use Variant Grid Entries" +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:65 +msgid "The :guilabel:`Product Configurator` provides a pop-up window that neatly displays all the available product variants for that particular product when it's added to a quotation. However, only one variant can be selected/added at a time." 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:-1 -msgid "Variant Grid Entry pop-up." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:69 +msgid "The :guilabel:`Order Grid Entry` provides the same information as the :guilabel:`Product Configurator` in a table layout, allowing the user to select larger numbers of unique product variants, and add them to a quotation/sales order, in a single view." 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." +msgid "Product configurator" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:76 +msgid "The product configurator feature appears as a :guilabel:`Configure` pop-up window, as soon as a product with (at least two) variants is added to a quotation or sales order, but **only** if the :guilabel:`Product Configurator` option is selected on its product form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 -msgid "Line items for grid variants." +msgid "The product configurator pop-up window that appears on a quotation or sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:85 +msgid "This :guilabel:`Configure` pop-up window also appears if the :guilabel:`Order Grid Entry` setting is **not** activated, as it is the default option Odoo uses when dealing with product variants on quotations and/or sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:89 +msgid "The :guilabel:`Product Configurator` option lets salespeople choose exactly which product variant to add to the quotation or sales order using a format similar to online shopping." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:93 +msgid "Order grid entry" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:95 +msgid "The order grid entry feature appears as a :guilabel:`Choose Product Variants` pop-up window, as soon as a product with (at least two) variants is added to a quotation or sales order, but **only** if the :guilabel:`Order Grid Entry` option is selected on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 +msgid "The choose product variants pop-up window that appears on a quotation in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:103 +msgid "The :guilabel:`Choose Product Variants` pop-up window features all the variant options for that particular product. From this pop-up window, the salesperson can designate how many of each variant they'd like to add to the quotation/sales order at once." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:107 +msgid "When all the desired quantities and variants have been selected, the salesperson simply clicks :guilabel:`Confirm`, and those orders are instantly added to the quotation/sales order in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 +msgid "Populated order lines tab after order grid entry has been chosen to select products." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:116 +msgid ":doc:`../products_prices/products/variants`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 @@ -6617,14 +8294,18 @@ msgid "Quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5 -msgid "In Odoo *Sales*, salespeople have the ability to create reusable quotation templates for common product or service offerings that the business offers. By using these templates, quotations can be tailored and sent to customers at a much faster pace, without having to create new quotations from scratch every time a sales negotiation occurs." +msgid "In Odoo *Sales*, salespeople have the ability to create reusable quotation templates for common products or services that the business offers." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:15 -msgid "Begin by activating the setting in :menuselection:`Sales app --> Configuration --> Settings`, and scroll to the :guilabel:`Quotations & Orders` heading." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:8 +msgid "By using these templates, quotations can be tailored and sent to customers at a much faster pace, without having to create new quotations from scratch every time a sales negotiation occurs." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:18 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:16 +msgid "Begin by activating the setting in :menuselection:`Sales app --> Configuration --> Settings`, and scroll to the :guilabel:`Quotations \\& Orders` heading." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 msgid "In that section, check the box beside the :guilabel:`Quotation Templates` option. Doing so reveals a new :guilabel:`Default Template` field, in which a default quotation template can be chosen from a drop-down menu." msgstr "" @@ -6632,128 +8313,268 @@ msgstr "" msgid "How to enable quotation templates on Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:26 -msgid "Also, upon activating the :guilabel:`Quotation Template` feature, an internal :guilabel:`āž”ļø Quotation Templates` link appears beneath the :guilabel:`Default Template` field. Clicking that link reveals the :guilabel:`Quotation Templates` page, from which templates can be created, viewed, and edited." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:27 +msgid "Also, upon activating the :guilabel:`Quotation Template` feature, an internal :guilabel:`āž”ļø Quotation Templates` link appears beneath the :guilabel:`Default Template` field." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:32 -msgid "Consider activating the :guilabel:`Quotation Builder` option in the :guilabel:`Settings`, as well, which is located in the right column beside the :guilabel:`Quotation Templates` option. This feature aides in the design and customization of quotation templates." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:30 +msgid "Clicking that link reveals the :guilabel:`Quotation Templates` page, from which templates can be created, viewed, and edited." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:36 -msgid "**Note:** enabling this feature also automatically installs the Odoo *Website* application." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33 +msgid "Before leaving the :guilabel:`Settings` page, don't forget to click the :guilabel:`Save` button to save all changes made during the session." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "How to enable quotation builder on Odoo Sales." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:42 -msgid "Before leaving the :guilabel:`Settings` page, don't forget to click the :guilabel:`Save` button to activate the feature(s) and save all changes made during the session." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:46 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:37 msgid "Create quotation templates" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:48 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:39 msgid "Click the :guilabel:`Quotation Templates` link on the :guilabel:`Settings` page, or navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates`. Both options reveal the :guilabel:`Quotation Templates` page, where quotation templates can be created, viewed, and edited." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:52 -msgid "To create a new quotation template, click the :guilabel:`Create` button, located in the upper-left corner. Doing so reveals a blank quotation template form that can be customized in a number of ways." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Quotation templates page in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:47 +msgid "To create a new quotation template, click the :guilabel:`New` button, located in the upper-left corner. Doing so reveals a blank quotation template form that can be customized in a number of ways." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 msgid "Create a new quotation template on Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:59 -msgid "Start by entering a name for the template in the :guilabel:`Quotation Template` field. Then, in the :guilabel:`Quotation expires after` field, designate how many days the quotation template will remain valid for, or leave the field on the default `0` to keep the template valid indefinitely." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 +msgid "Start by entering a name for the template in the :guilabel:`Quotation Template` field." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:63 -msgid "In the :guilabel:`Company` field, designate to which company this quotation template applies, if working in a multi-company environment." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:56 +msgid "Then, in the :guilabel:`Quotation expires after` field, designate how many days the quotation template will remain valid for, or leave the field on the default `0` to keep the template valid indefinitely." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:66 -msgid "Beneath those fields are three tabs: :guilabel:`Lines`, :guilabel:`Optional Products`, :guilabel:`Confirmation`." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:60 +msgid "If the :guilabel:`Online Signature` and/or :guilabel:`Online Payment` features are activated in the :guilabel:`Settings` (:menuselection:`Sales app --> Configuration --> Settings`), those options are available in the :guilabel:`Online confirmation` field." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 -msgid "In the :guilabel:`Lines` tab, products can be added to the quotation template by clicking :guilabel:`Add a product`, organized by clicking `Add a section` (and dragging/dropping section headers accordingly), and further explained with discretionary information (such as warranty details, terms, etc.) by clicking :guilabel:`Add a note`." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:64 +msgid "In the :guilabel:`Online confirmation` field, check the box beside :guilabel:`Signature` to request an online signature from the customer to confirm an order. Check the box beside :guilabel:`Payment` to request an online payment from the customer to confirm an order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:74 -msgid "In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each compatible cross-selling product related to the original items in the :guilabel:`Lines` tab, if applicable. The products added here ideally compliment the original offering as added value for the prospective buyer." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:68 +msgid "Both options can be enabled simultaneously, in which case the customer must provide **both** a signature **and** a payment to confirm an order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:78 -msgid "Lastly, in the :guilabel:`Confirmation` tab, enable options, as needed, to require an :guilabel:`Online Signature` and/or an :guilabel:`Online Payment`, which each allow buyers to confirm orders automatically using the web portal view after the required action is taken." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:71 +msgid "Next, in the :guilabel:`Confirmation Mail` field, click the blank field to reveal a drop-down menu. From the drop-down menu, select a pre-configured email template to be sent to customers upon confirmation of an order." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:82 -msgid "There's also an option to add a :guilabel:`Confirmation Mail` to the quotation template, as well - meaning whenever this template is used, and an order is confirmed, an email is sent to the customer informing them that their order has been confirmed." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:76 +msgid "To create a new email template directly from the :guilabel:`Confirmation Mail` field, start typing the name of the new email template in the field, and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:80 +msgid "Selecting :guilabel:`Create` creates the email template, which can be edited later. Selecting :guilabel:`Create and edit...` creates the email template, and a :guilabel:`Create Confirmation Mail` pop-up window appears, in which the email template can be customized and configured right away." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Allow customers to sign electronically or to pay online on Odoo Sales." +msgid "Create confirmation mail pop-up window from the quotation template form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:91 -msgid "Design quotation templates" +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:89 +msgid "When all modifications are complete, click :guilabel:`Save \\& Close` to save the email template and return to the quotation form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:94 -msgid "The following section on designing quotation templates only applies to databases that have the *Quotation Builder* feature enabled, which is accessible by following the :ref:`configuration steps above `." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:92 +msgid "If working in a multi-company environment, use the :guilabel:`Company` field to designate to which company this quotation template applies." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:98 -msgid "In the upper-left corner of the quotation template form, there's a :guilabel:`Design Template` button. When clicked, Odoo reveals a preview of the quotation template, as it will appear on the front-end of the website, with a :guilabel:`Template Header` specifying that this content will appear on all quotations using this specific template." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:95 +msgid "In the :guilabel:`Recurrence` field, choose from a variety of pre-configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`) to designate how often this quotation template should occur." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:103 -msgid "To edit the content, look, and overall design of the quotation template, click the :guilabel:`Edit` button in the upper-right corner. Doing so reveals a variety of design elements and feature-filled building blocks." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:100 +msgid "The :guilabel:`Recurrence` field **only** applies to subscription plans. For more information, check out the documentation on :doc:`../../subscriptions/plans`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:104 +msgid "Lines tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:106 +msgid "In the :guilabel:`Lines` tab, products can be added to the quotation template by clicking :guilabel:`Add a product`, organized by clicking :guilabel:`Add a section` (and dragging/dropping section headers), and further explained with discretionary information (such as warranty details, terms, etc.) by clicking :guilabel:`Add a note`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Design quotation template on Odoo Sales." +msgid "Populated lines tab on a quotation template form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:111 -msgid "Drag and drop any desired building blocks onto the blank quotation template, and proceed to further customize the content to fit any business need. When all blocks and customizations are complete, click the :guilabel:`Save` button to put those configurations into place." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:115 +msgid "To add a product to a quotation template, click :guilabel:`Add a product` in the :guilabel:`Lines` tab of a quotation template form. Doing so reveals a blank field in the :guilabel:`Product` column." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Drag and drop building blocks to create your quotation template on Odoo Sales." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:120 -msgid "Use quotation templates" +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:118 +msgid "When clicked, a drop-down menu with existing products in the database appear. Select the desired product from the drop-down menu to add it to the quotation template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:122 -msgid "When creating a quotation (:menuselection:`Sales app --> Create`), choose a preconfigured template in the :guilabel:`Quotation Template` field drop-down menu." +msgid "If the desired product isn't readily visible, type the name of the desired product in the :guilabel:`Product` field, and the option appears in the drop-down menu. Products can also be found by clicking :guilabel:`Search More...` from the drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Select a specific template on Odoo Sales." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:127 +msgid "When a product is added to a quotation template, the default :guilabel:`Quantity` is `1`, but that can be edited at any time." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:129 -msgid "To view what the customer will see, click the :guilabel:`Customer Preview` smart button to see how the quotation template will look on the front-end of the website." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:130 +msgid "Then, drag-and-drop the product to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:133 -msgid "Go to :menuselection:`Sales --> Configuration --> Settings` to select a :guilabel:`Default Template`." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:137 -msgid ":doc:`/applications/sales/sales/send_quotations/get_signature_to_validate`" +msgid "To add a *section*, which serves as a header to organize the lines of a sales order, click :guilabel:`Add a section` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired name of the section can be typed. When the name has been entered, click away to secure the section name." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138 -msgid ":doc:`/applications/sales/sales/send_quotations/get_paid_to_validate`" +msgid "Then, drag-and-drop the section name to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:141 +msgid "To add a note, which would appear as a piece of text for the customer on the quotation, click :guilabel:`Add a note` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired note can be typed. When the note has been entered, click away to secure the note." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:145 +msgid "Then, drag-and-drop the note to the desired position, via the :guilabel:`six squares` icon." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:147 +msgid "To delete any line item from the :guilabel:`Lines` tab (product, section, and/or note), click the :guilabel:`šŸ—‘ļø (trash can)` icon on the far-right side of the line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:151 +msgid "Optional Products tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:153 +msgid "The use of *optional products* is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:161 +msgid "Optional products appear as a section on the bottom of sales orders and eCommerce pages. Customers can immediately add them to their online sales orders themselves, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Optional products appearing on a typical sales order with Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:168 +msgid "In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each cross-selling product related to the original items in the :guilabel:`Lines` tab, if applicable. The products added here ideally complement the original offering as added value for the prospective buyer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Populated optional products tab on a quotation template in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:176 +msgid "Clicking :guilabel:`Add a line` reveals a blank field in the :guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:185 +msgid "Optional products are **not** required to create a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:188 +msgid "Terms \\& Conditions tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:190 +msgid "The :guilabel:`Terms \\& Conditions` tab provides the opportunity to add terms and conditions to the quotation template. To add terms and conditions, simply type (or copy/paste) the desired terms and conditions in this tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Terms and conditions tab in a quotation template form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:199 +msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:202 +msgid "Terms and conditions are **not** required to create a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:205 +msgid "Design quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:207 +msgid "In the upper-left corner of the quotation template form, there's a :guilabel:`Design Template` button." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Design template button in the upper-left corner of quotation template form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:214 +msgid "When clicked, Odoo reveals a preview of the quotation template, through the Odoo *Website* application, as it will appear on the front-end of the website to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:218 +msgid "This feature is **only** available if the *Website* application is installed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:220 +msgid "Odoo uses numerous blue placeholder blocks to signify where certain elements appear, and what they contain (e.g. :guilabel:`Template Header`, :guilabel:`Product`)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:223 +msgid "To edit the content, appearance, and overall design of the quotation template via the *Website* application, click the :guilabel:`Edit` button in the upper-right corner." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Design template edit button in the upper-right corner of quotation template design." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:230 +msgid "When :guilabel:`Edit` is clicked, Odoo reveals a sidebar filled with a variety of design elements and feature-rich building blocks. These building blocks can be dragged-and-dropped anywhere on the quotation template design." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Design quotation template building blocks sidebar in Odoo Website." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:238 +msgid "After a block has been dropped in the desired position, it can be customized and configured to fit any unique need, look, or style." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:242 +msgid "Quotation template design uses the same methodology and functionality with design building blocks as a typical web page design with Odoo *Website*. Be sure to check out the :doc:`../../../websites/website` documentation to learn more." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:246 +msgid "When all blocks and customizations are complete, click the :guilabel:`Save` button to put those configurations into place." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:249 +msgid "There is also a blue banner at the top of the quotation template design with a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo returns to the quotation template form in the back-end of the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:254 +msgid "Use quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:256 +msgid "When creating a quotation (:menuselection:`Sales app --> New`), choose a pre-configured template in the :guilabel:`Quotation Template` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Quotation templates field on a standard quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:263 +msgid "To view what the customer will see, click the :guilabel:`Preview` button at the top of the page to see how the quotation template appears on the front-end of the website through Odoo's customer portal." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "Customer preview of a quotation template in Odoo Sales." msgstr "" #: ../../content/applications/sales/subscriptions.rst:5 @@ -7230,7 +9051,7 @@ msgid "Subscription products" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:5 -msgid "By integrating closely with the Odoo *Sales* app, the *Subscriptions* app enables users to sell subscription products alongside regular sales products. While regular products are sold on a one-time basis, subscription products are sold on a renewing basis, generating recurring revenue." +msgid "By closely integrating with the Odoo *Sales* app, the *Subscriptions* app enables users to sell subscription products alongside regular sales products. While regular products are sold on a one-time basis, subscription products are sold on a renewing basis, generating recurring revenue." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:9 @@ -7242,86 +9063,150 @@ msgid "Configure recurrence periods" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:14 -msgid "To get started with subscriptions, first make sure that the *recurrence periods* are configured as needed." +msgid "To get started with subscriptions, the *recurrence periods* must be properly configured, as needed." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:17 +#: ../../content/applications/sales/subscriptions/products.rst:16 msgid "Recurrence periods are the time periods in which subscriptions renew. They designate how often the customer pays for (and receives) subscription products." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:20 -msgid "To configure recurrence periods, go to :menuselection:`Subscriptions --> Configuration --> Recurrence Periods`." -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:23 -msgid "The *Subscriptions* app comes with some basic recurrence periods already configured: Daily, Monthly, Quarterly, Weekly, Yearly, 3 Years, and 5 Years. These can be edited as needed, and any number of new recurrence periods can be added." -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:27 -msgid "To create a new recurrence period, click :guilabel:`New` on the recurrence periods dashboard. Then, type in the :guilabel:`Name` and :guilabel:`Duration` of the recurrence period, and select the :guilabel:`Unit` that defines the duration." -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:32 -msgid "To create a recurrence period for a subscription that will renew every two weeks, set the :guilabel:`Duration` to `2` and the :guilabel:`Unit` to `Weeks`." -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:0 -msgid "A recurrence period of 2 weeks." -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:40 -msgid "Configure the product form" -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:42 -msgid "To create a new subscription product, navigate to the :menuselection:`Subscriptions` app. Then go to :menuselection:`Subscriptions --> Products`, and click :guilabel:`New` to create a new product. Enter a :guilabel:`Product Name`." -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:46 -msgid "The :guilabel:`Product Type` for the new product is automatically set to :guilabel:`Service`. Subscription products can be set to other types as well; however, they currently *cannot* be set to :guilabel:`Storable Product`." -msgstr "" - -#: ../../content/applications/sales/subscriptions/products.rst:50 -msgid "The new product automatically has the :guilabel:`Recurring` checkbox activated. This enables Odoo to recognize it as a subscription product. Be sure to leave the :guilabel:`Recurring` and :guilabel:`Can be Sold` options enabled." +#: ../../content/applications/sales/subscriptions/products.rst:19 +msgid "To configure recurrence periods, go to :menuselection:`Subscriptions app --> Configuration --> Recurrence periods`." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:-1 -msgid "The \"Recurring\" checkbox on the product form." +msgid "The recurrence periods page in Odoo Subscriptions application." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:59 -msgid "Time-based pricing" +#: ../../content/applications/sales/subscriptions/products.rst:26 +msgid "The *Subscriptions* app comes with some basic recurrence periods already configured:" msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:61 -msgid "Next, configure the :guilabel:`Time-based pricing` tab on the product form." +#: ../../content/applications/sales/subscriptions/products.rst:28 +msgid ":guilabel:`Monthly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:29 +msgid ":guilabel:`Quarterly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:30 +msgid ":guilabel:`Weekly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:31 +msgid ":guilabel:`2 Weeks`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:32 +msgid ":guilabel:`Yearly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:33 +msgid ":guilabel:`3 Years`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:34 +msgid ":guilabel:`5 Years`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:36 +msgid "New recurrence periods can be added and/or edited at any time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:38 +msgid "To create a new recurrence period, click :guilabel:`New` on the :guilabel:`Recurrence Periods` page. Doing so reveals a blank recurrence period form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:-1 +msgid "A recurrence period form in Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:45 +msgid "Then, type in the :guilabel:`Name` and :guilabel:`Duration` of the recurrence period, and select the :guilabel:`Unit` that defines the duration." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:49 +msgid "The unit :guilabel:`Days` *cannot* be used as a recurrence period on subscriptions. The daily recurrence is meant for rentals, and **cannot** be added on recurring subscription sales orders." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:52 +msgid "This limitation is there to avoid sales orders that would generate daily invoices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:55 +msgid "Product form configuration" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:57 +msgid "To create a new subscription product, navigate to :menuselection:`Subscriptions app --> Products --> Products`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:60 +msgid "Doing so reveals a blank product form, which can be configured and customized in a number of ways." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:63 -msgid "Click :guilabel:`Add a price` to begin defining recurring prices. In the :guilabel:`Period` column, select a recurrence period. In the :guilabel:`Price` column, enter the price for that recurrence period." +msgid "By default, the :guilabel:`Recurring` option is already enabled, prompting Odoo to recognize it as a subscription product. Be sure to leave the :guilabel:`Recurring` and :guilabel:`Can be Sold` options enabled." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:68 -msgid ":guilabel:`Daily` and :guilabel:`Hourly` periods cannot be used on recurring products." +#: ../../content/applications/sales/subscriptions/products.rst:67 +msgid "The :guilabel:`Product Type` field is set to :guilabel:`Service` by default, as well. However, subscription products *can* be set to other types, if needed." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:70 -msgid "Add as many lines as needed to the :guilabel:`Time-based pricing` table." +#: ../../content/applications/sales/subscriptions/products.rst:-1 +msgid "A basic subscription product form in Odoo Subscriptions application." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:73 -msgid "An existing product can be made into a subscription product simply by marking it as :guilabel:`Recurring` and configuring :guilabel:`Time-based pricing` on the product form." +#: ../../content/applications/sales/subscriptions/products.rst:75 +msgid "Time-based pricing" msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:76 -msgid "A subscription product can still be sold as a regular product by adding it to a quotation and *not* selecting a :guilabel:`Recurrence` on the quotation." +#: ../../content/applications/sales/subscriptions/products.rst:77 +msgid "Once the desired fields in the :guilabel:`General Information` tab have been entered, click the :guilabel:`Time-based pricing` tab on the product form." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:82 -msgid "Use :doc:`pricelists ` with subscription products to give special pricing to customers included in pricelists. This can be configured either in the :guilabel:`Time-based pricing` tab of the product form, or on the pricelist form in the *Sales* app." +#: ../../content/applications/sales/subscriptions/products.rst:-1 +msgid "The time-based pricing tab on a subscription product form in Odoo Subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:87 +#: ../../content/applications/sales/subscriptions/products.rst:84 +msgid "From here, click :guilabel:`Add a price` to begin defining recurring prices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:86 +msgid "In the :guilabel:`Period` column, select a desired recurrence period. In the :guilabel:`Pricelist` column, select a pricelist, if needed. Then, in the :guilabel:`Price` column, enter the price for that recurrence period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:91 +msgid ":guilabel:`Daily` and :guilabel:`Hourly` periods **cannot** be used on recurring products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:0 +msgid "The validation error pop-up window that appears in Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:98 +msgid "There is *no limit* to how many lines can be added to the :guilabel:`Time-based pricing` table." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:101 +msgid "An existing product can be made into a subscription product, simply by marking it as :guilabel:`Recurring`, and configuring :guilabel:`Time-based pricing` on the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:104 +msgid "A subscription product can still be sold as a regular product, by adding it to a quotation and *not* selecting a :guilabel:`Recurrence` on the quotation." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:110 +msgid ":doc:`Pricelists <../sales/products_prices/prices/pricing>` can be used with subscription products to give special pricing to customers included in pricelists." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:113 +msgid "This can be configured either in the :guilabel:`Time-based pricing` tab of the product form, or on the pricelist form in the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:116 msgid "To create recurring price rules for specific pricelists in the :guilabel:`Time-based pricing` tab of the product form, select a pricelist in the :guilabel:`Pricelist` column." msgstr "" @@ -7329,22 +9214,42 @@ msgstr "" msgid "Pricelists in the \"Time-based pricing\" tab of the product form." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:94 +#: ../../content/applications/sales/subscriptions/products.rst:123 msgid "When pricelists are added to the :guilabel:`Time-based pricing` tab, the pricelist form in the *Sales* app is automatically updated." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:97 -msgid "Time-based pricing rules can also be configured directly on the pricelist form. To do this, go to :menuselection:`Sales --> Products --> Pricelists` and select a pricelist (or click :guilabel:`New` to create a new pricelist). In the :guilabel:`Time-based rules` tab, click :guilabel:`Add a line`." +#: ../../content/applications/sales/subscriptions/products.rst:126 +msgid "Time-based pricing rules can also be configured directly on the pricelist form." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:101 -msgid "Then, select a subscription product in the :guilabel:`Products` column, and select a recurrence period in the :guilabel:`Period` column. Enter a :guilabel:`Price` for that particular product and period. Add as many lines as needed." +#: ../../content/applications/sales/subscriptions/products.rst:128 +msgid "To do this, go to :menuselection:`Sales app --> Products --> Pricelists`, and select a pricelist (or click :guilabel:`New` to create a new pricelist)." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:105 +#: ../../content/applications/sales/subscriptions/products.rst:132 +msgid "Pricelists are also accessible through the Odoo *Subscriptions* app by following the same menu steps." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:135 +msgid "Then, on the pricelist form, under the :guilabel:`Time-based rules` tab, click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:-1 +msgid "The time-based rules tab on a pricelist form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:142 +msgid "Then, select a subscription product in the :guilabel:`Products` column, and select a recurrence period in the :guilabel:`Period` column. Lastly, enter a :guilabel:`Price` for that particular product and period. Add as many lines as needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:146 msgid "When :guilabel:`Time-based rules` are added to the pricelist form, the :guilabel:`Time-based pricing` tab of the product form is automatically updated." msgstr "" +#: ../../content/applications/sales/subscriptions/products.rst:150 +msgid ":doc:`ecommerce`" +msgstr "" + #: ../../content/applications/sales/subscriptions/renewals.rst:3 msgid "Renew a subscription" msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index c8e1be6dc..aff1cc192 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-09 13:19+0000\n" +"POT-Creation-Date: 2023-12-19 09:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -51,7 +51,7 @@ msgid "Configuration" msgstr "" #: ../../content/applications/services/field_service/default_warehouse.rst:18 -msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database." +msgid "To set up a user default warehouse, the :doc:`storage locations ` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database." msgstr "" #: ../../content/applications/services/field_service/default_warehouse.rst:23 @@ -59,7 +59,7 @@ msgid "You can either set it up :ref:`for your profile \n" "Language-Team: LANGUAGE \n" @@ -407,7 +407,7 @@ msgid "Own shipping methods" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:17 -msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :doc:`Fixed Price `, :doc:`Based on Rules `, and :guilabel:`Pickup in store`." +msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :doc:`Fixed Price `, :doc:`Based on Rules `, and :guilabel:`Pickup in store`." msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26 @@ -419,21 +419,21 @@ msgid ":guilabel:`Pickup in store` must first be **enabled** in the settings (:m msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:34 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/invoicing`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/multipack`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:37 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/cancel`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42 @@ -445,20 +445,20 @@ msgid "Another solution is to use one of the integrations with an existing shipp msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/labels`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55 @@ -1251,7 +1251,7 @@ msgid "Price per unit" msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:56 -msgid "It is possible to display a :doc:`price per unit ` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`." +msgid "It is possible to display a :doc:`price per unit ` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`." msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:-1 @@ -1271,7 +1271,7 @@ msgid "Pay attention that having the price per unit may be **mandatory** in some msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:78 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`" +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:83 @@ -3413,61 +3413,169 @@ msgid "Ratings" msgstr "" #: ../../content/applications/websites/livechat/ratings.rst:5 -msgid "Giving users the opportunity to rate their interactions can help you improving the experience you offer. That means staying on top of your customers' needs, besides keeping track of your operatorsā€™ performances." +msgid "At the end of a *Live Chat* conversation, customers have the opportunity to rate the quality of support they received from the live chat *operator*. Customers provide ratings as soon as they close the conversation. This allows operators to receive immediate feedback on their performance. It also allows customers the chance to share any final comments before leaving the chat window." msgstr "" -#: ../../content/applications/websites/livechat/ratings.rst:10 -msgid "Customer Rating" +#: ../../content/applications/websites/livechat/ratings.rst:11 +msgid "Rate live chat conversations" msgstr "" -#: ../../content/applications/websites/livechat/ratings.rst:12 -msgid "Once the user chooses to close the chat window, he can rate his interaction." +#: ../../content/applications/websites/livechat/ratings.rst:13 +msgid "Customers end a *live chat* conversation by clicking the :guilabel:`X` in the upper right-hand corner of the chat window. They are then prompted to select an icon that reflects their level of satisfaction. The icons represent the following ratings:" msgstr "" -#: ../../content/applications/websites/livechat/ratings.rst:14 -msgid "If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing for an explanation is shown." +#: ../../content/applications/websites/livechat/ratings.rst:17 +msgid "**Satisfied** - *green smiling face*" msgstr "" -#: ../../content/applications/websites/livechat/ratings.rst:15 -msgid "A copy of the conversation can also be sent by email." +#: ../../content/applications/websites/livechat/ratings.rst:18 +msgid "**Okay** - *yellow neutral face*" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:19 +msgid "**Dissatisfied** - *red frowning face*" msgstr "" #: ../../content/applications/websites/livechat/ratings.rst:-1 -msgid "View of the chat window from a userā€™s side for Odoo Live Chat" +msgid "View of the chat window from a user's side for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat/ratings.rst:22 -msgid "The rating is shown on the chat window itself for the operator." +#: ../../content/applications/websites/livechat/ratings.rst:26 +msgid "When customers end a conversation, a field marked :guilabel:`Receive a copy of this conversation` appears under the *ratings* icons. Customers can enter their email either before or after they submit a rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:30 +msgid "If the customer selects :guilabel:`Satisfied (smile)` icon, they are presented with a thank you message and a :guilabel:`Close Conversation` link." msgstr "" #: ../../content/applications/websites/livechat/ratings.rst:-1 -msgid "View of a chat window from an operatorā€™s side highlighting a rating for Odoo Live Chat" -msgstr "" - -#: ../../content/applications/websites/livechat/ratings.rst:28 -msgid "And under :menuselection:`Report --> Customer Ratings`." -msgstr "" - -#: ../../content/applications/websites/livechat/ratings.rst:-1 -msgid "View of the customer ratings page in Odoo Live Chat" -msgstr "" - -#: ../../content/applications/websites/livechat/ratings.rst:35 -msgid "Make the rating public" +msgid "View of customer's live chat window with thank you message." msgstr "" #: ../../content/applications/websites/livechat/ratings.rst:37 -msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel form, click on *Go to Website* and on *Unpublished*, to publish the rating of that channel on your website." +msgid "If the customer selects either :guilabel:`Okay (neutral)` icon or :guilabel:`Dissatisfied (frown)` icon, a text box will appear. Customers can add comments in this text box to explain why they chose this rating. This message will be sent to the live chat operator, along with the rating icon." msgstr "" #: ../../content/applications/websites/livechat/ratings.rst:-1 -msgid "View of the public ratings in the website for Odoo Live Chat" +msgid "View of a chat window from an operator's window highlighting a rating for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat/ratings.rst:45 +#: ../../content/applications/websites/livechat/ratings.rst:46 +msgid "Publish customer ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:48 +msgid "To publish a channel's ratings on the website, first navigate to a live chat channel's record by going to the :menuselection:`Live Chat` app and clicking on the kanban card for that team. Then click on the :guilabel:`Go to Website` smart button. This will open the :guilabel:`Live Chat Channel Statistics` page." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:53 +msgid "In the upper right corner of the page, click the red :guilabel:`Unpublished` slider. The slider changes from :guilabel:`Unpublished` to :guilabel:`Published`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:-1 +msgid "View of the published ratings on the portal for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:61 +msgid "The customer notes that are submitted with the rating will *not* be published on the website. These are kept internal. Only a statistical overview of the operators' performance for the *channel* appears on the website." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:66 +msgid "Add ratings page to site" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:68 +msgid "Once the rating page has been published, it has to be manually added to the website. To do this, go to the main Odoo dashboard and open the *Website* application. :menuselection:`Website app--> Site --> Content --> Pages`, then click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:72 +msgid "This will open a :guilabel:`New Page` pop-up window. In the :guilabel:`Page Title` field, enter `livechat`. This acts as the URL for the published webpage." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:76 +msgid "The URL *must* be named `livechat` in order for the database to recognize and connect the ratings page. After the page has been published, the page title can be changed later under the :guilabel:`Menu Editor`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:80 +msgid "Click :guilabel:`Create`, and the newly created webpage will open. The :guilabel:`Webpage Editor` appears in the right panel." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:83 +msgid "The page lists the names of the :guilabel:`Live Chat Channels` whose ratings pages have been published. On the left side of the channel name is a speech bubble icon, which users can click on to go to the ratings' page for the respective channel." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:-1 +msgid "View of the webpage for Live Chat ratings emphasizing the channel icon." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:91 +msgid "Make any desired changes or additions to this page, then click :guilabel:`Save` in the top right of the webpage editor. The website editor side panel closes, and the webpage remains on the screen." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:94 +msgid "To publish the `livechat` webpage, return to the list of webpages by navigating to :menuselection:`Site --> Content --> Pages`. Click the checkbox to the left of `livechat` in the list of pages to select the page and highlight the line. Then, click the checkbox under the column labeled :guilabel:`Is Published`. The field with the checkbox is highlighted in white. Click the checkbox a second time to activate the :guilabel:`Is Published` box. The webpage is now published." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:-1 +msgid "View of the list of pages for a website with the 'is published' box emphasized." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:104 +msgid "Once the page has been added to the site, ratings are set to be published by default. However, individual ratings can be manually selected to be hidden from the public. The rating will still be included in internal reports, and can still be viewed by internal teams. However, public website visitors and portal users will not have access." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:109 +msgid "See :ref:`Hide individual ratings ` for more information." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:112 +msgid "Customer ratings report" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:114 +msgid "The :guilabel:`Customer Ratings` report (:menuselection:`Live Chat --> Report --> Customer Ratings`) displays an overview of the ratings received on individual support tickets, as well as any additional comments submitted with the rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:-1 +msgid "View of the customer ratings report in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:122 +msgid "The report defaults to a kanban view, with each rating represented by a different card. To switch to a different view, click on one of the icons in the upper-right corner of the screen. The report is available in *list* view, *pivot* view, and *graph* view." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:126 +msgid "Click on an individual rating to see additional details about the conversation, and the rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:131 +msgid "Hide individual ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:133 +msgid "Ratings are set to be published by default. However, individual ratings can be manually selected to be hidden from the public. The rating will still be included in internal reports, and can still be viewed by internal teams. However, public website visitors and portal users will not have access." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:137 +msgid "To hide a rating, go to :menuselection:`Live Chat app --> Reports --> Customer Ratings`. Click on the kanban card for the rating to be hidden. On the individual rating's detail page, check the box labeled :guilabel:`Visible Internally Only`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:-1 +msgid "View of an individual rating's detail page with the visible internally setting checked." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:146 +msgid ":doc:`/applications/websites/livechat`" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:147 msgid ":doc:`responses`" msgstr "" +#: ../../content/applications/websites/livechat/ratings.rst:148 +msgid ":doc:`/applications/websites/website`" +msgstr "" + #: ../../content/applications/websites/livechat/responses.rst:3 msgid "Commands and canned responses" msgstr "" @@ -4348,63 +4456,199 @@ msgid "Add a language selector menu." msgstr "" #: ../../content/applications/websites/website/configuration/unsplash.rst:3 -msgid "Unsplash (free images)" +msgid "Unsplash" msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:6 -msgid "Generate an Unsplash access key" +#: ../../content/applications/websites/website/configuration/unsplash.rst:5 +msgid "**Unsplash** is a recognized stock photography library integrated with Odoo." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:9 -msgid "**As an Odoo Online user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash information since you will use our own Odoo Unsplash key in a transparent way." +#: ../../content/applications/websites/website/configuration/unsplash.rst:7 +msgid "If your database is hosted on **Odoo Online**, you can access Unsplash pictures without configuration." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:13 -msgid "Generate an Unsplash access key for non-Odoo Online users" +#: ../../content/applications/websites/website/configuration/unsplash.rst:10 +msgid "If your database is hosted on **Odoo.sh or on-premise**, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:12 +msgid "To **generate an Unsplash access key**, create or sign in to an `Unsplash account `_." msgstr "" #: ../../content/applications/websites/website/configuration/unsplash.rst:15 -msgid "Create an account on `Unsplash.com `_." +msgid "Access your `applications dashboard `_, click :guilabel:`New Application`, select all checkboxes, and click :guilabel:`Accept terms`." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:17 -msgid "Go to your `applications dashboard `_ and click on **New Application**." +#: ../../content/applications/websites/website/configuration/unsplash.rst:18 +msgid "In the pop-up window, enter your :guilabel:`Application Name`, starting with the prefix `Odoo:` (e.g., `Odoo: connection`), so Unsplash recognizes it as an Odoo instance. Then, add a :guilabel:`Description` and click :guilabel:`Create application`." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:23 -msgid "Accept the conditions and click on **Accept terms**." +#: ../../content/applications/websites/website/configuration/unsplash.rst:22 +msgid "On the application details page, scroll down to the :guilabel:`Keys` section and copy the :guilabel:`Access Key` and :guilabel:`Application ID`." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:28 -msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**." +#: ../../content/applications/websites/website/configuration/unsplash.rst:25 +msgid "In Odoo, go to :menuselection:`General Settings` and enable the :guilabel:`Unsplash Image Library` feature. Then, enter the Unsplash :guilabel:`Access Key` and :guilabel:`Application ID`." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:35 -msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**." +#: ../../content/applications/websites/website/configuration/unsplash.rst:29 +msgid "As a non-Odoo Online user, you are limited to a test key with a maximum of 50 Unsplash requests per hour." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:42 -msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour." +#: ../../content/applications/websites/website/mail_groups.rst:3 +msgid "Mail groups" msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:46 -msgid "Generate an Unsplash application ID" +#: ../../content/applications/websites/website/mail_groups.rst:5 +msgid "The **mail groups** feature allows website visitors to have a public discussion by email. They can join a group to receive emails from other group members (i.e., website users who have subscribed to the group) and send new ones to all group members." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:49 -msgid "You should first create and set up your Unsplash application." +#: ../../content/applications/websites/website/mail_groups.rst:9 +msgid "To activate the feature, :ref:`install ` the :guilabel:`Website Mail Group` (`website_mail_group`) module." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:51 -msgid "Go to your `applications dashboard `_ and click on your newly created Unsplash application under **Your applications**." +#: ../../content/applications/websites/website/mail_groups.rst:13 +msgid "The **mail groups** feature is not to be confused with the :doc:`../../marketing/email_marketing/mailing_lists` in the Email Marketing app." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:57 -msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/``" +#: ../../content/applications/websites/website/mail_groups.rst:19 +msgid "Configuring mail groups" msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:65 -msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction." +#: ../../content/applications/websites/website/mail_groups.rst:21 +msgid "To configure mail groups, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:23 +msgid "Configure a custom email alias domain by accessing the **General settings**, scrolling down to the :guilabel:`Discuss` section, enabling the :guilabel:`Custom Email Server` feature, and entering the :guilabel:`Alias domain` (e.g., `@mycompany.com`)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:26 +msgid "Go to :menuselection:`Website --> Configuration --> Mailing Lists`, then click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:27 +msgid "Specify a :guilabel:`Group Name`, the :guilabel:`Email Alias`, and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:28 +msgid "Enable :guilabel:`Moderate this group` and specify the :guilabel:`Moderators` if you wish to :ref:`moderate messages ` from this group. Alternatively, if the group is not moderated, you can define :guilabel:`Responsible Users` who can manage the messages in the group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:32 +msgid "In the :guilabel:`Privacy` tab, define who can subscribe to the mail group:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:34 +msgid ":guilabel:`Everyone`: to make the mail group public so anyone can subscribe to it;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:35 +msgid ":guilabel:`Members only`: to only allow users defined as members to subscribe to the mail group;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:36 +msgid ":guilabel:`Selected group of users`: to only allow users from the :guilabel:`Authorized group` to subscribe to the mail group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:39 +msgid "If the mail group is moderated, you can automatically notify authors when their message is pending moderation by enabling :guilabel:`Automatic notification` in the :guilabel:`Notify Members` tab and writing the :guilabel:`Notification message`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:42 +msgid "If you wish to send out guidelines to new subscribers, enable :guilabel:`Send guidelines to new subscribers` and write them in the :guilabel:`Guidelines` tab. This is particularly useful when the mail group is moderated." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:47 +msgid "Using mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:50 +msgid "Subscribing/unsubscribing" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:52 +msgid "Based on the :ref:`configuration of the mail group `, users can subscribe to and unsubscribe from mail groups from the website page (`/groups` by default)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:-1 +msgid "Mail group web page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:58 +msgid "Internal users can also do this from :menuselection:`Website --> Configuration --> Mailing Lists`, using the :guilabel:`Join` and :guilabel:`Leave` buttons." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:62 +msgid "Sending messages" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:64 +msgid "To send messages to a mail group, website users can email the :ref:`mail group's email address `. Internal users can also create messages directly from Odoo. To do so, go to :menuselection:`Website --> Configuration --> Mailing Lists`, select the mail group, click the :guilabel:`Emails` smart button, and click :guilabel:`New`. Then, fill in the fields and click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:71 +msgid "The list of messages can also be accessed by selecting the group from the `/groups` website page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:73 +msgid "Group members can also unsubscribe from the group, access the mail group page, and send emails to the group using the URLs in the footer of any group email they have received." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "URLs in the footer of a group email." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:82 +msgid "Moderating mail group messages" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:84 +msgid "If the :guilabel:`Moderate this group` feature has been enabled for the :ref:`mail group `, one of the :guilabel:`Moderators` must approve the group's messages before they are dispatched to the other members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:88 +msgid "To moderate messages, go to :menuselection:`Website --> Configuration --> Mailing Lists`, select the mail group, and click the :guilabel:`To review` smart button. You can moderate messages using the buttons at the end of the message line or select a message to view its content and moderate it accordingly." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "Moderation buttons in the message line." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:96 +msgid "The following actions are available:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:98 +msgid ":guilabel:`Accept`: to accept the email and send it to the mail group members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:99 +msgid ":guilabel:`Reject`: to reject the email. In the pop-up window that opens, click :guilabel:`Reject Silently` to reject the email without notifying the author, or specify an explanation for rejecting the message, then click :guilabel:`Send & Reject` to reject the message and send the explanation to the author." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:103 +msgid ":guilabel:`Whitelist`: to whitelist the author, i.e. automatically accept all of their emails. As a result, a :ref:`moderation rule ` is created for the author's email address with the status :guilabel:`Always allow`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:106 +msgid ":guilabel:`Ban`: to blacklist the author, i.e. automatically discard all their emails. In the pop-up window that opens, click :guilabel:`Ban` to ban the author without notifying them, or specify an explanation, then click :guilabel:`Send & Ban` to ban the author and send them the explanation. As a result, a :ref:`moderation rule ` is created for the author's email address with the status :guilabel:`Permanent ban`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:113 +msgid "Messages can also be moderated from the group's list of messages. Go to :menuselection:`Website --> Groups --> Mailing List Groups`, select the mail group and click the :guilabel:`Emails` smart button." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:120 +msgid "Whitelisting/Blacklisting authors" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:122 +msgid "You can whitelist or blacklist an author either directly :ref:`from a mail group message `, or by creating a moderation rule. To do so, go to :menuselection:`Website --> Configuration --> Moderation Rules` and click :guilabel:`New`. Then, select the :guilabel:`Group`, specify the author's :guilabel:`Email` and set the :guilabel:`Status` field." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:129 +msgid "You can also access the mail group's moderation rules by going to :menuselection:`Website --> Configuration --> Mailing Lists`, selecting the group, then clicking the :guilabel:`Moderations` smart button." msgstr "" #: ../../content/applications/websites/website/pages.rst:5 @@ -5520,30 +5764,66 @@ msgid "Website analytics helps website owners understand how people use their si msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:8 -msgid "You can track your Odoo website's traffic using :ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use. The Plausible analytics dashboard is also integrated into Odoo and can be accessed via :menuselection:`Website --> Reporting --> Analytics`." +msgid "You can track your Odoo website's traffic using :ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:16 -msgid "Plausible.io" +#: ../../content/applications/websites/website/reporting/analytics.rst:12 +msgid "The Plausible analytics dashboard is also integrated into Odoo and can be accessed via :menuselection:`Website --> Reporting --> Analytics`." msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:18 -msgid "If your database is hosted on Odoo Online, the Plausible.io integration is available in Odoo for free. To enable the feature, go to :menuselection:`Website --> Configuration --> Settings`, then, in the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics` and click :guilabel:`Save`. You can then access your Plausible analytics dashboard by going to :menuselection:`Website --> Reporting --> Analytics`." +msgid "Plausible.io" msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:24 -msgid "If your database is hosted on Odoo.sh or on-premise, or if you wish to use your own Plausible.io account, proceed as follows:" +#: ../../content/applications/websites/website/reporting/analytics.rst:20 +msgid "Odoo hosts its own Plausible.io server and provides a free and ready-to-work Plausible.io solution for **Odoo Online** databases. Go to :menuselection:`Website --> Configuration --> Settings`, and enable the feature in the :guilabel:`SEO` section. Odoo automatically creates and sets up your account. You can start using it by going to :menuselection:`Website --> Reporting --> Analytics`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:27 +#: ../../content/applications/websites/website/reporting/analytics.rst:26 +msgid "**If you already have a Plausible.io account** and you want to connect it to your Odoo Online database, you must create two `ir.config.parameters` to use Plausible.io's servers. To do so, enable the :ref:`developer mode ` and go to :menuselection:`General Settings --> Technical -- System Parameters`. Click :guilabel:`New` and fill in the following :guilabel:`Key` and :guilabel:`Value` fields:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:35 +msgid "Key" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:36 +msgid "Value" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:37 +msgid "`website.plausible_script`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:38 +msgid "`https://plausible.io/js/plausible.js`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:39 +msgid "`website.plausible_server`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:40 +msgid "`https://plausible.io`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:42 +msgid "Then, follow the steps below to connect your existing account with Plausible.io servers." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:44 +msgid "If your database is hosted on **Odoo.sh** or **On-premise**, or if you wish to use your own Plausible.io account, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:47 msgid "Create or sign in to a Plausible account using the following link: ``_." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:28 +#: ../../content/applications/websites/website/reporting/analytics.rst:48 msgid "If you are creating a new account, go through the registration and activation steps. When asked to provide your website details, add its :guilabel:`Domain` without including `www` (e.g., `example.odoo.com`) and change the :guilabel:`Reporting Timezone` if necessary. Click :guilabel:`Add snippet` to proceed to the next step. Ignore the :guilabel:`Add JavaScript snippet` instructions and click :guilabel:`Start collecting data`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:33 +#: ../../content/applications/websites/website/reporting/analytics.rst:53 msgid "Once done, click the Plausible logo in the upper-left part of the page to access your `list of websites `_, then click the gear icon next to the website." msgstr "" @@ -5551,11 +5831,11 @@ msgstr "" msgid "Click the gear icon in the list of websites." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:39 +#: ../../content/applications/websites/website/reporting/analytics.rst:59 msgid "In the sidebar, select :guilabel:`Visibility`, then click :guilabel:`+ New link`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:40 +#: ../../content/applications/websites/website/reporting/analytics.rst:60 msgid "Enter a :guilabel:`Name`, leave the :guilabel:`Password` field empty, as the Plausible analytics dashboard integration in Odoo doesn't support it, then click :guilabel:`Create shared link`." msgstr "" @@ -5563,7 +5843,7 @@ msgstr "" msgid "Credentials creation for the new shared link" msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:46 +#: ../../content/applications/websites/website/reporting/analytics.rst:66 msgid "Copy the shared link." msgstr "" @@ -5571,44 +5851,44 @@ msgstr "" msgid "Copy the shared link URL from Plausible.io" msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:51 -#: ../../content/applications/websites/website/reporting/analytics.rst:98 +#: ../../content/applications/websites/website/reporting/analytics.rst:71 +#: ../../content/applications/websites/website/reporting/analytics.rst:118 msgid "In Odoo, go to :menuselection:`Website --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:52 +#: ../../content/applications/websites/website/reporting/analytics.rst:72 msgid "In the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics`, then paste the :guilabel:`Shared Link` and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:56 +#: ../../content/applications/websites/website/reporting/analytics.rst:76 msgid "If you have :doc:`multiple websites <../configuration/multi_website>`, add your websites to your Plausible.io account by going to ``_ and clicking :guilabel:`+ Add website`. In Odoo, in the **Website settings**, make sure to select the website in the :guilabel:`Settings of Website` field before pasting the :guilabel:`Shared link`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:62 +#: ../../content/applications/websites/website/reporting/analytics.rst:82 msgid "Odoo automatically pushes two custom goals: `Lead Generation` and `Shop`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:65 +#: ../../content/applications/websites/website/reporting/analytics.rst:85 msgid "`Plausible Analytics documentation `_" msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:70 +#: ../../content/applications/websites/website/reporting/analytics.rst:90 msgid "Google Analytics" msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:72 +#: ../../content/applications/websites/website/reporting/analytics.rst:92 msgid "To follow your Odoo website's traffic with Google Analytics:" msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:74 +#: ../../content/applications/websites/website/reporting/analytics.rst:94 msgid "Create or sign in to a Google account using the following link: ``_." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:75 +#: ../../content/applications/websites/website/reporting/analytics.rst:95 msgid "If you are setting up Google Analytics for the first time, click :guilabel:`Start measuring` and go through the account creation step." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:77 +#: ../../content/applications/websites/website/reporting/analytics.rst:97 msgid "If you already have a Google Analytics account, sign in and click the gear icon in the bottom-left corner of the page to access the **Admin** page. Then, click :guilabel:`+ Create Property`." msgstr "" @@ -5616,11 +5896,11 @@ msgstr "" msgid "Measurement ID in Google Analytics." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:84 +#: ../../content/applications/websites/website/reporting/analytics.rst:104 msgid "Complete the next steps: `property creation `_, business details, and business objectives." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:86 +#: ../../content/applications/websites/website/reporting/analytics.rst:106 msgid "When you reach the **Data collection** step, choose the :guilabel:`Web` platform." msgstr "" @@ -5628,23 +5908,23 @@ msgstr "" msgid "Choose a platform for your Google Analytics property." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:91 +#: ../../content/applications/websites/website/reporting/analytics.rst:111 msgid "Set up your data stream: Specify your :guilabel:`Website URL` and a :guilabel:`Stream name`, then click :guilabel:`Create stream`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:93 +#: ../../content/applications/websites/website/reporting/analytics.rst:113 msgid "Copy the :guilabel:`Measurement ID`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:99 +#: ../../content/applications/websites/website/reporting/analytics.rst:119 msgid "In the :guilabel:`SEO` section, enable :guilabel:`Google Analytics`, then paste the :guilabel:`Measurement ID` and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:103 +#: ../../content/applications/websites/website/reporting/analytics.rst:123 msgid "If you have :doc:`multiple websites <../configuration/multi_website>` with separate domains, it is recommended to create `one property `_ per domain. In Odoo, in the **Website settings**, make sure to select the website in the :guilabel:`Settings of Website` field before pasting the :guilabel:`Measurement ID`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:109 +#: ../../content/applications/websites/website/reporting/analytics.rst:129 msgid "`Google documentation on setting up Analytics for a website `_" msgstr ""