NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[I18N] *: export source terms

Browse Source 
closes odoo/documentation#4144

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-04-13 05:58:40 +00:00
parent b4ee060aaa
commit c65b9863a7
7 changed files with 3321 additions and 2658 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

764
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

338
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-04-06 08:12+0000\n"
"POT-Creation-Date: 2023-04-13 05:55+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -225,11 +225,10 @@ msgid "Due to specific requirements in Azure's OAuth implementation, Microsoft A
msgstr ""
#: ../../content/applications/general/auth/azure.rst:9
msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
msgid ":doc:`../../productivity/calendar/outlook`"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:10
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
#: ../../content/applications/general/email_communication/email_servers.rst:67
msgid ":doc:`/administration/maintain/azure_oauth`"
msgstr ""
@ -247,11 +246,10 @@ msgid "This is particularly helpful if your organization uses Google Workforce a
msgstr ""
#: ../../content/applications/general/auth/google.rst:12
msgid ":doc:`/applications/general/calendars/google/google_calendar_credentials`"
msgid ":doc:`../../productivity/calendar/google`"
msgstr ""
#: ../../content/applications/general/auth/google.rst:13
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
#: ../../content/applications/general/email_communication/email_servers.rst:66
msgid ":doc:`/administration/maintain/google_oauth`"
msgstr ""
@ -446,334 +444,6 @@ msgstr ""
msgid "In **Template User**, indicate a template for the new profiles created. If left blanked, the admin profile will be used as template."
msgstr ""
#: ../../content/applications/general/calendars.rst:5
msgid "Calendars"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
msgid "Synchronize Google Calendar with Odoo"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
msgid "Synchronize Google Calendar with Odoo to see and manage meetings from both platforms (updates go in both directions). This integration helps organize your schedule so you never miss a meeting."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
msgid ":doc:`/applications/general/auth/google`"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
msgid "Setup in Google"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
msgid "Enable Google Calendar API"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
msgid "Begin by creating a new Google API project and enabling the Google Calendar API. Then, go to the `Google API Console <https://console.developers.google.com>`_ and log into your Google account."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
msgid "If this is your first time visiting this page, Google will prompt you to enter a country and agree to the Terms of Service. Select a country from the drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
msgid "Next, click :guilabel:`Select a project` and select or create an API project to store credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Create a new API project to store credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
msgid "Give the API Project a clear name like \"Odoo Sync\" so you can easily find it."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
msgid "Then, open the API Project and click :guilabel:`Enable APIs and Services`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Enable APIs and Services on the API Project."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
msgid "After that, search for *Google Calendar API* using the search bar and select :guilabel:`Google Calendar API` from the search results. Click :guilabel:`Enable`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Enable the Google Calendar API."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
msgid "Create credentials"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
msgid "Now that you have created your API project and enabled the Google Calendar API, you need to create credentials. Begin by clicking :guilabel:`Create Credentials`. Google will then guide you through four steps to create your API credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
msgid "In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google Calendar API` and :guilabel:`User Data` options. Then, click :guilabel:`Next`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Select Google Calendar API and User Data for the Credential Type."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
msgid "In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the :guilabel:`App name` field, select your email address for the :guilabel:`User support email` field, and type your email address for the :guilabel:`Developer contact information` section. Then, click :guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
msgid "Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
msgid "In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website application` for the :guilabel:`Application Type` field and type *My Odoo Database* for the :guilabel:`Name`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
msgid "Under the :guilabel:`Authorized JavaScript Origins` section, click :guilabel:`+ Add URI` and type your company's Odoo URL address."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
msgid "Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ Add URI` and type your company's Odoo URL address followed by */google_account/authentication*. Finally, click :guilabel:`Create` and :guilabel:`Done`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Add the authorized JavaScript origins and the authorized redirect URIs."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
msgid "After successfully creating a new API project, enabling the Google Calendar API, and generating the Google Calendar API credentials, you should now have a Client ID and Client Secret."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
msgid "Client ID & Client Secret"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
msgid "The **Client ID** and the **Client Secret** are both needed to connect Google Calendar to Odoo. Find the Client ID and the Client Secret by opening the Google Cloud Platform navigation menu and going to :menuselection:`API & Services --> Credentials --> OAuth 2.0 Client IDs`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
msgid "Next, locate the credentials you just created for the Google Calendar API. Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page will redirect to the edit page, where you can view the Client ID and the Client Secret."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Click Edit OAuth Client to view the credential details."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
msgid "Setup in Odoo"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
msgid "Once the Client ID and the Client Secret are located, open the Odoo database and go to :menuselection:`Settings --> General Settings --> Integrations --> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "The Google Calendar checkbox in General Settings."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
msgid "Next, copy and paste the Client ID and the Client Secret from the Google Calendar API Credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
msgid "Finally, open the Calendar module in Odoo and click on the :guilabel:`Google` sync button to sync Google Calendar with Odoo."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Click the Google sync button in Odoo Calendar to sync Google Calendar with Odoo."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
msgid "The first time you sync your Google Calendar with Odoo, the page will redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` to authorize Odoo to access Google Calendar."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Give Odoo permission to access Google Calendar."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:-1
msgid "Successfully sync between Odoo and Google Calendar."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
msgid "Synchronize Outlook Calendar with Odoo"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
msgid "Synchronizing a user's Outlook Calendar with Odoo is useful for keeping track of their tasks and appointments across all related applications."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
msgid ":doc:`/applications/general/auth/azure`"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
msgid "Register the application with Microsoft Azure"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
msgid "To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account is needed. Creating an account is free for users who have never tried or paid for Azure. For more information, `click here <https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
msgid "Refer to `Microsoft's documentation <https://docs.microsoft.com/en-us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to set up an Azure AD Tenant (also called an *environment*), which is a representation of an organization to manage and register apps."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
msgid "Then, `Register an Application <https://docs.microsoft.com/en-us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
msgid "When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and copy the Odoo database URI (URL) followed by `/microsoft_account/authentication`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
msgid "Enter `https://www.companyname.odoo.com/microsoft_account/authentication` for the :guilabel:`Redirect URI`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:-1
msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Azure AD portal."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
msgid "For more information on the restrictions and limitations of URIs, `check this page <https://docs. microsoft.com/en-us/azure/active-directory/develop/reply-url>`_."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
msgid "Regarding the application credentials, the user *must* add a client secret, which allows Odoo to authenticate itself, requiring no interaction from the user's side. :guilabel:`Certificates` are optional."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
msgid "To do add a client secret, click :guilabel:`Add a certificate or secret` and then click :guilabel:`New client secret`. Next, type a :guilabel:`Description` and select when the client secret :guilabel:`Expires`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months), so there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to generate the client secret (:guilabel:`Secret ID`)."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
msgid "Configuration in Odoo"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
msgid "In the Odoo database, go to :menuselection:`Settings --> General Settings --> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:-1
msgid "The \"Outlook Calendar\" setting activated in Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
msgid "From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:-1
msgid "The \"Client ID\" in the Microsoft Azure portal."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
msgid "In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the :guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:-1
msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
msgid "Finally, on the Odoo :menuselection:`Settings --> General Settings` page, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
msgid "Sync with Outlook"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
msgid "Odoo highly recommends testing the Outlook calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Outlook Calendar with the user's production database."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
msgid "If the user has any past, present, or future events on their Odoo calendar before syncing their Outlook calendar, Outlook will treat the events pulled from Odoo's calendar during the sync as new events, causing an email notification to be sent from Outlook to all the event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
msgid "To avoid unwanted emails being sent to all past, present, and future event attendees, the user must add the events from the Odoo calendar to the Outlook calendar before the first ever sync, delete the events from Odoo, and then start the sync."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Outlook will still send a notification to all event participants every time an event is edited (created, deleted, unarchived, or event date/time changed), with no exceptions. This is a limitation that cannot be fixed from Odoo's side."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:112
msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
msgid "Sync Odoo Calendar and Outlook"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:-1
msgid "The \"Outlook\" sync button in Odoo Calendar."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The configuration of Microsoft's Azure account is only done once, as Azure AD tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:143
msgid ":doc:`../../../productivity/mail_plugins/outlook`"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
msgid ":doc:`../google/google_calendar_credentials`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:5
msgid "Developer Mode (debug mode)"
msgstr ""
@ -3206,7 +2876,7 @@ msgid "To change the language for a different user, choose :menuselection:`Users
msgstr ""
#: ../../content/applications/general/users/language.rst:61
msgid ":doc:`../../websites/website/publish/translate`"
msgid ":doc:`../../websites/website/configuration/translate`"
msgstr ""
#: ../../content/applications/general/users/manage_users.rst:3

663
locale/sources/inventory_and_mrp.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-04-06 08:12+0000\n"
"POT-Creation-Date: 2023-04-13 05:55+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -351,7 +351,6 @@ msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/two_steps.rst:6
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:14
#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:13
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:18
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16
#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:45
#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:14
@ -368,6 +367,7 @@ msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:14
#: ../../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/purchase/manage_deals/control_bills.rst:10
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31
msgid "Configuration"
msgstr ""
@ -421,103 +421,83 @@ msgid "Warehouse Management"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:3
msgid "Send Products to Customers Directly from Suppliers (Drop-shipping)"
msgid "Use dropshipping to ship directly from suppliers to customers"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:6
msgid "What is Drop-Shipping?"
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/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/management/delivery/dropshipping.rst:8
msgid "Drop-Shipping is a system that allows orders taken from your store to be shipped straight from your supplier to your customer. On a usual delivery system, products are sent from your supplier to your warehouse to be put in stock and then shipped to your customers after ordering."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:12
msgid "Configure products to be dropshipped"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:13
msgid "With drop-shipping, no item is stocked. When a customer places an order in your shop, the item is delivered straight from the supplier to the customer. Therefore, the product doesn't need to get through your warehouse."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:14
msgid "To use dropshipping as a fulfillment strategy, navigate to the :guilabel:`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/management/delivery/dropshipping.rst:19
msgid "Points to be Considered while Implementing Drop-Shipping"
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:18
msgid "Next, go to the :guilabel:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the 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/management/delivery/dropshipping.rst:24
msgid "Use drop-shipping only for the products you can't or don't want to keep in stock."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/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/management/delivery/dropshipping.rst:22
msgid "One reason is that you'll always make smaller margins on items that are drop-shipped, so you should keep it only for items that take up a lot of space in your warehouse."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:26
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/management/delivery/dropshipping.rst:30
msgid "Drop-shipping is best for niche products."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:-1
msgid "The product form with a vendor specified."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:27
msgid "Chances are that products that are in high demand are being offered by large suppliers at a fraction of the price you'll be able to charge, so using a more costly shipping method won't be financially rewarding. But if your product is unique, then it makes sense!"
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:34
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/management/delivery/dropshipping.rst:33
msgid "To protect your customers from bad experiences."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:-1
msgid "Enable the Dropship option in the product inventory tab."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:33
msgid "Test drop-shipping companies for yourself beforehand and list the best ones."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:37
msgid "Make sure time is not against you."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:36
msgid "Drop-shipping should take a reasonable amount of time and surely not more than it would have taken you to handle it all by yourself. It's also nice to be able to provide your customers with a tracking number."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:42
msgid "Fulfill orders using dropshipping"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:44
msgid "Items have to be available from your supplier."
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 :guilabel:`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/management/delivery/dropshipping.rst:40
msgid "It's good to know if the product you're selling is available upstream. If you don't have that information, inform your customers that you don't hold the item in stock and that it's subject to availability from a third party."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:51
msgid "Dropship sales orders can also be created manually through the :guilabel:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for dropshipping."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:47
msgid "For more information and insights about Drop-Shipping, you can read our blog: `*What is drop-shipping and how to use it* <https://www.odoo.com/blog/business-hacks-1/post/what-is-drop-shipping-and-how-to-use-it-250>`__."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/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/management/delivery/dropshipping.rst:52
msgid "Configure Drop-Shipping"
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:58
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/management/delivery/dropshipping.rst:54
msgid "Activate the functionality in the *Purchase* application by going to :menuselection:`Configuration --> Settings`."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/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/management/delivery/dropshipping.rst:60
msgid "Then, go to the *Inventory* app, in :menuselection:`Configuration --> Settings` to activate the *Multi-Step Routes* feature. It will allow you to make the *Route* field appear on the sale order lines to specify you send a product via drop-shipping."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:66
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/management/delivery/dropshipping.rst:68
msgid "Now, in the *Sales* app, go to :menuselection:`Products --> Products`. Select the product you would like to drop-ship and add a vendor pricelist which contains the right supplier, via the purchase tab."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:-1
msgid "Validate the dropship receipt after delivery."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:76
msgid "Send Products from the Suppliers Directly to the Customers"
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:75
msgid "To view all dropship orders, simply navigate to the :guilabel:`Inventory` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:78
msgid "Create a *Sales Order* and add the product on which you just set the vendor. Add the *Route* field thanks to the widget on the right of the sale order line. Now, you are able to specify that your products’ route is *Drop-Shipping*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:89
msgid "Once the sale order is confirmed, Odoo automatically generates a *Request for Quotation* for the supplier who will proceed to the drop-shipping. You can find it in the *Purchase* app, with the sale order as *Source Document*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:97
msgid "Once this *Purchase Order* is confirmed, a *Receipt Order* is created and linked to it. The source location is the vendor location and the destination location is the customer location. Then, the product won’t go through your own stock when you validate the dropship document."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:105
msgid "You can also easily access the dropship document directly from your inventory dashboard."
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/dropshipping.rst:-1
msgid "Click the green button on the Dropship card to view all dropship orders."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/delivery/inventory_flow.rst:3
@ -1719,39 +1699,127 @@ msgid "Once all the products have been picked, click on *Validate* (on the last
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:3
msgid "Manage Stock that you don't own"
msgid "Consignment: buy and sell stock without owning it"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:5
msgid "Sometimes, suppliers can offer you to store and sell products without having to buy those items. This technique is called *consignee stock*."
msgid "Most of the time, products stored in a company's warehouse are either purchased from suppliers, or are manufactured in-house. However, suppliers will sometimes let companies store and sell products in the company's warehouse, without having to buy those items up-front. This is called *consignment*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:8
msgid "Consignee stock is a great way for manufacturers and suppliers to launch new products. As resellers may be reluctant to buy a product they are not sure to be able to sell, consignee stock will allow them to offer an item to check its market without having to pay for it in the first place."
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:10
msgid "Consignment is a useful method for suppliers to launch new products, and easily deliver to their customers. It's also a great way for the company storing the products (the consignee) to earn something back for their efforts. Consignees can even charge a fee for the convenience of storing products they don't actually own."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:14
msgid "Of course, Odoo has the ability to manage those consignee stocks through advanced settings."
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:16
msgid "Enable the consignment setting"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:20
msgid "To use this feature, go to :menuselection:`Inventory --> Configuration --> Settings` in the inventory app. Then, enable the *Consignment* feature in the *Traceability* section. Now, hit save."
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:18
msgid "To receive, store, and sell consignment stock, the feature needs to be enabled in the settings. To do this, go to :menuselection:`Inventory --> Configuration --> Settings`, and under the :guilabel:`Traceability` section, check the box next to :guilabel:`Consignment`, and then click :guilabel:`Save` to finish."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1
msgid "Enabled Consignment setting in Inventory configuration."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:28
msgid "Reception of Consignee Stock"
msgid "Receive (and store) consignment stock"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:30
msgid "When in the *Inventory* app, open the receipts and create a new reception. On the right side, you will see that a new line called *Assign Owner* has appeared. There, you can specify the partner which owns the stock."
msgid "With the feature enabled in Odoo, consignment stock can now be received into a warehouse. From the main :menuselection:`Inventory` dashboard, click into the :guilabel:`Receipts` section. Then, click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:35
msgid "Consignment stock is not actually purchased from the vendor; it is simply received and stored. Because of this, there are no quotations or purchase orders involved in receiving consignment stock. So, *every* receipt of consignment stock will start by creating manual receipts."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:39
msgid "If you are the owner, you can leave the field blank."
msgid "Choose a vendor to enter in the :guilabel:`Receive From` field, and then choose the same vendor to enter in the :guilabel:`Assign Owner` field."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:41
msgid "Once the receipt is validated, the products enter your stock but still belong to the owner. They don’t impact your inventory valuation."
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:43
msgid "Since the products received from the vendor will be owned by the same vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields must match."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:46
msgid "Once the vendor-related fields are set, enter products into the :guilabel:`Product` lines, and set the quantities to be received into the warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be changed, as well. Once all the consignment stock has been received, :guilabel:`Validate` the receipt."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1
msgid "Matching vendor fields in consignment Receipt creation."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:56
msgid "Sell and deliver consignment stock"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:58
msgid "Once consignment stock has been received into the warehouse, it can be sold the same as any other in-stock product that has the :guilabel:`Can Be Sold` option enabled on the product form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:61
msgid "To create a sales order, navigate to the :menuselection:`Sales` app, and from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, choose a customer to enter into the :guilabel:`Customer` field."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:66
msgid "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` that supplied the consignment stock received (and stored) in the warehouse."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:69
msgid "Add the consignment product under the :guilabel:`Product` column in the order lines, set the :guilabel:`Quantity`, and fill out any other pertinent product details on the form. Once the quotation is complete, click :guilabel:`Confirm`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1
msgid "Sales order of consignment stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:77
msgid "Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will become a sales order. From here, the products can be delivered by clicking on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate` to validate the delivery."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:82
msgid "Traceability and reporting of consignment stock"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:84
msgid "Although consignment stock is owned by the vendor who supplied it, and not by the company storing it in their warehouse, consignment products will *still* appear in certain inventory reports."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:87
msgid "To find inventory reports, go to :menuselection:`Inventory --> Reporting`, and choose a report to view."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:91
msgid "Since the consignee does not actually own consigment stock, these products are *not* reflected in the :guilabel:`Stock Valuation` report, and have no impact on the consignee's inventory valuation."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:96
msgid "Product moves report"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:98
msgid "To view all information about on-hand stock moves, navigate to the the :guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory --> Reporting --> Product Moves`. For consignment products, the information in this report is the same as any other product: the history of its product moves can be reviewed; the :guilabel:`Quantity Done` and :guilabel:`Reference` document are available; and its :guilabel:`Locations` are available, as well. The consignment stock will originate from :guilabel:`Partner Location/Vendors`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:106
msgid "To view a consignment product's moves by ownership, select the :guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to finish."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:-1
msgid "Consignment stock moves history."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:115
msgid "To see forecasted units of consignment stock, go to :menuselection:`Inventory --> Reporting --> Forecasted Inventory`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:119
msgid "Stock on hand report"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:121
msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consigment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:3
@ -5915,6 +5983,131 @@ msgstr ""
msgid "Quality control"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:3
msgid "Create quality alerts"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:5
msgid "Configuring quality control points is a great way to ensure that quality checks are performed at routine stages during specific operations. However, quality issues can often appear outside of these scheduled checks. Using Odoo *Quality*, users can create quality alerts for issues that are not detected by automated processes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:11
msgid ":doc:`Add quality control points <quality_control_points>`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:14
msgid "Find and fill out the quality alerts form"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:16
msgid "In some situations, it is necessary to manually create quality alerts within the *Quality* module."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:19
msgid "A helpdesk user who is notified of a product defect by a customer ticket can create an alert that brings the issue to the attention of the relevant quality team."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:22
msgid "To create a new quality alert, start from the :menuselection:`Quality` module and select :menuselection:`Quality Control --> Quality Alerts --> Create`. The quality alert form can then be filled out as follows:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:26
msgid ":guilabel:`Title`: choose a concise, yet descriptive title for the quality alert"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:27
msgid ":guilabel:`Product`: the product about which the quality alert is being created"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:28
msgid ":guilabel:`Product Variant`: the specific variant of the product that has the quality issue, if applicable"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:30
msgid ":guilabel:`Lot`: the lot number assigned to the product"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:31
msgid ":guilabel:`Work Center`: the work center where the quality issue originated"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:32
msgid ":guilabel:`Picking`: the picking operation during which the quality issue originated"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:33
msgid ":guilabel:`Team`: the quality team that will be notified by the quality alert"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:34
msgid ":guilabel:`Responsible`: the individual responsible for managing the quality alert"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:35
msgid ":guilabel:`Tags`: classify the quality alert based on user-created tags"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:36
msgid ":guilabel:`Root Cause`: the cause of the quality issue, if known"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:37
msgid ":guilabel:`Priority`: assign a priority between one and three stars to ensure more urgent issues are prioritized"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:40
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:40
msgid "The tabs at the bottom of the form can be used to provide additional information to quality teams:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:42
msgid ":guilabel:`Description`: provide additional details about the quality issue"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:43
msgid ":guilabel:`Corrective Actions`: the method for fixing affected products"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:44
msgid ":guilabel:`Preventive Actions`: procedures for preventing the issue from occurring in the future"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:46
msgid ":guilabel:`Miscellaneous`: the product vendor (if applicable), the company that produces the product, and the date assigned"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:-1
msgid "An example of a completed quality alert form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:54
msgid "Add quality alerts during the manufacturing process"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:56
msgid "Odoo enables manufacturing employees to create quality alerts within a work order without accessing the *Quality* module. From the work order tablet view, click the :guilabel:` ☰ ` hamburger menu icon in the top left corner and select :guilabel:`Quality Alert`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:-1
msgid "Access the work order menu."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:64
msgid "The quality alert form can then be filled out as detailed in the previous section. After saving the form, a new alert will appear on the :guilabel:`Quality Alerts` dashboard that can be found through the :menuselection:`Quality --> Quality Control` menu."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:69
msgid "Manage existing quality alerts"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:71
msgid "By default, quality alerts are organized in a kanban board view. The stages of the kanban board are fully configurable and alerts can be moved from one stage to the next by dragging and dropping or from within each alert. Additional options are available for viewing alerts, including graph, calendar, and pivot table views."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:77
msgid "Filter alerts based on diverse criteria like date assigned or date closed. Alerts can also be grouped by quality team, root cause, or other parameters found under the :guilabel:`Filters` button menu."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:3
msgid "Add quality controls"
msgstr ""
@ -5967,10 +6160,6 @@ msgstr ""
msgid ":guilabel:`Responsible`: add a point person to manage the status and evolution of the quality control point over time"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:40
msgid "The tabs at the bottom of the form can be used to provide additional information to quality teams:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:42
msgid ":guilabel:`Instructions`: describe the quality check to be performed"
msgstr ""
@ -6328,163 +6517,167 @@ msgid "Confirm an order in Odoo Purchase"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3
msgid "Control and know when vendor bills should be paid"
msgid "Bill control policies"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:5
msgid "With Odoo, you can define how your vendor bills are controlled. For each purchase order, you can decide when the related vendor bill should be paid: either before or after you have received your products. You can also check at a glance what is the billing status of each purchase order."
msgid "In Odoo, the *bill control* policy determines the quantities billed by vendors on every purchase order, for ordered or received quantities. The policy selected in the settings will act as the default value and will be applied to any new product created."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:9
msgid "With the 3-way matching feature, Odoo compares the information appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*, and lets you know if you should pay the bill. This way you can avoid paying incorrect or fraudulent vendor bills."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:12
msgid "To view the default bill control policy and make changes, go to :menuselection:`Purchase --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Here, there are the two :guilabel:`Bill Control` policy options: :guilabel:`Ordered quantities` and :guilabel:`Received quantities`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:14
msgid "Vendor bills default control policy"
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17
msgid "The policy selected will be the default for any new product created. The definition of each policy is as follows:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:16
msgid "As a first step, open your Purchase app and go to :menuselection:`Configuration --> Settings` to set the default bill control policy for all the products created onwards."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:20
msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:22
msgid ":guilabel:`Received quantities`: a bill is created only *after* part of the total order has been received. The products and quantities *received* are used to generate a draft bill. An error message will appear if creation of a vendor bill is attempted without receiving anything."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1
msgid "Vendor bills default control setting for new products in Odoo Purchase"
msgid "Bill control policy draft bill error message."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:23
msgid "By selecting *On ordered quantities*, you can create a vendor bill as soon as you confirm an order. The quantities mentioned in the purchase order are used to generate the draft bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:26
msgid "If you choose *On received quantities* instead, you can only create one once you have at least received some of the products you have ordered. The quantities you have received are used to generate the draft bill. If you try to create one without having received any product, you get an error message."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1
msgid "No invoiceable line error message in Odoo Purchase"
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:31
msgid "If one or two products need a different control policy, the default bill control setting can be overridden by going to the :guilabel:`Purchase` tab in a product's template and modifying its :guilabel:`Control Policy` field."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:36
msgid "Change a specific product's control policy"
msgid "Example flow: Ordered quantities"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:38
msgid "If you want to modify a specific product's control policy, go to :menuselection:`Products --> Products`, open it, click on *Edit* and go to the *Purchase tab*. There you can change a product's default bill control policy."
msgid "To complete an example workflow using the *ordered quantities* bill control policy, first go to :menuselection:`Purchase --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Ordered quantities`. Then, :guilabel:`Save` changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:47
msgid "View a purchase order's billing status"
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:42
msgid "In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for Quotation)`. Fill out the information on the quotation form, add products to the invoice lines, and click :guilabel:`Confirm Order`. Then, click :guilabel:`Create Bill`. Since the policy is set to *ordered quantities*, the draft bill can be confirmed as soon as it is created, without any products actually being received."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:49
msgid "Once you confirm an order, you can view its *Billing Status* by going to the *Other Information* tab."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:48
msgid "Example flow: Received quantities"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1
msgid "Purchase order billing status in Odoo Purchase"
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:50
msgid "To complete an example workflow using the *received quantities* bill control policy, first go to :menuselection:`Purchase --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Received quantities`. Then, :guilabel:`Save` changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:56
msgid "Below you can find a list of the different *Billing Status*, and when they are displayed, depending on the products' bill control policy."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:54
msgid "In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for Quotation)`. Fill out the information on the quotation form, add products to the invoice lines, and click :guilabel:`Confirm Order`. Then, click on the :guilabel:`Receipt smart button`. Set the quantities in the :guilabel:`Done` column to match the quantities in the :guilabel:`Demand` column, and :guilabel:`Validate` the changes. Then, in the purchase order, click :guilabel:`Create Bill` and :guilabel:`Confirm`. Since the policy is set to *received quantities*, the draft bill can be confirmed *only* when at least some of the quantities are received."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:60
msgid "**Billing status**"
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:63
msgid "3-way matching"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:60
msgid "**Conditions**"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:62
msgid "*On received quantities*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:62
msgid "*On ordered quantities*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:64
msgid "*Nothing to Bill*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:64
msgid "PO confirmed; no products received"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:64
msgid "*(Not applicable)*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:66
msgid "*Waiting Bills*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:66
msgid "All/some products received; bill not created"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:66
msgid "PO confirmed"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:68
msgid "*Fully Billed*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:68
msgid "All/some products received; draft bill created"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:68
msgid "Draft bill created"
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:65
msgid "Activating :guilabel:`3-way matching` ensures that vendor bills are only paid once some or all of the products included in the purchase order have actually been received. To activate it, go to :menuselection:`Purchase --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, click :guilabel:`3-way matching: purchases, receptions, and bills`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:72
msgid "Determine when to pay with 3-way matching"
msgid "3-way matching is *only* intended to work when the bill control policy is set to *received quantities*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:74
msgid "First, go to :menuselection:`Configuration --> Settings` and activate *3-way matching*."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:76
msgid "Pay vendor bills with 3-way matching"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:78
msgid "When :guilabel:`3-way matching` is activated, vendor bills will display the :guilabel:`Should Be Paid` field under the :guilabel:`Other Info` tab. When a new vendor bill is created, the field will be set to :guilabel:`Yes`, since a bill can't be created until at least some of the products included in a purchase order have been received."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1
msgid "3-way-matching setting in Odoo Purchase"
msgid "Draft bill should be paid field status."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:81
msgid "3-way matching is intended to work with the bill control policy set to *On received quantities*."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:88
msgid "If the total quantity of products from a purchase order has not been received, Odoo only includes the products that *have* been received in the draft vendor bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:84
msgid "Should I pay the vendor bill?"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:86
msgid "With the feature activated, your vendor bills now display the *Should Be Paid* field under the *Other info* tab."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1
msgid "Should Be Paid field under a vendor bill in Odoo Purchase"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:93
msgid "As you can't create a bill until you have received your products - and if you haven't received all of them, Odoo only includes the products you have received in the draft bill - the *Should Be Paid* status is set to *Yes* when you create one."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:91
msgid "Draft bills can be edited to increase the billed quantity, change the price of the products in the bill, and add additional products to the bill. If this is done, the :guilabel:`Should Be Paid` field status will be set to :guilabel:`Exception`. This means that Odoo notices the discrepancy, but doesn't block the changes or display an error message, since there might be a valid reason for making changes to the draft bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:97
msgid "If you edit a draft bill to increase the billed quantity, change the price, or add other products, the *Should Be Paid* status is set to *Exception*. It means Odoo notices the discrepancy, but that you might have a valid reason to have done so."
msgid "Once payment has been registered for a vendor bill and displays the green :guilabel:`Paid` banner, the :guilabel:`Should Be Paid` field status will be set to :guilabel:`No`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:101
msgid "Once the payment has been registered and mentions *Paid*, the *Should Be Paid* status is set to *No*."
msgid "The :guilabel:`Should Be Paid` status on bills is set automatically by Odoo. However, the status can be changed manually by clicking the field's drop-down menu inside the :guilabel:`Other Info` tab."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:106
msgid "View a purchase order's billing status"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:108
msgid "When a purchase order is confirmed, its :guilabel:`Billing Status` can be viewed under the :guilabel:`Other Information` tab on the purchase order form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1
msgid "Paid bill in Odoo Purchase"
msgid "Purchase order billing status."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:109
msgid "The *Should Be Paid* status is set automatically by Odoo. However, you can change the status manually when you are viewing a bill in edit mode."
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:115
msgid "Below is a list of the different statuses that a :guilabel:`Billing Status` could appear as and when they are displayed, depending on the bill control policy used."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119
msgid ":guilabel:`Billing Status`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119
msgid "**Conditions**"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121
msgid "*On received quantities*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121
msgid "*On ordered quantities*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123
msgid ":guilabel:`Nothing to Bill`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123
msgid "PO confirmed; no products received"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123
msgid "*Not applicable*"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125
msgid ":guilabel:`Waiting Bills`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125
msgid "All/some products received; bill not created"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125
msgid "PO confirmed"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127
msgid ":guilabel:`Fully Billed`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127
msgid "All/some products received; draft bill created"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127
msgid "Draft bill created"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:3
@ -6700,99 +6893,103 @@ msgid "When creating a vendor bill and selecting the appropriate purchase order,
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:3
msgid "Don’t run out of stock with reordering rules"
msgid "Configure reordering rules"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:5
msgid "To make sure you never run out of stock, you can define *Reordering Rules* on products. Thanks to them, Odoo can help you replenish your stock automatically when it reaches set quantities or whenever a sales order is created."
msgid "For certain products, it is necessary to ensure that there is always a minimum amount available on hand at any given time. By adding a reordering rule to a product, it is possible to automate the reordering process so that a purchase order is automatically created whenever the amount on hand falls below a set threshold."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:9
msgid "You need to install the *Inventory app* to use reordering rules."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:12
msgid "Configure your storable product"
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:11
msgid "The *Inventory* module must be installed to use reordering rules."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:14
msgid "Open or create a product with its *Product Type* set to *Storable Product*."
msgid "Configure products for reordering"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:16
msgid "Products must be configured in a specific way before a reordering rule can be added to them."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:18
msgid "Starting from the :menuselection:`Inventory`, :menuselection:`Manufacturing`, :menuselection:`Purchase`, or :menuselection:`Sales` module, navigate to :menuselection:`Products --> Products` and then click :guilabel:`Create` to make a new product. Alternatively, find a product that already exists in the database and click into it's product form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:23
msgid "Next, on the product form, enable reordering by checking the :guilabel:`Can be Purchased` option underneathe the :guilabel:`Product Name` field. Finally, set the :guilabel:`Product Type` to `Storable Product` under the :guilabel:`General Information` tab."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1
msgid "Set the product type in Odoo"
msgid "Configure a product for reordering in Odoo."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:20
msgid "As you are purchasing this product from a vendor, go to the product's *Purchase tab* and add a vendor by clicking on *Add a line*. You can add multiple vendors, but make sure to order them correctly, since reordering rules always use the first vendor in a list. You can add a price, but it isn't necessary for the reordering rule to work. In addition, you can add a minimum quantity you must order to benefit from that price."
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:32
msgid "Add a reordering rule to a product"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:27
msgid "If the quantity Odoo has to reorder doesn't match the minimum quantity specified, Odoo selects the next vendor on your list. If you don't have another vendor on your list, the reordering rule won't work. For that purpose, you can add the same vendor multiple times with different prices for different quantities."
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:34
msgid "After properly configuring a product, a reordering rule can be added to it by selecting the now visible :guilabel:`Reordering Rules` tab at the top of that product's form, and then clicking :guilabel:`Create` on the :guilabel:`Reordering Rules` dashboard."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1
msgid "Add vendor to a product in Odoo"
msgid "Access reordering rules for a product from the product page in Odoo."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:37
msgid "By default, a draft purchase order is created. However, if you have enabled *Purchase Agreements*, you can *Propose a call for tenders* instead as shown in the image above. For more information, see :doc:`../manage_deals/agreements`"
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:42
msgid "Once created, the reordering rule can be configured to generate purchase orders automatically by defining the following fields:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:41
msgid "Next, make sure the correct route is selected under the Inventory tab of your product. If you created your product within the Purchase app, the *Buy* route is selected by default. If you are looking to dropship your product, select *Dropship*."
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:45
msgid ":guilabel:`Location` specifies where the ordered quantities should be stored once they are received and entered into stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1
msgid "Choose product routes in Odoo"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:50
msgid "Set up your reordering rule"
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:47
msgid ":guilabel:`Min Quantity` sets the lower threshold for the reordering rule while :guilabel:`Max Quantity` sets the upper threshold. If the stock on hand falls below the minimum quantity, a new purchase order will be created to replenish it up to the maximum quantity."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:52
msgid "Open your product and click on the *Reordering Rules* button."
msgid "If :guilabel:`Min Quantity` is set to `5` and :guilabel:`Max Quantity` is set to `25` and the stock on hand falls to four, a purchase order will be created for 21 units of the product."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1
msgid "Reordering rules button on a product in Odoo"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:58
msgid "Once you are on the product's reordering rules page, click on *Create*."
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:55
msgid ":guilabel:`Multiple Quantity` can be configured so that products are only ordered in batches of a certain quantity. Depending on the number entered, this can result in the creation of a purchase order that would put the resulting stock on hand above what is specified in the :guilabel:`Max Quantity` field."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:61
msgid "You can access and create reordering rules from :menuselection:`Inventory --> Configuration --> Reordering Rules` and from :menuselection:`Inventory --> Operations --> Replenishment`. By default, the replenishment view presents a summary of all the products that you might need to purchase to fulfill your sales orders. From there, you can ask Odoo with a single click to order a product once or automate all orders for that product, future orders included."
msgid "If :guilabel:`Max Quantity` is set to `100` but :guilabel:`Multiple Quantity` is set to order the product in batches of `200`, a purchase order will be created for 200 units of the product."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:68
msgid "Define quantities"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:70
msgid "You can set a **minimum quantity** your stock should always have. Once set, if your stock goes below the minimum quantity, and if you selected the Buy route, a request for quotation is automatically generated to reach that minimum quantity, plus any additional quantity needed to fill in a sales order for example."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:75
msgid "If you set a **maximum quantity**, every time the product has to be replenished, enough products are reordered to reach the maximum quantity."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:78
msgid "If you want to order only the exact quantity needed to fill in a sales order for example, set both both the minimum and maximum quantity to **zero**. The quantity mentioned in the sales order is then used by the reordering rule."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:82
msgid "You can also add a **quantity multiple** to only order products in batches of a certain quantity. Click on the optional columns drop-down menu, and select *Multiple Quantity* to show the column. Bear in mind that you might go over the maximum quantity you set if your rule includes a quantity multiple, as Odoo orders enough products to reach the maximum quantity and respect the set quantity multiple."
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:65
msgid ":guilabel:`UoM` specifies the unit of measurement by which the quantity will be ordered. For discrete products, this should be set to `Units`. However, it can also be set to units of measurement like `Volume` or `Weight` for non-discrete products like water or bricks."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:-1
msgid "Create a reordering rule in Odoo"
msgid "Configure the reordering rule in Odoo."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:92
msgid "If you selected multiple routes for the same product under its Inventory tab, make sure to select your *Preferred Route* on your reordering rule by clicking on the optional columns drop-down menu, adding the *Preferred Route* column, and selecting the right route."
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:74
msgid "Manually trigger reordering rules using the scheduler"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:76
msgid "Reordering rules will be automatically triggered by the scheduler, which runs once a day by default. To trigger reordering rules manually, navigate to :menuselection:`Inventory --> Operations --> Run Scheduler`. On the pop-up window, confirm the manual action by clicking :guilabel:`Run Scheduler`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:82
msgid "Manually triggering reordering rules will also trigger any other scheduled actions."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:85
msgid "Manage reordering rules"
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:87
msgid "To manage the reordering rules for a single product, navigate to that product page's form and select the :guilabel:`Reordering Rules` tab at the top of the form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:90
msgid "To manage all reordering rules for every product, go to :menuselection:`Inventory --> Configuration --> Reordering Rules`. From this dashboard, typical bulk actions in Odoo can be performed such as exporting data or archiving rules that are no longer needed. As well, the :guilabel:`Filters`, :guilabel:`Group By` or triple-dotted menu on the form are available to search for and/or organize the reordering rules as desired."
msgstr ""
#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:3

769
locale/sources/productivity.pot
View File

File diff suppressed because it is too large Load Diff

760
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff

333
locale/sources/services.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-04-06 08:12+0000\n"
"POT-Creation-Date: 2023-04-13 05:55+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -236,55 +236,147 @@ msgid "`Coupons <https://www.odoo.com/slides/slide/coupon-programs-640?fullscree
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
msgid "Allow customers to close their tickets"
msgid "Closing tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
msgid "Allowing customers to close their own tickets gives them autonomy and minimizes misunderstandings around when an issue is considered solved or not. This results in operational capacity for support teams, and higher satisfaction for the customer."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
msgid "Enable ticket closing"
msgid "Once work has been completed on a *Helpdesk* ticket in Odoo, there are several ways it can be closed. Manually closing solved tickets keeps the pipeline up to date, while automatically closing inactive tickets prevents unnecessary blocking issues. Allowing customers to close their own tickets minimizes confusion around whether an issue is considered solved or not. This results in increased operational capacity for support teams, and higher customer satisfaction."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
msgid "Start by navigating to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit` and enable :guilabel:`Ticket closing` by checking the field box."
msgid "Manually close solved tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
msgid "As work on a ticket progresses, it is moved along to the next stage in the pipeline. Once the issue is solved, the ticket is moved to a *folded* stage. This marks the ticket as *closed*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
msgid "To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a team to open the pipeline. Hover over a stage's heading, and then click the gear icon that appears in the top-right corner of that stage's kanban column."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Ticket closing feature in Odoo Helpdesk."
msgid "View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage option."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
msgid "To designate which stage the ticket migrates to once it is closed, navigate to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` and clicking :guilabel:`Tickets` on the team's card."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
msgid "Clicking the gear icon also displays the option to :guilabel:`Fold` the stage. This setting folds the stage *temporarily* to simplify the kanban view. This does *not* close the tickets in this stage. It also does not permanently fold the stage. If a stage needs to be folded so the tickets can be marked as closed, continue following the steps below."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
msgid "There are two options: create a new Kanban stage or work with an existing one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing Stage`. After checking the field box, click :guilabel:`Save` to finish."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
msgid "From the menu that appears, select :guilabel:`Edit Stage`. This will open the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` towards the top of the window, and then :guilabel:`Save & Close` to confirm the changes. Now, tickets that reach this stage will be considered as *closed*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
msgid "If a closing stage is not specified, by default, the ticket is moved to the last stage in the kanban. If more than one stage is set as a closing stage, the ticket is placed in the first closing stage column."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Stage settings page."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
msgid "With the ticket closing settings now complete, customers can now view the option to :guilabel:`Close this ticket` when they log into their portal."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
msgid "Automatically close inactive tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
msgid "Tickets that are inactive for a set period of time can be automatically closed. At that point, they will be moved to a folded stage."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
msgid "Go to the team's settings page by going to :menuselection:`Helpdesk --> Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
msgid "If one of the team's stages is set to be folded in the kanban view, it will be the default selection in the :guilabel:`Move to Stage` field. If the team has more than one folded stage, the stage that occurs first in the pipeline will be the default. If no stage is folded, the default selection will be the last stage in the pipeline."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
msgid "The :guilabel:`After days of inactivity` field defaults to `7`, but can be adjusted if necessary."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
msgid "The :guilabel:`After days of inactivity` field does **not** take the working calendar into account when tracking the amount of time a ticket has been inactive."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
msgid "If only certain stages should be used to track days of inactivity, they can be added to the :guilabel:`In Stages` field."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
msgid "A team's pipeline is created with the following stages:"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
msgid "`New`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
msgid "`In Progress`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
msgid "`Customer Feedback`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
msgid "`Closed`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
msgid "Tickets can linger in the :guilabel:`Customer Feedback stage`, because once an issue is solved, customers may not respond immediately. At that point, the tickets can be closed automatically. However, tickets in the :guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due to assignment or workload issues. Closing these tickets automatically would result in issues going unsolved."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
msgid "Therefore, the :guilabel:`Automatic Closing` settings would be configured as below\\:\\"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
msgid ":guilabel:`Automatic Closing`: *checked*"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
msgid ":guilabel:`Move to Stage`: `Solved`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
msgid ":guilabel:`In Stages`: `Customer Feedback`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Example of Automatic Closing settings."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
msgid "Allow customers to close their own tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
msgid "Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own ticket(s) when they determine that their issue has been resolved."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
msgid "Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team. On the team's settings page, scroll to the :guilabel:`Self-Service` section and check the box for :guilabel:`Closure by Customers`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Customer closing setting in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
msgid "Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` button will be available for customers when they view their ticket through the customer portal."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Customer view of ticket closing in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
msgid "Get reports on tickets closed by customers"
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
msgid "Customers are able to view their tickets by clicking the :guilabel:`View the ticket` link they receive by email. The link is included in the :guilabel:`Request Acknowledgment` template, which is added to the first stage of a team by default. This link does not require a customer to have access to the portal to view or respond to their ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
msgid "To analyze the tickets that have been closed by customers, go to :menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the :guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set the custom filter parameters to :guilabel:`Closed by partner` and :guilabel:`is true`. Finally, click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
msgid "Customers with access to the portal will be able to view their tickets under :menuselection:`My Account --> Tickets`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview.rst:5
@ -633,7 +725,6 @@ msgid "View of the helpdesk ticket from a user’s portal emphasizing the link t
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:51
#: ../../content/applications/services/helpdesk/overview/sla.rst:47
msgid ":doc:`../advanced/close_tickets`"
msgstr ""
@ -792,7 +883,7 @@ msgid "Live Chat"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:121
msgid "The *Live Chat* feature allows website visitors to connect directly with a support agent or chatbot. During these conversations, *Helpdesk* tickets can be instantly created by using the :doc:`response command </applications/websites/livechat/overview/responses>` `/helpdesk`."
msgid "The *Live Chat* feature allows website visitors to connect directly with a support agent or chatbot. During these conversations, *Helpdesk* tickets can be instantly created by using the :doc:`response command </applications/websites/livechat/responses>` `/helpdesk`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
@ -945,7 +1036,7 @@ msgid "Once live chat is enabled, operators will be able to communicate with sit
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
msgid "During the conversation, an operator can use the shortcut :doc:`command </applications/websites/livechat/overview/responses>` `/helpdesk` to create a ticket without leaving the chat window. The transcript from the conversation will be added to the new ticket, under the :guilabel:`Description` tab."
msgid "During the conversation, an operator can use the shortcut :doc:`command </applications/websites/livechat/responses>` `/helpdesk` to create a ticket without leaving the chat window. The transcript from the conversation will be added to the new ticket, under the :guilabel:`Description` tab."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
@ -997,7 +1088,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
msgid ":doc:`/applications/websites/livechat/overview/get_started`"
msgid ":doc:`/applications/websites/livechat`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:3
@ -1087,51 +1178,195 @@ msgid "Service Level Agreements (SLA)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:5
msgid "Service Level Agreements (SLA) are commitments you make with your customers to outline how a service is delivered. It bolsters trust between you and your customers as it makes clear what needs to be done, to what standard, and when."
msgid "A Service Level Agreement (SLA) defines the level of service a customer can expect from a supplier. SLAs provide a timeline that tells customers when they can expect results, and keeps the support team on target."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:10
msgid "Create your policies"
msgid "Create a new SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:13
msgid "First, enable the feature on the settings of the team you would like policies to be applied, going to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:15
msgid "Create your policies through the team’s settings page or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`."
#: ../../content/applications/services/helpdesk/overview/sla.rst:12
msgid "To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`. Select a team, scroll to the :guilabel:`Performance` section, and then check the selection box next to :guilabel:`SLA Policies` to enable it for that specific team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of an SLA form in Odoo Helpdesk"
msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:23
msgid "Choose to which **Team** the policy is relevant and the **Minimum Priority** a ticket needs to have for the policy to be applied."
#: ../../content/applications/services/helpdesk/overview/sla.rst:22
msgid "The value indicated next to the :guilabel:`Working Hours` field is used to determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. By default, this is determined by the value set in the :guilabel:`Company Working Hours` field under :menuselection:`Settings app --> Employees --> Work Organization`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:27
msgid "**Target** is the stage a ticket needs to reach within the period defined to satisfy the SLA. The period is based on the ticket’s creation date, and a deadline is set on the ticket’s form once it matches an SLA policy rule. If a ticket has more than one policy applied to it, the closest deadline of all SLAs is the one considered."
msgid "To create a new policy, click the smart button on the team`s settings page or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`, and click :guilabel:`New`. Start by entering a :guilabel:`Title` and a :guilabel:`Description` for the new policy, and proceed to fill out the form using the steps below."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:29
msgid "When a ticket has satisfied an SLA policy, the SLA tag appears in green and the deadline field is not shown anymore."
#: ../../content/applications/services/helpdesk/overview/sla.rst:33
msgid "Define the criteria for an SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk"
#: ../../content/applications/services/helpdesk/overview/sla.rst:35
msgid "The :guilabel:`Criteria` section is used to identify what tickets this policy will be applied to. Fill out the following fields to adjust the selection criteria:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:37
msgid "SLA Analysis"
#: ../../content/applications/services/helpdesk/overview/sla.rst:38
msgid ":guilabel:`Team`: a policy can only be applied to one team. *This field is required.*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:39
msgid "Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply *Filters* and *Group by* to identify tickets that should be prioritized and keep track of upcoming deadlines."
msgid ":guilabel:`Priority`: the priority level for a ticket is identified by selecting the number of stars representing the priority level on the kanban card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will only be applied once the priority level has been updated on the ticket to match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is made in this field, this policy will only apply to tickets marked as `Low Priority` (zero stars)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:44
msgid ":guilabel:`Types`: ticket types can be helpful when indicating when a ticket is a customer question, that can be solved with a quick response, or an issue, that may require additional investigation. Multiple ticket types can be selected for this field. If no selection is made, this policy will apply to all ticket types."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:48
msgid ":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is about. Multiple tags can be applied to a single ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:50
msgid ":guilabel:`Customers`: individual contacts or companies may be selected in this field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:51
msgid ":guilabel:`Sales Order Items`: this field is available only if a team has the *Timesheets* app enabled. This allows the ticket to tie directly to a specific line on a sales order, which must be indicated on the ticket in the :guilabel:`Sales Order Item` field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:56
msgid "Unless otherwise indicated, multiple selections can be made for each field. (i.e. multiple :guilabel:`Tags` can be included in a policy, but only one :guilabel:`Priority` level)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of the SLA status analysis page emphasizing the group by option in Odoo Helpdesk"
msgid "View of a blank SLA policy record"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:64
msgid "Establish a target for an SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:66
msgid "The :guilabel:`Target` is the stage a ticket needs to reach, and the time alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service Level Agreement)` policy. Any stage assigned to a team may be selected for the :guilabel:`Reach Stage` field. Time spent in stages selected in :guilabel:`Excluding Stages` will not be included in the calculation of the :abbr:`SLA (Service Level Agreement)` deadline."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:73
msgid "An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks the working time before a ticket is completed, and would have `Solved` as the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level Agreement)` was titled `2 Days to Start`, it tracks the working time before work on a ticket has begun, and would have `In Progress` as the :guilabel:`Reach Stage`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:79
msgid "Meeting SLA deadlines"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:81
msgid "Once it is determined that a ticket fits the criteria of an :abbr:`SLA (Service Level Agreement)` policy, a deadline is calculated. The deadline is based on the creation date of the ticket, and the targeted working hours. The deadline is then added to the ticket, as well as a white tag indicating the name of the :abbr:`SLA (Service Level Agreement)` applied."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:91
msgid "If a ticket fits the criteria for more than one :abbr:`SLA (Service Level Agreement)`, the earliest occurring deadline will be displayed on the ticket. Once that deadline has passed, the next deadline will be displayed."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:95
msgid "Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the :abbr:`SLA (Service Level Agreement)` tag turns green, and the :guilabel:`Deadline` field disappears from view on the."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:102
msgid "If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level Agreement)` has failed, the red tag will stay on the ticket, even after the ticket is moved to the :guilabel:`Reach Stage`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:112
msgid "Analyzing SLA performance"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:114
msgid "The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA (Service Level Agreement)` is fulfilled, as well as the success rate of individual policies. Navigate to the report and corresponding pivot table by going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:120
msgid "Using the Pivot view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:122
msgid "By default, the report is displayed in a :guilabel:`Pivot` view, and is filtered to show the number of SLAs failed and the failure rate over the last 30 days, grouped by team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of the SLA status analysis report in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:129
msgid "To add the number of SLAs passed or in progress, click the :guilabel:`Measures` button to reveal a drop-down menu of reporting criteria, and choose from the options available based on the measurements preferred. Whenever a measurement is picked, a check mark will appear in the drop-down menu to indicate that that measurement is included, and a corresponding new column will emerge in the pivot table to show the relevant calculations."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:135
msgid "To add a group to a row or column, click the plus :guilabel:` + ` button next to :guilabel:`Total`, and then select one of the groups. To remove one, click the minus :guilabel:` - ` button and deselect."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:140
msgid "Using the Graph view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:142
msgid "The :guilabel:`Status Analysis` report can also be viewed as a :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between these views by selecting the appropriate icon at the top of the chart."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:148
msgid "Bar Chart"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in bar view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:154
msgid "Line Chart"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in line view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:160
msgid "Pie Chart"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in pie chart view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:167
msgid "Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed :guilabel:`Stacked`. This presents two or more groups to appear on top of each other instead of next to each other, making it easier to compare data."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:172
msgid "Using the Cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:174
msgid "The :guilabel:`Cohort` view is used to track the changes in data over a period of time. To display the :guilabel:`Status Analysis` report in a :guilabel:`Cohort` view, click the icon in the top right corner above the chart."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of the SLA status analysis report in cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:183
msgid ":ref:`Reporting views <reporting/views>`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:184
msgid ":doc:`Allow customers to close their tickets </applications/services/helpdesk/advanced/close_tickets>`"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5

2352
locale/sources/websites.pot
View File

File diff suppressed because it is too large Load Diff