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

[I18N] *: export latest terms

Browse Source 
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11495

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
This commit is contained in:
Tiffany Chang (tic) 2024-12-02 14:11:08 +01:00
parent 82378ce462
commit c7b9e0e159
8 changed files with 2104 additions and 1373 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"POT-Creation-Date: 2024-12-02 12:38+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"
@ -3175,11 +3175,11 @@ msgid "As the update notification must be able to reach Odoo's subscription vali
msgstr ""
#: ../../content/administration/on_premise.rst:64
msgid "Odoo 18.0 and above: `services.odoo.com` on port `443` (or `80`)"
msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`"
msgstr ""
#: ../../content/administration/on_premise.rst:65
msgid "Odoo 17.0 and below: `services.openerp.com` on port `443` (or `80`)"
msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`"
msgstr ""
#: ../../content/administration/on_premise.rst:67
@ -3203,7 +3203,7 @@ msgid "When the message appears, you have 30 days to act before the database exp
msgstr ""
#: ../../content/administration/on_premise.rst:82
#: ../../content/administration/on_premise.rst:108
#: ../../content/administration/on_premise.rst:102
msgid "To resolve the issue, either:"
msgstr ""
@ -3215,19 +3215,15 @@ msgstr ""
msgid ":ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation."
msgstr ""
#: ../../content/administration/on_premise.rst:89
msgid "If you are on a monthly subscription plan, the database will automatically update to reflect the added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the database. You can create the upsell quotation by clicking the banner to update the subscription or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue."
msgstr ""
#: ../../content/administration/on_premise.rst:94
#: ../../content/administration/on_premise.rst:88
msgid "Once your database has the correct number of users, the expiration message disappears automatically after a few days, when the next verification occurs."
msgstr ""
#: ../../content/administration/on_premise.rst:98
#: ../../content/administration/on_premise.rst:92
msgid "Database expired error"
msgstr ""
#: ../../content/administration/on_premise.rst:100
#: ../../content/administration/on_premise.rst:94
msgid "If your database expires before you renew your subscription, the following message should be displayed."
msgstr ""
@ -3235,15 +3231,15 @@ msgstr ""
msgid "Database expired error message"
msgstr ""
#: ../../content/administration/on_premise.rst:106
#: ../../content/administration/on_premise.rst:100
msgid "This message appears if you fail to act before the end of the 30-day countdown."
msgstr ""
#: ../../content/administration/on_premise.rst:110
#: ../../content/administration/on_premise.rst:104
msgid "Click the :guilabel:`Renew your subscription` link displayed in the message and complete the process. If you pay by wire transfer, your subscription will be renewed when the payment arrives which can take a few days. Credit card payments are processed immediately."
msgstr ""
#: ../../content/administration/on_premise.rst:113
#: ../../content/administration/on_premise.rst:107
msgid "`Send a support ticket <https://www.odoo.com/help>`_."
msgstr ""
@ -5102,7 +5098,7 @@ msgid "Even though we don't support older versions, you can always `upgrade from
msgstr ""
#: ../../content/administration/upgrade.rst:5
msgid "An upgrade involves moving a database from an older version to a newer supported version (e.g., from Odoo 15.0 to Odoo 17.0). Regular upgrades are crucial as each version offers new features, bug fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly recommended. Each major version is supported for three years."
msgid "An upgrade involves moving a database from an older version to a newer supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are crucial as each version offers new features, bug fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly recommended. Each major version is supported for three years."
msgstr ""
#: ../../content/administration/upgrade.rst:10
@ -5110,11 +5106,11 @@ msgid "Depending on the hosting type and Odoo version used, a database upgrade c
msgstr ""
#: ../../content/administration/upgrade.rst:16
msgid "If a database is on a **major version** (e.g., 15.0, 16.0, 17.0), an upgrade is mandatory every two years."
msgid "If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade is mandatory every two years."
msgstr ""
#: ../../content/administration/upgrade.rst:18
msgid "If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory a few weeks after the next version is released. Minor versions are usually released every three months."
msgid "If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory a few weeks after the next version is released. Minor versions are usually released every two months."
msgstr ""
#: ../../content/administration/upgrade.rst:24
@ -5638,21 +5634,17 @@ msgid "the **cleaning** of pre-existing data and configurations while upgrading;
msgstr ""
#: ../../content/administration/upgrade.rst:433
msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;"
msgid "the upgrade of **additional modules not covered by a maintenance contract** that are created in-house or by third parties, including Odoo partners; and"
msgstr ""
#: ../../content/administration/upgrade.rst:434
msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code <studio/automated-actions/action>`; and"
msgstr ""
#: ../../content/administration/upgrade.rst:437
#: ../../content/administration/upgrade.rst:435
msgid "**training** on using the upgraded version's features and workflows."
msgstr ""
#: ../../content/administration/upgrade.rst:440
#: ../../content/administration/upgrade.rst:438
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
msgstr ""
#: ../../content/administration/upgrade.rst:441
#: ../../content/administration/upgrade.rst:439
msgid ":doc:`Supported Odoo versions <supported_versions>`"
msgstr ""

1965
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

373
locale/sources/hr.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"POT-Creation-Date: 2024-12-02 12:38+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"
@ -2285,7 +2285,7 @@ msgid "Resumé tab"
msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:110
#: ../../content/applications/hr/payroll.rst:874
#: ../../content/applications/hr/payroll.rst:855
#: ../../content/applications/hr/recruitment/recruitment-flow.rst:38
msgid "Resumé"
msgstr ""
@ -3139,7 +3139,7 @@ msgstr ""
#: ../../content/applications/hr/fleet/service.rst:380
#: ../../content/applications/hr/frontdesk.rst:33
#: ../../content/applications/hr/lunch/products.rst:12
#: ../../content/applications/hr/payroll.rst:894
#: ../../content/applications/hr/payroll.rst:875
#: ../../content/applications/hr/payroll/work_entries.rst:56
#: ../../content/applications/hr/time_off.rst:221
msgid "Enter the following information on the form:"
@ -6649,7 +6649,7 @@ msgid "To create a new :guilabel:`Work Entry Type`, click the :guilabel:`New` bu
msgstr ""
#: ../../content/applications/hr/payroll.rst:265
#: ../../content/applications/hr/payroll.rst:730
#: ../../content/applications/hr/payroll.rst:711
#: ../../content/applications/hr/payroll/contracts.rst:40
msgid "General information section"
msgstr ""
@ -7076,7 +7076,7 @@ msgid ":guilabel:`Partner`: if another company financially contributes to this r
msgstr ""
#: ../../content/applications/hr/payroll.rst:619
#: ../../content/applications/hr/payroll.rst:815
#: ../../content/applications/hr/payroll.rst:796
msgid "Description tab"
msgstr ""
@ -7134,47 +7134,27 @@ msgid "A new Input Type form filled in."
msgstr ""
#: ../../content/applications/hr/payroll.rst:669
msgid "Salary attachment types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:671
msgid "Salary attachments, also thought of as \"wage garnishments\", are portions of earnings taken out of a payslip for something specific. Much like all other aspects of payroll configurations, the types of salary attachments **must** be defined."
msgstr ""
#: ../../content/applications/hr/payroll.rst:675
msgid "To view the currently configured salary attachments, navigate to :menuselection:`Payroll app --> Configuration --> Salary --> Salary Attachment Types`. The default salary attachment types are :guilabel:`Attachment of Salary`, :guilabel:`Assignment of Salary`, and :guilabel:`Child Support`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:679
msgid "To make a new type of salary attachment, click the :guilabel:`New` button. Then, enter the :guilabel:`Name`, the :guilabel:`Code` (used in the salary rules to compute payslips), and decide if it should have :guilabel:`No End Date`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:-1
msgid "A new salary attachment form filled in."
msgstr ""
#: ../../content/applications/hr/payroll.rst:688
#: ../../content/applications/hr/recruitment.rst:167
msgid "Salary package configurator"
msgstr ""
#: ../../content/applications/hr/payroll.rst:690
#: ../../content/applications/hr/payroll.rst:671
msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll app --> Configuration --> Salary Package Configurator` menu all affect an employee's potential salary. These sections (:guilabel:`Benefits`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package."
msgstr ""
#: ../../content/applications/hr/payroll.rst:695
#: ../../content/applications/hr/payroll.rst:676
msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated, as the applicant enters information."
msgstr ""
#: ../../content/applications/hr/payroll.rst:701
#: ../../content/applications/hr/payroll.rst:682
msgid "Benefits"
msgstr ""
#: ../../content/applications/hr/payroll.rst:703
#: ../../content/applications/hr/payroll.rst:684
msgid "When offering potential employees a position, there can be certain benefits set in Odoo, in addition to the salary, to make an offer more appealing (such as extra time off, the use of a company car, reimbursement for a phone or internet, etc.)."
msgstr ""
#: ../../content/applications/hr/payroll.rst:707
#: ../../content/applications/hr/payroll.rst:688
msgid "To view the benefits, go to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Benefits`. Benefits are grouped by :guilabel:`Structure type`, and the benefit listed for a particular structure type is only available for that specific structure."
msgstr ""
@ -7182,67 +7162,67 @@ msgstr ""
msgid "A list view of all the benefits available for each structure type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:716
#: ../../content/applications/hr/payroll.rst:697
msgid "A company has two structure types, one labeled :guilabel:`Employee`, and another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type contains the benefit of using a company car, while the :guilabel:`Intern` structure type has a meal voucher benefit available."
msgstr ""
#: ../../content/applications/hr/payroll.rst:720
#: ../../content/applications/hr/payroll.rst:701
msgid "A person hired under the :guilabel:`Employee` structure type can use the company car benefit, but cannot have meal vouchers. A person hired under the :guilabel:`Intern` structure type would have meal voucher benefits available to them, not the use of a company car."
msgstr ""
#: ../../content/applications/hr/payroll.rst:724
#: ../../content/applications/hr/payroll.rst:705
msgid "To make a new benefit, click the :guilabel:`New` button, and enter the information in the fields on the blank benefits form."
msgstr ""
#: ../../content/applications/hr/payroll.rst:727
#: ../../content/applications/hr/payroll.rst:708
msgid "The various fields for creating a benefit are as follows:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:732
#: ../../content/applications/hr/payroll.rst:713
msgid ":guilabel:`Benefits`: enter the name for the benefit. This field is required."
msgstr ""
#: ../../content/applications/hr/payroll.rst:733
#: ../../content/applications/hr/payroll.rst:714
msgid ":guilabel:`Benefit Field`: select from the drop-down menu the type of benefit this is."
msgstr ""
#: ../../content/applications/hr/payroll.rst:734
#: ../../content/applications/hr/payroll.rst:715
msgid ":guilabel:`Cost Field`: select from the drop-down menu the type of cost incurred by the company for this specific benefit. The default options are :guilabel:`Calendar Changed`, :guilabel:`Yearly Cost (Real)`, :guilabel:`Extra Time Off`, :guilabel:`Hourly Wage`, :guilabel:`Part Time`, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and :guilabel:`Work time rate`. Depending on the localization settings, additional options are available."
msgstr ""
#: ../../content/applications/hr/payroll.rst:739
#: ../../content/applications/hr/payroll.rst:720
msgid ":guilabel:`Related Type`: select from the drop-down menu what type of benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, :guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. This field is required."
msgstr ""
#: ../../content/applications/hr/payroll.rst:743
#: ../../content/applications/hr/payroll.rst:724
msgid ":guilabel:`Benefit Field`: select from the drop-down menu the specific field on the contract the benefit appears."
msgstr ""
#: ../../content/applications/hr/payroll.rst:745
#: ../../content/applications/hr/payroll.rst:726
msgid ":guilabel:`Cost Field`: select the specific field on the contract that the cost of the benefit is linked to, using the drop-down menu. If this field is left blank, the cost of the benefit is not computed in the employee budget."
msgstr ""
#: ../../content/applications/hr/payroll.rst:748
#: ../../content/applications/hr/payroll.rst:729
msgid ":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should impact the employee's net salary."
msgstr ""
#: ../../content/applications/hr/payroll.rst:750
#: ../../content/applications/hr/payroll.rst:731
msgid ":guilabel:`Requested Documents`: select any document that is required to be submitted for this benefit, from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll.rst:752
#: ../../content/applications/hr/payroll.rst:733
msgid ":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit that is required in order for this specific benefit to be offered to the employee."
msgstr ""
#: ../../content/applications/hr/payroll.rst:755
#: ../../content/applications/hr/payroll.rst:736
msgid "For example, a benefit for car insurance would populate `Company Car` in this field. This would allow the car insurance benefit to **only** be displayed if the employee has selected/enabled the benefit of a company car."
msgstr ""
#: ../../content/applications/hr/payroll.rst:758
#: ../../content/applications/hr/payroll.rst:739
msgid ":guilabel:`Salary Structure Type`: select from the drop-down menu which salary structure type this benefit applies to. This field is required."
msgstr ""
#: ../../content/applications/hr/payroll.rst:760
#: ../../content/applications/hr/payroll.rst:741
msgid ":guilabel:`Unit of Measure`: select the metric that the benefit is granted, using the drop-down menu. The options are :guilabel:`Days`, :guilabel:`Percent`, or :guilabel:`Currency`."
msgstr ""
@ -7250,100 +7230,100 @@ msgstr ""
msgid "A new benefit form filled out for an internet subscription."
msgstr ""
#: ../../content/applications/hr/payroll.rst:768
#: ../../content/applications/hr/payroll.rst:749
msgid "Display section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:770
#: ../../content/applications/hr/payroll.rst:751
msgid ":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in the salary package configurator."
msgstr ""
#: ../../content/applications/hr/payroll.rst:772
#: ../../content/applications/hr/payroll.rst:753
msgid ":guilabel:`Display Type`: select from the drop-down menu how this benefit is displayed. The options are :guilabel:`Always Selected`, :guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, :guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. This field is required."
msgstr ""
#: ../../content/applications/hr/payroll.rst:777
#: ../../content/applications/hr/payroll.rst:758
msgid "Depending on the selection made, additional configurations need to be made. For example, if :guilabel:`Radio Buttons` is selected, the individual radio buttons must be entered."
msgstr ""
#: ../../content/applications/hr/payroll.rst:779
#: ../../content/applications/hr/payroll.rst:760
msgid ":guilabel:`Icon`: an icon from the `Font Awesome 4 library <https://fontawesome.com/v4/icons/>`_ can be visible for this benefit. Enter the text code for the icon in this field. For example, to display a suitcase icon, the code `fa fa-suitcase` is entered on this line."
msgstr ""
#: ../../content/applications/hr/payroll.rst:782
#: ../../content/applications/hr/payroll.rst:763
msgid ":guilabel:`Hide Description`: tick the checkbox to hide the benefit description if the benefit is not selected by the employee."
msgstr ""
#: ../../content/applications/hr/payroll.rst:784
#: ../../content/applications/hr/payroll.rst:765
msgid ":guilabel:`Folded`: if the benefit should be folded, or hidden, because it is dependant on another benefit selection, tick the checkbox. The following fields appear when this is active:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:787
#: ../../content/applications/hr/payroll.rst:768
msgid ":guilabel:`Fold Label`: enter a name for the folded section of the benefit."
msgstr ""
#: ../../content/applications/hr/payroll.rst:788
#: ../../content/applications/hr/payroll.rst:769
msgid ":guilabel:`Fold Res Field`: select the contract field this benefit is tied to using the drop-down menu. If this field is selected on the contract, then this benefit becomes visible."
msgstr ""
#: ../../content/applications/hr/payroll.rst:792
#: ../../content/applications/hr/payroll.rst:773
msgid "Activity section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:794
#: ../../content/applications/hr/payroll.rst:775
msgid ":guilabel:`Activity Type`: from the drop-down menu, select the activity type that is automatically created when this benefit is selected by the employee."
msgstr ""
#: ../../content/applications/hr/payroll.rst:796
#: ../../content/applications/hr/payroll.rst:777
msgid ":guilabel:`Activity Creation`: select when the activity is created, either when the :guilabel:`Employee signs his contract`, or when the :guilabel:`Contract is countersigned`. Click the radio button next to the desired selection."
msgstr ""
#: ../../content/applications/hr/payroll.rst:799
#: ../../content/applications/hr/payroll.rst:780
msgid ":guilabel:`Activity Creation Type`: select the parameters for when the activity is created, either :guilabel:`When the benefit is set` or :guilabel:`When the benefit is modified`. Click the radio button next to the desired selection."
msgstr ""
#: ../../content/applications/hr/payroll.rst:802
#: ../../content/applications/hr/payroll.rst:783
msgid ":guilabel:`Assigned to`: select the user the activity is automatically assigned to, using the drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll.rst:806
#: ../../content/applications/hr/payroll.rst:787
#: ../../content/applications/hr/payroll/contracts.rst:163
msgid "Sign section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:808
#: ../../content/applications/hr/payroll.rst:789
msgid ":guilabel:`Template to Sign`: if the employee is required to sign a document when selecting this benefit, select the document template from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll.rst:811
#: ../../content/applications/hr/payroll.rst:792
msgid "For example, a benefit regarding the use of a company car may require the employee to sign a document acknowledging the company's car policies."
msgstr ""
#: ../../content/applications/hr/payroll.rst:817
#: ../../content/applications/hr/payroll.rst:798
msgid "Provide any additional information in this tab to help clarify the benefit."
msgstr ""
#: ../../content/applications/hr/payroll.rst:820
#: ../../content/applications/hr/payroll.rst:801
msgid "Personal info"
msgstr ""
#: ../../content/applications/hr/payroll.rst:822
#: ../../content/applications/hr/payroll.rst:803
msgid "Every employee in Odoo has an *employee card* which is created when a candidate becomes an employee. This card includes all of their personal information, resume, work information, and documents."
msgstr ""
#: ../../content/applications/hr/payroll.rst:826
#: ../../content/applications/hr/payroll.rst:807
msgid "The personal information is gathered from the salary package configurator section that a candidate fills out after being offered a position. This personal information is then transferred to the employee card when they are hired."
msgstr ""
#: ../../content/applications/hr/payroll.rst:830
#: ../../content/applications/hr/payroll.rst:811
msgid "To view an employee's card, go to the main :menuselection:`Employees` app dashboard, and click on the employee's card."
msgstr ""
#: ../../content/applications/hr/payroll.rst:834
#: ../../content/applications/hr/payroll.rst:815
msgid "An employee card can be thought of as an employee personnel file."
msgstr ""
#: ../../content/applications/hr/payroll.rst:836
#: ../../content/applications/hr/payroll.rst:817
msgid "The :guilabel:`Personal Info` section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Personal Info`."
msgstr ""
@ -7351,31 +7331,31 @@ msgstr ""
msgid "A list of all the personal information that appears on the employee card to enter."
msgstr ""
#: ../../content/applications/hr/payroll.rst:844
#: ../../content/applications/hr/payroll.rst:825
msgid "To edit a personal info entry, select an entry from the list on the :guilabel:`Personal Info` page, and modify the personal info on the form that appears."
msgstr ""
#: ../../content/applications/hr/payroll.rst:847
#: ../../content/applications/hr/payroll.rst:828
msgid "To create a new personal info entry, click the :guilabel:`New` button."
msgstr ""
#: ../../content/applications/hr/payroll.rst:849
#: ../../content/applications/hr/payroll.rst:830
msgid "The required fields, aside from entering the :guilabel:`Information` name, are :guilabel:`Related Model`, :guilabel:`Related Field`, and :guilabel:`Category`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:852
#: ../../content/applications/hr/payroll.rst:833
msgid "Select a :guilabel:`Related Model` from the drop-down menu. :guilabel:`Employee` populates the field by default, but the :guilabel:`Bank Account` option is also available if the information is related to a bank account, instead."
msgstr ""
#: ../../content/applications/hr/payroll.rst:856
#: ../../content/applications/hr/payroll.rst:837
msgid "Select a :guilabel:`Related Field` from the drop-down menu that best describes what kind of personal information this entry is, and where it is stored in the backend. Then, select a :guilabel:`Category` from the drop-down menu that the personal information should be under, such as :guilabel:`Address` or :guilabel:`Personal Documents`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:861
#: ../../content/applications/hr/payroll.rst:842
msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:864
#: ../../content/applications/hr/payroll.rst:845
msgid "Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card. The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, like a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more."
msgstr ""
@ -7383,71 +7363,71 @@ msgstr ""
msgid "New personal information entry."
msgstr ""
#: ../../content/applications/hr/payroll.rst:876
#: ../../content/applications/hr/payroll.rst:857
msgid "The resumé section, housed within the salary package configurator section of the settings menu, is how salary information rules are configured when offering a position to potential employees."
msgstr ""
#: ../../content/applications/hr/payroll.rst:879
#: ../../content/applications/hr/payroll.rst:860
msgid "When an offer is sent to a prospective employee, the values for the offer are computed from these settings, and appear on the offer page."
msgstr ""
#: ../../content/applications/hr/payroll.rst:882
#: ../../content/applications/hr/payroll.rst:863
msgid "To configure this section, navigate to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Resumé`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:885
#: ../../content/applications/hr/payroll.rst:866
msgid "By default, there are three :guilabel:`Salary Structure Types` pre-configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and :guilabel:`None`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:888
#: ../../content/applications/hr/payroll.rst:869
msgid "Each :guilabel:`Salary Structure Type` has several rules configured. These affect how an offer is calculated using that particular :guilabel:`Salary Structure Type`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:891
#: ../../content/applications/hr/payroll.rst:872
msgid "To create a new rule, click the :guilabel:`New` button, and a blank :guilabel:`Contract Salary Resumé` form loads."
msgstr ""
#: ../../content/applications/hr/payroll.rst:896
#: ../../content/applications/hr/payroll.rst:877
msgid ":guilabel:`Information`: type in a name for this field."
msgstr ""
#: ../../content/applications/hr/payroll.rst:897
#: ../../content/applications/hr/payroll.rst:878
msgid ":guilabel:`Category`: select the category this value is housed under, using the drop-down menu. The default options are :guilabel:`Monthly Salary`, :guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and :guilabel:`Total`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:901
#: ../../content/applications/hr/payroll.rst:882
msgid "New categories can be made if needed."
msgstr ""
#: ../../content/applications/hr/payroll.rst:903
#: ../../content/applications/hr/payroll.rst:884
msgid "Click the :guilabel:`New` button, then enter the name for the new category in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last, enter a number for the sequence. This corresponds to where this rule appears in the :guilabel:`Salary Structure Type` rule list."
msgstr ""
#: ../../content/applications/hr/payroll.rst:908
#: ../../content/applications/hr/payroll.rst:889
msgid "Finally, click :guilabel:`Save & Close`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:909
#: ../../content/applications/hr/payroll.rst:890
msgid ":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added in the monthly total calculation."
msgstr ""
#: ../../content/applications/hr/payroll.rst:911
#: ../../content/applications/hr/payroll.rst:892
msgid ":guilabel:`Unit of Measure`: select what kind of value this rule is, either :guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:914
#: ../../content/applications/hr/payroll.rst:895
msgid ":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for compensation in the form of time off, and :guilabel:`Percent` is for a monetary value awarded that is based upon another metric, such as commissions."
msgstr ""
#: ../../content/applications/hr/payroll.rst:917
#: ../../content/applications/hr/payroll.rst:898
msgid ":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure Type` this rule is nested under, from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll.rst:919
#: ../../content/applications/hr/payroll.rst:900
msgid ":guilabel:`Value Type`: select how the value is computed, using the drop-down menu. The default options are :guilabel:`Fixed Value`, :guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of Benefits Values`, and :guilabel:`Monthly Total`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:922
#: ../../content/applications/hr/payroll.rst:903
msgid ":guilabel:`Code`: select the code this rule applies to from the drop-down menu."
msgstr ""
@ -7455,28 +7435,28 @@ msgstr ""
msgid "The net wage rule form filled out, with all the information for net pay."
msgstr ""
#: ../../content/applications/hr/payroll.rst:929
#: ../../content/applications/hr/payroll.rst:910
msgid "Jobs"
msgstr ""
#: ../../content/applications/hr/payroll.rst:931
#: ../../content/applications/hr/payroll.rst:912
msgid "Since the *Payroll* application is responsible for paying employees for specific job positions, the complete list of job positions can be found in both the *Payroll* and *Recruitment* applications."
msgstr ""
#: ../../content/applications/hr/payroll.rst:937
#: ../../content/applications/hr/payroll.rst:918
#: ../../content/applications/hr/recruitment/new_job.rst:3
msgid "Job positions"
msgstr ""
#: ../../content/applications/hr/payroll.rst:939
#: ../../content/applications/hr/payroll.rst:920
msgid "The job positions listed in the *Payroll* application are identical to the job positions listed in the *Recruitment* application. If a new job position is added in the *Recruitment* application, it is also visible in the *Payroll* application, and vice versa."
msgstr ""
#: ../../content/applications/hr/payroll.rst:943
#: ../../content/applications/hr/payroll.rst:924
msgid "To view the job positions, navigate to :menuselection:`Payroll app --> Configuration --> Jobs: Job Positions`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:946
#: ../../content/applications/hr/payroll.rst:927
msgid "A list of all the job positions appear, along with the corresponding department, on the :guilabel:`Job Position` page."
msgstr ""
@ -7484,39 +7464,43 @@ msgstr ""
msgid "A list of all the job positions and corresponding departments."
msgstr ""
#: ../../content/applications/hr/payroll.rst:953
#: ../../content/applications/hr/payroll.rst:934
msgid "To create a new job description, click the :guilabel:`New` button and a job form appears."
msgstr ""
#: ../../content/applications/hr/payroll.rst:955
#: ../../content/applications/hr/payroll.rst:936
msgid "Enter the information on the form for the new position. The information is identical as to the information entered when creating a new job position in the *Recruitment* application."
msgstr ""
#: ../../content/applications/hr/payroll.rst:958
#: ../../content/applications/hr/payroll.rst:939
msgid "Refer to the :doc:`../hr/recruitment/new_job` documentation for more details on how to fill out this form."
msgstr ""
#: ../../content/applications/hr/payroll.rst:962
#: ../../content/applications/hr/payroll.rst:943
msgid ":doc:`payroll/contracts`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:963
msgid ":doc:`payroll/payslips`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:964
#: ../../content/applications/hr/payroll.rst:944
msgid ":doc:`payroll/work_entries`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:965
#: ../../content/applications/hr/payroll.rst:945
msgid ":doc:`payroll/salary_attachments`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:946
msgid ":doc:`payroll/payslips`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:947
msgid ":doc:`payroll/reporting`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:966
#: ../../content/applications/hr/payroll.rst:948
msgid ":doc:`payroll/work_entry_analysis`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:967
#: ../../content/applications/hr/payroll.rst:949
msgid ":doc:`payroll/salary_attachment`"
msgstr ""
@ -7913,6 +7897,7 @@ msgid "To send a contract using the :guilabel:`Generate Simulation Link`, there
msgstr ""
#: ../../content/applications/hr/payroll/contracts.rst:330
#: ../../content/applications/hr/payroll/salary_attachments.rst:3
msgid "Salary attachments"
msgstr ""
@ -8845,6 +8830,170 @@ msgstr ""
msgid "The salary attachment report modified to compare to the previous year."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:5
msgid "Salary attachments are portions of earnings taken directly out of a payslip for a specific purpose, whether voluntary or required."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:8
msgid "When the deduction is voluntary, they are typically considered *deductions*. When the deduction is court-ordered, or involuntary, it is sometimes referred to as a *wage garnishment*. In Odoo, these are all universally called, *salary attachments*."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:15
msgid "Salary attachment types"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:17
msgid "To view the currently configured salary attachment types, navigate to :menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. The default salary attachment types are: :guilabel:`Attachment of Salary`, :guilabel:`Assignment of Salary`, and :guilabel:`Child Support`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:21
msgid "Each salary attachment type displays the :guilabel:`Name` of the attachment type, the :guilabel:`Code` used when calculating payslips, a checkbox to indicate if there is :guilabel:`No End Date`, and whether it is :guilabel:`Country` specific (or universal)."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:-1
msgid "The default salary attachment types."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:29
msgid "Create new salary attachment types"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:32
msgid "Upon installation of the **Payroll** application, the pre-configured default salary attachment types are linked to a variety of rules that are linked to various salary structures, as well as the installed :ref:`localization package <fiscal_localizations/packages>`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:36
msgid "It is **not** recommended to alter or modify **any** of the preconfigured salary attachment types, especially if they have been previously used on payslips in the database. Doing so may affect various salary rules, and can prevent the creation of payslips."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:40
msgid "A new salary attachment type *can* be created, but this should only be done when absolutely necessary. All salary attachments can be associated with one of the three default salary attachment types."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:44
msgid "To make a new type of salary attachment, click the :guilabel:`New` button, and a blank :guilabel:`Salary Attachment Types` form loads. Enter the :guilabel:`Name` for the new salary attachment type in the corresponding field. Next, enter the :guilabel:`Code` used in the salary rules to compute payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary attachment never expires."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:50
msgid "If in a multi-company database, with locations in multiple countries, a :guilabel:`Country` field also appears on the :guilabel:`Salary Attachment Types` form. Select the country the attachment applies to, or leave blank if it is universal."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:57
msgid "Create a salary attachment"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:59
msgid "All salary attachments must be configured separately for each employee, for each type of salary attachment. To view the currently configured salary attachments, navigate to :menuselection:`Payroll app --> Contracts --> Salary Attachments`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:63
msgid "All salary attachments appear in a default list view, and displays the name of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, and current :guilabel:`Status`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:67
msgid "To create a new salary attachment, click the :guilabel:`New` button in the top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter the following information on the form:"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:70
msgid ":guilabel:`Employees`: Using the drop-down menu, select the desired employees. Multiple employees can be listed in this field."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:72
msgid ":guilabel:`Description`: Enter a short description of the salary attachment."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:73
msgid ":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary attachment type <payroll/salary-attachment/types>`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:75
msgid ":guilabel:`Start Date`: Using the calendar selector, select the date the salary attachment goes into effect."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:77
msgid ":guilabel:`Estimated End Date`: This field is **not** modifiable, and **only** appears after the :guilabel:`Monthly Amount` field is populated. This field is the estimated date when the salary attachment will be completed. Today's date populates the field by default. Then, when the :guilabel:`Total Amount` field is populated, this date is updated."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:81
msgid ":guilabel:`Document`: If any documentation is needed, such as a court order, click the :guilabel:`Upload your file` button, and a file explorer window loads. Select the desired document to attach it to the record. Only **one** document can be attached to a salary attachment."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:84
msgid ":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck every month in this field."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:85
msgid ":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary attachment type <payroll/salary-attachment/types>` has no end date (the :guilabel:`No End Date` option is **not** ticked.)"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:-1
msgid "The salary attachment form with all fields filled out."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:92
msgid "Since the salary attachment form auto saves as the fields are populated, after making a salary attachment for an individual employee, there is no further action required."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:95
msgid "If creating salary attachments for multiple employees on a single salary attachment form, after the form is filled out, click the :guilabel:`Create Individual Attachments` button. This creates separate salary attachments for each of the employees listed in the :guilabel:`Employees` field."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:99
msgid "After the separate salary attachments have been created, the screen returns to the :guilabel:`Salary Attachment` dashboard, but with a :guilabel:`Description` filter, populated with the description filled in on the salary attachment form. All the salary attachments have a status of :guilabel:`Running`, since they are currently active. Clear the filter in the search box to view the default :guilabel:`Salary Attachment` dashboard in its entirety."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:106
msgid "Manage salary attachments"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:108
msgid "Salary attachments can have one of three statuses: *Running*, *Completed*, or *Canceled*. To view the current status of all salary attachments, navigate to :menuselection:`Payroll app --> Contracts --> Salary Attachments`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:112
msgid "All salary attachments appear in the order they were configured. To view the salary attachments by a particular metric, such as the :guilabel:`Status`, or :guilabel:`Type`, click on the column title to sort by that specific column."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:117
msgid "Completed salary attachments"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:119
msgid "When a salary attachment is created, it has a status of :guilabel:`Running`. Once the salary attachment is finished (the *Total Amount* entered on the :ref:`salary attachment form <payroll/salary-attachment/create>` has been paid in full), the status automatically changes to *Completed*, and the employee no longer has the money taken out of future paychecks."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:124
msgid "If a salary attachment has been fulfilled, but has not automatically changed to *Completed*, the record can be manually updated. To change the status, open the *Salary Attachment* dashboard by navigating to :menuselection:`Payroll app --> Contracts --> Salary Attachments`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:128
msgid "Click on the record to update, and the detailed :guilabel:`Salary Attachment` form loads. On the individual :guilabel:`Salary Attachment` record, click the :guilabel:`Mark as Completed` button in the upper-left corner, and the status changes to :guilabel:`Completed`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:133
msgid "The following is an example of when a payroll manager may need to manually change a salary attachment from :guilabel:`Active` to :guilabel:`Cancelled`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:136
msgid "Rose Smith has a salary attachment for a lawsuit settlement, where she is required to pay $3,000.00. A salary attachment is created that takes $250.00 a month out of Rose's paycheck, to go towards this settlement payment."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:140
msgid "After six months, Rose has paid $1,500.00 from her salary. She received a tax refund, and uses the money to pay off the remainder of the lawsuit settlement. After sending the relevant documentation to the payroll manager, showing the settlement has been paid in full, the payroll manager manually changes the status of her salary attachment to :guilabel:`Completed`."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:146
msgid "Cancel salary attachments"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:148
msgid "Any salary attachment can be cancelled at any time. To cancel a salary attachment, click on the individual attachment record from the main :guilabel:`Salary Attachment` dashboard to open the record. From the :guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to cancel the salary attachment, and stop having the designated money taken out of future paychecks."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachments.rst:154
msgid ":doc:`salary_attachment`"
msgstr ""
#: ../../content/applications/hr/payroll/work_entries.rst:5
msgid "Work entries are created automatically in the *Payroll* app, based on the employee's :ref:`salary structure type <payroll/structure-types>`, and from the *Planning*, *Attendances*, and *Time Off* applications."
msgstr ""

398
locale/sources/inventory_and_mrp.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"POT-Creation-Date: 2024-12-02 12:38+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"
@ -247,8 +247,8 @@ msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:38
#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:20
#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:21
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:20
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/inventory_valuation_config.rst:44
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:18
#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:35
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:18
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:16
@ -2951,7 +2951,7 @@ msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:93
#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:162
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:81
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:77
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:54
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77
msgid "Create purchase order"
@ -3276,202 +3276,6 @@ msgstr ""
msgid "Inventory valuation"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:3
msgid "Landed costs"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:12
msgid "When shipping products to customers, the landed cost is the total price of a product or shipment, including all expenses associated with shipping the product."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:15
msgid "In Odoo, the *Landed Costs* feature is used to take additional costs into account when calculating the valuation of a product. This includes the cost of shipment, insurance, customs duties, taxes, and other fees."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:22
msgid "To add landed costs to products, the *Landed Costs* feature must first be enabled. To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll to the :guilabel:`Valuation` section."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:26
msgid "Tick the checkbox next to the :guilabel:`Landed Costs` option, and click :guilabel:`Save` to save changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:29
msgid "Once the page refreshes, a new :guilabel:`Default Journal` field appears below the :guilabel:`Landed Costs` feature in the :guilabel:`Valuation` section."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:32
msgid "Click the :guilabel:`Default Journal` drop-down menu to reveal a list of accounting journals. Select a journal for which all accounting entries related to landed costs should be recorded."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:-1
msgid "Landed Costs feature and resulting Default Journal field in the Inventory settings."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:40
msgid "Create landed cost product"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:42
msgid "For charges that are consistently added as landed costs, a landed cost product can be created in Odoo. This way, a landed cost product can be quickly added to a vendor bill as an invoice line, instead of having to be manually entered every time a new vendor bill is created."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:46
msgid "To do this, create a new product by going to :menuselection:`Inventory app --> Products --> Products`, and clicking :guilabel:`New`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:49
msgid "Assign a name to the landed cost product in the :guilabel:`Product Name` field (i.e. `International Shipping`). In the :guilabel:`Product Type` field, click the drop-down menu, and select :guilabel:`Service` as the :guilabel:`Product Type`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:54
msgid "Landed cost products **must** have their :guilabel:`Product Type` set to :guilabel:`Service`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:56
msgid "Click the :guilabel:`Purchase` tab, and tick the checkbox next to :guilabel:`Is a Landed Cost` in the :guilabel:`Vendor Bills` section. Once ticked, a new :guilabel:`Default Split Method` field appears below it, prompting a selection. Clicking that drop-down menu reveals the following options:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:60
msgid ":guilabel:`Equal`: splits the cost equally across each product included in the receipt, regardless of the quantity of each."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:62
msgid ":guilabel:`By Quantity`: splits the cost across each unit of all products in the receipt."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:63
msgid ":guilabel:`By Current Cost`: splits the cost according to the cost of each product unit, so a product with a higher cost receives a greater share of the landed cost."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:65
msgid ":guilabel:`By Weight`: splits the cost, according to the weight of the products in the receipt."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:66
msgid ":guilabel:`By Volume`: splits the cost, according to the volume of the products in the receipt."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:-1
msgid "Is a Landed Cost checkbox and Default Split Method on service type product form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:72
msgid "When creating new vendor bills, this product can be added as an invoice line as a landed cost."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:75
msgid "To apply a landed cost on a vendor bill, the products included in the original |PO| **must** belong to a *Product Category* with its *Force Removal Strategy* set to |FIFO|. The *Costing Method* can be set to either |AVCO| or |FIFO|, and the valuation method can be :doc:`manual <using_inventory_valuation>` or :doc:`automatic <inventory_valuation_config>`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:83
msgid "Navigate to :menuselection:`Purchase app --> New` to create a new request for quotation (RfQ). In the :guilabel:`Vendor` field, add a vendor to order products from. Then, click :guilabel:`Add a product`, under the :guilabel:`Products` tab, to add products to the |RfQ|."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:87
msgid "Once ready, click :guilabel:`Confirm Order` to confirm the order. Then, click :guilabel:`Receive Products` once the products have been received, followed by :guilabel:`Validate`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:91
msgid "Create vendor bill"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:93
msgid "Once the vendor fulfills the |PO| and sends a bill, a vendor bill can be created from the |PO| in Odoo."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:96
msgid "Navigate to the :menuselection:`Purchase app`, and click into the |PO| for which a vendor bill should be created. Then, click :guilabel:`Create Bill`. This opens a new :guilabel:`Vendor Bill` in the :guilabel:`Draft` stage."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:100
msgid "In the :guilabel:`Bill Date` field, click the line to open a calendar popover menu, and select the date on which this draft bill should be billed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:103
msgid "Then, under the :guilabel:`Invoice Lines` tab, click :guilabel:`Add a line`, and click the drop-down menu in the :guilabel:`Product` column to select the previously-created landed cost product. Click the :icon:`fa-cloud-upload` :guilabel:`(cloud with arrow)` icon to manually save and update the draft bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:-1
msgid "Landed Costs column checkboxes for product and landed cost."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:112
msgid "In the :guilabel:`Landed Costs` column, the product ordered from the vendor does **not** have its checkbox ticked, while the landed cost product's checkbox **is** ticked. This differentiates landed costs from all other costs displayed on the bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:116
msgid "Additionally, at the top of the form, a :guilabel:`Create Landed Costs` button appears."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:-1
msgid "Create Landed Costs button on vendor bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:123
msgid "Add landed cost"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:125
msgid "Once a landed cost is added to the vendor bill, click :guilabel:`Create Landed Costs` at the top of the vendor bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:128
msgid "Doing so automatically creates a landed cost record, with a set landed cost pre-filled in the product line in the :guilabel:`Additional Costs` tab."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:131
msgid "From the :guilabel:`Landed Cost` form, click the :guilabel:`Transfers` drop-down menu, and select which transfer the landed cost belongs to."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:-1
msgid "Landed cost form with selected receipt transfer."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:139
msgid "In addition to creating landed costs directly from a vendor bill, landed cost records can *also* be created by navigating to :menuselection:`Inventory app --> Operations --> Landed Costs`, and clicking :guilabel:`New`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:143
msgid "After setting the picking from the :guilabel:`Transfers` drop-down menu, click :guilabel:`Compute` (at the bottom of the form, under the :guilabel:`Total:` cost)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:146
msgid "Click the :guilabel:`Valuation Adjustments` tab to see the impact of the landed costs. The :guilabel:`Original Value` column lists the original price of the |PO|, the :guilabel:`Additional Landed Cost` column displays the landed cost, and the :guilabel:`New Value` displays the sum of the two, for the total cost of the |PO|."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:151
msgid "Once ready, click :guilabel:`Validate` to post the landed cost entry to the accounting journal."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:153
msgid "This causes a :guilabel:`Valuation` smart button to appear at the top of the form. Click the :guilabel:`Valuation` smart button to open a :guilabel:`Stock Valuation` page, with the product's updated valuation listed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:158
msgid "For a :guilabel:`Valuation` smart button to appear upon validation, the product's :guilabel:`Product Type` **must** be set to :guilabel:`Storable`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:161
msgid "To view the valuation of *every* product, including landed costs, navigate to :menuselection:`Inventory app --> Reporting --> Valuation`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:165
msgid "Each journal entry created for a landed cost on a vendor bill can be viewed in the *Accounting* app."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:168
msgid "To locate these journal entries, navigate to :menuselection:`Accounting app --> Accounting --> Journal Entries`, and locate the correct entry, by number (i.e. `PBNK1/2024/XXXXX`)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:171
msgid "Click into the journal entry to view the :guilabel:`Journal Items`, and other information about the entry."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.rst:0
msgid "Journal Entry form for landed cost created from vendor bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/inventory_valuation_config.rst:3
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/using_inventory_valuation.rst:15
msgid "Automatic inventory valuation"
@ -4089,6 +3893,202 @@ msgstr ""
msgid "Show Stock Valuation journals in a list."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:3
msgid "Landed costs"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:10
msgid "When shipping products to customers, the landed cost is the total price of a product or shipment, including all expenses associated with shipping the product."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:13
msgid "In Odoo, the *Landed Costs* feature is used to take additional costs into account when calculating the valuation of a product. This includes the cost of shipment, insurance, customs duties, taxes, and other fees."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:20
msgid "To add landed costs to products, the *Landed Costs* feature must first be enabled. To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll to the :guilabel:`Valuation` section."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:24
msgid "Tick the checkbox next to the :guilabel:`Landed Costs` option, and click :guilabel:`Save` to save changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:27
msgid "Once the page refreshes, a new :guilabel:`Default Journal` field appears below the :guilabel:`Landed Costs` feature in the :guilabel:`Valuation` section."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:30
msgid "Click the :guilabel:`Default Journal` drop-down menu to reveal a list of accounting journals. Select a journal for which all accounting entries related to landed costs should be recorded."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:-1
msgid "Landed Costs feature and resulting Default Journal field in the Inventory settings."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:37
msgid "Create landed cost product"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:39
msgid "For charges that are consistently added as landed costs, a landed cost product can be created in Odoo. This way, a landed cost product can be quickly added to a vendor bill as an invoice line, instead of having to be manually entered every time a new vendor bill is created."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:43
msgid "To do this, create a new product by going to :menuselection:`Inventory app --> Products --> Products`, and clicking :guilabel:`New`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:46
msgid "Assign a name to the landed cost product in the :guilabel:`Product Name` field (i.e. `International Shipping`). In the :guilabel:`Product Type` field, click the drop-down menu, and select :guilabel:`Service` as the :guilabel:`Product Type`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:51
msgid "Landed cost products **must** have their :guilabel:`Product Type` set to :guilabel:`Service`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:53
msgid "Click the :guilabel:`Purchase` tab, and tick the checkbox next to :guilabel:`Is a Landed Cost` in the :guilabel:`Vendor Bills` section. Once ticked, a new :guilabel:`Default Split Method` field appears below it, prompting a selection. Clicking that drop-down menu reveals the following options:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:57
msgid ":guilabel:`Equal`: splits the cost equally across each product included in the receipt, regardless of the quantity of each."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:59
msgid ":guilabel:`By Quantity`: splits the cost across each unit of all products in the receipt."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:60
msgid ":guilabel:`By Current Cost`: splits the cost according to the cost of each product unit, so a product with a higher cost receives a greater share of the landed cost."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:62
msgid ":guilabel:`By Weight`: splits the cost, according to the weight of the products in the receipt."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:63
msgid ":guilabel:`By Volume`: splits the cost, according to the volume of the products in the receipt."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:-1
msgid "Is a Landed Cost checkbox and Default Split Method on service type product form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:68
msgid "When creating new vendor bills, this product can be added as an invoice line as a landed cost."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:71
msgid "To apply a landed cost on a vendor bill, products in the original |PO| **must** belong to a *Product Category* with a *Costing Method* of either |AVCO| or |FIFO|, and the valuation method can be :doc:`manual <using_inventory_valuation>` or :doc:`automatic <inventory_valuation_config>`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:79
msgid "Navigate to :menuselection:`Purchase app --> New` to create a new request for quotation (RfQ). In the :guilabel:`Vendor` field, add a vendor to order products from. Then, click :guilabel:`Add a product`, under the :guilabel:`Products` tab, to add products to the |RfQ|."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:83
msgid "Once ready, click :guilabel:`Confirm Order` to confirm the order. Then, click :guilabel:`Receive Products` once the products have been received, followed by :guilabel:`Validate`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:87
msgid "Create vendor bill"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:89
msgid "Once the vendor fulfills the |PO| and sends a bill, a vendor bill can be created from the |PO| in Odoo."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:92
msgid "Navigate to the :menuselection:`Purchase app`, and click into the |PO| for which a vendor bill should be created. Then, click :guilabel:`Create Bill`. This opens a new :guilabel:`Vendor Bill` in the :guilabel:`Draft` stage."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:96
msgid "In the :guilabel:`Bill Date` field, click the line to open a calendar popover menu, and select the date on which this draft bill should be billed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:99
msgid "Then, under the :guilabel:`Invoice Lines` tab, click :guilabel:`Add a line`, and click the drop-down menu in the :guilabel:`Product` column to select the previously-created landed cost product. Click the :icon:`fa-cloud-upload` :guilabel:`(cloud with arrow)` icon to manually save and update the draft bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:-1
msgid "Landed Costs column checkboxes for product and landed cost."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:107
msgid "In the :guilabel:`Landed Costs` column, the product ordered from the vendor does **not** have its checkbox ticked, while the landed cost product's checkbox **is** ticked. This differentiates landed costs from all other costs displayed on the bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:111
msgid "Additionally, at the top of the form, a :guilabel:`Create Landed Costs` button appears."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:-1
msgid "Create Landed Costs button on vendor bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:117
msgid "Add landed cost"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:119
msgid "Once a landed cost is added to the vendor bill, click :guilabel:`Create Landed Costs` at the top of the vendor bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:122
msgid "Doing so automatically creates a landed cost record, with a set landed cost pre-filled in the product line in the :guilabel:`Additional Costs` tab."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:125
msgid "From the :guilabel:`Landed Cost` form, click the :guilabel:`Transfers` drop-down menu, and select which transfer the landed cost belongs to."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:-1
msgid "Landed cost form with selected receipt transfer."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:132
msgid "In addition to creating landed costs directly from a vendor bill, landed cost records can *also* be created by navigating to :menuselection:`Inventory app --> Operations --> Landed Costs`, and clicking :guilabel:`New`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:136
msgid "After setting the picking from the :guilabel:`Transfers` drop-down menu, click :guilabel:`Compute` (at the bottom of the form, under the :guilabel:`Total:` cost)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:139
msgid "Click the :guilabel:`Valuation Adjustments` tab to see the impact of the landed costs. The :guilabel:`Original Value` column lists the original price of the |PO|, the :guilabel:`Additional Landed Cost` column displays the landed cost, and the :guilabel:`New Value` displays the sum of the two, for the total cost of the |PO|."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:144
msgid "Once ready, click :guilabel:`Validate` to post the landed cost entry to the accounting journal."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:146
msgid "This causes a :guilabel:`Valuation` smart button to appear at the top of the form. Click the :guilabel:`Valuation` smart button to open a :guilabel:`Stock Valuation` page, with the product's updated valuation listed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:151
msgid "For a :guilabel:`Valuation` smart button to appear upon validation, the product's :guilabel:`Product Type` **must** be set to :guilabel:`Storable`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:154
msgid "To view the valuation of *every* product, including landed costs, navigate to :menuselection:`Inventory app --> Reporting --> Valuation`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:158
msgid "Each journal entry created for a landed cost on a vendor bill can be viewed in the *Accounting* app."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:161
msgid "To locate these journal entries, navigate to :menuselection:`Accounting app --> Accounting --> Journal Entries`, and locate the correct entry, by number (i.e. `PBNK1/2024/XXXXX`)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:164
msgid "Click into the journal entry to view the :guilabel:`Journal Items`, and other information about the entry."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/landed_costs.rst:0
msgid "Journal Entry form for landed cost created from vendor bill."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/using_inventory_valuation.rst:3
msgid "Using inventory valuation"
msgstr ""

228
locale/sources/marketing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"POT-Creation-Date: 2024-12-02 12:38+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"
@ -1007,134 +1007,234 @@ msgid "Analyze metrics"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:7
msgid "In order to properly understand the success or failure of an email marketing campaign, it is necessary to monitor several key metrics. The insights gained from these metrics can then be used to optimize future campaigns. Odoo's *Email Marketing* application tracks several :ref:`key metrics <email-marketing/key-metrics>`, that can be interpreted to improve future campaigns."
msgid "In order to properly understand the success or failure of an email marketing campaign, it is necessary to monitor several key metrics. The insights gained from these metrics can then be used to optimize future campaigns. Odoo's **Email Marketing** application tracks several :ref:`key metrics <email-marketing/view-metrics>`, that can be interpreted through :ref:`reports <email_marketing/create_reports>` to improve future campaigns."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:13
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:16
msgid "View metrics"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:15
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:18
msgid "After a mass mail has been sent, the results for that particular mailing are displayed in multiple locations."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:18
msgid "To access the metrics for an individual mailing, navigate to :menuselection:`Email Marketing app --> Mailings`. Locate the specific mailing in the list view, and use the column headings to view the results for that mailing. Click on one of the mailings in the list to open the record. At the top of the record, detailed metrics are displayed as smart buttons."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:21
msgid "To access the metrics for an individual mailing, navigate to :menuselection:`Email Marketing app --> Mailings`. Locate the specific mailing in the list view, and use the column headings to view the results for that mailing. Click on one of the mailings in the list to open the record."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:25
msgid "At the top of the record, detailed metrics are displayed as smart buttons."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:-1
msgid "The smart buttons on a mass mailing, displaying the results of the message."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:28
msgid "Click on the smart buttons to see the recipient records for each metric."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:33
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:32
msgid "Opened rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:35
msgid "The *Opened* rate measures the percentage of emails opened by recipients against the total number of sent emails."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:34
msgid "The percentage of emails opened by recipients, against the total number of sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:38
msgid "A high open rate may indicate that the subject line was timely, compelling, and successfully prompted the recipients to view the message."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:36
msgid "In cases where a reply is expected, such as cold outreach emails, high open rate may indicate the subject line was timely, compelling, and successfully prompted the recipients to view the message."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:41
msgid "A low open rate may indicate the subject line failed to capture the recipients' interest. It could also indicate the email ended up in a spam or junk folder due to having a poor sender reputation or failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>`."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:39
msgid "In cases where a reply is not expected, such as promotional emails, it may indicate an issue with the email, such as incorrect product links or coupon codes."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:46
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:42
msgid "In cases where a reply is expected, a low open rate may indicate the subject line failed to capture the recipients' interest or the message ended up in a spam or junk folder. It could also indicate the email ended up in a spam or junk folder."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:47
msgid "Emails that consistently land in recipient spam folders could be due to having a poor sender reputation (i.e. high unsubscribe rate, high percentage of past emails marked as spam, etc.), or failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:53
msgid "Replied rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:48
msgid "The *Replied* rate measures the percentage of recipients who responded to the email directly against the total number of sent emails."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:55
msgid "The percentage of recipients who responded to the email, against the total number of sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:51
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:57
msgid "A high replied rate may indicate the email resonated with recipients, prompting them to take action or provide feedback."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:54
msgid "A low replied rate may suggest that the message lacked relevance or did not contain a clear call to action."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:60
msgid "A low replied rate may suggest the message lacked relevance or did not contain a clear call-to-action."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:58
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:64
msgid "Clicked rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:60
msgid "The *Clicked* through rate (CTR), measures the percentage of recipients who clicked on a link within the email against the total number of sent emails."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:66
msgid "This represents the *Clicked through rate (CTR)*, which measures the percentage of recipients who clicked on a link within the email, against the total number of sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:63
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:70
msgid "A high |CTR| may indicate the email content was relevant and appropriately targeted. Recipients were motivated to click the links provided, and likely found the content engaging."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:66
msgid "A low |CTR| may indicate issues with either the targeting, or the content itself. Recipients may have been unmotivated by the calls to action, if there were any, or the message itself may have been directed toward the wrong audience."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:73
msgid "A low |CTR| may indicate issues with either the targeting, or the content itself. Recipients may have been unmotivated by the calls-to-action, if there were any, or the message itself may have been directed toward the wrong audience."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:71
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:78
msgid "Received rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:73
msgid "The *Received* rate measures the percentage of emails that were successfully delivered against the total number of sent emails."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:80
msgid "This rate measures the percentage of emails that were **successfully** delivered, against the total number of sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:76
msgid "A high received rate can indicate that the mailing list used is up to date and the sender authentication is trusted by email providers."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:79
msgid "A low received rate may indicate issues either with the mailing list used for the mailing or with the sender authentication. View the :ref:`email-marketing/deliverability-issues` section for more information."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:84
msgid "Bounced rate"
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:83
msgid "A high received rate can indicate the mailing list used is up-to-date, and the sender authentication is trusted by email providers."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:86
msgid "The *Bounced* rate measures the percentage of emails that were unsuccessfully delivered, against the total number of sent emails."
msgid "A low received rate may indicate issues, either with the mailing list used for the mailing, or with the sender authentication. View the :ref:`email-marketing/deliverability-issues` section for more information."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:89
msgid "A high bounce rate could indicate issues either with the mailing list used for the mailing or with the sender authentication."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:91
msgid "Bounced rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:92
msgid "A low bounce rate may indicate that the mailing list used is up to date and the sender authentication is trusted by email providers. View the :ref:`email-marketing/deliverability-issues` section for more information."
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:93
msgid "This rate measures the percentage of emails that were **unsuccessfully** delivered, and did not enter a recipient's inbox, against the total number of sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:96
msgid "A high bounce rate could indicate issues, either with the mailing list used for the mailing, or with the sender authentication."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:99
msgid "Deliverability issues"
msgid "A low bounce rate may indicate that the mailing list used is up-to-date, and the sender authentication is trusted by email providers. View the :ref:`email-marketing/deliverability-issues` section for more information."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:101
msgid "The following define possible reasons for a high bounce rate or low received rate:"
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:104
msgid "Click on the respective smart buttons to see all the corresponding recipient records that are attributed to each metric. When these filtered records are in view, multiple types of reports can be run for further analysis."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:103
msgid "Using a mailing list that contains outdated contact information, or malformed email addresses are likely to result in a high bounce rate and/or a low received rate."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:105
msgid "Mailings sent using a *From* email address that differs from the sender's domain are likely to bounce with certain email providers due to failing :ref:`DMARC authentication <email-domain-dmarc>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:108
msgid "Failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>` can also result in a high bounce rate."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:112
msgid ":ref:`Mailing campaigns <email_marketing/mailing-campaigns>`"
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:111
msgid "Create metrics reports"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:113
msgid "Individual metrics can be analyzed by creating a report. To begin, click on the smart button of the desired metric."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:116
msgid "Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar to see a drop-down menu of filtering and grouping parameters."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:119
msgid ":guilabel:`Filters`, located in the left column of the search options, can be used to keep only the results that fit the filter. For example, selecting the *Bounced* filter only shows emails that could not be delivered."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:123
msgid ":guilabel:`Group By`, found in the middle column, is used to organize the results into groups, and can be used with or without filters."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:127
msgid "Setting multiple :guilabel:`Group By` options creates nested groups, according to which option is selected first. For example, selecting :guilabel:`Sent Period`, followed by :guilabel:`Add Custom Group --> Responsible`, in the :guilabel:`Group By` column, sorts all results *first* by the sent period, *then* by the team member responsible. This is a useful metric for analyzing who on the team is sending in volume or quantity over a set time period."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:133
msgid "This can be verified by looking at the direction, and order, of the selections in the group tile that appears in the search bar after the selections are made."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:137
msgid "A monthly newsletter has been sent out, and 6.9% of the sent emails were bounced."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "The metrics smart buttons of the newsletter."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:143
msgid "To see what these bounced recipients have in common, the records are grouped using a custom group targeting :guilabel:`Mailing Lists`, which groups all records by the mailing lists they are on. The records are then filtered using a custom filter with the rule `Created on >= 07/01/2024 00:00:00`, to filter by when the mailing list was last checked. This filter only includes recipients that have been created on, or after, July 1st, 2024, in the report."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "The custom filter creation form."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:153
msgid "Using these configurations, it is evident that all the recipients with bounced emails were added after the list was last checked. Looking closer at the domains, it is evident that each recipient has a malformed email domain (i.e: @yaoo.com instead of @yahoo.com), likely due to a manual entry error while updating the database."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "A list of bounced email addresses with malformed email domains."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:163
msgid "View :doc:`../../essentials/search` for more information about making custom groups and filters."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:169
msgid "Mass mailing analysis"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:171
msgid "It is also possible to analyze the success between mailing campaigns by creating a *Mass Mailing Analysis* report. To begin, navigate to :menuselection:`Email Marketing app --> Reporting --> Mass Mailing Analysis`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:175
msgid "A dashboard appears displaying a bar chart containing each mailing campaign. By default, :guilabel:`Sent` is selected, displaying the number of sent records on the y-axis. To change the measure, click the :guilabel:`Measures` button, and select the desired measure from the drop-down menu."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:181
msgid "The following chart displays the number of opened emails from two different mass mailings."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:183
msgid "In this view, it can be seen that the first mass mailing led to a higher opened rate than the second. Because a lower opened rate can sometimes be attributed to a subject line that failed to capture readers' attention, the subject line of each mass mailing can be a good place to begin looking."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "A bar chart displaying the different opened rate between two mass mailing campaigns."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:192
msgid "Comparing the two subject lines, it is clear the newsletter's subject line was less engaging, which may have led to the lower opened rate, when compared to the other mass mailing."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "alt text"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:200
msgid "Deliverability issues"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:202
msgid "The following define possible reasons for a high bounce rate or low received rate:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:204
msgid "Using a mailing list that contains outdated contact information, or malformed email addresses are likely to result in a high bounce rate and/or a low received rate."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:206
msgid "Mailings sent using a *From* email address that differs from the sender's domain are likely to bounce with certain email providers due to failing :ref:`DMARC authentication <email-domain-dmarc>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:209
msgid "Failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>` can also result in a high bounce rate."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:213
msgid ":ref:`Mailing campaigns <email_marketing/mailing-campaigns>`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:214
msgid ":doc:`Manage unsubscriptions <unsubscriptions>`"
msgstr ""

359
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"POT-Creation-Date: 2024-12-02 12:38+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"
@ -385,7 +385,7 @@ msgid "Information added to the :guilabel:`Extra Message on Confirmation` field
msgstr ""
#: ../../content/applications/productivity/calendar/google.rst:3
msgid "Synchronize Google calendar with Odoo"
msgid "Google Calendar synchronization"
msgstr ""
#: ../../content/applications/productivity/calendar/google.rst:5
@ -1525,124 +1525,285 @@ msgid "Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:8
msgid "Odoo *Discuss* is an internal communication app that allows users to connect through messages, notes, and file sharing, either through a persistent chat window that works across applications, or through the dedicated *Discuss* dashboard."
msgid "Odoo **Discuss** is an internal communication app that allows users to connect through messages, notes, file sharing, and video calls. **Discuss** enables communication through a persistent chat window that works across applications, or through the dedicated *Discuss* dashboard."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:12
msgid "Upon opening the :menuselection:`Discuss app`, the :guilabel:`Discuss` dashboard appears."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:15
msgid "Choose notifications preference"
msgid "Inbox, starred, and history"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:17
msgid "Access user-specific preferences for the *Discuss* app by navigating to :menuselection:`Settings app --> Users --> User --> Preferences tab`."
msgid "Upon opening the :menuselection:`Discuss app`, the *Discuss* dashboard appears."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:19
msgid "On the :guilabel:`Discuss` dashboard, unread messages are visible in the :icon:`fa-inbox` :guilabel:`Inbox`. :icon:`fa-star-o` :guilabel:`Starred` is where starred messages are stored. :icon:`fa-history` :guilabel:`History` shows chatter updates for records in the Odoo database the user has been assigned to, or tagged on."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:25
msgid "Direct messages"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:27
msgid "*Direct messages* allow the user to communicate privately with one or multiple team members. To start a new direct message, click the :icon:`fa-plus` icon, next to :guilabel:`Direct Messages` on the :guilabel:`Discuss` dashboard, and enter the name of the desired person in the :guilabel:`Start a conversation` search bar that appears."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:33
msgid "Multiple names can be selected in the :guilabel:`Start a conversation` search bar. Once all of the names have been entered, press :kbd:`Enter`."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:37
msgid "Direct message actions"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:39
msgid "Hover over a direct message in the chat window to see a menu of actions to take on the message."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:41
msgid ":icon:`oi-smile-add` :guilabel:`(Add a Reaction)`: open a drop-down menu of emojis that can be used to react to the direct message."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:43
msgid ":icon:`fa-reply` :guilabel:`(Reply)`: reply to the direct message in a thread."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:44
msgid ":icon:`fa-star-o` :guilabel:`(Mark as Todo)`: add the message to the :guilabel:`Starred` tab."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:45
msgid ":icon:`fa-ellipsis-h` :guilabel:`(Expand)`: reveals more message actions, including:"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:47
msgid ":icon:`fa-thumb-tack` :guilabel:`Pin`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:48
msgid ":icon:`fa-eye-slash` :guilabel:`Mark as Unread`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:49
msgid ":icon:`fa-pencil` :guilabel:`Edit`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:50
msgid ":icon:`fa-trash` :guilabel:`Delete`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:53
msgid "Conversation actions"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:55
msgid "The icons in the top-right corner of a direct message conversation represent different actions the user can take on that conversation."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:58
msgid "Click :icon:`fa-bell` :guilabel:`Notification Settings` to set up notification preferences for the conversation, or click :icon:`fa-phone` :guilabel:`Start a Call` to begin a meeting. See the :ref:`Meetings <discuss/meetings>` section for more information about meetings."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:62
msgid "At the top of the direct message window, click the name of the direct message to change the group name, and choose to add a description in the adjacent :guilabel:`Add a description` field."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of the conversation actions."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:70
msgid "The :guilabel:`Add a description` field is **only** available for group messages with more than two participants."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:74
msgid "User status"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:76
msgid "It is helpful to see what colleagues are up to, and how quickly they can respond to messages, by checking their status. The status is displayed as a circle in the bottom-right corner of a contact's photo in the :icon:`fa-users` :guilabel:`(Members List)`."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:80
msgid "The color of the circle represents the user's status:"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:82
msgid "Green = online"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:83
msgid "Orange = away"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:84
msgid "White = offline"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:85
msgid "Airplane = out of the office"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:88
msgid "Leave a direct message conversation"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:90
msgid "To leave a direct message conversations, click the :icon:`fa-times` :guilabel:`(Leave this channel)` icon next to the conversation name in the :guilabel:`Direct Messages` section of the sidebar."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:94
msgid "Leaving a conversation does **not** delete the direct messages in the conversation. The direct message conversation's history is visible when another direct message with the same person, or group, is created."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:101
msgid "Meetings"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:103
msgid "In **Discuss**, *Meetings* are video calls. To start a meeting from the :guilabel:`Discuss` dashboard, click :guilabel:`Start a meeting` in the top-left corner, and select who to invite to the meeting, via the :guilabel:`Invite People` drop-down window that appears. To start a meeting from a direct message, click the :icon:`fa-phone` :guilabel:`Start a Call` icon in the top-right corner."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of a Meeting in Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:111
msgid "Once a meeting has been started, the following buttons can be used:"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:114
msgid "Icon"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:114
#: ../../content/applications/productivity/knowledge/articles_editing.rst:119
#: ../../content/applications/productivity/knowledge/articles_editing.rst:149
#: ../../content/applications/productivity/knowledge/articles_editing.rst:169
#: ../../content/applications/productivity/knowledge/articles_editing.rst:183
#: ../../content/applications/productivity/knowledge/articles_editing.rst:201
#: ../../content/applications/productivity/knowledge/articles_editing.rst:215
#: ../../content/applications/productivity/knowledge/articles_editing.rst:240
msgid "Use"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:116
msgid ":icon:`fa-microphone`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:116
msgid ":guilabel:`Mute`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:118
msgid ":icon:`fa-microphone-slash`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:118
msgid ":guilabel:`Unmute`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:120
msgid ":icon:`fa-headphones`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:120
msgid ":guilabel:`Deafen`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:122
msgid ":icon:`fa-deaf`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:122
msgid ":guilabel:`Undeafen`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:124
msgid ":icon:`fa-video-camera`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:124
msgid ":guilabel:`Turn camera on/off`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:126
msgid ":icon:`fa-hand-paper-o`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:126
msgid ":guilabel:`Raise Hand`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:128
msgid ":icon:`fa-desktop`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:128
msgid ":guilabel:`Share Screen`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:130
msgid ":icon:`fa-arrows-alt`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:130
msgid ":guilabel:`Enter Full Screen`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:136
msgid "User-specific notification preferences"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:138
msgid "Access user-specific preferences for the **Discuss** app by navigating to :menuselection:`Settings app --> Manage Users`, select a user, then click the :guilabel:`Preferences` tab."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of the Preferences tab for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:23
msgid "By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this setting enabled, a notification email will be sent by Odoo every time a message is sent from the chatter, a note is sent with an `@` mention (from chatter), or a notification is sent for a record that the user follows. Something that triggers a notification is changing of the stage (if an email\\ is configured to be sent, for example if the task is set to :guilabel:`Done`)."
#: ../../content/applications/productivity/discuss.rst:144
msgid "By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this setting enabled, a notification email is sent by Odoo every time a message is sent from the chatter of a record, a note is sent with an `@` mention (from the chatter of a record), or a notification is sent for a record the user follows."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:29
msgid "By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the *Discuss* app's *inbox*. Messages can have the following actions taken on them: respond with an emoji by clicking :guilabel:`Add a Reaction`, or reply to the message by clicking on :guilabel:`Reply`. Additional actions may include starring the message by clicking :guilabel:`Marked as Todo`, or pinning the message by selecting :guilabel:`Pin` or even mark the message as unread by selecting :guilabel:`Marked as unread`."
#: ../../content/applications/productivity/discuss.rst:149
msgid "By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the **Discuss** app's *Inbox*."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:153
msgid "Chat from different applications"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:155
msgid "The **Discuss** application enables communication across all of Odoo's applications. To view chats and channels, or start a new message, select the speech bubbles that are consistently present in the upper-right corner of the database header."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of an inbox message and its action options in Odoo Discuss."
msgid "Use Discuss across other applications by clicking the speech bubbles."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:39
msgid "Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the :guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the message to :guilabel:`History`."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of messages marked as todo in Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:46
msgid "Start chatting"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:48
msgid "The first time a user logs in to their account, OdooBot sends a message asking for permission to send desktop notifications for chats. If accepted, the user will receive push notifications on their desktop for the messages they receive, regardless of where the user is in Odoo."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of the messages under the messaging menu emphasizing the request for push\n"
"notifications for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:57
msgid "To stop receiving desktop notifications, reset the notifications settings of the browser."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:59
msgid "To start a chat, go to the :menuselection:`Discuss` app and click on the :guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or :guilabel:`Channels` in the left menu of the dashboard."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of Discuss's panel emphasizing the titles channels and direct messages in Odoo\n"
"Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:67
msgid "A company can also easily create :doc:`public and private channels <discuss/team_communication>`."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:70
msgid "Mentions in the chat and on the chatter"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:72
msgid "To mention a user within a chat or the chatter, type `@user-name`; to refer to a channel, type `#channel-name`. The user mentioned will be notified in their *inbox* or through an email, depending on their communication settings."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of a couple of chat window messages for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:80
msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task's followers, and secondly on employees. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:85
msgid "User status"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:87
msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *status*. The status is shown on the left side of a contact's name on the :guilabel:`Discuss` sidebar, on the *messaging menu* and when listed in the *chatter*."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:91
msgid "Green = online"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:92
msgid "Orange = away"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:93
msgid "White = offline"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:94
msgid "Airplane = out of the office"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:-1
msgid "View of the contacts' status for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss.rst:101
#: ../../content/applications/productivity/discuss.rst:163
msgid ":doc:`discuss/team_communication`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:102
#: ../../content/applications/productivity/discuss.rst:164
#: ../../content/applications/productivity/discuss/team_communication.rst:114
msgid ":doc:`/applications/essentials/activities`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:165
msgid ":doc:`discuss/ice_servers`"
msgstr ""
#: ../../content/applications/productivity/discuss.rst:166
msgid ":doc:`discuss/chatter`"
msgstr ""
#: ../../content/applications/productivity/discuss/chatter.rst:3
msgid "Chatter"
msgstr ""
@ -3032,16 +3193,6 @@ msgstr ""
msgid "Command"
msgstr ""
#: ../../content/applications/productivity/knowledge/articles_editing.rst:119
#: ../../content/applications/productivity/knowledge/articles_editing.rst:149
#: ../../content/applications/productivity/knowledge/articles_editing.rst:169
#: ../../content/applications/productivity/knowledge/articles_editing.rst:183
#: ../../content/applications/productivity/knowledge/articles_editing.rst:201
#: ../../content/applications/productivity/knowledge/articles_editing.rst:215
#: ../../content/applications/productivity/knowledge/articles_editing.rst:240
msgid "Use"
msgstr ""
#: ../../content/applications/productivity/knowledge/articles_editing.rst:120
msgid ":guilabel:`Bulleted list`"
msgstr ""

30
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"POT-Creation-Date: 2024-12-02 12:38+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"
@ -61,7 +61,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:20
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:12
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:19
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:13
@ -5432,7 +5432,7 @@ msgid "Epson printers using Wi-Fi/Ethernet connections and following the `EPOS S
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:60
msgid "Thermal printers using ESC/POS or StarPRNT protocol are compatible **with** an :doc:`IoT Box </applications/general/iot/devices/printer>`."
msgid "Thermal printers using ESC/POS are compatible **with** an :doc:`IoT Box </applications/general/iot/devices/printer>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:62
@ -6114,7 +6114,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:73
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:41
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:30
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:81
@ -6420,38 +6420,34 @@ msgid "Connecting a SIX payment terminal allows you to offer a fluid payment flo
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9
msgid "Starting in July 2022, it will **not** be possible anymore to connect and use a Six payment terminal in PoS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:11
msgid "Even though Worldline has recently acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are therefore not compatible with this integration."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:17
msgid "Install the POS IoT Six module"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:21
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19
msgid "To activate the POS IoT Six module, go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds the necessary driver and interface to your database to detect Six terminals."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:26
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:24
msgid "This module replaces the **POS Six** module."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:27
msgid "Connect an IoT box"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:31
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29
msgid "Connecting a Six payment terminal to Odoo is requires :doc:`using a Raspberry Pi or virtual (for Windows OS only) IoT box </applications/general/iot/config/connect>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33
msgid "Configure the terminal ID"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35
msgid "Navigate to your IoT Box homepage, where you can find the :guilabel:`Six payment terminal` field once your database server is connected to the IoT box. Click :guilabel:`Configure`, fill in the :guilabel:`Terminal ID` field with the ID received from Six, and click :guilabel:`Connect`. Your Six terminal ID should appear in the :guilabel:`Current Terminal Id` section."
msgstr ""
@ -6459,7 +6455,7 @@ msgstr ""
msgid "Setting the Six terminal ID"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:45
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:43
msgid "Odoo automatically restarts the IoT box when the Six terminal ID is configured. If your Six terminal is online, it will be automatically detected and connected to the database. Check the IoT box homepage under the :guilabel:`Payments` section to confirm the connection."
msgstr ""
@ -6467,7 +6463,7 @@ msgstr ""
msgid "Confirming the connection to the Six payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:57
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55
msgid "Enable the payment terminal :ref:`in the application settings <configuration/settings>` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`SIX IOT` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field."
msgstr ""

82
locale/sources/websites.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"POT-Creation-Date: 2024-12-02 12:38+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"
@ -1755,91 +1755,71 @@ msgid "Cross-selling and upselling"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:5
msgid "Any sales process is an opportunity to maximize revenues. **Cross-selling and upselling** are sales techniques consisting in selling customers additional or more expensive products and services than what they were originally shopping for. It is a great way to maximize the value of each one of your customers."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:10
msgid "**Cross-selling** can be done via **two** features:"
msgid ":ref:`Cross-selling <ecommerce/cross_selling>` and :ref:`upselling <ecommerce/cross_upselling/alternative>` are sales techniques designed to encourage customers to purchase additional or higher-priced products and services from your :doc:`catalog`."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:12
msgid ":ref:`Optional products <cross_upselling/optional>` upon **adding to cart**;"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:13
msgid ":ref:`Accessory products <cross_upselling/accessory>` on the **checkout page**."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:15
msgid "**Upselling** is only done via :ref:`alternative products <cross_upselling/alternative>` on the **product page**."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:19
msgid ":doc:`catalog`"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:22
msgid "Cross-selling"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:27
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:14
msgid "Cross-selling can be achieved by suggesting :ref:`optional products <ecommerce/cross_upselling/optional>` when items are added to the cart or by recommending :ref:`accessory products <ecommerce/cross_upselling/accessory>` on the checkout page."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:21
msgid "Optional products"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:29
msgid "**Optional products** are suggested when customers click :guilabel:`Add to cart`, either from the **product page** or **catalog page**. Upon clicking, a pop-up window opens with the **optional products** displayed in the :guilabel:`Available Options` section."
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:23
msgid "**Optional products** are suggested when the customer selects a product and clicks :guilabel:`Add to cart`."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:26
msgid "To enable **optional products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Optional Products` field."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:-1
msgid "Optional products cross-selling"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:37
msgid "To enable **optional products** go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Optional Products` field. Optional products are **linked** to the product(s) they are set up with on the **product template**. They only appear when that product is added to the cart."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:43
msgid "You can also access the :guilabel:`Sales` tab of the **product template** by selecting a product on your **main shop page** and clicking :guilabel:`Product` in the top-right corner."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:49
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:36
msgid "Accessory products"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:51
msgid "**Accessory products** are displayed in the :guilabel:`Suggested Accessories` section before processing to checkout at the :guilabel:`Review Order` step."
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:38
msgid "**Accessory products** are showcased in the :guilabel:`Suggested Accessories` section during the :guilabel:`Review Order` step, just before proceeding to checkout."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:41
msgid "To enable **accessory products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Accessory Products` field."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:-1
msgid "Suggested accessories at checkout during cart review"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:58
msgid "To enable **accessory products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Accessory Products` field. Suggested accessory products are **linked** to the product(s) they are set up with on the **product template**. They only appear when that product is at the checkout process review."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:65
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:51
msgid "Upselling"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:70
msgid "Alternative products"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:72
msgid "**Alternative products** are suggested on the **product page** and usually incentivize customers to buy a more expensive variant or product than the one they were initially shopping for."
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:53
msgid "You can display **alternative products** at the bottom of the product page as an upselling technique, encouraging customers to consider a more expensive variant or product than their initial choice by presenting appealing alternatives."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:-1
msgid "Alternative products on the product page"
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:79
msgid "To enable **alternative products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Alternative Products` field. Then, go to the related **product page** by clicking :guilabel:`Go To Website`, and click :menuselection:`Edit`. Stay on the :guilabel:`Blocks` tab, and scroll down to the :guilabel:`Dynamic Content` section. Then, drag and drop the :guilabel:`Products` building block anywhere on the **product page**."
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:60
msgid "To enable alternative products, navigate to :menuselection:`Website --> eCommerce --> Products`, select the desired product, and go to the :guilabel:`Sales` tab. In the :guilabel:`Alternative Products` field, add the products you want to feature."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:86
msgid "When placed, in :guilabel:`Edit` mode, click the **block** to access various settings for that :guilabel:`Products` building block. In the :guilabel:`Filter` field, select :guilabel:`Alternative Products`. You can configure several additional settings, such as how many elements are displayed (:guilabel:`Fetched Elements`), the :guilabel:`Template` used, etc."
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:64
msgid "Click :guilabel:`Go to Website` to view the alternative products displayed at the bottom of the product page."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:67
msgid "To adjust the settings, click :guilabel:`Edit` and select the related :doc:`building block <../../website/web_design/building_blocks>`. In the :guilabel:`Customize` tab, scroll to the :guilabel:`Alternative Products` section and modify the settings as needed to tailor the display to your preferences."
msgstr ""
#: ../../content/applications/websites/ecommerce/products/price_management.rst:3