diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 19908ffee..2a51ba3e2 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -377,7 +377,7 @@ msgid "Deactivated features" msgstr "" #: ../../content/administration/neutralized_database.rst:24 -msgid "Here is a non-exhaustive list of the deactivated parameters:" +msgid "Here is a non-exhaustive list of the deactivated features:" msgstr "" #: ../../content/administration/neutralized_database.rst:26 @@ -404,7 +404,11 @@ msgstr "" msgid ":abbr:`IAP (In-App Purchase)` tokens" msgstr "" -#: ../../content/administration/neutralized_database.rst:34 +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 msgid "**A red banner at the top of the screen is displayed on the neutralized database so that it can be seen immediately.**" msgstr "" @@ -2831,7 +2835,6 @@ msgstr "" #: ../../content/administration/supported_versions.rst:47 #: ../../content/administration/supported_versions.rst:48 #: ../../content/administration/supported_versions.rst:49 -#: ../../content/administration/supported_versions.rst:53 #: ../../content/administration/supported_versions.rst:77 #: ../../content/administration/supported_versions.rst:78 #: ../../content/administration/supported_versions.rst:79 @@ -4952,14 +4955,7 @@ msgstr "" msgid "Odoo saas~16.4" msgstr "" -#: ../../content/administration/supported_versions.rst:56 -msgid "August 2023" -msgstr "" - -#: ../../content/administration/supported_versions.rst:58 -msgid "Odoo saas~16.3" -msgstr "" - +#: ../../content/administration/supported_versions.rst:53 #: ../../content/administration/supported_versions.rst:59 #: ../../content/administration/supported_versions.rst:65 #: ../../content/administration/supported_versions.rst:71 @@ -4977,6 +4973,14 @@ msgstr "" msgid "|red|" msgstr "" +#: ../../content/administration/supported_versions.rst:56 +msgid "August 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "Odoo saas~16.3" +msgstr "" + #: ../../content/administration/supported_versions.rst:62 msgid "June 2023" msgstr "" diff --git a/locale/sources/essentials.pot b/locale/sources/essentials.pot index 13fb727a4..751b09c17 100644 --- a/locale/sources/essentials.pot +++ b/locale/sources/essentials.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -24,59 +24,59 @@ msgstr "" msgid "Activities" msgstr "" -#: ../../content/applications/essentials/activities.rst:5 +#: ../../content/applications/essentials/activities.rst:7 msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." msgstr "" -#: ../../content/applications/essentials/activities.rst:9 -msgid "The icon used to display activities varies depending on the :ref:`activity type `:" -msgstr "" - #: ../../content/applications/essentials/activities.rst:11 -msgid ":guilabel:`🕘 (clock)`: the default icon, which appears if nothing is scheduled." -msgstr "" - -#: ../../content/applications/essentials/activities.rst:12 -msgid ":guilabel:`📞 (phone)`: this icon appears if a phone call is scheduled." -msgstr "" - -#: ../../content/applications/essentials/activities.rst:13 -msgid ":guilabel:`✉️ (envelope)`: this icon appears if an email is scheduled." +msgid "The icon used to display activities varies, depending on the :ref:`activity type `:" msgstr "" #: ../../content/applications/essentials/activities.rst:14 -msgid ":guilabel:`✔️ (checkmark)`: this icon appears if a to-do is scheduled." +msgid ":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." msgstr "" #: ../../content/applications/essentials/activities.rst:15 -msgid ":guilabel:`(group of people)`: this icon appears if a meeting is scheduled." +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." msgstr "" #: ../../content/applications/essentials/activities.rst:16 -msgid ":guilabel:`(arrow pointing up above a line)`: this icon appears if a document is scheduled to be uploaded." +msgid ":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." msgstr "" #: ../../content/applications/essentials/activities.rst:18 -msgid ":guilabel:`(pencil in a box)`: this icon appears if a signature request is scheduled." +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." msgstr "" -#: ../../content/applications/essentials/activities.rst:21 -msgid "Schedule activities" +#: ../../content/applications/essentials/activities.rst:19 +msgid ":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid ":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature request is scheduled." msgstr "" #: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 msgid "Activities can be scheduled on any page of the database that contains a :ref:`chatter ` thread, :ref:`Kanban view `, :ref:`list view `, or :ref:`activities view ` of an application." msgstr "" -#: ../../content/applications/essentials/activities.rst:30 +#: ../../content/applications/essentials/activities.rst:32 msgid "Chatter" msgstr "" -#: ../../content/applications/essentials/activities.rst:32 +#: ../../content/applications/essentials/activities.rst:34 msgid "Activities can be created from the chatter on any record." msgstr "" -#: ../../content/applications/essentials/activities.rst:34 +#: ../../content/applications/essentials/activities.rst:36 msgid "To schedule a new activity, click the :guilabel:`Activities` button, located at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up window that appears, :ref:`fill out the Schedule Activity form `." msgstr "" @@ -84,23 +84,19 @@ msgstr "" msgid "New activity type form." msgstr "" -#: ../../content/applications/essentials/activities.rst:45 +#: ../../content/applications/essentials/activities.rst:47 msgid "Kanban view" msgstr "" -#: ../../content/applications/essentials/activities.rst:47 -msgid "Another way that activities are created is from the Kanban view in an application." +#: ../../content/applications/essentials/activities.rst:49 +msgid "Activities can also be created from the :icon:`oi-view-kanban` :guilabel:`(Kanban)` view." msgstr "" -#: ../../content/applications/essentials/activities.rst:-1 -msgid "The Kanban icon in the top menu, highlighted." +#: ../../content/applications/essentials/activities.rst:51 +msgid "To do so, click on the |clock| located at the bottom of an individual record." msgstr "" #: ../../content/applications/essentials/activities.rst:53 -msgid "To do so, click on the :guilabel:`🕘 (clock)` icon located at the bottom of an individual record." -msgstr "" - -#: ../../content/applications/essentials/activities.rst:55 msgid "Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the Schedule Activity form `." msgstr "" @@ -108,145 +104,141 @@ msgstr "" msgid "Kanban view of the CRM pipeline and the option to schedule an activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:63 -#: ../../content/applications/essentials/activities.rst:82 -msgid "If a record already has a scheduled activity, the :guilabel:`🕘 (clock)` icon is replaced by the icon that represents the existing scheduled activity. Click on the activity type's icon to schedule another activity." +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "If a record already has a scheduled activity, the |clock| is replaced by the icon that represents the existing scheduled activity. Click on the activity type's icon to schedule another activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:70 +#: ../../content/applications/essentials/activities.rst:67 msgid "List view" msgstr "" -#: ../../content/applications/essentials/activities.rst:72 -msgid "Activities can also be created from a list view." +#: ../../content/applications/essentials/activities.rst:69 +msgid "Activities can also be created from a :icon:`oi-view-list` :guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "If the :guilabel:`Activities` column is hidden, reveal it using the :icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-right of the top row." msgstr "" #: ../../content/applications/essentials/activities.rst:74 -msgid "If the :guilabel:`Activities` column is hidden, reveal it using the :guilabel:`(additional options toggle)` icon in the far-right of the top row, represented by two horizontal lines with two dots." -msgstr "" - -#: ../../content/applications/essentials/activities.rst:77 -msgid "Then, click on the :guilabel:`🕘 (clock)` icon for the record the activity is being added to, then click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the Schedule Activity form ` that appears." +msgid "Then, click on the |clock| for the record the activity is being added to, and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the Schedule Activity form ` that appears." msgstr "" #: ../../content/applications/essentials/activities.rst:-1 msgid "List view of the CRM pipeline and the option to schedule an activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:93 +#: ../../content/applications/essentials/activities.rst:89 msgid "Activity view" msgstr "" -#: ../../content/applications/essentials/activities.rst:95 -msgid "Most applications in Odoo have an *Activity* view available. If available, a :guilabel:`🕘 (clock)` activity icon is visible in the top-right of the main menu bar." +#: ../../content/applications/essentials/activities.rst:91 +msgid "Most applications in Odoo have an *Activity* view available. If available, a |clock| is visible in the top-right corner of the main menu bar, amongst the other view option icons." msgstr "" -#: ../../content/applications/essentials/activities.rst:98 -msgid "To open the activity view, click the :guilabel:`🕘 (clock)` activity icon." +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." msgstr "" #: ../../content/applications/essentials/activities.rst:-1 msgid "Top-right menu with the Activities icon called out." msgstr "" -#: ../../content/applications/essentials/activities.rst:104 +#: ../../content/applications/essentials/activities.rst:100 msgid "In this view, all the available activities are listed in the columns, while the horizontal entries represent all the individual records." msgstr "" -#: ../../content/applications/essentials/activities.rst:107 +#: ../../content/applications/essentials/activities.rst:103 msgid "Activities that appear green have a due date in the future, activities that appear orange are due today, while activities appearing red are overdue." msgstr "" -#: ../../content/applications/essentials/activities.rst:110 +#: ../../content/applications/essentials/activities.rst:106 msgid "Color bars in each column represent records for specific activity types, and display a number indicating how many activities are scheduled for that type." msgstr "" -#: ../../content/applications/essentials/activities.rst:113 +#: ../../content/applications/essentials/activities.rst:109 msgid "If multiple activity types are scheduled for a record, a number appears in the box, indicating the total number of scheduled activities." msgstr "" -#: ../../content/applications/essentials/activities.rst:117 -msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view." +#: ../../content/applications/essentials/activities.rst:113 +msgid "Activity colors, and their relation to an activity's due date, are consistent throughout Odoo, regardless of the activity type, or the view." msgstr "" -#: ../../content/applications/essentials/activities.rst:120 -msgid "To schedule an activity for a record, hover over the corresponding field, and a :guilabel:`➕ (plus sign)` appears. Click the :guilabel:`➕ (plus sign)`, and then :ref:`fill out the Schedule Activity form `." +#: ../../content/applications/essentials/activities.rst:116 +msgid "To schedule an activity for a record, hover over the corresponding field. Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then :ref:`fill out the Schedule Activity form `." msgstr "" #: ../../content/applications/essentials/activities.rst:-1 msgid "Activity view of the CRM pipeline and the option to schedule an activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:131 +#: ../../content/applications/essentials/activities.rst:127 msgid "Schedule Activity form" msgstr "" -#: ../../content/applications/essentials/activities.rst:133 +#: ../../content/applications/essentials/activities.rst:129 msgid "Activities can be scheduled from many different places, such as from the :ref:`chatter ` of a record, or from one of multiple views in an application, when available: the :ref:`Kanban view `, :ref:`list view `, or :ref:`activity view `." msgstr "" -#: ../../content/applications/essentials/activities.rst:138 -#: ../../content/applications/essentials/activities.rst:220 +#: ../../content/applications/essentials/activities.rst:134 +#: ../../content/applications/essentials/activities.rst:210 msgid "Enter the following information on the form:" msgstr "" -#: ../../content/applications/essentials/activities.rst:140 +#: ../../content/applications/essentials/activities.rst:136 msgid ":guilabel:`Activity Type`: select the type of activity from the drop-down menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other applications are installed, additional options may be available." msgstr "" -#: ../../content/applications/essentials/activities.rst:145 -msgid "Individual applications have a list of dedicated :ref:`activity types `. For example, installing the *Sales* application makes :guilabel:`Order Upsell` available, while installing the *Sign* application makes :guilabel:`Request Signature` available." -msgstr "" - -#: ../../content/applications/essentials/activities.rst:149 +#: ../../content/applications/essentials/activities.rst:139 msgid ":guilabel:`Summary`: enter a short title for the activity, such as `Discuss Proposal`." msgstr "" -#: ../../content/applications/essentials/activities.rst:150 +#: ../../content/applications/essentials/activities.rst:140 msgid ":guilabel:`Due Date`: using the calendar popover, select the activity's deadline." msgstr "" -#: ../../content/applications/essentials/activities.rst:151 +#: ../../content/applications/essentials/activities.rst:141 msgid ":guilabel:`Assigned to`: by default, the current user populates this field. To assign a different user to the activity, select them from the drop-down menu." msgstr "" -#: ../../content/applications/essentials/activities.rst:153 +#: ../../content/applications/essentials/activities.rst:143 msgid ":guilabel:`Notes`: add any additional information for the activity in this field." msgstr "" -#: ../../content/applications/essentials/activities.rst:155 +#: ../../content/applications/essentials/activities.rst:145 msgid "When the :guilabel:`Schedule Activity` pop-up window is completed, click one of the following buttons:" msgstr "" -#: ../../content/applications/essentials/activities.rst:158 +#: ../../content/applications/essentials/activities.rst:148 msgid ":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:160 +#: ../../content/applications/essentials/activities.rst:150 msgid "Click on the desired date and time for the activity, and a :guilabel:`New Event` pop-up window appears. The summary from the *Schedule Activity* pop-up window populates the :guilabel:`Title` field." msgstr "" -#: ../../content/applications/essentials/activities.rst:164 +#: ../../content/applications/essentials/activities.rst:154 msgid "Enter the information in the :guilabel:`New Event` pop-up window, then click :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is added to the chatter under the :guilabel:`Planned Activities` section." msgstr "" -#: ../../content/applications/essentials/activities.rst:169 +#: ../../content/applications/essentials/activities.rst:159 msgid "The :guilabel:`Open Calendar` button **only** appears if the :guilabel:`Activity Type` is set to either :guilabel:`Call` or :guilabel:`Meeting`." msgstr "" -#: ../../content/applications/essentials/activities.rst:172 +#: ../../content/applications/essentials/activities.rst:162 msgid ":guilabel:`Schedule`: schedules the activity, and adds the activity to the chatter under :guilabel:`Planned Activities`." msgstr "" -#: ../../content/applications/essentials/activities.rst:174 +#: ../../content/applications/essentials/activities.rst:164 msgid ":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, and is automatically marked as done." msgstr "" -#: ../../content/applications/essentials/activities.rst:176 +#: ../../content/applications/essentials/activities.rst:166 msgid ":guilabel:`Done & Schedule Next`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, is automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up window appears." msgstr "" -#: ../../content/applications/essentials/activities.rst:179 +#: ../../content/applications/essentials/activities.rst:169 msgid ":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule Activity` pop-up window." msgstr "" @@ -254,27 +246,27 @@ msgstr "" msgid "View of CRM leads and the option to schedule an activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:188 +#: ../../content/applications/essentials/activities.rst:178 msgid "All scheduled activities" msgstr "" -#: ../../content/applications/essentials/activities.rst:190 -msgid "To view a consolidated list of activities, organized by application, click the :guilabel:`🕘 (clock)` icon in the header menu, located in the top-right." +#: ../../content/applications/essentials/activities.rst:180 +msgid "To view a consolidated list of activities, organized by application, click the |clock| in the header menu, located in the top-right corner." msgstr "" -#: ../../content/applications/essentials/activities.rst:193 -msgid "If any activities are scheduled, the number of activities appear in a red bubble on the :guilabel:`🕘 (clock)` icon." +#: ../../content/applications/essentials/activities.rst:183 +msgid "If any activities are scheduled, the number of activities appear in a red bubble on the |clock|." msgstr "" -#: ../../content/applications/essentials/activities.rst:196 +#: ../../content/applications/essentials/activities.rst:186 msgid "All activities for each application are further divided into subsections, indicating where in the application the activity is to be completed. Each sub-section lists the number of scheduled activities that are :guilabel:`Late`, due :guilabel:`Today`, and scheduled in the :guilabel:`Future`." msgstr "" -#: ../../content/applications/essentials/activities.rst:202 +#: ../../content/applications/essentials/activities.rst:192 msgid "In the *Time Off* application, one activity is scheduled to be done in the *All Time Off* requests dashboard, and six activities are scheduled to be done in the *Allocations* dashboard." msgstr "" -#: ../../content/applications/essentials/activities.rst:205 +#: ../../content/applications/essentials/activities.rst:195 msgid "These requests appear in two separate lists in the all activities drop-down menu: one labeled `Time Off` and one labeled `Time Off Allocation`." msgstr "" @@ -283,39 +275,39 @@ msgid "The list of activities that is accessed from the main menu bar. Two entri "Off application are highlighted." msgstr "" -#: ../../content/applications/essentials/activities.rst:214 +#: ../../content/applications/essentials/activities.rst:204 msgid "Request a document" msgstr "" -#: ../../content/applications/essentials/activities.rst:216 +#: ../../content/applications/essentials/activities.rst:206 msgid "The option to :guilabel:`Request a Document` is available at the bottom of the list of :ref:`all scheduled activities `, the option to :guilabel:`Request a Document` appears. Click :guilabel:`Request a Document`, and a :guilabel:`Request a file` pop-up window appears." msgstr "" -#: ../../content/applications/essentials/activities.rst:222 +#: ../../content/applications/essentials/activities.rst:212 msgid ":guilabel:`Document Name`: enter a name for the document being requested." msgstr "" -#: ../../content/applications/essentials/activities.rst:223 +#: ../../content/applications/essentials/activities.rst:213 msgid ":guilabel:`Request To`: select the user the document is being requested from using the drop-down menu." msgstr "" -#: ../../content/applications/essentials/activities.rst:225 +#: ../../content/applications/essentials/activities.rst:215 msgid ":guilabel:`Due Date In`: enter a numerical value indicating when the document is due. Next to this field, a :guilabel:`Days` field is visible. Click :guilabel:`Days`, the default option, to reveal a drop-down menu. Select the desired time-frame option from the list. The options are :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`." msgstr "" -#: ../../content/applications/essentials/activities.rst:229 +#: ../../content/applications/essentials/activities.rst:219 msgid ":guilabel:`Workspace`: using the drop-down menu, select the specific :ref:`Workspace ` the document is being uploaded to." msgstr "" -#: ../../content/applications/essentials/activities.rst:231 +#: ../../content/applications/essentials/activities.rst:221 msgid ":guilabel:`Tags`: select any desired tags from the drop-down menu. The available tags displayed are based on the tags configured for the selected :guilabel:`Workspace`." msgstr "" -#: ../../content/applications/essentials/activities.rst:233 +#: ../../content/applications/essentials/activities.rst:223 msgid ":guilabel:`Message`: enter a message to clarify the document request in this field." msgstr "" -#: ../../content/applications/essentials/activities.rst:235 +#: ../../content/applications/essentials/activities.rst:225 msgid "When all the fields are completed, click :guilabel:`Request` to send the document request." msgstr "" @@ -323,11 +315,11 @@ msgstr "" msgid "The Request a file form, with all fields filled out to request a contract." msgstr "" -#: ../../content/applications/essentials/activities.rst:244 +#: ../../content/applications/essentials/activities.rst:234 msgid "Activity types" msgstr "" -#: ../../content/applications/essentials/activities.rst:246 +#: ../../content/applications/essentials/activities.rst:236 msgid "To view the currently configured types of activities in the database, navigate to :menuselection:`Settings app --> Discuss section --> Activities setting --> Activity Types`." msgstr "" @@ -335,123 +327,127 @@ msgstr "" msgid "Activity Types button in the Settings application under the Discuss section." msgstr "" -#: ../../content/applications/essentials/activities.rst:253 +#: ../../content/applications/essentials/activities.rst:243 msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found." msgstr "" +#: ../../content/applications/essentials/activities.rst:246 +msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`." +msgstr "" + #: ../../content/applications/essentials/activities.rst:-1 msgid "The list of activity types already configured and available." msgstr "" -#: ../../content/applications/essentials/activities.rst:260 +#: ../../content/applications/essentials/activities.rst:255 msgid "Edit activity types" msgstr "" -#: ../../content/applications/essentials/activities.rst:262 +#: ../../content/applications/essentials/activities.rst:257 msgid "To edit an existing :ref:`activity type `, click on the activity type, and the activity type form loads." msgstr "" -#: ../../content/applications/essentials/activities.rst:265 -msgid "Make any desired changes to the activity type form. The form automatically saves, but it can be saved manually at any time by clicking the :guilabel:`Save Manually` option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +#: ../../content/applications/essentials/activities.rst:260 +msgid "Make any desired changes to the activity type form. The form automatically saves, but it can be saved manually at any time by clicking the :guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon, located in the top-left corner of the page." msgstr "" -#: ../../content/applications/essentials/activities.rst:270 +#: ../../content/applications/essentials/activities.rst:265 msgid "Create new activity types" msgstr "" -#: ../../content/applications/essentials/activities.rst:272 +#: ../../content/applications/essentials/activities.rst:267 msgid "To create a new :ref:`activity type `, click :guilabel:`New` from the :guilabel:`Activity Types` page, and a blank activity type form loads." msgstr "" -#: ../../content/applications/essentials/activities.rst:275 +#: ../../content/applications/essentials/activities.rst:270 msgid "Enter a :guilabel:`Name` for the activity type at the top of the form, then enter the following information on the form." msgstr "" -#: ../../content/applications/essentials/activities.rst:279 +#: ../../content/applications/essentials/activities.rst:274 msgid "Activity Settings section" msgstr "" -#: ../../content/applications/essentials/activities.rst:281 +#: ../../content/applications/essentials/activities.rst:276 msgid ":guilabel:`Action`: using the drop-down menu, select an action associated with this new activity type. Some actions trigger specific behaviors after an activity is scheduled, such as:" msgstr "" -#: ../../content/applications/essentials/activities.rst:284 +#: ../../content/applications/essentials/activities.rst:279 msgid ":guilabel:`Upload Document`: if selected, a link to upload a document is automatically added to the planned activity in the chatter." msgstr "" -#: ../../content/applications/essentials/activities.rst:286 +#: ../../content/applications/essentials/activities.rst:281 msgid ":guilabel:`Call` or :guilabel:`Meeting`: if selected, users have the option to open their calendar to select a date and time for the activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:288 +#: ../../content/applications/essentials/activities.rst:283 msgid ":guilabel:`Request Signature`: if selected, a link to open a signature request pop-up window is automatically added to the planned activity in the chatter. This requires the Odoo *Sign* application to be installed." msgstr "" -#: ../../content/applications/essentials/activities.rst:293 +#: ../../content/applications/essentials/activities.rst:288 msgid "Available activity types vary based on the installed applications in the database." msgstr "" -#: ../../content/applications/essentials/activities.rst:295 +#: ../../content/applications/essentials/activities.rst:290 msgid ":guilabel:`Folder`: select a specific :ref:`workspace ` folder to save a document to. This field **only** appears if :guilabel:`Upload Document` is selected for the :guilabel:`Action`." msgstr "" -#: ../../content/applications/essentials/activities.rst:299 +#: ../../content/applications/essentials/activities.rst:294 msgid "Using the drop-down menu, select the :guilabel:`Folder` the document is saved to." msgstr "" -#: ../../content/applications/essentials/activities.rst:301 +#: ../../content/applications/essentials/activities.rst:296 msgid ":guilabel:`Default User`: select a user from the drop-down menu to automatically assign this activity to the selected user when this activity type is scheduled. If this field is left blank, the activity is assigned to the user who creates the activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:304 +#: ../../content/applications/essentials/activities.rst:299 msgid ":guilabel:`Default Summary`: enter a note to include whenever this activity type is created." msgstr "" -#: ../../content/applications/essentials/activities.rst:307 +#: ../../content/applications/essentials/activities.rst:302 msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved." msgstr "" -#: ../../content/applications/essentials/activities.rst:311 +#: ../../content/applications/essentials/activities.rst:306 msgid ":guilabel:`Keep Done`: tick this checkbox to keep activities that have been marked as `Done` visible in the :ref:`activity view `." msgstr "" -#: ../../content/applications/essentials/activities.rst:313 +#: ../../content/applications/essentials/activities.rst:308 msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." msgstr "" -#: ../../content/applications/essentials/activities.rst:316 +#: ../../content/applications/essentials/activities.rst:311 msgid "Next Activity section" msgstr "" -#: ../../content/applications/essentials/activities.rst:318 +#: ../../content/applications/essentials/activities.rst:313 msgid "It is possible to have another activity either suggested or triggered. To do so, configure the :guilabel:`Next Activity` section." msgstr "" -#: ../../content/applications/essentials/activities.rst:321 +#: ../../content/applications/essentials/activities.rst:316 msgid ":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` field is displayed." msgstr "" -#: ../../content/applications/essentials/activities.rst:326 +#: ../../content/applications/essentials/activities.rst:321 msgid "The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload Document` is selected for the :guilabel:`Action`." msgstr "" -#: ../../content/applications/essentials/activities.rst:329 +#: ../../content/applications/essentials/activities.rst:324 msgid ":guilabel:`Suggest/Trigger`: depending on what is selected for the :guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or :guilabel:`Trigger`. Using the drop-down menu, select the activity to recommend or schedule as a follow-up task to the activity type." msgstr "" -#: ../../content/applications/essentials/activities.rst:332 +#: ../../content/applications/essentials/activities.rst:327 msgid ":guilabel:`Schedule`: configure when the next activity is suggested or triggered." msgstr "" -#: ../../content/applications/essentials/activities.rst:334 +#: ../../content/applications/essentials/activities.rst:329 msgid "First, enter a numerical value indicating when the activity is suggested or triggered." msgstr "" -#: ../../content/applications/essentials/activities.rst:336 +#: ../../content/applications/essentials/activities.rst:331 msgid "Next to this field, a :guilabel:`Days` field is visible. Click :guilabel:`Days`, the default option, to reveal a drop-down menu. Select the desired time-frame option from the list. The options are :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`." msgstr "" -#: ../../content/applications/essentials/activities.rst:340 +#: ../../content/applications/essentials/activities.rst:335 msgid "Lastly, using the drop-down menu, select whether the activity is scheduled or triggered either :guilabel:`after previous activity deadline` or :guilabel:`after completion date`." msgstr "" @@ -459,14 +455,366 @@ msgstr "" msgid "A new Activity form with all the fields filled out." msgstr "" -#: ../../content/applications/essentials/activities.rst:348 +#: ../../content/applications/essentials/activities.rst:343 msgid ":doc:`../productivity/discuss`" msgstr "" -#: ../../content/applications/essentials/activities.rst:349 +#: ../../content/applications/essentials/activities.rst:344 msgid ":doc:`../productivity/discuss/team_communication`" msgstr "" +#: ../../content/applications/essentials/activities.rst:345 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:3 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "The *Contacts* application comes installed on all Odoo databases. Contacts are created for customers the company does business with through Odoo. A contact is a repository of vital business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:10 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "To create a new contact, navigate to the :menuselection:`Contacts app`, and click :guilabel:`Create`. A new form appears where various contact information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:16 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:22 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "First, fill in the name of the :guilabel:`Individual` or :guilabel:`Company`. This is how the name appears throughout the database. This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:28 +msgid ":guilabel:`Individual` contacts can have a :guilabel:`Company` contact linked to it. After selecting :guilabel:`Individual`, a new :guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:33 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Next, enter the :guilabel:`Address` of the :guilabel:`Company` or :guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:38 +msgid "If the :guilabel:`Individual` option is chosen, then the *type of address* can be chosen from a drop-down menu. Options for this drop-down menu include: :guilabel:`Contact`, :guilabel:`Invoice Address`, :guilabel:`Delivery Address`, :guilabel:`Other Address`, and :guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:44 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional details are included on the initial form. The following fields are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:49 +msgid ":guilabel:`Citizen Identification`: citizen or government identification number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid ":guilabel:`Job Position`: list the job position of the :guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid ":guilabel:`Phone`: list phone number (with country code). Make a call, send an SMS, or WhatsApp message by hovering over the field on the saved form, and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid ":guilabel:`Mobile`: list mobile phone number (with country code). Make a call, send an SMS, or WhatsApp message by hovering over the field on the saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:58 +msgid ":guilabel:`Website`: enter the full website address, starting with `http` or `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, :guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid ":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or clicking the drop-down menu, and selecting one. To create a new one, type the new tag in the field, and click :guilabel:`Create` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:66 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "At the bottom of the contact form are several tabs. On the :guilabel:`Contacts & Addresses` tab, contacts can be added that are associated with a :guilabel:`Company` and related addresses. For example, a specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:72 +msgid "Multiple addresses can be added on both :guilabel:`Individual` and :guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the :guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:80 +msgid "On the :guilabel:`Create Contact` pop-up form, start by clicking the default :guilabel:`Other Address` field at the top to reveal a drop-down menu of address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:83 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid ":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:86 +msgid ":guilabel:`Invoice Address`: adds a specific invoice address to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid ":guilabel:`Delivery Address`: adds a specific delivery address to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid ":guilabel:`Other Address`: adds an alternate address to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid ":guilabel:`Private Address`: adds a private address to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:95 +msgid "Once an option is selected, enter the corresponding contact information that should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:98 +msgid "Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:101 +msgid "Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` address type has been selected. This is similar to the :guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:104 +msgid "To add a note, click on the text field next to :guilabel:`Notes`, and write anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:107 +msgid "Then, click :guilabel:`Save & Close` to save the address, and close the :guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:111 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the *Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:116 +msgid "The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:120 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can be assigned to a contact. To do that, click the :guilabel:`Salesperson` drop-down field, and select one. Create a new :guilabel:`Salesperson` by typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:126 +msgid "Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can also be set, if needed. Click the drop-down menu next to :guilabel:`Payment Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:131 +msgid "Click into the :guilabel:`Delivery Method` field to select an option from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:134 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` that can be used to identify the contact. Use the :guilabel:`Loyalty Points` field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:141 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:147 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add any additional information for this contact. If this contact should only be accessible for one company in a multi-company database, select it from the :guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-down menu to restrict the publishing of this contact to one website (if working on a database with multiple websites). Select one or more :guilabel:`Website Tags` to assist in filtering published customers on the `/customers` website page. Select an :guilabel:`Industry` for this contact from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a *Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:159 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "The :guilabel:`Accounting` tab appears when the *Accounting* application is installed. Here, a user can add any related :guilabel:`Bank Accounts`, or set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:164 +msgid "Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:168 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` tab, where notes can be left on this contact form, just like on the contact form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:174 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Next is the :guilabel:`Partner Assignment` tab, which by default, includes a :guilabel:`Geolocation` section, and other partner options, including :guilabel:`Partner Activation` and :guilabel:`Partner Review` configurations. These are **only** present when the *Resellers* module is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:181 +msgid "Follow the :doc:`Resellers documentation <../sales/crm/track_leads/resellers>` for more information on publishing partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:185 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Finally, there is the :guilabel:`Membership` tab on contact forms, which can help users manage any memberships that are being offered to this specific contact. It should be noted that this tab **only** appears when the *Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:192 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "To activate a contact's membership, click :guilabel:`Buy Membership` in the :guilabel:`Membership` tab of a contact form. On the pop-up window that appears, select a :guilabel:`Membership` from the drop-down menu. Then, configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:199 +msgid "Alternatively, to offer a free membership, tick the :guilabel:`Free Member` checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:203 +msgid "Publish members directory" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "To publish a list of active members on the website, the *Online Members Directory* application must first be :ref:`installed `. After installing the module, add the `/members` page to the website's menu by :doc:`editing the website menu <../websites/website/pages/menus>`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:210 +msgid "Publish individual members" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:212 +msgid "Return to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a member. Click the :guilabel:`Go to Website` smart button at the top of the page to open the member's webpage." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:216 +msgid "After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:219 +msgid "Repeat these steps for all members." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:224 +msgid "At the top of the contact form, there are some additional options available, known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:227 +msgid "Here, Odoo displays a variety of records, related to this contact, that were created on other apps. Odoo integrates information from every single app, so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "For example, there is an :guilabel:`Opportunities` smart button, where all the opportunities related to this customer from the *CRM* app are accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:235 +msgid "If the corresponding applications are installed, their related smart buttons appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the :guilabel:`More` smart button reveals additional options, via a drop-down menu. A user can even quickly access :guilabel:`Purchases`, :guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, :guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the :guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "Deliveries, documents, loyalty cards, and direct debits are *also* linked to smart buttons, like this, should there be any outstanding/on-file for this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:247 +msgid "If the contact is a partner, the user can visit their partner page on the Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:251 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:253 +msgid "If a user decides they no longer want to have this contact active, the record can be archived. To do that, go to the :icon:`fa-cog` :guilabel:`Action` menu at the top of the contact form, and click :guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:259 +msgid "With this contact successfully archived, as indicated by a banner at the top, they do not show up in the main contacts page, but they can still be searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:263 +msgid "A contact can be *unarchived*, if the user decides to work with them again. To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at the top of the archived contact form, and click :guilabel:`Unarchive`. Upon doing so, the :guilabel:`Archived` banner is removed, and the contact is restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:269 +msgid ":doc:`Add different addresses in CRM <../sales/sales/send_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:270 +msgid "`Odoo's eLearning Contacts tutorial `_" +msgstr "" + #: ../../content/applications/essentials/export_import_data.rst:3 msgid "Export and import data" msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 8754fa2d4..898c02550 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,7 +49,7 @@ msgid "Odoo uses the double-entry bookkeeping system, whereby every entry needs msgstr "" #: ../../content/applications/finance/accounting.rst:67 -#: ../../content/applications/finance/accounting.rst:222 +#: ../../content/applications/finance/accounting.rst:224 msgid ":doc:`Accounting Cheat Sheet `" msgstr "" @@ -65,252 +65,255 @@ msgstr "" msgid ":doc:`Cash basis `" msgstr "" -#: ../../content/applications/finance/accounting.rst:80 +#: ../../content/applications/finance/accounting.rst:82 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:107 msgid "Multi-company" msgstr "" -#: ../../content/applications/finance/accounting.rst:82 +#: ../../content/applications/finance/accounting.rst:84 msgid "Several companies can be managed within the same database. Each company has its :doc:`chart of accounts `, which is also useful to generate consolidation reports. Users can access several companies but can only work on a single company's accounting at a time." msgstr "" -#: ../../content/applications/finance/accounting.rst:88 +#: ../../content/applications/finance/accounting.rst:90 msgid "Multi-currency environment" msgstr "" -#: ../../content/applications/finance/accounting.rst:90 +#: ../../content/applications/finance/accounting.rst:92 msgid "A :doc:`multi-currency ` environment with an automated exchange rate to ease international transactions is available in Odoo. Every transaction is recorded in the company's default currency; for transactions occurring in another currency, Odoo stores both the value in the company's currency and the transactions' currency value. Odoo generates currency gains and losses after reconciling the journal items." msgstr "" -#: ../../content/applications/finance/accounting.rst:97 +#: ../../content/applications/finance/accounting.rst:99 msgid ":doc:`Manage a bank in a foreign currency `" msgstr "" -#: ../../content/applications/finance/accounting.rst:100 +#: ../../content/applications/finance/accounting.rst:102 msgid "Branch management" msgstr "" -#: ../../content/applications/finance/accounting.rst:102 +#: ../../content/applications/finance/accounting.rst:104 msgid "Multiple branches can be managed thanks to multi-company hierarchies. This allows to post journal entries on each branch as well as setting up a common lock date managed by the main company." msgstr "" -#: ../../content/applications/finance/accounting.rst:106 +#: ../../content/applications/finance/accounting.rst:108 msgid "International standards" msgstr "" -#: ../../content/applications/finance/accounting.rst:108 +#: ../../content/applications/finance/accounting.rst:110 msgid "Odoo Accounting supports more than 70 countries. It provides the central standards and mechanisms common to all nations, and thanks to country-specific modules, local requirements are fulfilled. Fiscal positions exist to address regional specificities like the chart of accounts, taxes, or any other requirements." msgstr "" -#: ../../content/applications/finance/accounting.rst:114 +#: ../../content/applications/finance/accounting.rst:116 msgid ":doc:`Fiscal localization packages `" msgstr "" -#: ../../content/applications/finance/accounting.rst:117 +#: ../../content/applications/finance/accounting.rst:119 msgid "Accounts receivable and payable" msgstr "" -#: ../../content/applications/finance/accounting.rst:119 +#: ../../content/applications/finance/accounting.rst:121 msgid "By default, there is a single account for the account receivable entries and one for the account payable entries. As transactions are linked to your **contacts**, you can run a report per customer, vendor, or supplier." msgstr "" -#: ../../content/applications/finance/accounting.rst:123 +#: ../../content/applications/finance/accounting.rst:125 msgid "The **Partner Ledger** report displays the balance of your customers and suppliers. It is available by going to :menuselection:`Accounting --> Reporting --> Partner Ledger`." msgstr "" -#: ../../content/applications/finance/accounting.rst:127 +#: ../../content/applications/finance/accounting.rst:129 #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:79 #: ../../content/applications/finance/accounting/reporting.rst:5 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:79 msgid "Reporting" msgstr "" -#: ../../content/applications/finance/accounting.rst:129 +#: ../../content/applications/finance/accounting.rst:131 msgid "The following financial :doc:`reports ` are available and updated in real-time:" msgstr "" -#: ../../content/applications/finance/accounting.rst:133 +#: ../../content/applications/finance/accounting.rst:135 #: ../../content/applications/finance/fiscal_localizations/austria.rst:28 #: ../../content/applications/finance/fiscal_localizations/chile.rst:1206 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 msgid "Financial reports" msgstr "" -#: ../../content/applications/finance/accounting.rst:135 +#: ../../content/applications/finance/accounting.rst:137 msgid "Statement" msgstr "" -#: ../../content/applications/finance/accounting.rst:135 +#: ../../content/applications/finance/accounting.rst:137 #: ../../content/applications/finance/accounting/customer_invoices.rst:214 msgid "Balance sheet" msgstr "" -#: ../../content/applications/finance/accounting.rst:137 +#: ../../content/applications/finance/accounting.rst:139 #: ../../content/applications/finance/accounting/customer_invoices.rst:204 msgid "Profit and loss" msgstr "" -#: ../../content/applications/finance/accounting.rst:139 +#: ../../content/applications/finance/accounting.rst:141 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:363 msgid "Cash flow statement" msgstr "" -#: ../../content/applications/finance/accounting.rst:141 -#: ../../content/applications/finance/accounting.rst:180 +#: ../../content/applications/finance/accounting.rst:143 +#: ../../content/applications/finance/accounting.rst:182 #: ../../content/applications/finance/accounting/get_started/vat_units.rst:77 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:38 msgid "Tax report" msgstr "" -#: ../../content/applications/finance/accounting.rst:143 +#: ../../content/applications/finance/accounting.rst:145 msgid "ES sales list" msgstr "" -#: ../../content/applications/finance/accounting.rst:145 +#: ../../content/applications/finance/accounting.rst:147 msgid "Audit" msgstr "" -#: ../../content/applications/finance/accounting.rst:145 +#: ../../content/applications/finance/accounting.rst:147 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1076 msgid "General ledger" msgstr "" -#: ../../content/applications/finance/accounting.rst:147 +#: ../../content/applications/finance/accounting.rst:149 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1038 msgid "Trial balance" msgstr "" -#: ../../content/applications/finance/accounting.rst:149 +#: ../../content/applications/finance/accounting.rst:151 msgid "Journal report" msgstr "" -#: ../../content/applications/finance/accounting.rst:151 +#: ../../content/applications/finance/accounting.rst:153 msgid "Intrastat report" msgstr "" -#: ../../content/applications/finance/accounting.rst:153 +#: ../../content/applications/finance/accounting.rst:155 msgid "Check register" msgstr "" -#: ../../content/applications/finance/accounting.rst:155 +#: ../../content/applications/finance/accounting.rst:157 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:140 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:138 #: ../../content/applications/finance/fiscal_localizations/peru.rst:334 msgid "Partner" msgstr "" -#: ../../content/applications/finance/accounting.rst:155 +#: ../../content/applications/finance/accounting.rst:157 msgid "Partner ledger" msgstr "" -#: ../../content/applications/finance/accounting.rst:157 +#: ../../content/applications/finance/accounting.rst:159 msgid "Aged receivable" msgstr "" -#: ../../content/applications/finance/accounting.rst:159 +#: ../../content/applications/finance/accounting.rst:161 msgid "Aged payable" msgstr "" -#: ../../content/applications/finance/accounting.rst:161 +#: ../../content/applications/finance/accounting.rst:163 msgid "Management" msgstr "" -#: ../../content/applications/finance/accounting.rst:161 +#: ../../content/applications/finance/accounting.rst:163 msgid "Invoice analysis" msgstr "" -#: ../../content/applications/finance/accounting.rst:163 +#: ../../content/applications/finance/accounting.rst:165 msgid "Unrealized currency gains/losses" msgstr "" -#: ../../content/applications/finance/accounting.rst:165 +#: ../../content/applications/finance/accounting.rst:167 msgid "Depreciation schedule" msgstr "" -#: ../../content/applications/finance/accounting.rst:167 +#: ../../content/applications/finance/accounting.rst:169 msgid "Disallowed expenses" msgstr "" -#: ../../content/applications/finance/accounting.rst:169 +#: ../../content/applications/finance/accounting.rst:171 msgid "Budget analysis" msgstr "" -#: ../../content/applications/finance/accounting.rst:171 +#: ../../content/applications/finance/accounting.rst:173 msgid "Product margins" msgstr "" -#: ../../content/applications/finance/accounting.rst:173 +#: ../../content/applications/finance/accounting.rst:175 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:339 msgid "1099 report" msgstr "" -#: ../../content/applications/finance/accounting.rst:177 +#: ../../content/applications/finance/accounting.rst:179 msgid ":doc:`Create and customize reports ` with Odoo's report engine." msgstr "" -#: ../../content/applications/finance/accounting.rst:182 +#: ../../content/applications/finance/accounting.rst:184 msgid "Odoo computes all accounting transactions for the specific tax period and uses these totals to calculate the tax obligation." msgstr "" -#: ../../content/applications/finance/accounting.rst:186 +#: ../../content/applications/finance/accounting.rst:188 msgid "Once the tax report has been generated for a period, Odoo locks it and prevents the creation of new journal entries involving VAT. Any correction to customer invoices or vendor bills has to be recorded in the next period." msgstr "" -#: ../../content/applications/finance/accounting.rst:191 +#: ../../content/applications/finance/accounting.rst:193 msgid "Depending on the country's localization, an XML version of the tax report can be generated to be uploaded to the VAT platform of the relevant taxation authority." msgstr "" -#: ../../content/applications/finance/accounting.rst:195 +#: ../../content/applications/finance/accounting.rst:197 #: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:5 msgid "Bank synchronization" msgstr "" -#: ../../content/applications/finance/accounting.rst:197 +#: ../../content/applications/finance/accounting.rst:199 msgid "The bank synchronization system directly connects with your bank institution to automatically import all transactions into your database. It gives an overview of your cash flow without logging into an online banking system or waiting for paper bank statements." msgstr "" -#: ../../content/applications/finance/accounting.rst:202 +#: ../../content/applications/finance/accounting.rst:204 msgid ":doc:`Bank synchronization `" msgstr "" -#: ../../content/applications/finance/accounting.rst:205 +#: ../../content/applications/finance/accounting.rst:207 msgid "Inventory valuation" msgstr "" -#: ../../content/applications/finance/accounting.rst:207 +#: ../../content/applications/finance/accounting.rst:209 msgid "Both periodic (manual) and perpetual (automated) inventory valuations are supported in Odoo. The available methods are standard price, average price, :abbr:`LIFO (Last-In, First-Out)` and :abbr:`FIFO (First-In, First-Out).`" msgstr "" -#: ../../content/applications/finance/accounting.rst:212 +#: ../../content/applications/finance/accounting.rst:214 msgid ":doc:`../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config`" msgstr "" -#: ../../content/applications/finance/accounting.rst:215 +#: ../../content/applications/finance/accounting.rst:217 msgid "Retained earnings" msgstr "" -#: ../../content/applications/finance/accounting.rst:217 +#: ../../content/applications/finance/accounting.rst:219 msgid "Retained earnings are the portion of income retained by a business. Odoo calculates current year earnings in real-time, so no year-end journal or rollover is required. The profit and loss balance is automatically reported on the balance sheet report." msgstr "" -#: ../../content/applications/finance/accounting.rst:227 +#: ../../content/applications/finance/accounting.rst:229 msgid "Fiduciaries" msgstr "" -#: ../../content/applications/finance/accounting.rst:229 +#: ../../content/applications/finance/accounting.rst:231 msgid "The :guilabel:`Accounting Firms` mode can be activated by going to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Firms mode`. When enabled:" msgstr "" -#: ../../content/applications/finance/accounting.rst:232 +#: ../../content/applications/finance/accounting.rst:234 msgid "The document's sequence becomes editable on all documents;" msgstr "" -#: ../../content/applications/finance/accounting.rst:233 +#: ../../content/applications/finance/accounting.rst:235 msgid "The :guilabel:`Total (tax incl.)` field appears to speed up and control the encoding by automating line creation with the right account and tax;" msgstr "" -#: ../../content/applications/finance/accounting.rst:235 +#: ../../content/applications/finance/accounting.rst:237 msgid ":guilabel:`Invoice Date` and :guilabel:`Bill Date` are pre-filled when encoding a transaction." msgstr "" -#: ../../content/applications/finance/accounting.rst:236 +#: ../../content/applications/finance/accounting.rst:238 msgid "A :guilabel:`Quick encoding` option is available for customer invoices and vendor bills." msgstr "" @@ -474,10 +477,12 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:6 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:6 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:34 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:647 #: ../../content/applications/finance/payment_providers/adyen.rst:17 #: ../../content/applications/finance/payment_providers/alipay.rst:12 #: ../../content/applications/finance/payment_providers/authorize.rst:9 -#: ../../content/applications/finance/payment_providers/authorize.rst:60 +#: ../../content/applications/finance/payment_providers/authorize.rst:62 #: ../../content/applications/finance/payment_providers/demo.rst:9 #: ../../content/applications/finance/payment_providers/mollie.rst:8 #: ../../content/applications/finance/payment_providers/paypal.rst:101 @@ -1958,6 +1963,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:33 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:116 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:51 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:234 msgid "Taxes" msgstr "" @@ -2996,7 +3002,7 @@ msgid "Every PDF generated by Odoo includes an integrated **Factur-X** XML file. msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:58 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:184 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 #: ../../content/applications/finance/accounting/taxes/avatax.rst:125 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 @@ -4314,7 +4320,7 @@ msgid ":doc:`Using inventory valuation <../../../inventory_and_mrp/inventory/war msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:35 -msgid ":ref:`Other inventory valuation methods `" +msgid ":ref:`Other inventory valuation methods `" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:40 @@ -4750,7 +4756,7 @@ msgid "In addition to using |AVCO|, companies that use **Anglo-Saxon accounting* msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:266 -msgid ":ref:`Anglo-Saxon vs. Continental `" +msgid ":ref:`Anglo-Saxon vs. Continental `" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:268 @@ -5007,6 +5013,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:24 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:115 msgid "Chart of accounts" msgstr "" @@ -5026,95 +5033,95 @@ msgstr "" msgid "Group the accounts by type in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:21 msgid "Configuration of an account" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:21 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:23 msgid "The country you select during the creation of your database (or additional company in your database) determines which :doc:`fiscal localization package <../../fiscal_localizations>` is installed by default. This package includes a standard chart of accounts already configured according to the country's regulations. You can use it directly or set it according to your company's needs." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:26 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:28 msgid "To create a new account, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click :guilabel:`Create`, and fill in (at the minimum) the required fields (:guilabel:`Code, Account Name, Type`)." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:31 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:33 msgid "It is not possible to modify the **fiscal localization** of a company once a journal entry has been posted." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:35 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:37 msgid "Code and name" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:37 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:39 msgid "Each account is identified by its :guilabel:`Code` and :guilabel:`Name`, which also indicate the account's purpose." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:43 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:56 msgid "Type" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 msgid "Correctly configuring the **account type** is critical as it serves multiple purposes:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:49 msgid "Information on the account's purpose and behavior" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:48 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:50 msgid "Generate country-specific legal and financial reports" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:49 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:51 msgid "Set the rules to close a fiscal year" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:50 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:52 msgid "Generate opening entries" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:52 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "To configure an account type, open the :guilabel:`Type` field's drop-down selector and select the corresponding type from the following list:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 msgid "Report" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 msgid "Category" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 msgid "Account Types" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 #: ../../content/applications/finance/accounting/reporting.rst:36 #: ../../content/applications/finance/fiscal_localizations/germany.rst:23 msgid "Balance Sheet" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:98 msgid "Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:59 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:62 msgid "Receivable" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:62 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:68 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:71 msgid "Bank and Cash" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:62 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:64 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:74 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:77 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:80 @@ -5122,145 +5129,145 @@ msgstr "" msgid "Current Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:64 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:66 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:86 msgid "Non-current Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:66 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 msgid "Prepayments" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 msgid "Fixed Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:72 msgid "Liabilities" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:72 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:65 msgid "Payable" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:72 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:74 msgid "Credit Card" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:74 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:76 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:89 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:92 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:95 msgid "Current Liabilities" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:76 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:98 msgid "Non-current Liabilities" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 msgid "Equity" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:101 msgid "Current Year Earnings" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 #: ../../content/applications/finance/fiscal_localizations/germany.rst:24 #: ../../content/applications/finance/fiscal_localizations/netherlands.rst:20 msgid "Profit & Loss" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 msgid "Income" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 msgid "Other Income" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:88 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:88 msgid "Expense" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:88 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 msgid "Depreciation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 msgid "Cost of Revenue" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:94 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:94 msgid "Other" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:94 msgid "Off-Balance Sheet" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:98 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:100 msgid "Some **account types** can **automate** the creation of :ref:`asset ` entries. To **automate** entries, click :guilabel:`View` on an account line and go to the :guilabel:`Automation` tab." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:102 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:104 msgid "You have three choices for the :guilabel:`Automation` tab:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:104 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:106 msgid ":guilabel:`No`: this is the default value. Nothing happens." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 msgid ":guilabel:`Create in draft`: whenever a transaction is posted on the account, a draft entry is created but not validated. You must first fill out the corresponding form." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:109 msgid ":guilabel:`Create and validate`: you must also select a :guilabel:`Deferred Expense Model`. Whenever a transaction is posted on the account, an entry is created and immediately validated." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:111 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 #: ../../content/applications/finance/accounting/taxes.rst:14 msgid "Default taxes" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:115 msgid "In the :guilabel:`View` menu of an account, select a **default tax** to be applied when this account is chosen for a product sale or purchase." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:117 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:119 msgid "Tags" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:119 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:121 msgid "Some accounting reports require **tags** to be set on the relevant accounts. To add a tag, under :guilabel:`View`, click the :guilabel:`Tags` field and select an existing tag or :guilabel:`Create` a new one." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:124 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 msgid "Account groups" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:128 msgid "**Account groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and thus consolidate reports such as the **Trial Balance**. By default, groups are handled automatically based on the code of the group. For example, a new account `131200` is going to be part of the group `131000`. You can attribute a specific group to an account in the :guilabel:`Group` field under :guilabel:`View`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:133 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:135 msgid "Create account groups manually" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:136 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:138 msgid "Regular users should not need to create account groups manually. The following section is only intended for rare and advanced use cases." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:139 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:141 msgid "To create a new account group, activate :ref:`developer mode ` and head to :menuselection:`Accounting --> Configuration --> Account Groups`. Here, create a new group and enter the :guilabel:`name, code prefix, and company` to which that group account should be available. Note that you must enter the same code prefix in both :guilabel:`From` and :guilabel:`to` fields." msgstr "" @@ -5268,7 +5275,7 @@ msgstr "" msgid "Account groups creation." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:147 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:149 msgid "To display your **Trial Balance** report with your account groups, go to :menuselection:`Accounting --> Reporting --> Trial Balance`, then open the :guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." msgstr "" @@ -5276,19 +5283,19 @@ msgstr "" msgid "Account Groups in the Trial Balance in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:155 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:157 msgid "Allow reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:157 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:159 msgid "Some accounts, such as accounts made to record the transactions of a payment method, can be used for the reconciliation of journal entries." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:160 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:162 msgid "For example, an invoice paid with a credit card can be marked as :guilabel:`paid` if reconciled with its payment. Therefore, the account used to record credit card payments needs to be configured as **allowing reconciliation**." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:164 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:166 msgid "To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and :guilabel:`Save`; or enable the button from the chart of accounts view." msgstr "" @@ -5296,35 +5303,35 @@ msgstr "" msgid "Allow reconciliation for accounts in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:171 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:173 msgid "Deprecated" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:173 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:175 msgid "It is not possible to delete an account once a transaction has been recorded on it. You can make them unusable by using the **Deprecated** feature: check the :guilabel:`Deprecated` box in the account's settings, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:178 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 msgid ":doc:`cheat_sheet`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 msgid ":doc:`../vendor_bills/assets`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 msgid ":doc:`../vendor_bills/deferred_expenses`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 msgid ":doc:`../customer_invoices/deferred_revenues`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:185 msgid "`Odoo Tutorials: Chart of accounts `_" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:184 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:186 msgid "`Odoo Tutorials: Update your chart of accounts `_" msgstr "" @@ -5551,7 +5558,7 @@ msgid "Total to pay" msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:190 -#: ../../content/applications/finance/accounting/reporting.rst:149 +#: ../../content/applications/finance/accounting/reporting.rst:155 msgid "Bank Reconciliation" msgstr "" @@ -5886,15 +5893,15 @@ msgstr "" msgid "`Odoo Tutorials: Bank Configuration `_" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:24 +#: ../../content/applications/finance/accounting/payments.rst:26 msgid "Registering payment from an invoice or bill" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:26 +#: ../../content/applications/finance/accounting/payments.rst:28 msgid "When clicking :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new journal entry and changes the amount due according to the payment amount. The counterpart is reflected in an :ref:`outstanding ` **receipts** or **payments** account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the outstanding account is reconciled with a bank statement line, the invoice or vendor bill changes to the :guilabel:`Paid` status." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:33 +#: ../../content/applications/finance/accounting/payments.rst:35 msgid "The information icon near the payment line displays more information about the payment. You can access additional information, such as the related journal, by clicking :guilabel:`View`." msgstr "" @@ -5902,39 +5909,39 @@ msgstr "" msgid "See detailed information of a payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:40 +#: ../../content/applications/finance/accounting/payments.rst:42 msgid "The customer invoice or vendor bill must be in the :guilabel:`Posted` status to register the payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:42 +#: ../../content/applications/finance/accounting/payments.rst:44 msgid "If you unreconcile a payment, it still appears in your books but is no longer linked to the invoice." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:44 +#: ../../content/applications/finance/accounting/payments.rst:46 msgid "If you (un)reconcile a payment in a different currency, a journal entry is automatically created to post the currency exchange gains/losses (reversal) amount." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:46 +#: ../../content/applications/finance/accounting/payments.rst:48 msgid "If you (un)reconcile a payment and an invoice having cash basis taxes, a journal entry is automatically created to post the cash basis tax (reversal) amount." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:50 +#: ../../content/applications/finance/accounting/payments.rst:52 msgid "If your main bank account is set as an :ref:`outstanding account `, and the payment is registered in Odoo (not through a related bank statement), invoices and bills are directly registered as :guilabel:`Paid`." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:55 +#: ../../content/applications/finance/accounting/payments.rst:57 msgid "Registering payments not tied to an invoice or bill" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:57 +#: ../../content/applications/finance/accounting/payments.rst:59 msgid "When a new payment is registered via :menuselection:`Customers / Vendors --> Payments` menu, it is not directly linked to an invoice or bill. Instead, the account receivable or the account payable is matched with the **outstanding account** until it is manually matched with its related invoice or bill." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:63 +#: ../../content/applications/finance/accounting/payments.rst:65 msgid "Matching invoices and bills with payments" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:65 +#: ../../content/applications/finance/accounting/payments.rst:67 msgid "A blue banner appears when you validate a new invoice/bill and an **outstanding payment** exists for this specific customer or vendor. It can easily be matched from the invoice or bill by clicking :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." msgstr "" @@ -5942,31 +5949,31 @@ msgstr "" msgid "Shows the ADD option to reconcile an invoice or a bill with a payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:72 +#: ../../content/applications/finance/accounting/payments.rst:74 msgid "The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its corresponding bank statement." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:78 +#: ../../content/applications/finance/accounting/payments.rst:80 msgid "Batch payment" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:80 +#: ../../content/applications/finance/accounting/payments.rst:82 msgid "Batch payments allow you to group different payments to ease :doc:`reconciliation `. They are also useful when you deposit :doc:`checks ` to the bank or for :doc:`SEPA payments `. To do so, go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view of payments, you can select and group several payments in a batch by clicking :menuselection:`Action --> Create Batch Payment`." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:88 +#: ../../content/applications/finance/accounting/payments.rst:90 msgid ":doc:`payments/batch`" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:89 +#: ../../content/applications/finance/accounting/payments.rst:91 msgid ":doc:`payments/batch_sdd`" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:94 +#: ../../content/applications/finance/accounting/payments.rst:96 msgid "Payments matching" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:96 +#: ../../content/applications/finance/accounting/payments.rst:98 msgid "The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and allows you to process them individually, matching all payments and invoices in one place. You can reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`, click the drop-down menu button (:guilabel:`⋮`), and select :guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> Accounting --> Reconciliation`." msgstr "" @@ -5974,15 +5981,15 @@ msgstr "" msgid "Payments matching menu in the drop-down menu." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:106 +#: ../../content/applications/finance/accounting/payments.rst:108 msgid "During the :doc:`reconciliation `, if the sum of the debits and credits does not match, there is a remaining balance. This either needs to be reconciled at a later date or needs to be written off directly." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:111 +#: ../../content/applications/finance/accounting/payments.rst:113 msgid "Batch payments matching" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:113 +#: ../../content/applications/finance/accounting/payments.rst:115 msgid "You can use the **batch reconciliation feature** to reconcile several outstanding payments or invoices simultaneously for a specific customer or vendor. Go to your **Accounting Dashboard** and open your **bank journal**. In the **bank reconciliation** view, select a **transaction**, and click the :guilabel:`Batch Payments` tab. From here, you can reconcile your :doc:`batch payments ` with your outstanding payments or invoices." msgstr "" @@ -5990,11 +5997,11 @@ msgstr "" msgid "The batch payment reconcile option." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:123 +#: ../../content/applications/finance/accounting/payments.rst:125 msgid "Registering a partial payment" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:125 +#: ../../content/applications/finance/accounting/payments.rst:127 msgid "To register a **partial payment**, click :guilabel:`Register payment` from the related invoice or bill, and enter the amount received or paid. Upon entering the amount, a prompt appears to decide whether to :guilabel:`Keep open` the invoice or bill, or :guilabel:`Mark as fully paid`. Select :guilabel:`Keep open` and click :guilabel:`Create payment`. The invoice or bill is now marked as :guilabel:`Partial`. Select :guilabel:`Mark as fully paid` if you wish to settle the invoice or bill with a difference in the amount." msgstr "" @@ -6002,11 +6009,11 @@ msgstr "" msgid "Partial payment of an invoice or bill." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:136 +#: ../../content/applications/finance/accounting/payments.rst:138 msgid "Reconciling payments with bank statements" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:138 +#: ../../content/applications/finance/accounting/payments.rst:140 msgid "Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The next step is :doc:`reconciling ` it with the related bank statement line to have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`." msgstr "" @@ -6778,6 +6785,7 @@ msgid "Compatible check stationery for printing checks" msgstr "" #: ../../content/applications/finance/accounting/payments/pay_checks.rst:30 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:3 msgid "United States" msgstr "" @@ -7109,128 +7117,128 @@ msgstr "" msgid "The **Balance Sheet** shows a snapshot of the assets, liabilities and equity of your organisation as at a particular date." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:44 +#: ../../content/applications/finance/accounting/reporting.rst:46 msgid "Profit and Loss" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:46 +#: ../../content/applications/finance/accounting/reporting.rst:48 msgid "The **Profit and Loss** report (or **Income Statement**) shows your organisation's net income, by deducting expenses from revenue for the report period." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:53 +#: ../../content/applications/finance/accounting/reporting.rst:57 msgid "Executive Summary" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:55 +#: ../../content/applications/finance/accounting/reporting.rst:59 msgid "The **Executive Summary** allows for a quick look at all the important figures you need to run your company." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:58 +#: ../../content/applications/finance/accounting/reporting.rst:62 msgid "In very basic terms, this is what each of the items in this section is reporting :" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:73 +#: ../../content/applications/finance/accounting/reporting.rst:77 msgid "**Performance:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:64 +#: ../../content/applications/finance/accounting/reporting.rst:68 msgid "**Gross profit margin:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:63 +#: ../../content/applications/finance/accounting/reporting.rst:67 msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales (things like labour, materials, etc)." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:70 +#: ../../content/applications/finance/accounting/reporting.rst:74 msgid "**Net profit margin:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:67 +#: ../../content/applications/finance/accounting/reporting.rst:71 msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales, as well as any fixed overheads your company has (things like rent, electricity, taxes you need to pay as a result of those sales)." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:73 +#: ../../content/applications/finance/accounting/reporting.rst:77 msgid "**Return on investment (p.a.):**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:73 +#: ../../content/applications/finance/accounting/reporting.rst:77 msgid "The ratio of net profit made, to the amount of assets the company used to make those profits." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:93 +#: ../../content/applications/finance/accounting/reporting.rst:97 msgid "**Position:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:77 +#: ../../content/applications/finance/accounting/reporting.rst:81 msgid "**Average debtor days:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:77 +#: ../../content/applications/finance/accounting/reporting.rst:81 msgid "The average number of days it takes your customers to pay you (fully), across all your customer invoices." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:80 +#: ../../content/applications/finance/accounting/reporting.rst:84 msgid "**Average creditor days:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:80 +#: ../../content/applications/finance/accounting/reporting.rst:84 msgid "The average number of days it takes you to pay your suppliers (fully) across all your bills." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:85 +#: ../../content/applications/finance/accounting/reporting.rst:89 msgid "**Short term cash forecast:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:83 +#: ../../content/applications/finance/accounting/reporting.rst:87 msgid "How much cash is expected in or out of your organisation in the next month i.e. balance of your **Sales account** for the month less the balance of your **Purchases account** for the month." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:93 +#: ../../content/applications/finance/accounting/reporting.rst:97 msgid "**Current assets to liabilities:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:88 +#: ../../content/applications/finance/accounting/reporting.rst:92 msgid "Also referred to as **current ratio**, this is the ratio of current assets (assets that could be turned into cash within a year) to the current liabilities (liabilities which will be due in the next year). This is typically used as as a measure of a company's ability to service its debt." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:98 +#: ../../content/applications/finance/accounting/reporting.rst:102 msgid "General Ledger" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:100 +#: ../../content/applications/finance/accounting/reporting.rst:104 msgid "The **General Ledger Report** shows all transactions from all accounts for a chosen date range. The initial summary report shows the totals for each account and from there you can view a detailed transaction report or any exceptions. This report is useful for checking every transaction that occurred during a certain period of time." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:111 +#: ../../content/applications/finance/accounting/reporting.rst:115 msgid "Aged Payable" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:113 +#: ../../content/applications/finance/accounting/reporting.rst:117 msgid "Run the **Aged Payable Details** report to display information on individual bills, credit notes and overpayments owed by you, and how long these have gone unpaid." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:122 +#: ../../content/applications/finance/accounting/reporting.rst:126 msgid "Aged Receivable" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:124 +#: ../../content/applications/finance/accounting/reporting.rst:128 msgid "The **Aged Receivables** report shows the sales invoices that were awaiting payment during a selected month and several months prior." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:130 +#: ../../content/applications/finance/accounting/reporting.rst:136 msgid "Cash Flow Statement" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:132 +#: ../../content/applications/finance/accounting/reporting.rst:138 msgid "The **Cash Flow Statement** shows how changes in balance sheet accounts and income affect cash and cash equivalents, and breaks the analysis down to operating, investing and financing activities." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:141 +#: ../../content/applications/finance/accounting/reporting.rst:147 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:101 msgid "Tax Report" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:143 +#: ../../content/applications/finance/accounting/reporting.rst:149 msgid "This report allows you to see the **net** and **tax amounts** for all the taxes grouped by type (sale/purchase)." msgstr "" @@ -9356,6 +9364,7 @@ msgid "Exercise tax is **not** supported. This includes tobacco/vape taxes, fuel msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:35 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:266 msgid "Avalara's support documents: `About AvaTax `_" msgstr "" @@ -9511,8 +9520,6 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:14 #: ../../content/applications/finance/fiscal_localizations/india.rst:16 #: ../../content/applications/finance/fiscal_localizations/italy.rst:17 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 @@ -9521,6 +9528,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/thailand.rst:14 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:62 msgid "Name" msgstr "" @@ -9535,8 +9543,6 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:15 #: ../../content/applications/finance/fiscal_localizations/india.rst:17 #: ../../content/applications/finance/fiscal_localizations/italy.rst:18 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:72 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:116 @@ -9545,6 +9551,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/thailand.rst:15 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:63 msgid "Technical name" msgstr "" @@ -9562,8 +9569,6 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:16 #: ../../content/applications/finance/fiscal_localizations/india.rst:18 #: ../../content/applications/finance/fiscal_localizations/italy.rst:19 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 @@ -9572,6 +9577,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:64 msgid "Description" msgstr "" @@ -9580,6 +9586,7 @@ msgid ":guilabel:`Avatax`" msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:167 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:91 msgid "`account_avatax`" msgstr "" @@ -10151,6 +10158,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:1019 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:85 #: ../../content/applications/finance/fiscal_localizations/spain.rst:42 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:272 msgid "Reports" msgstr "" @@ -12547,7 +12555,7 @@ msgid "Ukraine - Accounting" msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:124 -msgid "United States - Accounting" +msgid ":doc:`United States - Accounting `" msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:125 @@ -12592,6 +12600,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:24 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:37 #: ../../content/applications/finance/fiscal_localizations/germany.rst:61 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:53 msgid "Modules installation" msgstr "" @@ -14067,6 +14076,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 #: ../../content/applications/finance/fiscal_localizations/chile.rst:373 #: ../../content/applications/finance/fiscal_localizations/romania.rst:79 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:180 msgid ":doc:`../accounting/get_started/chart_of_accounts`" msgstr "" @@ -14201,6 +14211,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:230 #: ../../content/applications/finance/fiscal_localizations/australia.rst:234 #: ../../content/applications/finance/fiscal_localizations/australia.rst:238 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:229 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 @@ -14774,6 +14785,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:540 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:93 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:444 msgid "Payroll" msgstr "" @@ -15943,6 +15955,7 @@ msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:420 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:402 msgid "Cash discount" msgstr "" @@ -15955,6 +15968,7 @@ msgid "To apply the right tax amount and report it correctly in your VAT return, msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:408 msgid ":doc:`../accounting/customer_invoices/cash_discounts`" msgstr "" @@ -16852,6 +16866,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:470 #: ../../content/applications/finance/fiscal_localizations/chile.rst:595 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:337 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" msgstr "" @@ -21015,7 +21030,7 @@ msgid "2-digits comparison" msgstr "" #: ../../content/applications/finance/fiscal_localizations/france.rst:184 -#: ../../content/applications/finance/payment_providers/authorize.rst:80 +#: ../../content/applications/finance/payment_providers/authorize.rst:82 msgid "Template" msgstr "" @@ -23208,7 +23223,19 @@ msgstr "" msgid "The user can verify the :ref:`GSTR-1 ` report before uploading it to the **GST portal** by clicking :guilabel:`GSTR-1 Report`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:365 +#: ../../content/applications/finance/fiscal_localizations/india.rst:366 +msgid "The user can also get details to be submitted in **GSTR-1** in **Spreadsheet view** by clicking on :guilabel:`Generate`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 generate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Spreadsheet View" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:375 msgid "If the **GSTR-1** report is correct, then click :guilabel:`Push to GSTN` to send it to the **GST portal**. The status of the :guilabel:`GSTR-1` report changes to :guilabel:`Sending`;" msgstr "" @@ -23216,7 +23243,7 @@ msgstr "" msgid "GSTR-1 in the Sending Status" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:371 +#: ../../content/applications/finance/fiscal_localizations/india.rst:381 msgid "After a few seconds, the status of the **GSTR-1** report changes to :guilabel:`Waiting for Status`. It means that the **GSTR-1** report has been sent to the :guilabel:`GST Portal` and is being verified on the :guilabel:`GST Portal`;" msgstr "" @@ -23224,11 +23251,11 @@ msgstr "" msgid "GSTR-1 in the Waiting for Status" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:378 +#: ../../content/applications/finance/fiscal_localizations/india.rst:388 msgid "Once more, after a few seconds, the status either changes to :guilabel:`Sent` or :guilabel:`Error in Invoice`. The status :guilabel:`Error in Invoice` indicates that some of the invoices are not correctly filled out to be validated by the **GST portal**;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:382 +#: ../../content/applications/finance/fiscal_localizations/india.rst:392 msgid "If the state of the **GSTR-1** is :guilabel:`Sent`, it means your **GSTR-1** report is ready to be filed on the **GST portal**." msgstr "" @@ -23236,7 +23263,7 @@ msgstr "" msgid "GSTR-1 Sent" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:388 +#: ../../content/applications/finance/fiscal_localizations/india.rst:398 msgid "If the state of the **GSTR-1** is :guilabel:`Error in Invoice`, invoices can be checked for errors in the :guilabel:`Log Note`. Once issues have been resolved, the user can click :guilabel:`Push to GSTN` to submit the file again on the **GST portal**." msgstr "" @@ -23248,7 +23275,7 @@ msgstr "" msgid "GSTR-1 Error in Invoice Log" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:398 +#: ../../content/applications/finance/fiscal_localizations/india.rst:408 msgid "Click :guilabel:`Mark as Filed` after filing the **GSTR-1** report on the **GST portal**. The status of the report changes to :guilabel:`Filed` in **Odoo**." msgstr "" @@ -23256,15 +23283,15 @@ msgstr "" msgid "GSTR-1 in the Filed Status" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:407 +#: ../../content/applications/finance/fiscal_localizations/india.rst:417 msgid "Receive GSTR-2B" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:409 +#: ../../content/applications/finance/fiscal_localizations/india.rst:419 msgid "Users can retrieve the **GSTR-2B Report** from the **GST portal**. This automatically reconciles the **GSTR-2B** report with your Odoo bills;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:412 +#: ../../content/applications/finance/fiscal_localizations/india.rst:422 msgid "Click :guilabel:`Fetch GSTR-2B Summary` to retrieve the **GSTR-2B** summary. After a few seconds, the status of the report changes to :guilabel:`Waiting for Reception`. This means Odoo is trying to receive the **GSTR-2B** report from the **GST portal**;" msgstr "" @@ -23273,15 +23300,15 @@ msgstr "" msgid "GSTR-2B in Waiting for Reception" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:419 +#: ../../content/applications/finance/fiscal_localizations/india.rst:429 msgid "Once more, after a few seconds, the status of the **GSTR-2B** changes to the :guilabel:`Being Processed`. It means Odoo is reconciling the **GSTR-2B** report with your Odoo bills;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:425 +#: ../../content/applications/finance/fiscal_localizations/india.rst:435 msgid "Once it is done, the status of the **GSTR-2B** report changes to either :guilabel:`Matched` or :guilabel:`Partially Matched`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:428 +#: ../../content/applications/finance/fiscal_localizations/india.rst:438 msgid "If the status is :guilabel:`Matched`:" msgstr "" @@ -23289,7 +23316,7 @@ msgstr "" msgid "GSTR-2B Matched" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:433 +#: ../../content/applications/finance/fiscal_localizations/india.rst:443 msgid "If the status is :guilabel:`Partially Matched`, you can make changes in bills by clicking :guilabel:`View Reconciled Bills`. Once it is done, click :guilabel:`re-match`." msgstr "" @@ -23301,20 +23328,20 @@ msgstr "" msgid "GSTR-2B Reconciled Bills" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:445 -#: ../../content/applications/finance/fiscal_localizations/india.rst:490 +#: ../../content/applications/finance/fiscal_localizations/india.rst:455 +#: ../../content/applications/finance/fiscal_localizations/india.rst:500 msgid "GSTR-3 report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:447 +#: ../../content/applications/finance/fiscal_localizations/india.rst:457 msgid "The :ref:`GSTR-3 ` report is a monthly summary of **sales** and **purchases**. This return is auto-generated by extracting information from **GSTR-1** and **GSTR-2**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:450 +#: ../../content/applications/finance/fiscal_localizations/india.rst:460 msgid "Users can compare the **GSTR-3** report with the **GSTR-3** report available on the **GST portal** to verify if they match by clicking :guilabel:`GSTR-3 Report`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:453 +#: ../../content/applications/finance/fiscal_localizations/india.rst:463 msgid "Once the **GSTR-3** report has been verified by the user and the tax amount on the **GST portal** has been paid. Once paid, the report can be **closed** by clicking :guilabel:`Closing Entry`;" msgstr "" @@ -23322,7 +23349,7 @@ msgstr "" msgid "GSTR-3" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:459 +#: ../../content/applications/finance/fiscal_localizations/india.rst:469 msgid "In :guilabel:`Closing Entry`, add the tax amount paid on the **GST portal** using challan, and click :guilabel:`POST` to post the :guilabel:`Closing Entry`;" msgstr "" @@ -23330,7 +23357,7 @@ msgstr "" msgid "GSTR-3 Post Entry" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:465 +#: ../../content/applications/finance/fiscal_localizations/india.rst:475 msgid "Once posted, the **GSTR-3** report status changes to :guilabel:`Filed`." msgstr "" @@ -23338,15 +23365,15 @@ msgstr "" msgid "GSTR-3 Filed" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:473 +#: ../../content/applications/finance/fiscal_localizations/india.rst:483 msgid "Tax reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:478 +#: ../../content/applications/finance/fiscal_localizations/india.rst:488 msgid "GSTR-1 report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:480 +#: ../../content/applications/finance/fiscal_localizations/india.rst:490 msgid "The :guilabel:`GSTR-1` report is divided into sections. It displays the :guilabel:`Base` amount, :abbr:`CGST (Central Goods and Services Tax)`, :abbr:`SGST (State Goods and Service Tax)`, :abbr:`IGST (Integrated Goods and Services Tax)`, and :guilabel:`CESS` for each section." msgstr "" @@ -23354,23 +23381,23 @@ msgstr "" msgid "GSTR-1 Report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:492 +#: ../../content/applications/finance/fiscal_localizations/india.rst:502 msgid "The :guilabel:`GSTR-3` report contains different sections:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:494 +#: ../../content/applications/finance/fiscal_localizations/india.rst:504 msgid "Details of inward and outward supply subject to a **reverse charge**;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:495 +#: ../../content/applications/finance/fiscal_localizations/india.rst:505 msgid "Eligible :abbr:`ITC (Income Tax Credit)`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:496 +#: ../../content/applications/finance/fiscal_localizations/india.rst:506 msgid "Values of **exempt**, **Nil-rated**, and **non-GST** inward supply;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/india.rst:497 +#: ../../content/applications/finance/fiscal_localizations/india.rst:507 msgid "Details of inter-state supplies made to **unregistered** persons." msgstr "" @@ -24310,131 +24337,477 @@ msgid "Kenya" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:10 -msgid ":ref:`Install ` the following modules to get all the features of the Kenyan localization:" +msgid "Install the 🇰🇪 **Kenyan** :ref:`fiscal localization package ` to get all the features of the Kenyan localization." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:19 -msgid ":guilabel:`Kenyan - Accounting`" +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:14 +msgid "eTIMS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 +msgid "The `Kenya Revenue Authority (KRA) `_ has implemented the `electronic Tax Invoice Management System (eTIMS) `_ for tax collection." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:20 -msgid "`l10n_ke`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:21 -msgid "Installing this module grants you access to the list of accounts used in the local GAAP and the list of common taxes (VAT, etc.)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:23 -msgid ":guilabel:`Kenyan - Accounting Reports`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:24 -msgid "`l10n_ke_reports`" +msgid "To submit documents through eTIMS, you must use an :abbr:`OSCU (Online Sales Control Unit)` that integrates with the existing **Trader Invoicing System (TIS)**, such as the one provided by Odoo. The OSCU is used to validate, encrypt, sign, transmit, and store tax invoices." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:25 -msgid "Installing this module grants you access to improved accounting reports for Kenya, such as Profit and Loss and Balance Sheets." +msgid "Make sure to :ref:`install ` the **Kenya eTIMS EDI** modules to use the OSCU device fully." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:28 -msgid "You also have to install the **Kenya Tremol Device EDI Integration** package to be able to report your taxes to the **Kenya Revenue Authority (KRA)** using the Tremol G03 Control Unit:" +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:31 +msgid "OSCU device initialization" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:33 +msgid "The OSCU must be initialized before use. To do so, navigate to :menuselection:`Settings --> General Settings`, click :guilabel:`Update Info` in the :guilabel:`Companies` section, and enter your :guilabel:`Tax ID`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:37 -msgid ":guilabel:`Kenya Tremol Device EDI Integration`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:38 -msgid "`l10n_ke_edi_tremol`" +msgid "To initialize the OSCU:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:39 -msgid "Installing this module integrates with the Kenyan G03 Tremol control unit device to report taxes to KRA through TIMS." +msgid "Go to the :guilabel:`eTIMS` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 -msgid "The three modules for the Kenya Fiscal Localization Package on Odoo" +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:40 +msgid "Fill in the :guilabel:`eTIMS Branch Code` and :guilabel:`Serial Number` of the device." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:41 +msgid "Set the :guilabel:`eTIMS Server Mode` to :guilabel:`Test` for the initialization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:42 +msgid "Tick the **user agreement** and click :guilabel:`Initialize OSCU`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:45 +msgid "Three server modes are available:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:47 -msgid "Kenyan TIMS integration" +msgid ":guilabel:`Demo`: Designed for demo purposes; it uses mock data and does not require an initialized OSCU;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:49 -msgid "The Kenya Revenue Authority (KRA) has decided to go digital for tax collection through the **Tax Invoice Management System (TIMS)**. As of December 1st, 2022, all VAT-registered persons should comply with TIMS. The goal is to reduce VAT fraud, increase tax revenue, and increase VAT compliance through standardization, validation, and transmission of invoices to KRA on a real-time or near real-time basis." +msgid ":guilabel:`Test`: Used to test the connection to eTIMS;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:55 -msgid "All VAT-registered taxpayers should use a **compliant tax register**. Odoo decided to develop the integration of the **Tremol G03 Control Unit (type C)**, which can be run locally through USB. This device validates invoices to ensure financial documents meet the new regulations and send the validated tax invoices directly to KRA. Installing a proxy server that provides a gateway between users and the internet is required." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:50 +msgid ":guilabel:`Production`: Used for live databases that are ready to send data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:53 +msgid "If your device has **already been initialized** (through another ERP, for example), enable the :doc:`../../general/developer_mode`, go to the :guilabel:`eTIMS` tab, and enter the key obtained through a previous initialization in the :guilabel:`Device Communication Key` field. Click :guilabel:`Save manually`, then :guilabel:`Initialize OSCU` (which may take a moment to become available)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:60 +msgid "eTIMS codes" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:62 -msgid "Installing the proxy server on a Windows device" +msgid "Common standard codes are **automatically** fetched from the KRA eTIMS API servers every two days. To fetch them manually, proceed as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:64 -msgid "Go to `odoo.com/download `_, fill out the required information and click :guilabel:`Download`." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:65 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:84 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:98 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:296 +msgid "Enable the :doc:`../../general/developer_mode`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:66 +msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Fetch KRA standard codes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:68 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:87 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:299 +msgid "Click the action in the list, then click :guilabel:`Run Manually` to fetch the codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:70 +msgid "Go to :menuselection:`Accounting --> Vendors --> KE OSCU Codes` to view the complete list of fetched OSCU codes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 -msgid "Install the Proxy Server on a Windows device" +msgid "List of fetched OSCU codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:71 -msgid "Once it is loaded on your computer, a wizard opens. You have to read and agree with the terms of the agreement. On the next page, select the :guilabel:`type of install: Odoo IoT`. Then, click :guilabel:`Next` and :guilabel:`Install`. Once completed, click :guilabel:`Next`. Check the :guilabel:`Start Odoo` box to be redirected to Odoo automatically, and then click :guilabel:`Finish`." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:79 +msgid "UNSPSC codes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:76 -msgid "A new page opens, confirming your :doc:`IoT Box <../../general/iot/config/connect>` is up and running. Connect your physical device **Tremol G03 Control Unit (type C)** to your laptop via USB. In the :guilabel:`IoT Device` section, check that your Tremol G03 Control Unit (type C) appears, confirming the connection between the device and your computer." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:81 +msgid "The KRA needs UNSPSC codes for a product to be **registered**. UNSPSC codes are **automatically** fetched from the KRA eTIMS API servers every day. To fetch them manually, proceed as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 -msgid "Your IoT box is up and running" +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:85 +msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Fetch UNSPSC codes from eTIMS`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:86 -msgid "If the device is not detected, try to plug it in again or click on the :guilabel:`Restart` button in the top right corner." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:90 -msgid ":doc:`Connect an IoT box to your database <../../general/iot/config/connect>`" +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:89 +msgid "Go to :menuselection:`Accounting --> Vendors --> KE UNSPSC Codes` to view the complete list of fetched UNSPSC codes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:93 -msgid "Sending the data to KRA using the Tremol G03 Control Unit" +msgid "Notices" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:95 -msgid "As a pre-requisite, check out that the :ref:`Kenyan Accounting modules ` are installed on your database. Then, go to :menuselection:`Accounting --> Configuration --> Settings --> Kenya TIMS Integration section`, and check that the :guilabel:`control Unit Proxy Address` matches the address of the IoT box." +msgid "Notices are **automatically** fetched from the KRA eTIMS API servers every day. To fetch them **manually**, proceed as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:100 -msgid "To send data to KRA, create a new invoice by going to :menuselection:`Accounting Dashboard --> Customer Invoice card` and clicking :guilabel:`New Invoice`. Upon confirmation of a new invoice, the :guilabel:`Send invoice to Fiscal Device` button appears. Clicking on it sends the invoice details to the device and from the device to the government. The :guilabel:`CU Invoice Number` field is now completed in your invoice, confirming the information has been sent." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:99 +msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Fetch KRA notices from eTIMS`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:106 -msgid "The :guilabel:`Tremol G03 Fiscal Device` tab contains fields that are automatically completed once the invoice is sent to the government:" +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:101 +msgid "Click the action in the list, then click :guilabel:`Run Manually` to fetch the notices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:109 -msgid ":guilabel:`CU QR Code`: Url from the KRA portal which reflects a QR code." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:103 +msgid "Go to :menuselection:`Accounting --> Vendors --> KE OSCU Notices` to view the complete list of fetched notices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:110 -msgid ":guilabel:`CU Serial Number`: reflects the serial number of the device." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:112 +msgid ":doc:`../../general/companies`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:111 -msgid ":guilabel:`CU Signing Date and Time`: The date and time when the invoice has been sent to KRA." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:114 +msgid "If you have :ref:`multiple companies `, you can centralize and manage them all on a single Odoo database. The KRA identifies and differentiates the **main** company from its **subsidiaries** by using IDs. Furthermore, subsidiaries are classified as **branches** of the main company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:113 -msgid "If you click on :guilabel:`Send and Print`, a .pdf of the invoice is generated. The :guilabel:`Kenyan Fiscal Device Info` is mentioned on the document." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:119 +msgid "To configure the company ID, open the **Settings** app, click :guilabel:`Update Info` in the :guilabel:`Companies` section, then click the :guilabel:`eTIMS` tab. The **main company** has a branch ID equal to `00` in a multi-company environment. Companies that are *not* the main company have a branch ID other than `00` and are assigned an ID by the KRA." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:117 -msgid "To verify KRA has received the invoice information, take the :guilabel:`CU Invoice Number` and enter it in the :guilabel:`Invoice Number Checker` section on `Kenya Revenue Authority website `_. Click :guilabel:`Validate` and find the invoice details." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:124 +msgid "To add a branch, go to the :guilabel:`Branches` tab in the **company settings** and click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:127 +msgid "To fetch the **branch ID** from the KRA for your non-main companies, ensure the main company has a Kenyan :guilabel:`Tax ID` and the OSCU device has been :ref:`initialized `. Then, go to the :guilabel:`Branches` tab and click :guilabel:`Populate from KRA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:132 +msgid "The KRA considers each **place of supply** as a separate branch (ID)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:133 +msgid "The **OSCU** device must be :ref:`initialized independently ` for each branch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 +msgid "\"Populate from KRA\" button for branches." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:140 +msgid "Contact branch ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:142 +msgid "To attribute a branch ID to a contact, access the contact form, go to the :guilabel:`Accounting` tab, and enter the branch code in the :guilabel:`eTIMS Branch Code` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:146 +msgid "By default, contacts' branch IDs are set to `OO`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:149 +msgid "KRA sequences" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:152 +msgid "Odoo invoice sequences and KRA sequences are **different**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:154 +msgid "In Odoo, invoice sequences depend on the **main company**. Main companies can see the invoices of branches, but branches **cannot** see the main company's invoices or those of other branches." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:157 +msgid "The KRA needs **independent** sequences per branch. Therefore, Odoo manages sequences individually per branch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:161 +msgid "If you have a main company with two branches, the invoice sequence would be the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:163 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:169 +msgid "Creating an invoice on **branch 1**: INV/2024/00001;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:164 +msgid "Creating an invoice on **branch 2**: INV/2024/00002;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:165 +msgid "Creating an invoice on the **main company**: INV/2024/00003." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:167 +msgid "This is how Odoo manages sequences to be compliant with the KRA regulations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:170 +msgid "Creating an invoice on **branch 2**: INV/2024/00001;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:171 +msgid "Creating an invoice on the **main company**: INV/2024/00001." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:174 +msgid "Insurance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:176 +msgid "For **health service providers**, you can send insurance information about the main and branch companies and update it in eTIMS. To do so, open the **Settings** app, click :guilabel:`Update Info` in the :guilabel:`Companies` section, and in the :guilabel:`eTIMS` tab, fill in the fields related to your company: :guilabel:`Insurance Code`, :guilabel:`Insurance Name`, and :guilabel:`Insurance Rate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:185 +msgid "Product registration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:187 +msgid "The KRA requires **products to be registered** first before conducting business operations (such as stock movements, :abbr:`BOM (Bill of Materials)`, customer invoices, etc.). For a product to be registered, the following fields must be defined on the product form:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:191 +msgid "In the :guilabel:`General Information` tab: :guilabel:`Cost`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:192 +msgid "In the :guilabel:`Accounting` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:194 +msgid ":guilabel:`Packaging Unit`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:195 +msgid ":guilabel:`Packaging Quantity`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:196 +msgid ":guilabel:`Origin Country`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:197 +msgid ":guilabel:`eTIMS Product Type`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:198 +msgid ":guilabel:`Insurance Applicable`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:199 +msgid ":ref:`UNSPSC Category `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:201 +msgid "If the elements above are defined, the product is automatically registered while sending the operation to the KRA. If not, you will be alerted by a yellow banner at the top of the screen inviting you to check the missing elements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 +msgid "Product registration template." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:209 +msgid "Stock movements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:211 +msgid "All **stock movements** must be sent to the KRA. They do not require an invoice if they are internal operations or stock adjustments; therefore, Odoo automatically sends them if at least one of the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:215 +msgid "No contact is set for the move;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:216 +msgid "The contact is your main company or a branch of the main company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:218 +msgid "If the stock moves are **external operations** (e.g., to contacts that are not part of the main company or its branches), the stock moves are automatically sent *after* the invoice is sent to eTIMS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:223 +msgid "The stock move must be confirmed before sending the invoice to eTIMS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:224 +msgid "The product(s) must be :ref:`registered ` for the stock move to be sent to eTIMS. If the product has not been registered yet, a yellow banner will prompt the products' registration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:231 +msgid "Odoo automatically fetches new vendor bills from eTIMS every day. You need to confirm the fetched vendor bills and send the confirmation to the KRA. To confirm a vendor bill, it must be linked to one or several confirmed purchase order line(s)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:237 +msgid "In the case of purchases (not customs imports), the steps to link purchase order lines with bills are the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:240 +msgid "Go to :menuselection:`Accounting --> Vendors --> Bills`. The vendor bill is fetched from the KRA servers. The JSON file is available in the chatter of the vendor bill if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:243 +msgid "Odoo looks at the :guilabel:`Tax ID` (PIN) of the vendor (partner);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:245 +msgid "If it is unknown, a new contact (partner) is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:246 +msgid "If it is known and the branch ID is the same, Odoo uses the known contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:248 +msgid "In the fetched bill from the KRA, select the :guilabel:`Product`. Each vendor bill *must* contain a product to be confirmed and sent to eTIMS later on." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:250 +msgid "Odoo checks existing purchase order lines matching the product(s) entered at the previous step and the partner (if any). Click the :guilabel:`Purchase Order Line` field, and select the correct related purchase order line(s) matching the product(s). The quantities on the bill *must* be the same as the received quantities indicated on the purchase order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:255 +msgid "If no existing purchase order line matches the lines of the fetched bill, click :guilabel:`Create Purchase Order` and create a purchase order based on the unmatched line(s). :guilabel:`Validate` the resulting stock move and :guilabel:`Confirm` the bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:259 +msgid "Set a method in the :guilabel:`eTIMS Payment Method` field.." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:260 +msgid "Once all steps are completed, click :guilabel:`Send to eTIMS` to send the vendor bill. When the vendor bill has been confirmed on eTIMS, the **KRA invoice number** can be found in the :guilabel:`eTIMS Details` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 +msgid "Bill registration steps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:268 +msgid "Invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:271 +msgid "The KRA does *not* accept sales if the product is not in stock." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:273 +msgid "This is the **advised sales flow** in Odoo when selling:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:275 +msgid "Create a **sales order**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:276 +msgid ":guilabel:`Validate` the delivery." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:277 +msgid ":guilabel:`Confirm` the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:278 +msgid "Click :guilabel:`Send and print`, and then enable :guilabel:`Send to eTIMS`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:279 +msgid "Click :guilabel:`Send & print` to send the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:281 +msgid "Once the invoice has been sent and signed by the KRA, the following information can be found on it:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:284 +msgid "**KRA invoice number**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:285 +msgid "Mandatory KRA invoice fields, such as **SCU information**, **date**, **SCU ID**, **receipt number**, **item count**, **internal date**, and **receipt signature**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:287 +msgid "The **KRA tax table**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:288 +msgid "A unique **KRA QR code** for the signed invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:291 +msgid "Imports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:293 +msgid "Customs import codes are **automatically** fetched from the KRA eTIMS API servers every day. To fetch them manually, proceed as follows:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:297 +msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Receive Customs Imports from the OSCU`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:301 +msgid "Go to :menuselection:`Accounting --> Vendors --> Customs Imports` to view the imported codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:303 +msgid "The following steps are required to send and have **customs imports** signed by the KRA:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:305 +msgid "Go to :menuselection:`Accounting --> Vendors --> Customs Imports`; The customs import is fetched automatically from the KRA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:307 +msgid "Match the imported item with an existing registered product in the :guilabel:`Product` field (or create a product if no related product exists)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:309 +msgid "Set a vendor in the :guilabel:`Partner` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:310 +msgid "Based on the partner, match the imported item with its related purchase order (see :ref:`purchase steps `). The stock must be correctly adjusted when the customs import is approved." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:314 +msgid "If no related purchase order exists, create one and :guilabel:`Confirm` it. Then, confirm the delivery by clicking :guilabel:`Receive Products`, then :guilabel:`Validate` on the purchase order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:318 +msgid "Click :guilabel:`Match and Approve` or :guilabel:`Match and Reject`, depending on the situation of the goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:322 +msgid "The JSON file received from the KRA is attached to the chatter of the customs import." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:325 +msgid "BOM" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:327 +msgid "The KRA requires all BOMs to be sent to them. To send BOMs to eTIMS, the product and its components *must* be :ref:`registered `. To access a product's BOM, click on the product and then click the :guilabel:`Bill of Materials` smart button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:331 +msgid "Fill in the KRA's required fields in the :guilabel:`KRA eTIMS details` section of the :guilabel:`Accounting` tab, then click :guilabel:`Send to eTIMS`. The successful sending of the BOM is confirmed in the chatter, where you can also find the sent information in an attached JSON file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:339 +msgid "The KRA does not accept credit notes with quantities or prices higher than the initial invoice. When reversing the invoice, a KRA reason must be indicated: in the credit note form, go to the :guilabel:`eTIMS Details` tab, select the :guilabel:`eTIMS Credit Note Reason`, and then select the invoice number in the :guilabel:`Reversal of` field." msgstr "" #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:3 @@ -24582,6 +24955,7 @@ msgid "In order to electronically sign any documents in Odoo, ensure the *Sign* msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:554 msgid "Requirements" msgstr "" @@ -26639,6 +27013,7 @@ msgid "The creation of the |GRE| delivery guide in Odoo **must** be sent directl msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst:670 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:466 msgid "Required information" msgstr "" @@ -28720,6 +29095,961 @@ msgstr "" msgid "During this process, the :guilabel:`Connect to HMRC` button no longer appears for other UK-based companies." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:15 +msgid "The Odoo fiscal localization package for the United States follows the Generally Acceptable Accounting Principles (GAAP) accounting standards and rules used to prepare financial statements, as outlined by the Financial Accounting Standards Board (FASB) and adopted by the Securities and Exchange Commission (SEC)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:21 +msgid "`Financial Accounting Standards Board (FASB) `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:22 +msgid "`Securities and Exchange Commission (SEC) `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:24 +msgid "In addition, a series of videos on the subject of Accounting are available through Odoo's eLearning platform. These videos cover how to start from scratch, set up configurations, complete common workflows, and provide in-depth looks at some specific use cases, as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:29 +msgid "`Odoo Tutorials: Accounting & Invoicing `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:31 +msgid "`Odoo SmartClass: Accounting `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:36 +msgid "Below are the available modules in Odoo for accounting use in the United States." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:39 +msgid "The modules listed below are either for reference only or are optional, as the core requirements to operate under the US fiscal localization in Odoo are already included under the default package that came installed during database initialization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:43 +msgid "Verify the default package is in use by navigating to :menuselection:`Accounting App --> Settings` and under the :guilabel:`Fiscal Localization` section at the top, look for the `Generic Chart Template` selection to be listed next to the :guilabel:`Package` field label. This chart template includes the necessary settings for the US localization for the Odoo *Accounting* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid "The Generic Chart Template comes pre-configured for the US localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:55 +msgid ":ref:`Install ` the following modules to get all the features of the United States localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:65 +msgid ":guilabel:`United States - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:66 +msgid "`l10n_us`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:67 +msgid "Base accounting module for United States localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:68 +msgid ":ref:`US - Accounting Reports `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:69 +msgid "`l10n_us_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:70 +msgid "Adds United States accounting reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:71 +msgid ":guilabel:`US Checks Layout`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:72 +msgid "`l10n_us_check_printing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:73 +msgid "Enables the printing of payments on pre-printed check paper. Supports the three most common check formats and will work out of the box with the linked checks from `checkdepot.net `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:77 +msgid "`Check on top: Quicken / QuickBooks standard `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:79 +msgid "`Check on middle: Peachtree standard `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:81 +msgid "`Check on bottom: ADP standard `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:84 +msgid ":ref:`NACHA Payments `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:85 +msgid "`l10n_us_payment_nacha`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:86 +msgid "Export payments as NACHA files for use in the United States." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:87 +msgid ":ref:`1099 Reporting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:88 +msgid "`l10n_us_1099`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:89 +msgid "Export 1099 data for e-filing with a 3rd party." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:90 +msgid ":ref:`Avatax `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:92 +msgid "Module for the :doc:`AvaTax integration <../accounting/taxes/avatax>` with Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:93 +msgid ":ref:`United States - Payroll `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:94 +msgid "`l10n_us_hr_payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:95 +msgid "Includes the necessary rules for United States payroll, including:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:97 +msgid "Employee Details" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:98 +msgid "Employee Contracts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:99 +msgid "Passport-based Contracts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:100 +msgid "Allowances/Deductions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:101 +msgid "Allow Configurations for Basic/Gross/Net Salary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:102 +msgid "Employee Payslip" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:103 +msgid "Integration with Leaves Management" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:105 +msgid ":ref:`United States - Payroll with Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:106 +msgid "`l10n_us_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:107 +msgid "Contains the necessary accounting data for the United States payroll rules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:108 +msgid ":ref:`United States - Payroll - Export to ADP `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:109 +msgid "`l10n_us_hr_payroll_adp`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:110 +msgid "Export Work Entries to the ADP payroll software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:117 +msgid "The :doc:`chart of accounts (COA) <../accounting/get_started/chart_of_accounts>` for the United States localization, in Odoo, follows the standard |GAAP| structure, with accounts grouped into seven main categories, with corresponding numeric values that prefix individual journal entries:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:121 +msgid "**Receivable**: the balance of money (or credit) due to the business for goods or services delivered or used, but not yet paid for by customers. |AR| is indicated by the journal code labeled (or beginning) with :guilabel:`1`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:124 +msgid "**Payable**: the business's short-term obligations owed to its creditors or suppliers, which have not yet been paid. |AP| is indicated by the journal code labeled (or beginning) with :guilabel:`2`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:127 +msgid "**Equity**: the amount of money that would be returned to a company's shareholders if all of the assets were liquidated and all of the company's debt was paid off in the case of liquidation. Equity is indicated by the journal code labeled (or beginning) with :guilabel:`3` or :guilabel:`9`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:131 +msgid "**Assets**: items listed on the balance sheet that contains economic value or have the ability to generate cash flows in the future, such as a piece of machinery, a financial security, or a patent. Assets are indicated by the journal code labeled (or beginning) with :guilabel:`1`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:134 +msgid "**Liability**: refers to a company's financial debts or obligations that arise during the course of business operations. Liabilities are indicated by the journal code labeled (or beginning) with :guilabel:`2`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:137 +msgid "**Income**: synonymous with *net income*, this is the profit a company retains after paying off all relevant expenses from sales revenue earned. Income is indicated by the journal code labeled (or beginning) with :guilabel:`4` or :guilabel:`6`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:140 +msgid "**Expenses**: the cost of operations that a company incurs to generate revenue. Expenses are indicated by the journal code labeled (or beginning) with a :guilabel:`6`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:144 +msgid "Predefined accounts are included in Odoo, as part of the |CoA| that's installed with the US localization package. The accounts listed below are preconfigured to perform certain operations within Odoo. It is recommended to **not** delete these accounts; however, if changes are needed, rename the accounts instead." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:153 +msgid ":guilabel:`Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:154 +msgid ":guilabel:`Account Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:155 +msgid ":guilabel:`Current Assets`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Bank Suspense Account`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Outstanding Receipts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Outstanding Payments`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Liquidity Transfer`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Stock Valuation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Stock Interim (Received)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Stock Interim (Delivered)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Cost of Production`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:164 +msgid ":guilabel:`Income`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Foreign Exchange Gain`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Cash Difference Gain`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Cash Discount Gain`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:168 +msgid ":guilabel:`Expenses`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Cash Discount Loss`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Foreign Exchange Loss`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid ":guilabel:`Cash Difference Loss`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:172 +msgid ":guilabel:`Current Year Earnings`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:173 +msgid ":guilabel:`Undistributed Profits/Losses`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:174 +msgid ":guilabel:`Receivable`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:175 +msgid ":guilabel:`Account Receivable`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:176 +msgid ":guilabel:`Payable`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:177 +msgid ":guilabel:`Account Payable`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:181 +msgid ":doc:`../accounting/get_started/cheat_sheet`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:184 +msgid "View, edit, and sort accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:186 +msgid "Access the *Chart of Accounts* dashboard in Odoo by navigating to :menuselection:`Accounting app --> Configuration --> Accounting: Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:189 +msgid "From the :guilabel:`Chart of Accounts` dashboard, create new accounts by clicking the purple :guilabel:`New` button in the top-left corner of the dashboard and :ref:`filling in the corresponding form `. Search and sort through existing accounts by using specific :guilabel:`Filters` and :guilabel:`Group By` criteria, which are available in the mega menu under the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:195 +msgid "To filter accounts by category, click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon to access the mega menu and look under the :guilabel:`Filters` column for individual selections. Clicking on a specific category will only show accounts that match that particular filter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:199 +msgid "To view all the available account types, remove all of the filters in the :guilabel:`Search...` bar, and then click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon to access the mega menu. From there, select :guilabel:`Account Type` under the :guilabel:`Group By` column heading to list all of the account types in the table." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:-1 +msgid "Chart of Accounts grouped by Account Type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:208 +msgid "Besides structure, there are other key differences in the chart of accounts in the United States, compared to other countries:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:211 +msgid "**Specificity**: US |GAAP| often requires more detailed accounts compared to some other countries. This can include separate accounts for various types of revenue, expenses, and assets, providing more granular information in financial reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:214 +msgid "**Regulatory Requirements**: In the United States, there are specific regulatory requirements set by bodies such as the |SEC| for publicly traded companies. These requirements may influence the structure and content of the |COA| to ensure compliance with reporting standards." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:217 +msgid "**Industry Practices**: Certain industries in the United States may have unique accounting requirements or specialized |COA| structures. For example, financial institutions often have specific accounts related to loans, investments, and interest income." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:220 +msgid "**Tax Considerations**: The |COA| may also reflect tax considerations, such as accounts for deductible expenses, deferred tax assets, and liabilities, to ensure compliance with tax laws and facilitate tax reporting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:224 +msgid "These differences, ultimately, should be reflected in the |COA| structure itself, with the addition of new accounts, as needed, in order to meet the demands of US accounting reporting requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:228 +msgid ":ref:`Create a new account `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:229 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:334 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:236 +msgid "In the United States, tax rates and what is considered taxable vary by jurisdiction. Default *Sales* and *Purchase* taxes are created automatically when the Odoo *Accounting* application is installed. To manage existing or configure additional taxes, navigate to :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:244 +msgid "AvaTax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:246 +msgid "**Avalara AvaTax** is a cloud-based tax calculation and compliance software that integrates with Odoo for the United States and Canadian accounting localizations. Integrating AvaTax with Odoo provides real-time and region-specific tax calculations when items are sold, purchased, and invoiced in the database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:252 +msgid "AvaTax is only available for integration with databases/companies that have locations in the United States and Canada. This means the fiscal position/country of a database can only be set to the United States or Canada. Reference this documentation for more information: :ref:`avatax/fiscal_country`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:258 +msgid "Refer to the documentation articles below to integrate and configure an AvaTax account with an Odoo database:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:261 +msgid ":doc:`AvaTax integration <../accounting/taxes/avatax>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:262 +msgid ":doc:`Avalara management portal <../accounting/taxes/avatax/avalara_portal>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:263 +msgid ":doc:`Calculate taxes with AvaTax <../accounting/taxes/avatax/avatax_use>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:264 +msgid "`US Tax Compliance: AvaTax elearning video `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:274 +msgid "A number of :doc:`report selections <../accounting/reporting>` are readily available for the US localization, under the :menuselection:`Accounting app --> Reporting` drop-down menu:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:277 +msgid ":ref:`Balance Sheet `: a \"snapshot\" of a company's financial position at a specific point in time, which contains an overview of a company's assets, liabilities, and equity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:280 +msgid ":ref:`Profit & Loss `: otherwise known as a *P&L statement* or *income statement*, provides a summary of a company's revenues, expenses, and profits/losses over a given period of time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:283 +msgid ":ref:`Cash Flow Statement `: shows how much cash and cash equivalents a company has received and spent in a given period." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:285 +msgid ":ref:`Executive Summary `: an overview report that covers the key performance indicators of a company's financial position, such as revenue, profit, and debt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:288 +msgid ":ref:`Tax Report `: an official form filed for a tax authority that reports income, expenses, and other pertinent tax information. Tax reports allow taxpayers to calculate their tax liability, schedule tax payments, or request refunds for the overpayment of taxes. In Odoo, the tax report can be made monthly, every two months, quarterly, every 4 months, semi-annually, and annually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:293 +msgid ":guilabel:`Check Register`: a report that displays cash transactions (regardless of the journal) with their running balance after the transaction. Only visible with the *US - Accounting Reports* (`l10n_us_reports`) module installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:296 +msgid ":ref:`1099 Report `: a CSV download of payments made to non-employees in a period to file electronically in a third-party service. Only visible with the *1099 Reporting* (`l10n_us_1099`) module installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:302 +msgid "Depending on the type of report, certain filters are available at the top of the dashboard:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:304 +msgid "a *date* filter, indicated by a :icon:`fa-calendar` :guilabel:`(calendar)` icon that precedes a date in *MM/DD/YYYY* format. Use this to select a specific date or date range for the report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:306 +msgid "a :icon:`fa-bar-chart` :guilabel:`Comparison` filter, to compare reporting periods against each other" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:308 +msgid "a *journal* filter, as indicated by a :icon:`fa-book` :guilabel:`(book)` icon and the default setting of :guilabel:`All Journals`. Use this filter to specify which journals should be included in the report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:311 +msgid "an *entries type* filter, as indicated by a :icon:`fa-filter` :guilabel:`(filter)` icon, with the default setting of :guilabel:`Posted Entries Only, Accrual Basis`. Use this filter to determine which type of journal entries should be included in the report (e.g. posted or draft), along with the type of accounting method (e.g. accrual or cash basis)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:316 +msgid "There are view options in this filter, as well, one that will :guilabel:`Hide lines at 0` for more relevant viewing, along with a :guilabel:`Split Horizontally` option to keep the report above the screen's fold, removing the need to scroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid "Accounting method filter menu for reports, covering accrual vs. cash basis methods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:324 +msgid "a *decimal* filter, that by default, includes figures with cents, as indicated by the :guilabel:`In .$` setting. Use the other options in the drop-down menu to change figures in the report to whole numbers (:guilabel:`In $`), thousands (:guilabel:`In K$`), or millions (:guilabel:`In M$`) formats." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:328 +msgid "a report *customization* filter, indicated by the :icon:`fa-cogs` :guilabel:`(gears)` icon. Use this filter to customize the current report's sections and line items, or build new reports, as desired." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:333 +msgid ":doc:`Accounting reporting <../accounting/reporting>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:341 +msgid "The 1099 report, available by :ref:`installing ` the *1099 Reporting* (`l10n_us_1099`) module, includes payments that are made to non-employees across a given reporting period. Use the available CSV download from the report in Odoo to file 1099 payments electronically via a third-party service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:346 +msgid "To generate a 1099 report, navigate to :menuselection:`Accounting app --> Reporting --> Management: 1099 Report` to open a :guilabel:`1099 Report` wizard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:349 +msgid "First, enter the date range of the transactions to report in the :guilabel:`Start Date` and :guilabel:`End Date` fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:352 +msgid "Then, edit the journal items that appear on the wizard. Click :guilabel:`Add a line` to add any items that are missing. Be sure to remove any items that should not be included in the report by clicking :icon:`fa-times` :guilabel:`(delete)` on the row." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:356 +msgid "Finally, once all necessary items are included in the 1099 report, click on the :guilabel:`Generate` button. Doing so, downloads a CSV file that groups transactions by the partner that received the payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:365 +msgid "Navigate to the *Cash Flow Statement* (CFS) dashboard by going to :menuselection:`Accounting app --> Reporting --> Statement Reports: Cash Flow Statement`. From here, |CFS| reports can be generated using the various :ref:`filters ` that are available at the top of the dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:370 +msgid "Odoo uses the *direct* cash flow method to compile cash flow statements, which measures actual cash inflows and outflows from the company's operations, such as when cash is received from customers or when cash payments are made to suppliers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:374 +msgid "By default, an account labeled with any of the three default :guilabel:`Tags` on the :guilabel:`Chart of Accounts` dashboard will be included in the report, which includes: :guilabel:`Operating Activities`, :guilabel:`Financing Activities`, and :guilabel:`Investing & Extraordinary Activities`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:-1 +msgid "Examples of tagged accounts that are included in the Cash Flow Statement in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:383 +msgid "Additionally, the cash flow statement in Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:385 +msgid "is limited to the *Bank* and *Cash* journals to reflect money coming in or out; and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:386 +msgid "also contains *Expenses* accounts, to show the counterpart transactions versus *Bank* or *Cash* journal entries, while excluding |AR| and |AP| activity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:390 +msgid "Create a vendor bill for $100, as an operating expense (not |AP|). Doing so will **not** reflect a transaction on the cash flow statement. However, register a corresponding payment for $100, and the transaction **will** reflect on the cash flow statement as :guilabel:`Cash paid for operating activities`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:0 +msgid "Example of a bill registered as an operating expense as part of a cash flow statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:404 +msgid "Cash discounts can be configured from :menuselection:`Accounting app --> Payment Terms`. Each payment term can be set up with a cash discount and reduced tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:413 +msgid "Writing checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:415 +msgid "Using checks is still a common payment practice in the US. Be sure the *US Checks Layout* (`l10n_us_check_printing`) module for the US localization is :ref:`installed `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:418 +msgid "To enable check printing from Odoo, navigate to :menuselection:`Accounting --> Configuration --> Settings` and find the :guilabel:`Vendor Payments` section. From here, tick the :guilabel:`Checks` checkbox to reveal several fields for check configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:422 +msgid "Select a :guilabel:`Check Layout` from the drop-down menu:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:424 +msgid ":guilabel:`Print Check (Top) - US`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:425 +msgid ":guilabel:`Print Check (Middle) - US`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:426 +msgid ":guilabel:`Print Check (Bottom) - US`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:428 +msgid "Next, choose whether or not to enable the :guilabel:`Multi-Pages Check Stub` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:430 +msgid "Optionally set a :guilabel:`Check Top Margin` and :guilabel:`Check Left Margin`, if required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:432 +msgid "Once all check configurations are complete, :guilabel:`Save` the settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:435 +msgid "Some of the check formats may require pre-printed paper from a third party vendor, https://checkdepot.net/collections/odoo-checks is recommended." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:439 +msgid ":doc:`../accounting/payments/pay_checks`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:446 +msgid "The *Payroll* application is responsible for calculating an employee's pay, taking into account all work, vacation, and sick time, benefits, and deductions. The *Payroll* app pulls information from the *Attendances*, *Timesheets*, *Time Off*, *Employees* and *Expenses* applications, to calculate the worked hours and compensation for each employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:451 +msgid "When using an external payroll provider, such as *ADP*, it is necessary to export the various payroll-related data, such as work entries, repayment of expenses, taxes, commissions, and any other relevant data, so the data can be uploaded into the payroll provider, who then issues the actual paychecks or directly deposits the funds into an employee's bank account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:456 +msgid "In order to export the payroll data, the work entries must first be validated and correct. Refer to the :doc:`work entries <../../hr/payroll/work_entries>` documentation for more information regarding validating work entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:460 +msgid "Once work entries are validated, the information can be :ref:`exported to ADP `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:462 +msgid "After payments have been issued to employees, payslips can be processed into batches, validated, and posted to the corresponding accounting journals to keep all financial records in Odoo current." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:468 +msgid "It is important to have the *Employees* application installed, and all employee information populated. Several fields in both the :ref:`employee records `, as well as in an :ref:`employee contracts `, are necessary to properly process the employee's pay. Ensure the following fields are filled out in their respective places." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:477 +msgid "Employee records" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:479 +msgid "In each employee record, there is various information the *Payroll* application requires to properly process payslips, including various banking, tax, and work information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:482 +msgid "Navigate to the :menuselection:`Employees app` and select an employee record to view the sections of the employee form that directly affect *Payroll*:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:485 +msgid ":guilabel:`Work Information` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:487 +msgid ":guilabel:`Work Address`: indicates where the employee is located, including the state, which affects the tax calculations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:489 +msgid ":guilabel:`Working Hours`: determines how pay is calculated, and determines if an employee earns overtime." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:492 +msgid ":guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:494 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:528 +msgid ":guilabel:`SSN No`: the last four digits of the employee's Social Security Number (SSN) appears on payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:496 +msgid ":guilabel:`Bank Account Number`: the bank account associated with the NACHA payment file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:498 +msgid ":guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:500 +msgid ":guilabel:`Federal Tax Filing Status`: the tax status an employee uses for Payroll tax calculations, which can be different from their state status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:502 +msgid ":guilabel:`State Tax Filing Status`: the tax status an employee uses for their state portion of the Payroll tax calculation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:504 +msgid ":guilabel:`W-2 Form`: a US tax form indicating the summary of wages, taxes, and benefits paid to an employee during a tax period (typically one year)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:506 +msgid ":guilabel:`W-4 Form`: an IRS form that helps outline the amount of federal taxes to withhold for an employee, which is paid to the IRS by the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:512 +msgid "Employee contracts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:514 +msgid "Additionally, there is information that is found in an employee contract that also affects the *Payroll* application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:517 +msgid "Navigate to the :menuselection:`Employees app --> Employees --> Contracts` and select a contract record to view the sections of a contract that directly affect *Payroll*:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:520 +msgid ":guilabel:`General Information`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:522 +msgid ":guilabel:`Salary Structure Type: United States: Employee`: defines when the employee is paid, their working schedule, and the work entry type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:524 +msgid ":guilabel:`Work Entry source`: determines how work entries are calculated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:526 +msgid ":guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:530 +msgid ":guilabel:`Wage type`: determines how the employee is paid, wether a Fixed wage (salary) or Hourly wage." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:532 +msgid ":guilabel:`Schedule Pay`: defines how often the employee is paid, either :guilabel:`Annually`, :guilabel:`Semi-annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, :guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, :guilabel:`Weekly`, or :guilabel:`Daily`. In the US, Semi-monthly (24 payments a year) or bi-weekly (26 payments a year) are the most common." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:536 +msgid ":guilabel:`Wage, Yearly, and Monthly cost`: used to show the total cost of an employee. It is recommended to populate the :guilabel:`Yearly` wage first, as it auto-populates the other fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:539 +msgid ":guilabel:`Pre-tax benefits`: populate this section according to the employee's selections. Pre-tax benefits decrease the gross wage, which lowers the base amount that is taxed. These are displayed at the beginning of the payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:542 +msgid ":guilabel:`Post-tax benefits`: these benefits are deductions made *after* taxes are calculated. These appear towards the end of the payslip before the net amount is displayed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:546 +msgid ":doc:`Employees documentation <../../hr/employees/new_employee>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:551 +msgid "Export work entries to ADP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:556 +msgid "In order to create a report that can be uploaded to ADP, there are some initial configuration steps that must be completed first." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:559 +msgid "First, ensure the *United States - Payroll - Export to ADP* (`l10n_us_hr_payroll_adp`) module is :ref:`installed `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:562 +msgid "Then, the company **must** have an *ADP Code* entered in the company settings. To do so, navigate to :menuselection:`Payroll app --> Configuration --> Settings`. Enter the :guilabel:`ADP Code` in the :guilabel:`US Localization` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:566 +msgid "Next, work entry types **must** have the correct ADP code listed in the *External Code* field for each work entry type that is being referenced." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:569 +msgid "Lastly, every employee **must** have an *ADP Code* entered on their employee form. To do so, navigate to :menuselection:`Employees app`, select an employee record, and open the :guilabel:`HR Settings` tab. Enter the :guilabel:`ADP Code` in the :guilabel:`ADP Information` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:573 +msgid "The :guilabel:`ADP Code` code is how ADP identifies that particular employee, and is typically a six-digit number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:577 +msgid ":ref:`payroll/new-work-entry`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:578 +msgid ":doc:`../../hr/employees/new_employee`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:581 +msgid "Export data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:583 +msgid "Once :doc:`work entries <../../hr/payroll/work_entries>` have been verified, the information can be exported to a CSV file, which can then be uploaded into ADP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:586 +msgid "To export the data, navigate to :menuselection:`Payroll app --> Reporting --> United States: ADP Export`, then click :guilabel:`New`. Next, enter the :guilabel:`Start Date` and :guilabel:`End Date` for the work entries using the calendar pop-over." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:590 +msgid "Then, enter a :guilabel:`Batch ID` in the corresponding field. The recommendation for this field is to enter the date in a `YY-MM-DD` format, followed by any other characters to distinguish that specific batch, such as a department name, or any other defining characteristics for the batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:594 +msgid "Enter a :guilabel:`Batch Description` in the corresponding field. This should be short and descriptive, but distinct from the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:597 +msgid "Ensure the correct company populates the :guilabel:`Company` field. Change the selected company with the drop-down menu, if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:600 +msgid "Lastly, add the employee's work entry information to the list. Click :guilabel:`Add a line` and an :guilabel:`Add: Employee` pop-up window loads. The list can be :doc:`filtered <../../essentials/search>` to more easily find the employees to add to the list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:605 +msgid "Process the data export in multiple groups instead of in one large group that contains all employees. This helps to meaningfully differentiate the batches and makes processing more tenable, overall. The most common ways to group employees is by department, or by wage type (hourly or salaried)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:610 +msgid "Select the employees to add to the list by ticking the box to the left of their name. Once all desired employees have been selected, click the :guilabel:`Select` button in the lower-left corner, and the employees appear in the list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:614 +msgid "To create the CSV file, click the :guilabel:`Generate` button in the top-left corner." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:619 +msgid "ACH - electronic transfers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:621 +msgid "Automated Clearing House (ACH) payments are a modern way to transfer funds electronically between bank accounts, replacing traditional paper-based methods. |ACH| payments are commonly used for direct deposits, bill payments, and business transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:626 +msgid "Receive ACH payments: payment provider integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:628 +msgid "|ACH| payments are supported by *Authorize.net* and *Stripe* payment integrations in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:631 +msgid ":ref:`Setting up Authorize.net for ACH payments (Odoo) `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:632 +msgid "`Authorize.net's ACH payment processing for small businesses documentation `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:634 +msgid ":doc:`Setting up Stripe for ACH payments (Odoo) <../payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:635 +msgid "`Stripe's ACH Direct Debit documentation `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:640 +msgid "Send payments: NACHA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:642 +msgid "Odoo can generate a National Automated Clearing House Association (NACHA) compatible |ACH| file to send to a company's bank. For each individual *Bank* journal that the company wishes to pay vendors with, a |NACHA| configuration section needs to be filled out on the Odoo database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:649 +msgid "First, navigate to the :menuselection:`Accounting app --> Configuration --> Journals`. Open the bank journal and click into the :guilabel:`Outgoing Payments` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:-1 +msgid "NACHA (National Automated Clearing House Association) configuration settings on Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:657 +msgid "The following |NACHA| configuration information is normally provided by the company's financial institution once they have been approved to send payments via their account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:660 +msgid "Under the section labeled, :guilabel:`NACHA configuration` are the fields required to generate a |NACHA| compatible |ACH| file to send to a company's bank. First, enter the routing number of the financial institution in the field labeled, :guilabel:`Immediate Destination`. This information is widely available on the Internet and generally varies by bank location. This number is usually provided during the initial account setup." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:666 +msgid "Next, enter the registered name of the financial institution in the field called, :guilabel:`Destination`. This information will be provided by the bank or credit union." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:669 +msgid "Following the :guilabel:`Destination` field is the :guilabel:`Immediate Origin` field. Enter the 9-digit company ID or Employer Identification Number (EIN) into this field. This information is provided by the financial institution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:673 +msgid "Next, enter the :guilabel:`Company Identification` number, which is a 10-digit number made from combining the 9-digit company ID or Employer Identification Number (EIN), along with an additional number at the start of the sequence. This number is often a `1`. Check with the financial institution should this first number differ to verify that it is correct, as this number is provided for |ACH| approved accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:679 +msgid "Enter the :guilabel:`Originating DFI Identification` number next, which should contain an assigned 8-digit number from the financial institution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:683 +msgid "Enter the numerical values in this section *exactly* as the company's financial institution (e.g. bank or credit union) has provided them, otherwise risk failing a successful |NACHA| configuration in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:-1 +msgid "NACHA settings with the standard entry class code drop-down menu highlighted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:691 +msgid "There are two options for the next field: :guilabel:`Standard Entry Class Code`. Select the drop-down menu to the right of the field and pick either :guilabel:`Corporate Credit or Debit (CCD)` or :guilabel:`Prearranged Payment and Deposit (PPD)`. Again, this information will be provided by the financial institution. By default :guilabel:`Corporate Credit or Debit (CCD)` is selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:696 +msgid "Finally, the last option is for :guilabel:`Generated Balanced Files`. Tick the checkbox to the right of the field to enable :guilabel:`Generated Balanced Files`. Consult the company's accountant or financial advisor to make an informed decision for this field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:700 +msgid "Manually save the configuration by clicking the :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon, or navigate away from this screen to auto-save. The configuration is now complete." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:706 +msgid "Create batch payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:708 +msgid "Now, record each payment in Odoo using the |NACHA| payment method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:711 +msgid ":ref:`Register Payments in Odoo `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:714 +msgid "Be aware of the cut-off time for same-day payments. Either the file needs to have a future date associated with each payment or the file needs to be sent prior to the cut-off, if the dates included in it match today's date. Consult the financial institution for the exact cut-off time for their processing of same-day payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:719 +msgid "Once all the payments to be included in the |NACHA| |ACH| file have been made, a batch payment needs to be made from the :icon:`fa-cog` :guilabel:`Action` menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:722 +msgid "To create the batch payments, access the payments page, by navigating to :menuselection:`Accounting --> Vendors --> Payments`. Select all the payments that should be included in the |NACHA| |ACH| file, by ticking the checkboxes to the far-left of the rows." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:-1 +msgid "On the payments screen, the action menu is highlighted with create a batch payment\n" +"selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:732 +msgid "All payments in the batch must share the same payment method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:734 +msgid "Next, navigate to the batched payment (:menuselection:`Accounting --> Vendors --> Batch Payments`). Click into the payment just created and then click into the :guilabel:`Exported File` tab. The generated file is listed with the :guilabel:`Generation Date`. Click the :icon:`fa-download` :guilabel:`(download)` button to download the file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:-1 +msgid "The exported file tab highlighted in the batch payment with the download circled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:743 +msgid "If any adjustments need to be made, click the :guilabel:`Re-generate Export File` button to recreate a new |NACHA| |ACH| file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:747 +msgid ":doc:`../accounting/payments/batch`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:748 +msgid ":doc:`Europe's direct debiting <../accounting/payments/batch_sdd>`" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/vietnam.rst:3 msgid "Vietnam" msgstr "" @@ -29707,51 +31037,51 @@ msgstr "" msgid "After **30 days**, the transaction is **voided automatically** by Authorize.Net." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:54 +#: ../../content/applications/finance/payment_providers/authorize.rst:56 msgid "ACH payments (USA only)" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:56 +#: ../../content/applications/finance/payment_providers/authorize.rst:58 msgid ":abbr:`ACH (automated clearing house)` is an electronic funds transfer system used between bank accounts in the United States." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:62 +#: ../../content/applications/finance/payment_providers/authorize.rst:64 msgid "To give customers the possibility to pay using ACH, `sign up for Authorize.Net eCheck's service `_. Once eCheck is activated, duplicate the previously configured Authorize.Net payment provider on Odoo by going to :menuselection:`Accounting --> Configuration --> Payment Providers --> Authorize.net`. Then, click the cog icon (:guilabel:`⛭`) and select :guilabel:`Duplicate`. Change the provider's name to differentiate both versions (e.g., `Authorize.net - Banks`)." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:69 +#: ../../content/applications/finance/payment_providers/authorize.rst:71 msgid "When ready, change the provider's :guilabel:`State` to :guilabel:`Enabled` for a regular account or :guilabel:`Test Mode` for a sandbox account." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:73 +#: ../../content/applications/finance/payment_providers/authorize.rst:75 msgid "Import an Authorize.Net statement" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:76 +#: ../../content/applications/finance/payment_providers/authorize.rst:78 msgid "Export from Authorize.Net" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:82 +#: ../../content/applications/finance/payment_providers/authorize.rst:84 msgid "`Download the Excel import template `_" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:84 +#: ../../content/applications/finance/payment_providers/authorize.rst:86 msgid "To export a statement:" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:86 +#: ../../content/applications/finance/payment_providers/authorize.rst:88 msgid "Log in to Authorize.Net." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:87 +#: ../../content/applications/finance/payment_providers/authorize.rst:89 msgid "Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement Statement`." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:88 +#: ../../content/applications/finance/payment_providers/authorize.rst:90 msgid "Define an export range using an *opening* and *closing* batch settlement. All transactions within the two batch settlements will be exported to Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:90 +#: ../../content/applications/finance/payment_providers/authorize.rst:92 msgid "Select all transactions within the desired range, copy them, and paste them into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import template `." msgstr "" @@ -29763,75 +31093,75 @@ msgstr "" msgid "Settlement batch of an Authorize.Net statement" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:103 +#: ../../content/applications/finance/payment_providers/authorize.rst:105 msgid "In this case, the first batch (01/01/2021) of the year belongs to the settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:106 +#: ../../content/applications/finance/payment_providers/authorize.rst:108 msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:108 +#: ../../content/applications/finance/payment_providers/authorize.rst:110 msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:109 +#: ../../content/applications/finance/payment_providers/authorize.rst:111 msgid "Under the :guilabel:`Settlement Date` section, select the previously used range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:` fields and click :guilabel:`Search`." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:111 +#: ../../content/applications/finance/payment_providers/authorize.rst:113 msgid "When the list has been generated, click :guilabel:`Download to File`." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:112 +#: ../../content/applications/finance/payment_providers/authorize.rst:114 msgid "In the pop-up window, select :guilabel:`Expanded Fields with CAVV Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and click :guilabel:`Submit`." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:114 +#: ../../content/applications/finance/payment_providers/authorize.rst:116 msgid "Open the text file, select :guilabel:`All`, copy the data, and paste it into the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template `." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:116 +#: ../../content/applications/finance/payment_providers/authorize.rst:118 msgid "Transit lines are automatically filled in and updated in the :guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets of the :ref:`Excel import template `. Make sure all entries are present, and **if not**, copy the formula from previously filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` sheets and paste it into the empty lines." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:123 +#: ../../content/applications/finance/payment_providers/authorize.rst:125 msgid "To get the correct closing balance, **do not remove** any line from the Excel sheets." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:126 +#: ../../content/applications/finance/payment_providers/authorize.rst:128 msgid "Import into Odoo" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:128 +#: ../../content/applications/finance/payment_providers/authorize.rst:130 msgid "To import the data into Odoo:" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:130 +#: ../../content/applications/finance/payment_providers/authorize.rst:132 msgid "Open the :ref:`Excel import template `." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:131 +#: ../../content/applications/finance/payment_providers/authorize.rst:133 msgid "Copy the data from the :guilabel:`transit for report 2` sheet and use *paste special* to only paste the values in the :guilabel:`Odoo Import to CSV` sheet." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:133 +#: ../../content/applications/finance/payment_providers/authorize.rst:135 msgid "Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are chargeback entries without any reference number. As they cannot be imported as such, go to :menuselection:`Authorize.Net --> Account --> Statements --> eCheck.Net Settlement Statement`." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:136 +#: ../../content/applications/finance/payment_providers/authorize.rst:138 msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:137 +#: ../../content/applications/finance/payment_providers/authorize.rst:139 msgid "Copy the invoice description, paste it into the :guilabel:`Label` cell of the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the description." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:139 +#: ../../content/applications/finance/payment_providers/authorize.rst:141 msgid "If there are multiple invoices, add a line into the :ref:`Excel import template ` for each invoice and copy/paste the description into each respective :guilabel:`Label` line." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:144 +#: ../../content/applications/finance/payment_providers/authorize.rst:146 msgid "For **combined chargeback/returns** in the payouts, create a new line in the :ref:`Excel import template ` for each invoice." msgstr "" @@ -29839,31 +31169,31 @@ msgstr "" msgid "Chargeback description" msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:152 +#: ../../content/applications/finance/payment_providers/authorize.rst:154 msgid "Next, delete *zero transaction* and *void transaction* line items, and change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo Import to CSV` sheet to *Number*." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:154 +#: ../../content/applications/finance/payment_providers/authorize.rst:156 msgid "Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a Transaction` and search again for the previously used batch settlements dates." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:156 +#: ../../content/applications/finance/payment_providers/authorize.rst:158 msgid "Verify that the batch settlement dates on eCheck.Net match the related payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo Import to CSV`." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:158 +#: ../../content/applications/finance/payment_providers/authorize.rst:160 msgid "If it does not match, replace the date with the one from eCheck.Net. Sort the column by *date*, and make sure the format is `MM/DD/YYYY`." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:160 +#: ../../content/applications/finance/payment_providers/authorize.rst:162 msgid "Copy the data - column headings included - from the :guilabel:`Odoo Import to CSV` sheet, paste it into a new Excel file, and save it using the CSV format." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:162 +#: ../../content/applications/finance/payment_providers/authorize.rst:164 msgid "Open the Accounting app, go to :menuselection:`Configuration --> Journals`, tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites --> Import records --> Load file`. Select the CSV file and upload it into Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/authorize.rst:167 +#: ../../content/applications/finance/payment_providers/authorize.rst:169 msgid "List of `eCheck.Net return codes `_" msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index ade57eb15..21c2689c0 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2345,22 +2345,22 @@ msgid "Email is not sent" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:15 -msgid "The first indicator showing that an email has not been sent is the presence of a red :guilabel:`✉️ (envelope)` icon, next to the date and time of the message, located in the chatter." +msgid "The first indicator showing that an email has not been sent is the presence of a red :icon:`fa-envelope` :guilabel:`(envelope)` icon, next to the date and time of the message, located in the chatter." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:-1 msgid "Red envelope icon displayed in chatter." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:22 +#: ../../content/applications/general/email_communication/faq.rst:23 msgid "Unsent emails also appear in the Odoo email queue. In :ref:`developer mode `, the email queue can be accessed by going to :menuselection:`Settings app --> Technical menu --> Email --> Emails`. Unsent emails appear in turquoise, while sent emails appear in grey." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:27 +#: ../../content/applications/general/email_communication/faq.rst:28 msgid "Common error messages" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:32 +#: ../../content/applications/general/email_communication/faq.rst:33 msgid "Daily limit reached" msgstr "" @@ -2368,83 +2368,83 @@ msgstr "" msgid "Warning in Odoo upon email limit reached." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:38 +#: ../../content/applications/general/email_communication/faq.rst:39 msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, or sometimes, per minute. This is the same for Odoo, which limits a customer's sending to prevent Odoo's email servers from being blacklisted." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:42 +#: ../../content/applications/general/email_communication/faq.rst:43 msgid "Here are the default limits for new databases:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:44 +#: ../../content/applications/general/email_communication/faq.rst:45 msgid "**200 emails per day** for Odoo Online and Odoo.sh databases with an active subscription." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:45 -msgid "**20 emails per day** for one-app free databases." -msgstr "" - #: ../../content/applications/general/email_communication/faq.rst:46 -msgid "**50 emails per day** for trial databases." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:47 -msgid "In the case of migration, the daily limit might be reset to 50 emails per day." +msgid "**50 emails per day** for one-app free and trial databases." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:49 -msgid "If the daily limit is reached:" +msgid "In a one-app free database, if the *Email Marketing* app is installed, the email limit is **20 emails per day**." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:51 -msgid "Contact the Odoo support team, who may increase the daily limit depending on the following factors:" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:54 -msgid "How many users are in the database?" +#: ../../content/applications/general/email_communication/faq.rst:53 +msgid "In the case of migration, the daily limit might be reset to 50 emails per day." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:55 +msgid "If the daily limit is reached:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:57 +msgid "Contact the Odoo support team, who may increase the daily limit, depending on the following factors:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:60 +msgid "How many users are in the database?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:61 msgid "Which apps are installed?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:56 +#: ../../content/applications/general/email_communication/faq.rst:62 msgid "The bounce rate: the percentage of email addresses that did not receive emails because they were returned by a mail server on its way to the final recipient." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:59 +#: ../../content/applications/general/email_communication/faq.rst:65 msgid "Use an external outgoing email server to be independent of Odoo's mail limit (refer to the corresponding :doc:`email documentation `)." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:62 +#: ../../content/applications/general/email_communication/faq.rst:68 msgid "Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the email. In :ref:`developer mode `, go to :menuselection:`Settings app --> Technical menu --> Email --> Emails`, then click the :guilabel:`Retry` button next to an unsent email." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:67 +#: ../../content/applications/general/email_communication/faq.rst:73 msgid "The daily email limit is comprehensive to the database. By default, any internal message, notification, logged note, etc. counts as an email in the daily limit if it notifies someone via email. This can be mitigated by receiving :ref:`notifications in Odoo `, instead of emails." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:73 +#: ../../content/applications/general/email_communication/faq.rst:79 msgid "SMTP error" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:75 -msgid "Simple Mail Transport Protocol (SMTP) error messages explain why an email wasn't transmitted successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email structure, and transmits data from messages over the Internet. The error messages generated by email services are helpful tools to diagnose and troubleshoot email problems." +#: ../../content/applications/general/email_communication/faq.rst:81 +msgid "*Simple Mail Transport Protocol (SMTP)* error messages explain why an email was not transmitted successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email structure, and transmits data from messages over the Internet. The error messages generated by email services are helpful tools to diagnose and troubleshoot email problems." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:81 +#: ../../content/applications/general/email_communication/faq.rst:87 msgid "This is an example of a 554 SMTP permanent delivery error: `554: delivery error: Sorry, your message to ------@yahoo.com cannot be delivered. This mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this line is a copy of the message.`" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:85 -msgid "The debug menu can be used to investigate SMTP sending issues from a database. To access the menu, :ref:`developer mode ` must be activated. Once activated, navigate to the :menuselection:`Debug Menu` in the top right of the menu bar (the :guilabel:`🐞 (bug)` icon), :menuselection:`Debug Menu --> Manage Messages`" +#: ../../content/applications/general/email_communication/faq.rst:91 +msgid "The debug menu can be used to investigate SMTP sending issues from a database. To access the menu, :ref:`developer mode ` **must** be activated. Once activated, navigate to the :menuselection:`Debug Menu` in the top-right of the menu bar (the :icon:`fa-bug` :guilabel:`(bug)` icon), and select :menuselection:`Debug Menu --> Manage Messages` from the resulting drop-down menu." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:90 +#: ../../content/applications/general/email_communication/faq.rst:96 msgid "The :guilabel:`Manage Messages` menu opens a list of all the messages sent in a particular record. Within each message there is information on sending, including the type, and subtype, of the message." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:94 +#: ../../content/applications/general/email_communication/faq.rst:100 msgid "Other information includes to whom the message was sent, and whether Odoo received a bounce-back message from an email server." msgstr "" @@ -2452,152 +2452,152 @@ msgstr "" msgid "Manage messages menu option on the debug menu." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:102 +#: ../../content/applications/general/email_communication/faq.rst:108 msgid "A user must be on a view in Odoo that has a chatter in order for the :guilabel:`Manage Messages` menu option to appear." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:106 +#: ../../content/applications/general/email_communication/faq.rst:112 msgid "No error populated" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:108 +#: ../../content/applications/general/email_communication/faq.rst:114 msgid "Odoo is not always capable of providing information for the reason it failed. The different email providers implement a personalized policy of bounced emails, and it is not always possible for Odoo to interpret it correctly." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:112 +#: ../../content/applications/general/email_communication/faq.rst:118 msgid "If this is a recurring problem with the same client, or the same domain, do not hesitate to contact `Odoo Support `_ for help in finding a reason." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:116 +#: ../../content/applications/general/email_communication/faq.rst:122 msgid "One of the most common reasons for an email failing to send with no error message is related to :ref:`SPF ` and/or :ref:`DKIM ` configuration. Also, check to make sure the `mail.bounce.alias` is defined in the *system parameters*. Access system parameters in :ref:`developer mode ` by navigating to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:126 +#: ../../content/applications/general/email_communication/faq.rst:132 msgid "Email is sent late" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:128 -msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy in order to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode ` by going to :menuselection:`Settings app --> Technical menu --> Automation --> Scheduled Actions`." +#: ../../content/applications/general/email_communication/faq.rst:134 +msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode ` by going to :menuselection:`Settings app --> Technical menu --> Automation: Scheduled Actions`." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:-1 msgid "Email scheduled to be sent later." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:142 +#: ../../content/applications/general/email_communication/faq.rst:147 msgid "What is a **cron**? A cron is an action that Odoo runs in the background to execute particular code to complete a task." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:146 +#: ../../content/applications/general/email_communication/faq.rst:151 msgid "By default, the *Mass Mailing cron* runs every 60 minutes. This can be changed to no less than 5 minutes. However, running the action every 5 minutes would bog down the Odoo database (stress the system), so this is not recommended. To edit the mass mailing cron, select the scheduled action :guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary adjustments." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:151 +#: ../../content/applications/general/email_communication/faq.rst:156 msgid "Emails that are considered urgent (communication from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:155 +#: ../../content/applications/general/email_communication/faq.rst:160 msgid "Incoming emails" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:157 -msgid "When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It is the sending email client, who tries to contact a database, that will get a bounce-back message (most of the time a :guilabel:`550: mailbox unavailable` error message)." +#: ../../content/applications/general/email_communication/faq.rst:162 +msgid "When there is an issue with incoming emails, there might not be an indication in Odoo. It is the sending email client, who tries to contact a database, that gets a bounce-back message (most of the time it is a :guilabel:`550: mailbox unavailable` error message)." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:162 +#: ../../content/applications/general/email_communication/faq.rst:167 msgid "Email is not received" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:164 +#: ../../content/applications/general/email_communication/faq.rst:169 msgid "The steps that should be taken depend on the Odoo platform where the database is hosted." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:166 +#: ../../content/applications/general/email_communication/faq.rst:171 msgid "**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:168 +#: ../../content/applications/general/email_communication/faq.rst:173 msgid "Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Failure to send can also be seen by logs that indicate that the message tried to send repeatedly. Logs will show every action to the email servers from the database." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:174 +#: ../../content/applications/general/email_communication/faq.rst:179 msgid "The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh dashboard) of an Odoo.sh database contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM (UTC)." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:179 +#: ../../content/applications/general/email_communication/faq.rst:184 msgid "The two most recent days (today and yesterday) are not compressed, while the older ones are, in order to save space. The naming of the files for today and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:183 +#: ../../content/applications/general/email_communication/faq.rst:188 msgid "For the following days, they are named with their dates, and then compressed. Use the command :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:187 +#: ../../content/applications/general/email_communication/faq.rst:192 msgid "For more information on logs and how to access them via the Odoo.sh dashboard, see :ref:`this administration documentation `." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:190 +#: ../../content/applications/general/email_communication/faq.rst:195 msgid "For more information on accessing logs via the command line visit :ref:`this developer documentation `." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:193 +#: ../../content/applications/general/email_communication/faq.rst:198 msgid "**Odoo Online** users won't have access to the logs. However `Odoo Support `_ can be contacted if there is a recurring issue with the same client or domain." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:198 +#: ../../content/applications/general/email_communication/faq.rst:203 msgid "Get help from Odoo support" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:200 +#: ../../content/applications/general/email_communication/faq.rst:205 msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful when reaching out to the Odoo Support team about an issue:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:203 +#: ../../content/applications/general/email_communication/faq.rst:208 msgid "Send a copy of the email headers. The `.EML` file (or **headers**) of the email is the file format containing all the technical information required for an investigation. The documentation from the email provider might explain how to access the EML file/header files. Once the headers of the email are obtained, adding it into the Odoo Support ticket is the most efficient way for the Odoo Support team to investigate." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:210 +#: ../../content/applications/general/email_communication/faq.rst:215 msgid "`Gmail documentation on headers `_" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:211 +#: ../../content/applications/general/email_communication/faq.rst:216 msgid "`Outlook documentation on headers `_" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:214 +#: ../../content/applications/general/email_communication/faq.rst:219 msgid "Explain the exact flow that is being followed to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:217 +#: ../../content/applications/general/email_communication/faq.rst:222 msgid "Is this a notification message from a reply being received in Odoo?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:218 +#: ../../content/applications/general/email_communication/faq.rst:223 msgid "Is this a message being sent from the Odoo database?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:219 +#: ../../content/applications/general/email_communication/faq.rst:224 msgid "Is there an incoming email server being used, or is the email somehow being redirected?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:220 +#: ../../content/applications/general/email_communication/faq.rst:225 msgid "Is there an example of an email that has been correctly forwarded?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:222 +#: ../../content/applications/general/email_communication/faq.rst:227 msgid "Provide answers to the following questions:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:224 +#: ../../content/applications/general/email_communication/faq.rst:229 msgid "Is it a generic issue, or is it specific to a use case? If specific to a use case, which one exactly?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:226 +#: ../../content/applications/general/email_communication/faq.rst:231 msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database, and display the :ref:`red envelope `." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:230 -msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`. Then select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't already set." +#: ../../content/applications/general/email_communication/faq.rst:235 +msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters: System Parameters`. Then, select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it is not already set." msgstr "" #: ../../content/applications/general/email_communication/google_oauth.rst:3 diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index f039af3d2..4ff4fcef1 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -431,7 +431,7 @@ msgid "The feedback section for both employees and managers. The toggle buttons msgstr "" #: ../../content/applications/hr/appraisals.rst:332 -#: ../../content/applications/hr/recruitment.rst:748 +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:167 msgid "Skills tab" msgstr "" @@ -472,7 +472,7 @@ msgid "If managers want to leave notes that are only visible to other managers, msgstr "" #: ../../content/applications/hr/appraisals.rst:365 -#: ../../content/applications/hr/recruitment.rst:797 +#: ../../content/applications/hr/recruitment.rst:533 msgid "Schedule a meeting" msgstr "" @@ -569,106 +569,13 @@ msgid "If no meetings are scheduled, the :guilabel:`Meeting` smart button reads msgstr "" #: ../../content/applications/hr/appraisals.rst:440 -#: ../../content/applications/hr/attendances.rst:433 -#: ../../content/applications/hr/frontdesk.rst:210 -#: ../../content/applications/hr/payroll/reporting.rst:3 -#: ../../content/applications/hr/referrals.rst:444 -#: ../../content/applications/hr/time_off.rst:830 -msgid "Reporting" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:442 -msgid "The *Appraisals* application tracks two metrics across two different reports: an :ref:`appraisal analysis `, and a :ref:`skills evolution `." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:448 -msgid "Appraisal analysis" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:450 -msgid "To access the *Appraisal Analysis* report, navigate to :menuselection:`Appraisals application --> Reporting --> Appraisal Analysis`. This displays a report of all the appraisals in the database, highlighted in different colors to represent their status." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:454 -msgid "Appraisals in yellow are completed, appraisals in orange are in-progress (the appraisal is confirmed, but not completed), and appraisals in gray are scheduled (according to the :ref:`appraisals/appraisal-plan`), but have not been confirmed yet." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:458 -msgid "The report displays the whole current year, by default, grouped by department." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:460 -msgid "To change the calendar view presented, change the date settings in the top-left of the report. The options to display are :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, and :guilabel:`Year`. Use the arrows to move forward or backward in time." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:464 -msgid "At any point, click the :guilabel:`Today` button to present the calendar to include today's date in the view." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:467 -msgid "The report can have other filters and groupings set in the :guilabel:`Search...` bar at the top." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "A report showing all the appraisals for the Appraisal Analysis report." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:476 -msgid "Skills evolution" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:478 -msgid "To access the *Skills Evolution* report, navigate to :menuselection:`Appraisals application --> Reporting --> Skills Evolution`. This displays a report of all skills, grouped by employee." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:481 -msgid "All the lines of the report are collapsed, by default. To view the details of a line, click on a line to expand the data." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:484 -msgid "Each skill has the following information listed:" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:486 -msgid ":guilabel:`Employee`: name of the employee." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:487 -msgid ":guilabel:`Skill Type`: the category the skill falls under." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:488 -msgid ":guilabel:`Skill`: the specific, individual skill." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:489 -msgid ":guilabel:`Previous Skill Level`: the level the employee had previously achieved for the skill." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:490 -msgid ":guilabel:`Previous Skill Progress`: the previous percentage of competency achieved for the skill (based on the :guilabel:`Skill Level`)." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:492 -msgid ":guilabel:`Current Skill Level`: the current level the employee has achieved for the skill." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:493 -msgid ":guilabel:`Current Skill Progress`: the current percentage of competency achieved for the skill." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:494 -msgid ":guilabel:`Justification`: any notes entered on the skill explaining the progress." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "A report showing all the skills grouped by employee." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:501 msgid ":doc:`appraisals/goals`" msgstr "" +#: ../../content/applications/hr/appraisals.rst:441 +msgid ":doc:`appraisals/reporting`" +msgstr "" + #: ../../content/applications/hr/appraisals/goals.rst:3 msgid "Goals" msgstr "" @@ -781,6 +688,177 @@ msgstr "" msgid "To mark a goal as `Done` from the goal card itself, click on a goal card to open that goal's form. Then, click the :guilabel:`Mark as Done` button in the top-left of the form. When clicked, a green :guilabel:`Done` banner appears in the top-right corner of the goal form." msgstr "" +#: ../../content/applications/hr/appraisals/reporting.rst:3 +#: ../../content/applications/hr/attendances.rst:433 +#: ../../content/applications/hr/frontdesk.rst:210 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals.rst:329 +#: ../../content/applications/hr/time_off.rst:595 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:5 +msgid "In Odoo's *Appraisals* app, two metrics are tracked as appraisals are completed: an :ref:`appraisal analysis `, and a :ref:`skills evolution `." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:11 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:13 +msgid "To access the *Appraisal Analysis* report, navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:16 +msgid "On the :guilabel:`Appraisal Analysis` page, there is a report of all the appraisals in the database, highlighted in different colors to represent their status." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:19 +msgid "Appraisals in yellow are *Done*, appraisals in orange are in progress (the *Appraisal Sent*, but not completed), appraisals in red have been *Cancelled*, and appraisals in gray are scheduled *To Start* (according to the :ref:`appraisals/appraisal-plan`), but have not been confirmed yet." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:23 +msgid "The report displays the current year, in a default Gantt view, and is grouped by department." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:25 +msgid "To change the period of time that is presented by default, adjust the date settings in the top-left of the report. The options to display are :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, and :guilabel:`Year`. Use the arrows to move forward or backward in time." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:29 +msgid "At any point, click the :guilabel:`Today` button to have the Gantt view include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:32 +#: ../../content/applications/hr/appraisals/reporting.rst:93 +msgid "The report can have other :ref:`filters ` and :ref:`groupings ` set in the :guilabel:`Search...` bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:40 +msgid "Appraisals that have been cancelled appear in red on the :guilabel:`Appraisal Analysis` report, but there is no preconfigured filter to show only cancelled appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:43 +msgid "To view only cancelled appraisals, click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:46 +msgid "Next, click :guilabel:`Add Custom Filter` in the :guilabel:`Filters` section, and a :guilabel:`Add Custom Filter` pop up window loads." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:49 +msgid "Using the drop-down menu, select :guilabel:`Status` for the first drop-down, then select :guilabel:`Cancelled` for the third drop-down field. Click the :guilabel:`Add` button, and only appraisals that have been cancelled appear." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:0 +msgid "The Custom Filter pop-up with the parameters set to only show cancelled appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:60 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:62 +msgid "To access the *Skills Evolution* report, navigate to :menuselection:`Appraisals app --> Reporting --> Skills Evolution`. The :guilabel:`Appraisal Skills Report` page displays a report of all skills, grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:66 +msgid "Skill levels are **only** updated after an appraisal is marked as done. Any skill level changes from any ongoing appraisals that have **not** been finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:69 +msgid "All the lines of the report are collapsed, by default. To view the details of a line, click anywhere on a line to expand the data." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:72 +msgid "Each skill has the following information listed:" +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:74 +msgid ":guilabel:`Employee`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:75 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:76 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:77 +msgid ":guilabel:`Previous Skill Level`: the level the employee had previously achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:78 +msgid ":guilabel:`Previous Skill Progress`: the previous percentage of competency achieved for the skill (based on the :guilabel:`Skill Level`)." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:80 +msgid ":guilabel:`Current Skill Level`: the current level the employee has achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:81 +msgid ":guilabel:`Current Skill Progress`: the current percentage of competency achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:82 +msgid ":guilabel:`Justification`: any notes entered on the skill, explaining the progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:84 +msgid "The color of the skill text indicates any changes from the previous appraisal. Skill levels that have increased since the last appraisal appear in green as an *Improvement*, skill levels that have not changed appear in black as *No Change*, and skills that have regressed appear in red as *Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:97 +msgid "Since the :guilabel:`Appraisal Skills Report` organizes all skills by employee, it can be difficult to find employees with a specific skill at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:101 +msgid "To view only employees with an :guilabel:`Expert` level of the :guilabel:`Javascript` skill, first remove any active filters in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:104 +msgid "Next, click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon in the :guilabel:`Search...` bar, then click :guilabel:`Add Custom Filter` in the :guilabel:`Filters` section to load an :guilabel:`Add Custom Filter` pop up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:108 +msgid "Using the drop-down menu, select :guilabel:`Skill` for the first drop-down, then select :guilabel:`Javascript` for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:111 +msgid "Next, click the :guilabel:`New Rule` button, and another line appears. In this second line, select :guilabel:`Current Skill Level` for the first drop-down, then select :guilabel:`Expert` for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:115 +msgid "After the :guilabel:`New Rule` button is clicked, the word :guilabel:`any` in the sentence :guilabel:`Match any of the following rules:` changes from plain text into a drop-down menu. Click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon after the word :guilabel:`any`, and select :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:120 +msgid "Finally, click the :guilabel:`Add` button, and only employees that have an :guilabel:`Expert` level for the skill :guilabel:`Javascript` appear." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:0 +msgid "The Custom Filter pop-up with the parameters set to only show employees with expert\n" +"level for the skill javascript." +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:129 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/reporting.rst:130 +msgid ":doc:`../../essentials/search`" +msgstr "" + #: ../../content/applications/hr/attendances.rst:5 msgid "Attendances" msgstr "" @@ -1034,7 +1112,7 @@ msgid "The goodbye message with all the employee's check out information." msgstr "" #: ../../content/applications/hr/attendances.rst:271 -#: ../../content/applications/hr/time_off.rst:681 +#: ../../content/applications/hr/time_off.rst:551 msgid "Overview" msgstr "" @@ -3543,9 +3621,9 @@ msgstr "" #: ../../content/applications/hr/fleet/service.rst:380 #: ../../content/applications/hr/frontdesk.rst:33 -#: ../../content/applications/hr/lunch.rst:230 +#: ../../content/applications/hr/lunch/products.rst:12 #: ../../content/applications/hr/payroll.rst:894 -#: ../../content/applications/hr/payroll/work_entries.rst:54 +#: ../../content/applications/hr/payroll/work_entries.rst:56 #: ../../content/applications/hr/time_off.rst:222 msgid "Enter the following information on the form:" msgstr "" @@ -4434,127 +4512,51 @@ msgid "A list view of the locations with the new button highlighted." msgstr "" #: ../../content/applications/hr/lunch.rst:221 -msgid "Products" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:223 -msgid "Before any orders can be placed, the individual products that are being offered must be configured, as no products are pre-configured in Odoo, by default." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:226 -msgid "First, navigate to the products page by going to :menuselection:`Lunch app --> Configuration: Products`. Next click the :guilabel:`New` button in the top-left corner and a blank product form loads." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:232 -msgid ":guilabel:`Product Name*`: enter the name for the product." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:233 -msgid ":guilabel:`Product Category*`: using the drop-down menu, select the category this product falls under." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:235 -msgid ":guilabel:`Vendor*`: using the drop-down menu, select the vendor that supplies this product." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:236 -msgid ":guilabel:`Price`: enter the price for the product. The currency is determined by the localization of the company." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:238 -msgid ":guilabel:`Description`: enter a description of the product in this field. This description appears beneath the product photo when users are viewing the options for the day." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:240 -msgid ":guilabel:`New Until`: using the calendar popover, select the date that the product will no longer be labeled as new. Until this date, a green `New` tag appears on the product." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:242 -msgid ":guilabel:`Company`: if the product should only be available to a specific company, select it from the drop-down menu. If this field is left blank, this product is available for all companies in the database." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:245 -msgid "Image: hover over the image box in the top-right corner of the form, and click the :guilabel:`✏️ (pencil)` edit icon that appears. A file explorer pop-up window appears. Navigate to the image, then click :guilabel:`Open`." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:249 -msgid "(*) indicates required field." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:-1 -msgid "A product form filled out for a nine inch pizza." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:256 -msgid "Product categories" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:258 -msgid "Product categories are a way to organize the offerings in the *Lunch* app, and allows for users to quickly filter the offerings when reviewing the menu for the day." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:261 -msgid "To add or modify categories, navigate to :menuselection:`Lunch app --> Configuration: Product Categories`. The available categories appear in a list view. In the *Lunch* app, there are four default categories : :guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and :guilabel:`Drinks`." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:266 -msgid "To add a new category, click the :guilabel:`New` button in the top-left corner, and a blank category form loads. Enter a name in the :guilabel:`Product Category` field. If the category is company-specific and should only appear for a certain company, select the :guilabel:`Company` from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:271 -msgid "If desired, add a photo for the category. Hover over the image box in the top-right, and click the :guilabel:`✏️ (pencil)` edit icon that appears. A file explorer pop-up window appears. Navigate to the image, then click :guilabel:`Open`." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:-1 -msgid "The category form, with the fields filled out for a Soup category." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:280 -#: ../../content/applications/hr/referrals.rst:392 +#: ../../content/applications/hr/referrals/alerts.rst:3 msgid "Alerts" msgstr "" -#: ../../content/applications/hr/lunch.rst:282 +#: ../../content/applications/hr/lunch.rst:223 msgid "It is possible to set up alerts that can either be displayed in the *Lunch* app, or be sent to specific employees via the *Discuss* app." msgstr "" -#: ../../content/applications/hr/lunch.rst:285 +#: ../../content/applications/hr/lunch.rst:226 msgid "No alerts are pre-configured by default. To set up an alert, navigate to :menuselection:`Lunch app --> Configuration: Alerts`. Click the :guilabel:`New` button in the top-left corner and a blank lunch alert form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/lunch.rst:289 +#: ../../content/applications/hr/lunch.rst:230 msgid ":guilabel:`Alert Name`: enter a name for the alert. This should be short and descriptive, such as `New Lunch Vendor` or `Order by 11`. This field is **required**." msgstr "" -#: ../../content/applications/hr/lunch.rst:291 +#: ../../content/applications/hr/lunch.rst:232 msgid ":guilabel:`Display`: select whether the alert is visible in the *Lunch* app (:guilabel:`Alert in app)` or sent to employees via the *Discuss* app in a chat window (:guilabel:`Chat notification`)." msgstr "" -#: ../../content/applications/hr/lunch.rst:294 +#: ../../content/applications/hr/lunch.rst:235 msgid ":guilabel:`Recipients`: this field only appears if :guilabel:`Chat notification` is selected for the :guilabel:`Display` option. Select who receives the chat alert. The options are: :guilabel:`Everyone`, :guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered last month`, or :guilabel:`Employee who ordered last year`." msgstr "" -#: ../../content/applications/hr/lunch.rst:299 +#: ../../content/applications/hr/lunch.rst:240 msgid ":guilabel:`Location`: select the locations the alert should appear for from the drop-down menu. Multiple locations can be selected. This field is **required**, therefore, if the alert applies to all locations, select all the locations from the drop-down menu." msgstr "" -#: ../../content/applications/hr/lunch.rst:302 +#: ../../content/applications/hr/lunch.rst:243 msgid ":guilabel:`Show Until`: if the alert should expire on a specific date, select the date from the calendar picker." msgstr "" -#: ../../content/applications/hr/lunch.rst:304 +#: ../../content/applications/hr/lunch.rst:245 msgid ":guilabel:`Active`: this option is on (appears green) by default. To turn off the alert, click the toggle so that it no longer appears green." msgstr "" -#: ../../content/applications/hr/lunch.rst:306 +#: ../../content/applications/hr/lunch.rst:247 msgid ":guilabel:`Message`: Enter the alert message in this field. This field is **required**." msgstr "" -#: ../../content/applications/hr/lunch.rst:307 +#: ../../content/applications/hr/lunch.rst:248 msgid ":guilabel:`Notification Time`: select the days of the week the alert should be sent. By default, all seven days are active. Click on a checkbox to change the setting from active to inactive." msgstr "" -#: ../../content/applications/hr/lunch.rst:310 +#: ../../content/applications/hr/lunch.rst:251 msgid "If :guilabel:`Chat notification` was selected for the :guilabel:`Display` option, a :guilabel:`Time` field also appears. Enter the time the chat message should be sent. Next, select if the time is either :guilabel:`AM` or :guilabel:`PM` using the drop-down menu to the right of the :guilabel:`Time` field." msgstr "" @@ -4563,15 +4565,19 @@ msgid "An alert form with all of the information filled out for a chat alert sen "asking employees to submit orders by 11:30 AM." msgstr "" -#: ../../content/applications/hr/lunch.rst:321 +#: ../../content/applications/hr/lunch.rst:262 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:263 msgid ":doc:`lunch/orders`" msgstr "" -#: ../../content/applications/hr/lunch.rst:322 +#: ../../content/applications/hr/lunch.rst:264 msgid ":doc:`lunch/user-accounts`" msgstr "" -#: ../../content/applications/hr/lunch.rst:323 +#: ../../content/applications/hr/lunch.rst:265 msgid ":doc:`lunch/management`" msgstr "" @@ -5053,6 +5059,86 @@ msgid "The My Account dashboard with the entry for adding funds to the user's lu "highlighted." msgstr "" +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "Odoo's *Lunch* app does **not** come with any products preconfigured. The individual products being offered must first be configured before orders can be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "To add and configure products for the *Lunch* app, navigate to :menuselection:`Lunch app --> Configuration --> Products`. Next, click the :guilabel:`New` button in the top-left corner, and a blank product form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid ":guilabel:`Product Name`: enter the name for the product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid ":guilabel:`Product Category`: using the drop-down menu, select the :ref:`category ` this product falls under. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid ":guilabel:`Vendor`: using the drop-down menu, select the vendor that supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid ":guilabel:`Price`: enter the price for the product. The currency is determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid ":guilabel:`Description`: enter a description of the product in this field. This description appears beneath the product photo when users are viewing the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid ":guilabel:`New Until`: using the calendar popover, select the date on which the product is no longer labeled as new. Until this date, a green `New` tag appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid ":guilabel:`Company`: if the product should only be available to a specific company, select it from the drop-down menu. If this field is left blank, this product is available for all companies in the database." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:28 +msgid "**Image**: hover over the image box in the top-right corner of the form, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file explorer pop-up window appears. Navigate to the image, then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:41 +msgid "Product categories organize the offerings in the *Lunch* app, and allows users to quickly filter them when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:44 +msgid "To add or modify categories, navigate to :menuselection:`Lunch app --> Configuration: Product Categories`. The available categories appear in a list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:47 +msgid "In the *Lunch* app, there are four default categories: :guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:50 +msgid "To add a new category, click the :guilabel:`New` button in the top-left corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:53 +msgid "Enter a name in the :guilabel:`Product Category` field. If the category is company-specific and should only appear for a certain company, select the :guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:56 +msgid "If desired, add a photo for the category. Hover over the image box in the top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. This opens a file explorer pop-up window. Navigate to the image, then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + #: ../../content/applications/hr/lunch/user-accounts.rst:3 msgid "Manage user accounts" msgstr "" @@ -5377,7 +5463,6 @@ msgid "Salary information tab" msgstr "" #: ../../content/applications/hr/payroll.rst:163 -#: ../../content/applications/hr/payroll/contracts.rst:104 msgid ":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage` from the drop-down menu." msgstr "" @@ -5496,7 +5581,7 @@ msgstr "" #: ../../content/applications/hr/payroll.rst:265 #: ../../content/applications/hr/payroll.rst:730 -#: ../../content/applications/hr/payroll/contracts.rst:43 +#: ../../content/applications/hr/payroll/contracts.rst:40 msgid "General information section" msgstr "" @@ -6149,7 +6234,7 @@ msgid ":guilabel:`Assigned to`: select the user the activity is automatically as msgstr "" #: ../../content/applications/hr/payroll.rst:806 -#: ../../content/applications/hr/payroll/contracts.rst:143 +#: ../../content/applications/hr/payroll/contracts.rst:163 msgid "Sign section" msgstr "" @@ -6355,7 +6440,7 @@ msgid ":doc:`payroll/reporting`" msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:5 -msgid "Every employee in Odoo is required to have a contract to be paid. A contract outlines the terms of an employee's job position, compensation, working hours, and any other details specific to their role." +msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, working hours, and any other details about their position." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:10 @@ -6363,203 +6448,238 @@ msgid "Contract documents (PDFs) are uploaded and organized using the *Documents msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:15 -msgid "To view the employee contracts, go to :menuselection:`Payroll app --> Contracts --> Contracts` from the top menu. All employee contracts are displayed in a default list view, grouped into four categories: :guilabel:`New`, :guilabel:`Running`, :guilabel:`Expired`, and :guilabel:`Cancelled`." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:19 -msgid "The default view has all categories collapsed. The number of contracts in each category is displayed next to the category name (example: `Running (20)`). To view the list of contracts under any category, click on the category, and the list expands downward, showing all contracts beneath it." +msgid "To view the employee contracts, go to the :menuselection:`Payroll app --> Contracts --> Contracts` from the top menu. All employee contracts, and their current contract status, are displayed in a Kanban view, by default. The Kanban view displays running contracts, contracts that require action, expired contracts, and cancelled contracts." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:-1 msgid "Contracts dashboard view showing running contracts and contracts with issues." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:28 +#: ../../content/applications/hr/payroll/contracts.rst:25 msgid "The list of contracts in the *Payroll* application matches the list of contracts in the *Employees* application." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:34 -msgid "Create new contracts" +#: ../../content/applications/hr/payroll/contracts.rst:30 +msgid "In order for an employee to be paid, an active contract is required. If a new contract is needed, click the :guilabel:`Create` button on the :guilabel:`Contracts` dashboard. A contract form appears where the information can be entered. Required fields are underlined in bold." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:36 -msgid "For an employee to be paid, an active contract is required. When a new contract is needed, click the :guilabel:`New` button on the :guilabel:`Contracts` dashboard. A contract form appears where the information can be entered." +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:45 +#: ../../content/applications/hr/payroll/contracts.rst:42 +#: ../../content/applications/hr/payroll/contracts.rst:91 msgid ":guilabel:`Contact Reference`: type in the name or title for the contract, such as `John Smith Contract`. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:47 +#: ../../content/applications/hr/payroll/contracts.rst:44 msgid ":guilabel:`Employee`: using the drop-down menu, select the employee that the contract applies to." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:48 +#: ../../content/applications/hr/payroll/contracts.rst:45 msgid ":guilabel:`Contract Start Date`: the date the contract starts. To choose a date, click the drop-down menu, navigate to the correct month and year with the :guilabel:`< > (arrow)` icons, then click on the desired date. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:51 +#: ../../content/applications/hr/payroll/contracts.rst:48 msgid ":guilabel:`Contract End Date`: if the contract has a specific end date, click the drop-down menu, navigate to the correct month and year with the :guilabel:`< > (arrow)` icons, then click on the desired date." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:54 +#: ../../content/applications/hr/payroll/contracts.rst:51 +#: ../../content/applications/hr/payroll/contracts.rst:105 msgid ":guilabel:`Working Schedule`: select one of the working schedules from the drop-down menu. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:58 +#: ../../content/applications/hr/payroll/contracts.rst:55 msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working schedules for the selected company. To modify or add to this list, go to :menuselection:`Payroll app --> Configuration --> Working Schedules`. Click :guilabel:`New`, and create a new working schedule, or click on an existing working schedule and make edits." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:63 +#: ../../content/applications/hr/payroll/contracts.rst:60 msgid ":guilabel:`Work Entry Source`: select how the :doc:`work entries ` are generated. This field is **required**. Click the radio button next to the desired selection. The options are:" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:66 +#: ../../content/applications/hr/payroll/contracts.rst:63 msgid ":guilabel:`Working Schedule`: work entries are generated based on the selected :guilabel:`Working Schedule`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:68 +#: ../../content/applications/hr/payroll/contracts.rst:65 msgid ":guilabel:`Attendances`: work entries are generated based on the employee's check-in records in the *Attendances* application. (This requires the *Attendances* application)." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:70 +#: ../../content/applications/hr/payroll/contracts.rst:67 msgid ":guilabel:`Planning`: work entries are generated based on the planned schedule for the employee from the *Planning* application. (This requires the *Planning* application)." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:73 +#: ../../content/applications/hr/payroll/contracts.rst:70 msgid ":guilabel:`Salary Structure Type`: select one of the salary structure types from the drop-down menu. The default salary structure types are :guilabel:`Employee` or :guilabel:`Worker`. A :ref:`new salary structure type ` can be created, if needed." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:76 +#: ../../content/applications/hr/payroll/contracts.rst:73 msgid ":guilabel:`Department`: select the department the contract applies to from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:77 +#: ../../content/applications/hr/payroll/contracts.rst:74 msgid ":guilabel:`Job Position`: select the specific job position the contract applies to from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:81 +#: ../../content/applications/hr/payroll/contracts.rst:78 msgid "If the selected :guilabel:`Job Position` has a contract template linked to it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary Structure Type` changes to the one associated with that :guilabel:`Job Position`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:85 +#: ../../content/applications/hr/payroll/contracts.rst:82 msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:86 +#: ../../content/applications/hr/payroll/contracts.rst:83 msgid ":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, :guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or :guilabel:`Part-Time` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:94 +#: ../../content/applications/hr/payroll/contracts.rst:-1 msgid "New contract form to be filled in when creating a new contract, with required fields\n" "outlined in red." msgstr "" +#: ../../content/applications/hr/payroll/contracts.rst:93 +msgid ":guilabel:`Employee`: name of the employee the contract applies to." +msgstr "" + #: ../../content/applications/hr/payroll/contracts.rst:94 -msgid "The general information section filled out, with the required fields highlighted in red." +msgid ":guilabel:`Contract Start Date`: the date the contract starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then clicking on the desired date. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:97 -msgid "Salary Information tab" -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:99 -msgid "This section is where the specific salary details are defined. This section is country-specific, so depending on where the company is located, these fields may vary." +#: ../../content/applications/hr/payroll/contracts.rst:98 +msgid ":guilabel:`Contract End Date`: the date the contract ends. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then clicking on the desired date. This field is **required**." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:102 -msgid "The following fields are universal and apply to all localizations:" +msgid ":guilabel:`Salary Structure Type`: select one of the salary structure types from the drop-down menu. The default salary structure types are :guilabel:`Employee` or :guilabel:`Worker`. A new salary structure type can be created by typing the name in the field. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:106 -msgid ":guilabel:`Schedule Pay`: select how often the employee is paid using the drop-down menu. Options are :guilabel:`Annually`, :guilabel:`Semi-annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, :guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, :guilabel:`Weekly`, or :guilabel:`Daily`." +#: ../../content/applications/hr/payroll/contracts.rst:107 +msgid ":guilabel:`Department`: the department the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:108 +msgid ":guilabel:`Job Position`: the specific job position the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:109 +msgid ":guilabel:`Wage on Payroll`: the amount to be paid to the employee each month." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:110 -msgid ":guilabel:`Wage`: enter the employee's gross wage. The metric for the :guilabel:`Wage` is based on what is selected for the :guilabel:`Schedule Pay`." +msgid ":guilabel:`Contract Type`: choose from :guilabel:`CDI`, :guilabel:`CDD`, or :guilabel:`PFI` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:113 +msgid ":guilabel:`CDI` is an open-ended contract with only a start date, but no end date." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:114 -msgid "If :guilabel:`Annually` is selected for the :guilabel:`Schedule Pay`, then the :guilabel:`Wage` field appears in a `$0.00/year` format. If the :guilabel:`Schedule Pay` is set to :guilabel:`Bi-weekly`, then the :guilabel:`Wage` field appears in a `$0.00/two weeks` format." +msgid ":guilabel:`CDD` is a contract with both a start date and an end date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:115 +msgid ":guilabel:`PFI` is a Belgian-specific contract used when hiring employees that need training, and covers the training period specifically." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:118 +msgid ":guilabel:`HR Responsible`: if there is a specific person in HR that is responsible for the contract, select the person from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:122 +msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working times for the selected :guilabel:`Company`. To modify or add to this list, go to :menuselection:`Payroll app --> Configuration --> Working Times`, and either :guilabel:`Create` a new working time, or click on an existing working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:127 msgid ":guilabel:`Yearly Cost (Real)`: this field automatically updates after the :guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This amount is the total yearly cost for the employer. This field can be modified. However, if this is modified, the :guilabel:`Wage` field updates, accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost (Real)` are correct if this field is modified." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:123 +#: ../../content/applications/hr/payroll/contracts.rst:132 msgid ":guilabel:`Monthly Cost (Real)`: this field automatically updates after the :guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This amount is the total monthly cost for the employer. This field **cannot** be modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:0 +#: ../../content/applications/hr/payroll/contracts.rst:-1 msgid "Optional tabs for a new contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:133 +#: ../../content/applications/hr/payroll/contracts.rst:142 msgid "Contract Details tab" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:135 -msgid "The contract details section allows for the addition and editing of a contract, and the ability to send the contract to the employee for approval and signatures." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:138 -msgid ":guilabel:`Contract Template`: select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the configuration menu, and stored in the *Documents* application." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:145 -msgid ":guilabel:`HR Responsible`: select the person who is responsible for validating the contract from the drop-down menu. This field is required." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:147 -msgid ":guilabel:`New Contract Document Template`: select a contract from the drop-down menu to be modified for this new employee contract. These documents are stored in the *Sign* application." +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "The :guilabel:`Contract Details` tab allows for the addition and editing of a contract, along with specifying which template to use when a new contract is created. These fields **must** be populated in order to create a new contract." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:149 -msgid ":guilabel:`Contract Update Document Template`: select a contract from the drop-down menu, if the employee has an existing contract that requires updating. These documents are stored in the *Sign* application." +msgid "To access the various contract template fields in the :guilabel:`Contract Details` tab, the *Salary Configurator* (`hr_contract_salary`) module **must** be :ref:`installed `." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:154 -msgid "The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, and :guilabel:`Contract Update Document Template` fields are only visible if the *Sign* application is installed, along with the `hr_contract_salary` and `hr_contract_salary_payroll` :doc:`modules <../../general/apps_modules>`. The *Sign* application is where the contract templates are stored. This application is required for an employee to sign any contract." +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "When the *Salary Configurator* module is installed, the *Salary Configurator - Holidays* and *Salary Configurator - Payroll* modules install, as well." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:161 -msgid "Accounting section" +#: ../../content/applications/hr/payroll/contracts.rst:156 +msgid "Once the modules are installed, the database reverts to the main dashboard." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:163 -msgid ":guilabel:`Analytic Account`: select the account the contract affects from the drop-down menu. It is recommended to check with the accounting department to ensure the correct account is selected." +#: ../../content/applications/hr/payroll/contracts.rst:158 +msgid ":guilabel:`Contract Template`: select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:165 +msgid ":guilabel:`HR Responsible`: select the person who is responsible for validating the contract from the drop-down menu. This field is required." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:167 -msgid "Part Time section" +msgid ":guilabel:`New Contract Document Template`: select a contract from the drop-down menu to be modified for this new employee contract. These documents are stored in the *Sign* application." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:169 -msgid ":guilabel:`Part Time`: tick this box if the employee is working part-time. When active, additional fields appear:" -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:172 -msgid ":guilabel:`% (Percentage)`: enter the percent of time the employee works as compared to a full-time employee." +msgid ":guilabel:`Contract Update Document Template`: select a contract from the drop-down menu, if the employee has an existing contract that requires updating. These documents are stored in the *Sign* application." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:174 -msgid ":guilabel:`Standard Calendar`: select the working hours that a typical full-time worker uses from the drop-down menu." +msgid "The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, and :guilabel:`Contract Update Document Template` fields are only visible if the *Sign* application is installed, along with the `hr_contract_salary` and `hr_contract_salary_payroll` :doc:`modules <../../general/apps_modules>`. The *Sign* application is where the contract templates are stored. This application is required for an employee to sign any contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:176 -msgid ":guilabel:`Part Time Work Entry Type`: select the work entry type that generates the balance of a full-time working schedule." +#: ../../content/applications/hr/payroll/contracts.rst:181 +msgid "Accounting section" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:180 -msgid "If a full-time employee works 40 hours a week, and the employee works 20, enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 hours). The employee generates twenty (20) hours of work entries under the work entry type `part-time`, and another twenty (20) hours of work entries under the work entry type `generic time off`, for a total of forty (40) hours worth of work entries." +#: ../../content/applications/hr/payroll/contracts.rst:183 +msgid ":guilabel:`Analytic Account`: select the account the contract affects from the drop-down menu. It is recommended to check with the accounting department to ensure the correct account is selected." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:187 -msgid "Notes section" +msgid "Part Time section" msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:189 +msgid ":guilabel:`Part Time`: tick this box if the employee is working part-time. When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:192 +msgid ":guilabel:`% (Percentage)`: enter the percent of time the employee works as compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:194 +msgid ":guilabel:`Standard Calendar`: select the working hours that a typical full-time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:196 +msgid ":guilabel:`Part Time Work Entry Type`: select the work entry type that generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:200 +msgid "If a full-time employee works 40 hours a week, and the employee works 20, enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 hours). The employee generates twenty (20) hours of work entries under the work entry type `part-time`, and another twenty (20) hours of work entries under the work entry type `generic time off`, for a total of forty (40) hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:207 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:209 msgid ":guilabel:`Notes`: a text field where any notes for the employee contract are entered for future reference." msgstr "" @@ -6567,201 +6687,213 @@ msgstr "" msgid "Contract details in optional tabs for a new contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:197 -msgid "Personal Documents tab" +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid ":guilabel:`Analytic Account`: this field allows a link between the contract and a specific analytic account for accounting purposes." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:199 -msgid "Once an :guilabel:`Employee` is selected in the :ref:`General Information section `, the :guilabel:`Personal Documents` tab appears." +#: ../../content/applications/hr/payroll/contracts.rst:218 +msgid ":guilabel:`Contract Template`: select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:202 -msgid "If any documents are needed to keep on file, add them in the :guilabel:`Personal Documents` tab. Depending on what other applications are installed, and what kind of benefits are enabled (and offered) to the employee, the various options to add a file varies. The :guilabel:`Image` option always appears, and is available by default." +#: ../../content/applications/hr/payroll/contracts.rst:220 +msgid ":guilabel:`New Contract Document Template`: select a contract from the drop-down menu to be modified for this new employee contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:207 -msgid "Click the :guilabel:`Upload your file` button next to the corresponding document, navigate to the file, then click :guilabel:`Open` to select the document and add it to the tab." +#: ../../content/applications/hr/payroll/contracts.rst:222 +msgid ":guilabel:`Contract Update Document Template`: select a contract from the drop-down menu, if the employee has an existing contract that requires updating." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:211 -msgid "Modifying contract templates" -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:213 -msgid "Contracts templates can be modified at any point when changes are needed." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:215 -msgid "To modify a contract template, refer to the :ref:`contract templates ` section of the main payroll documentation." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:219 -msgid "Salary attachments" -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:221 -msgid "Any automatic deductions or allocations for an employee, such as child support payments and wage garnishments, are referred to as a *salary attachment*. Navigate to :menuselection:`Payroll app --> Contracts --> Salary Attachments` to view a list of all the currently configured salary attachments." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:225 -msgid "Each salary attachment appears with all its relevant details displayed. The :guilabel:`Status` for each attachment is color-coded in the far right column." +#: ../../content/applications/hr/payroll/contracts.rst:224 +msgid ":guilabel:`Notes`: the notes field is a text field where any notes for the employee contract can be entered for future reference." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:228 -msgid "Currently running salary attachments have a :guilabel:`Status` of :guilabel:`Running`, and appear in green. Salary attachments that have been paid in-full, and are no longer active, have a :guilabel:`Status` of :guilabel:`Completed`, and appear in blue. Cancelled salary attachments have a :guilabel:`Status` of :guilabel:`Cancelled`, and appear in red." +msgid "Modify a contract template" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "A list view of all the salary attachments with their status displayed." +#: ../../content/applications/hr/payroll/contracts.rst:230 +msgid "Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the end of either the :guilabel:`New Contract Document Template` or :guilabel:`Contract Update Document Template` to open the corresponding contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:234 +msgid "Click the :guilabel:`Upload your file` button next to the corresponding document, navigate to the file, then click :guilabel:`Open` to select the document and add it to the tab." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:238 -msgid "New salary attachment" +msgid "Modifying contract templates" msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:240 -msgid "To create a new salary attachment from the :guilabel:`Salary Attachment` page, click :guilabel:`New`, and a blank salary attachment form loads. Enter the following information on the form:" +msgid "Contracts templates can be modified at any point when changes are needed." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:244 -msgid ":guilabel:`Employees`: add any employees the salary attachment applies to using the drop-down menu." +#: ../../content/applications/hr/payroll/contracts.rst:242 +msgid ":guilabel:`Tags`: select any tags associated with the contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:248 -msgid "Multiple employees can be added, if the salary attachment details are identical. After all employees are added, a :guilabel:`Create Individual Attachments` button appears at the top of the form." +#: ../../content/applications/hr/payroll/contracts.rst:243 +msgid ":guilabel:`Signed Document Workspace`: this is where the signatures are stored. Choose a pre-configured workspace, or create a new one. To create a new :guilabel:`Signed Document Workspace`, type in the name of the workspace, then click either :guilabel:`Create` to add the new workspace, or :guilabel:`Create and Edit` to add the workspace and modify the workspace details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:247 +msgid ":guilabel:`Signed Document Tags`: select or create any tags that are only associated with the signed contract, as opposed to the original unsigned contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:249 +msgid ":guilabel:`Redirect Link`: enter a redirect link for the employee to access the contract. A redirect link takes the user from one URL to another. In this case, it takes them to the newly-updated contract specifically written for them." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:252 -msgid "After the form is completed, click the :guilabel:`Create Individual Attachments` button to create separate salary attachments for each of the employees listed in this field." +msgid ":guilabel:`Who can Sign`: select either :guilabel:`All Users` or :guilabel:`On Invitation`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:0 -msgid "The Create Individual Attachments button that appears after multiple employees are\n" -"added to the Employees field." +#: ../../content/applications/hr/payroll/contracts.rst:254 +msgid ":guilabel:`All Users`: any user in the organization can sign the contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:260 -msgid "This is a time-saving tip, so that separate salary attachments do not need to be created individually. They can be created in a batch using this method." +#: ../../content/applications/hr/payroll/contracts.rst:255 +msgid ":guilabel:`On Invitation`: only users selected in this field can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:257 +msgid ":guilabel:`Invited Users`: select the person (or people) that can sign the document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:258 +msgid ":guilabel:`Document`: the attached document can be replaced by clicking the :icon:`fa-pencil` :guilabel:`(pencil)` icon. A pop-up window appears, so another document can be selected for upload. The file **must** be a PDF. To remove the document, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:263 -msgid ":guilabel:`Description`: enter a description for the specific type of salary attachment." +msgid "Once the edits are complete, click the :guilabel:`Save` button. All the information for the selected contract template populates the fields in the :guilabel:`Salary Information` tab. Any additional tabs, such as :guilabel:`Personal Documents`, appears if applicable." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:264 -msgid ":guilabel:`Type`: select the :ref:`type of salary attachment ` from the drop-down menu. The options listed come from the salary attachment types configured in the configuration menu." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:267 -msgid ":guilabel:`Start Date`: enter the date the salary attachment begins. The first of the current month populates this field, by default. Click on the date, and a calendar appears. Navigate to the desired month and year, using the :guilabel:`< > (arrow)` icons, and click on the date to select it." -msgstr "" - -#: ../../content/applications/hr/payroll/contracts.rst:271 -msgid ":guilabel:`Document`: if any documents are needed for the salary attachment, click the :guilabel:`Upload your file` button, and a file explorer appears. Navigate to the file, and click :guilabel:`Open` to select them, and attach them to the form." +#: ../../content/applications/hr/payroll/contracts.rst:268 +msgid "Salary information" msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:274 -msgid ":guilabel:`Monthly Amount`: enter the amount to be taken out of the paycheck each month for this salary attachment." +msgid "This section is where the specific salary details are defined. This section is country-specific, so these fields vary, depending on where the company is located." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:276 -msgid ":guilabel:`Estimated End Date`: this field only appears after the :guilabel:`Monthly Amount` field is populated, and if the :guilabel:`Type` is **not** set to :guilabel:`Child Support`. This date is when the salary attachment is predicted to end, and is automatically calculated once both, the :guilabel:`Monthly Amount` and :guilabel:`Total Amount`, fields are populated. This is calculated based on how much is required to be paid, and how much is paid towards that amount each month. If either the :guilabel:`Monthly Amount` or :guilabel:`Total Amount` changes, this field automatically updates. It is **not** possible to modify this field." +#: ../../content/applications/hr/payroll/contracts.rst:277 +msgid "Enter the amount in the various fields, or tick a checkbox to apply a benefit. Some options that can be entered here include :guilabel:`Group Insurance Sacrifice Rate` and :guilabel:`Canteen Cost`, for example." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:283 -msgid ":guilabel:`Total Amount`: enter the total amount to be paid in this field. If :guilabel:`Child Support` is selected for the :guilabel:`Type`, this field does **not** appear." +#: ../../content/applications/hr/payroll/contracts.rst:281 +msgid "Some fields may be automatically filled in as other fields are entered. For example, the :guilabel:`Yearly Cost (Real)` and :guilabel:`Monthly Cost (Real)` updates once the :guilabel:`Wage` is populated." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Enter a new line for each type of garnishment." +#: ../../content/applications/hr/payroll/contracts.rst:286 +msgid "Personal documents" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:291 -msgid "When the total amount has been paid for the salary attachment, navigate to the individual salary attachment, and click the :guilabel:`Mark as Completed` button at the top of the form. This changes the status to :guilabel:`Completed`, and the garnishments are no longer taken out of the employee's paychecks." +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "This tab **only** appears after an :guilabel:`Employee` is selected, and houses any documents that are linked to the employee on their employee record. Documents cannot be added to this tab, this tab **only** shows documents that are already uploaded and associated with the employee." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:297 -msgid "Offers" +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "The available documents in this tab can be downloaded. Click the :icon:`fa-download` :guilabel:`(download)` icon next to the document to download it." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:299 -msgid "Once a contract has been created or modified, the contract **must** be sent to the employee to be accepted and signed." +#: ../../content/applications/hr/payroll/contracts.rst:296 +msgid "Save and send the contract" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:303 -msgid "Send an offer" +#: ../../content/applications/hr/payroll/contracts.rst:298 +msgid "Once a contract has been created and/or modified, save the contract by clicking the :guilabel:`Save` button. Next, the contract must be sent to the employee to be signed." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:305 -msgid "Open an individual contract by navigating to :menuselection:`Payroll app --> Contracts -> Contracts`, and click on a contract to open the contract form. Click on the :guilabel:`Generate Offer` button at the top of the page, and a :guilabel:`Generate Simulation Link` pop-up form appears." +#: ../../content/applications/hr/payroll/contracts.rst:301 +msgid "Click on one of the following buttons to send the contract to the employee:" msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:-1 msgid "Send the contract to the employee via one of the buttons." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:314 -msgid "The :guilabel:`Generate Simulation Link` pop-up form contains all the information pulled from the contract, including the :guilabel:`Contract Template`, :guilabel:`Job Position`, :guilabel:`Job Title`, :guilabel:`Department`, :guilabel:`Contract Start Date`, :guilabel:`Default Vehicle`, :guilabel:`Contract Type`, and :guilabel:`Yearly Cost`." +#: ../../content/applications/hr/payroll/contracts.rst:307 +msgid ":guilabel:`Generate Simulation Link`: this option is **only** for Belgian companies. Clicking this opens a pop-up window that contains the basic information from the contract, as well as a link for the contract when using the salary configurator. Click :guilabel:`Send` to send an email to the employee, so they can sign the contract." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:319 +#: ../../content/applications/hr/payroll/contracts.rst:312 msgid "At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This is the timeframe that the contract offer is valid for. By default, this field is pre-populated with `30 days`, but it can be modified." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:323 -msgid "Click the :guilabel:`Send By Email` button, and a :guilabel:`Send Offer Email` template pop-up window appears. Make any modifications to the email, and attach any additional documents needed, then click :guilabel:`Send` to send the offer." +#: ../../content/applications/hr/payroll/contracts.rst:317 +msgid "In order to send a contract using the :guilabel:`Generate Simulation Link`, there **must** be a signature field in the contract PDF being sent to the employee, so they can sign it." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "The email template pop-up to send an offer." +#: ../../content/applications/hr/payroll/contracts.rst:320 +msgid ":guilabel:`Signature Request`: clicking this reveals a pop-up window, where an email can be typed to the employee. Select the document (such as a contract, NDA, or Homeworking Policy) from the drop-down menu, and fill out the email section. Click :guilabel:`Send` when the email is ready to be sent." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:332 +#: ../../content/applications/hr/payroll/contracts.rst:326 msgid "To send a contract using the :guilabel:`Generate Simulation Link`, there **must** be a signature field in the contract PDF being sent to the employee, so they can sign it." msgstr "" +#: ../../content/applications/hr/payroll/contracts.rst:330 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:332 +msgid "Any automatic deductions or allocations for an employee, such as child support payments and wage garnishments, are referred to as a *salary attachment*. This section is where all of these deductions or allocations are set." +msgstr "" + #: ../../content/applications/hr/payroll/contracts.rst:336 -msgid "Accept an offer" +msgid "To add a new deduction, first navigate to :menuselection:`Payroll app --> Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new salary attachment form loads." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:338 -msgid "Once the offer email is received, the offer can be accepted, and the contract can be signed." +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "The salary attachment form with everything filled in for Ronnie Hart's child support." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:340 -msgid "In the offer email, click the :guilabel:`Configure your package` button, and the offer loads in a new tab. Enter the requested information on the form. Next, click the :guilabel:`Review Contract & Sign` button to begin the signing process." +#: ../../content/applications/hr/payroll/contracts.rst:343 +#: ../../content/applications/hr/time_off.rst:268 +msgid "Fill out the following fields on the form:" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:344 -msgid "Click the :guilabel:`CLICK TO START` button at the top-left of the contract. Follow the prompts to complete the signature request. The contract auto-populates with the information entered on the :guilabel:`Configure your package` page. When done, click the :guilabel:`Validate & Send Completed Document` button at the bottom of the contract." +#: ../../content/applications/hr/payroll/contracts.rst:345 +msgid ":guilabel:`Employee`: using the drop-down menu, select the employee the salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:347 +msgid ":guilabel:`Description`: enter a short description for the salary attachment, such as `Child Support` or `529 Contribution`." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:349 -msgid "After the document is signed by the (potential) employee, management signs the contract next. The manager's signature is completed directly in the *Sign* application." +msgid ":guilabel:`Type`: using the drop-down menu, select the type of salary attachment being created. Choose from:" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "The contract offer, ready to sign with the Click to Start button highlighted." +#: ../../content/applications/hr/payroll/contracts.rst:352 +msgid ":guilabel:`Attachment of Salary`: any payments taken out towards something that is *not* child support. Typically any garnishments, such as lawsuit payments, payments toward taxes owed, etc." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:357 -msgid "Depending on the localization settings, there may be the option to customize the offer in the :guilabel:`Configure your package` tab." +#: ../../content/applications/hr/payroll/contracts.rst:354 +msgid ":guilabel:`Assignment of Salary`: any deduction that is not required, but voluntary, such as a pre-tax allocation to a college savings account." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:361 -msgid "View offers" +#: ../../content/applications/hr/payroll/contracts.rst:356 +msgid ":guilabel:`Child Support`: any payments taken out specifically for child support." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:363 -msgid "To view the current offers, navigate to :menuselection:`Payroll app --> Contracts --> Offers`. This presents all offers in a list view, grouped by status, and displays the number of offers in each status category. The statuses are: :guilabel:`Fully Signed`, :guilabel:`Partially Signed`, :guilabel:`In Progress`, and :guilabel:`Expired`." +#: ../../content/applications/hr/payroll/contracts.rst:358 +msgid ":guilabel:`Start Date`: the date the salary attachment starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then clicking on the desired date. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:368 -msgid "To view the offers with a specific status, click on the status to expand the list. If a specific status has no offers, the status is not visible in the list." +#: ../../content/applications/hr/payroll/contracts.rst:362 +msgid ":guilabel:`Estimated End Date`: this field automatically populates after both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are populated. This field is **not** modifiable." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "The offers in a list view, grouped by status." +#: ../../content/applications/hr/payroll/contracts.rst:365 +msgid ":guilabel:`Document`: attach any documents relevant to the salary attachment. Click the :guilabel:`Upload Your File` button, navigate to the desired document in the file explorer, then click :guilabel:`Open` to select the document, and attach it to the form. To change the attached document, click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a different document. To remove a document, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:370 +msgid ":guilabel:`Monthly Amount`: enter the amount to be taken out of the employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:372 +msgid ":guilabel:`Total Amount`: enter the total amount that the employee pays for the salary attachment to be completed." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:3 @@ -7698,51 +7830,51 @@ msgstr "" msgid "At any point, to return to a view containing the current day, click the :guilabel:`Today` button." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:46 +#: ../../content/applications/hr/payroll/work_entries.rst:48 msgid "Add a new work entry" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:48 +#: ../../content/applications/hr/payroll/work_entries.rst:50 msgid "If a work entry is missing and needs to be added, such as sick time, or if an employee forgot to clock in and out for a shift, click :guilabel:`New` on the :guilabel:`Work Entry` dashboard, to create a new work entry." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:52 +#: ../../content/applications/hr/payroll/work_entries.rst:54 msgid "A :guilabel:`Create` work entry pop-up form appears." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/payroll/work_entries.rst:58 msgid ":guilabel:`Description`: enter a short description for the work entry, such as `Sick Time`. If this field is left blank, it automatically populates once an employee is selected. The default entry is `Attendance: (Employee)`." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:59 +#: ../../content/applications/hr/payroll/work_entries.rst:61 msgid ":guilabel:`Employee`: select the employee the work entry is for, using the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:60 +#: ../../content/applications/hr/payroll/work_entries.rst:62 msgid ":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:62 +#: ../../content/applications/hr/payroll/work_entries.rst:64 msgid ":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and end (:guilabel:`To`) dates and times for the work entry." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:65 +#: ../../content/applications/hr/payroll/work_entries.rst:67 msgid "First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal a calendar pop-up window. Select the date by navigating to the correct month and year, using the :guilabel:`< (left arrow)` and :guilabel:`> (right arrow)` icons, then click on the specific day." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:69 +#: ../../content/applications/hr/payroll/work_entries.rst:71 msgid "Next, select the time, by clicking on either the hour or minute fields at the bottom of the calendar, and select the desired time for both the hour and minutes." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:72 +#: ../../content/applications/hr/payroll/work_entries.rst:74 msgid "When the date and time are correct for the entry, click the :guilabel:`Apply` button." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:73 +#: ../../content/applications/hr/payroll/work_entries.rst:75 msgid ":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and :guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` field (the :guilabel:`From` field does not change)." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:77 +#: ../../content/applications/hr/payroll/work_entries.rst:79 msgid "Once the desired information is entered, click :guilabel:`Save & Close` to save the entry, and close the pop-up form." msgstr "" @@ -7750,19 +7882,19 @@ msgstr "" msgid "Filling in the work entry Create form in Odoo." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:87 +#: ../../content/applications/hr/payroll/work_entries.rst:89 msgid "Conflicts" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:89 +#: ../../content/applications/hr/payroll/work_entries.rst:91 msgid "A conflict appears for any request that has not been approved, such as sick time or vacation, or if there are any errors on the work entry, such as required fields being left blank. Conflicts are required to be resolved before payslips can be generated." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:93 +#: ../../content/applications/hr/payroll/work_entries.rst:95 msgid "Any work entry that has a conflict to be resolved is indicated on the main :guilabel:`Work Entry` dashboard, which can be accessed by navigating to :menuselection:`Payroll app --> Work Entries --> Work Entries`. Only conflicts needing resolution are shown by default." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:97 +#: ../../content/applications/hr/payroll/work_entries.rst:99 msgid "Conflicts are indicated with an orange triangle in the top-left corner of each individual work entry. Click on an individual work entry to see the date and time for the specific work entry, then click :guilabel:`Edit` to view the conflict details in a pop-up window." msgstr "" @@ -7770,15 +7902,15 @@ msgstr "" msgid "A row of conflicts, with one entry showing details for the conflict." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:105 +#: ../../content/applications/hr/payroll/work_entries.rst:107 msgid "The conflict is briefly explained in an orange text box in the :guilabel:`Open` pop-up window that appears." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:108 +#: ../../content/applications/hr/payroll/work_entries.rst:110 msgid "The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry Type` are listed on the left side of the pop-up window. The :guilabel:`From` and :guilabel:`To` date and time range, as well as the total time (in hours) in the :guilabel:`Duration` field, appears on the right side." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:112 +#: ../../content/applications/hr/payroll/work_entries.rst:114 msgid "If the conflict is due to a time off request that has not been approved yet, a :guilabel:`Time Off` field appears on the left side, with the type of time off requested in the description." msgstr "" @@ -7786,43 +7918,43 @@ msgstr "" msgid "The detailed conflict pop-up window that appears when Edit is clicked." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:120 +#: ../../content/applications/hr/payroll/work_entries.rst:122 msgid "Time off conflicts" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:122 +#: ../../content/applications/hr/payroll/work_entries.rst:124 msgid "The most common work entry conflicts are for time off requests that have been submitted, but not yet approved, which results in duplicate work entries for that employee (one for time off and another for regular work)." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:126 +#: ../../content/applications/hr/payroll/work_entries.rst:128 msgid "If there is a conflict because a time off request is in the system for the same time that a regular work entry already exists, the time off request is entered in the :guilabel:`Time Off` field." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:129 +#: ../../content/applications/hr/payroll/work_entries.rst:131 msgid "The time off conflict can be resolved either on the work entry pop-up window, or on a detailed time off request pop-up window." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:133 +#: ../../content/applications/hr/payroll/work_entries.rst:135 msgid "Resolve on work entry" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:135 +#: ../../content/applications/hr/payroll/work_entries.rst:137 msgid "To resolve the time off conflict on this work entry pop-up window, click the :guilabel:`Approve Time Off` button to approve the time off request, and resolve the work entry conflict." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:138 +#: ../../content/applications/hr/payroll/work_entries.rst:140 msgid "The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons disappear. Click the :guilabel:`Save & Close` button to close the pop-up window. The conflict disappears from the :guilabel:`Work Entry` dashboard, since the conflict is resolved." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:143 +#: ../../content/applications/hr/payroll/work_entries.rst:145 msgid "Resolve on time off request" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:145 +#: ../../content/applications/hr/payroll/work_entries.rst:147 msgid "To resolve the time off conflict on the detailed time off request pop-up window, click the :guilabel:`Internal Link` button at the end of the :guilabel:`Time Off` entry line, and the time off request details appear in a new pop-up window. The request can be modified, if needed." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:149 +#: ../../content/applications/hr/payroll/work_entries.rst:151 msgid "Click the :guilabel:`Approve` button to approve the request, then click the :guilabel:`Save & Close` button to save the changes, and go back to the work entry conflict pop-up window." msgstr "" @@ -7830,47 +7962,47 @@ msgstr "" msgid "The detailed time off request form." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:156 +#: ../../content/applications/hr/payroll/work_entries.rst:158 msgid "Now, the :guilabel:`Approve Time Off` button is hidden, only the :guilabel:`Refuse Time Off` button is visible." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:159 +#: ../../content/applications/hr/payroll/work_entries.rst:161 msgid "If the approval was a mistake, the request can be refused here, by clicking the :guilabel:`Refuse Time Off` button." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:162 +#: ../../content/applications/hr/payroll/work_entries.rst:164 msgid "Since the time off was approved in the time off window, click the :guilabel:`X` in the top-right corner to close the window. The conflict disappears from the :guilabel:`Work Entry` dashboard, since it has been resolved." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:169 +#: ../../content/applications/hr/payroll/work_entries.rst:171 msgid "Regenerate work entries" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:171 +#: ../../content/applications/hr/payroll/work_entries.rst:173 msgid "When regenerating work entries, any manual changes, such as resolved conflicts, are overwritten, and work entries are regenerated (or recreated) from the applications that created them." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:174 +#: ../../content/applications/hr/payroll/work_entries.rst:176 msgid "This method for correcting a large amount of conflicts is recommended to keep all records correct. While :ref:`conflicts ` *can* be resolved individually, if the conflicts are caused from another application, it is best practice to ensure the records in the other applications are also correct. That is why it is recommended to resolve these conflicts in the applications that created the conflict." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:180 +#: ../../content/applications/hr/payroll/work_entries.rst:182 msgid "Another reason this method is recommended is because, when work entries are regenerated, the conflicts reappear, if the issue in the related application is **not** resolved." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:183 +#: ../../content/applications/hr/payroll/work_entries.rst:185 msgid "First, ensure the issues are resolved in the specific applications that caused the work entry conflicts." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:186 +#: ../../content/applications/hr/payroll/work_entries.rst:188 msgid "Next, click the :guilabel:`Regenerate Work Entries` button at the top of the :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry Regeneration` pop-up window appears." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:189 +#: ../../content/applications/hr/payroll/work_entries.rst:191 msgid "Select the :guilabel:`Employees` to regenerate work entries for from the drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, so the correct date range is displayed." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:192 +#: ../../content/applications/hr/payroll/work_entries.rst:194 msgid "Click the :guilabel:`Regenerate Work Entries` button, and the work entries are recreated. Once finished, the pop-up window closes." msgstr "" @@ -7878,47 +8010,47 @@ msgstr "" msgid "Regenerate a work entry for a particular employee." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:200 +#: ../../content/applications/hr/payroll/work_entries.rst:202 msgid "An employee has incorrect work entries generated from the *Planning* app because they were incorrectly assigned to two work stations simultaneously. This should be fixed in the *Planning* app, instead of the *Payroll* app." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:204 +#: ../../content/applications/hr/payroll/work_entries.rst:206 msgid "To correct this issue, modify the employee's schedule in the *Planning* app, so they are correctly assigned to only one work station. Then, in the *Payroll* app, regenerate work entries for that employee, for that specific time period." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:208 +#: ../../content/applications/hr/payroll/work_entries.rst:210 msgid "The *Payroll* app then pulls the new, corrected data form the *Planning* app, and recreates the correct work entries for that employee. All conflicts for that employee are now resolved." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:212 +#: ../../content/applications/hr/payroll/work_entries.rst:214 msgid "Generating payslips" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:214 +#: ../../content/applications/hr/payroll/work_entries.rst:216 msgid "To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the :guilabel:`Conflicting` filter is removed. When the desired pay period is displayed, click the :guilabel:`Generate Payslips` button." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:219 +#: ../../content/applications/hr/payroll/work_entries.rst:221 msgid "If the :guilabel:`Generate Payslips` button is not active (appears pale purple, instead of dark purple), that indicates there are conflicts, or the date selected includes dates in the future. Resolve all conflicts before generating payslips." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:223 +#: ../../content/applications/hr/payroll/work_entries.rst:225 msgid "When the :guilabel:`Generate Payslips` button is clicked, a batch entry appears on a separate page for the time period selected." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:226 +#: ../../content/applications/hr/payroll/work_entries.rst:228 msgid "The batch name populates the :guilabel:`Batch Name` field in a default `From (date) to (date)` format." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:229 +#: ../../content/applications/hr/payroll/work_entries.rst:231 msgid "The date range to which the payslips apply appears in the :guilabel:`Period` field, and the company appears in the :guilabel:`Company` field. It is **not** possible to make changes to this form." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:232 +#: ../../content/applications/hr/payroll/work_entries.rst:234 msgid "Click the :guilabel:`Create Draft Entry` button to create the payslips for the batch." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:234 +#: ../../content/applications/hr/payroll/work_entries.rst:236 msgid "Click the :guilabel:`Payslips` smart button at the top of the page to view all the payslips for the batch." msgstr "" @@ -7926,19 +8058,19 @@ msgstr "" msgid "Information that appears when generating payslips." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:242 +#: ../../content/applications/hr/payroll/work_entries.rst:244 msgid "Printing payslips" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:244 +#: ../../content/applications/hr/payroll/work_entries.rst:246 msgid "To print payslips, first view the individual payslips by clicking the :guilabel:`Payslips` smart button on the batch form." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:247 +#: ../../content/applications/hr/payroll/work_entries.rst:249 msgid "Next, select the payslips to print from the :guilabel:`Payslips` list. Click the box next to each payslip to print, or click the box to the left of the :guilabel:`Reference` column title, to select all the payslips in the list at once." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:251 +#: ../../content/applications/hr/payroll/work_entries.rst:253 msgid "Click the :guilabel:`Print` button, and a PDF file is created with all the specified payslips." msgstr "" @@ -7946,35 +8078,35 @@ msgstr "" msgid "Print button for printing the payslips." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:258 +#: ../../content/applications/hr/payroll/work_entries.rst:260 msgid "The :guilabel:`Print` button does **not** appear until at least one payslip is selected in the list." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:262 +#: ../../content/applications/hr/payroll/work_entries.rst:264 msgid "Time off to report" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:264 +#: ../../content/applications/hr/payroll/work_entries.rst:266 msgid "If a time off request is submitted for a time period that was already processed on a payslip, the time off request appears in the *Time Off* page in the *Payroll* app, which is accessible by navigating to :menuselection:`Payroll app --> Work Entries --> Time Off to Report`." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:268 +#: ../../content/applications/hr/payroll/work_entries.rst:270 msgid "On the :guilabel:`Time Off` page, the request appears with a status of :guilabel:`To defer to next payslip`. This is because the employee was already paid for that day, and it was logged as time spent at work, as a typical work day." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:272 +#: ../../content/applications/hr/payroll/work_entries.rst:274 msgid "In order to keep the employee's time off balances correct, the time off request **must** be applied to the following pay period. This not only ensures time off request balances are current, it also eliminates the need to redo work entries, cancel paychecks, and reissue paychecks." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:276 +#: ../../content/applications/hr/payroll/work_entries.rst:278 msgid "The most common scenario when this situation occurs, is when payslips are processed a day or two before the pay period ends, and an employee is unexpectedly sick on one of the last days of the pay period. The employee puts in a time off request for a day that was already processed on a payslip as a regular work day. Instead of canceling the payslip, modifying the work entries, and reissuing the paycheck, Odoo allows for those time off requests to be applied to the following pay period, instead." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:283 +#: ../../content/applications/hr/payroll/work_entries.rst:285 msgid "To view all the time off requests that need to be deferred to the next payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time Off to Report`. The default filter for this report is :guilabel:`To Defer`." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:287 +#: ../../content/applications/hr/payroll/work_entries.rst:289 msgid "All time off requests that need to be applied to the following pay period appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next payslip`." msgstr "" @@ -7982,19 +8114,19 @@ msgstr "" msgid "A list of all time off requests that were not approved before payslips were generated." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:295 +#: ../../content/applications/hr/payroll/work_entries.rst:297 msgid "Defer multiple time off entries" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:297 +#: ../../content/applications/hr/payroll/work_entries.rst:299 msgid "To select the work entries to defer, click the box to the left of the work entry line. To select all work entries in the list, click the box to the left of the :guilabel:`Employees` column title, at the top of the list." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:301 +#: ../../content/applications/hr/payroll/work_entries.rst:303 msgid "Once any work entry is selected, two buttons appear at the top of the report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` button. The :guilabel:`(#) Selected` button indicates how many entries are currently selected." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:305 +#: ../../content/applications/hr/payroll/work_entries.rst:307 msgid "When all the desired work entries are selected, click the :guilabel:`Actions` button, and a menu appears with several choices. Click :guilabel:`Defer to Next Month` in the list, and all selected entries are deferred to the following month." msgstr "" @@ -8002,27 +8134,27 @@ msgstr "" msgid "The actions button and # Selected buttons that appear after any selections are made." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:314 +#: ../../content/applications/hr/payroll/work_entries.rst:316 msgid "Defer individual time off entries" msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:316 +#: ../../content/applications/hr/payroll/work_entries.rst:318 msgid "Time off requests appearing on the :guilabel:`Time Off to Report` list can be deferred individually." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:318 +#: ../../content/applications/hr/payroll/work_entries.rst:320 msgid "Click on an individual time off request, and the details for that request load." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:320 +#: ../../content/applications/hr/payroll/work_entries.rst:322 msgid "The specific details for the time off request appear on the left-hand side, and all of the employee's submitted time off requests appear on the right-hand side (including the request in the details on the left-hand side)." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:324 +#: ../../content/applications/hr/payroll/work_entries.rst:326 msgid "To defer the time off request to the next payslip, click the :guilabel:`Report to Next Month` button at the top. Once processed, the :guilabel:`Report to Next Month` button disappears, and the :guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` to :guilabel:`Computed in Current Payslip`." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:329 +#: ../../content/applications/hr/payroll/work_entries.rst:331 msgid "To go back to the :guilabel:`Time Off to Report` list, click on :guilabel:`Time Off` in the breadcrumb menu." msgstr "" @@ -8030,7 +8162,7 @@ msgstr "" msgid "The time off details for an individual request that needs to be deferred." msgstr "" -#: ../../content/applications/hr/payroll/work_entries.rst:337 +#: ../../content/applications/hr/payroll/work_entries.rst:339 msgid ":ref:`Configure work entries `" msgstr "" @@ -8441,7 +8573,6 @@ msgid "Change the stage of an applicant by clicking on the desired stage at the msgstr "" #: ../../content/applications/hr/recruitment.rst:395 -#: ../../content/applications/hr/recruitment.rst:643 msgid "New" msgstr "" @@ -8510,7 +8641,7 @@ msgid "Email templates use dynamic placeholders to personalize the email to the msgstr "" #: ../../content/applications/hr/recruitment.rst:471 -#: ../../content/applications/hr/recruitment.rst:1066 +#: ../../content/applications/hr/recruitment.rst:802 msgid "If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button." msgstr "" @@ -8531,325 +8662,23 @@ msgid "Send a custom survey, also referred to as an interview form, to an applic "pre-configured template." msgstr "" -#: ../../content/applications/hr/recruitment.rst:494 -msgid "Refuse" -msgstr "" - #: ../../content/applications/hr/recruitment.rst:496 -msgid "At any point in the recruitment pipeline, an applicant can be refused from the job application process. To refuse an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, there are several buttons. Click the one labeled :guilabel:`Refuse`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:501 -msgid "A :guilabel:`Refuse Reason` pop-up window appears. Click the :guilabel:`Refuse Reason` from the presented options. The default refuse reasons in Odoo, and their corresponding email templates, are:" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:508 -msgid "Email Template" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:509 -msgid "Refusal Reason" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:510 -msgid ":guilabel:`Recruitment: Refuse`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Doesn't fit the job requirements`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Language issues`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Role already fulfilled`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Duplicate`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Spam`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:516 -msgid ":guilabel:`Recruitment: Not interested anymore`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Refused by Applicant: don't like job`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Refused by Applicant: better offer`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:0 -msgid ":guilabel:`Refused by Applicant: salary`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:521 -msgid "Additional refusal reasons :ref:`can be created and existing ones can be modified or deleted `." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:525 -msgid "Pre-configured email templates in Odoo sometimes use dynamic placeholders, which are customized pieces of data that populate dynamic content. For example, if the applicant's name is a piece of dynamic content, the applicant's name appears anytime that dynamic placeholder appears on the email template. For more detailed information on email templates, refer to the :doc:`../general/companies/email_template` documentation." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:531 -msgid "After a :guilabel:`Refuse Reason` is selected, two fields appear below the refusal reason: :guilabel:`Send Email` and :guilabel:`Email Template`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:534 -msgid "The applicant's email address automatically populates the :guilabel:`Send Email` field; additional email recipients cannot be added. If an email should **not** be sent to the applicant, uncheck the :guilabel:`Send Email` checkbox." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:538 -msgid "The email template associated with the refusal reason populates the :guilabel:`Email Template` field. If a different email template is desired, select a different template from the :guilabel:`Email Template` drop-down menu. To view the email template, click the :guilabel:`External Link` icon to the right of the :guilabel:`Email Template` field. The email template loads in a :guilabel:`Open: Email Template` pop-up window, and can be modified if needed. After making modifications, click :guilabel:`Save & Close`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:545 -msgid "To send the refusal email to the applicant, click :guilabel:`Refuse`. The refusal email is sent to the applicant, and a :guilabel:`Refused` banner appears on the applicant's card in the top-right corner." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:-1 -msgid "An applicant's card with the refused banner appearing in the top-right corner in red." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:553 -msgid "After refusal, the applicant's card is no longer visible in the job position's Kanban view. To view the refused applicants only, click the :guilabel:`▼ Toggle Search Panel` button in the search box, then click :guilabel:`Refused` under the :guilabel:`Filters` section. All applicants that have been refused for the job position appear, in the stage they were when they were refused." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:558 -msgid "To view all applicants that have been refused from all job positions, navigate to the :menuselection:`Recruitment app --> Applications --> All Applications`. Click the :guilabel:`▼ Toggle Search Panel` button in the search box, then click :guilabel:`Refused` under the :guilabel:`Filters` section. All applications for all job positions are presented in a list view, organized by stage." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:567 -msgid "Create or modify refuse reasons" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:569 -msgid "To view all currently configured refuse reasons, navigate to :menuselection:`Recruitment app --> Settings --> Applications: Refuse Reasons`. All the refuse reasons appear in a list view." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:572 -msgid "To create a new refuse reason, click the :guilabel:`New` button in the top-left corner. A blank line appears at the bottom of the :guilabel:`Description` column." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:575 -msgid "Type in the new refuse reason in the field. It is recommended to enter a reason that is short and concise, such as `offer expired` or `withdrew application`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:578 -msgid "Then, in the :guilabel:`Email Template` field, click on the field to reveal a drop-down menu. Select an :guilabel:`Email Template` from the list to be used when this refuse reason is selected." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:581 -msgid "If a new :guilabel:`Email Template` is desired, type in the name for the new template in the field. Then, click :guilabel:`Create and edit...` and a :guilabel:`Create Email Template` form pop-up window appears." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:585 -msgid "Enter a :guilabel:`Name` for the form and an email :guilabel:`Subject` in the corresponding fields. Enter the email content in the :guilabel:`Content` tab. Make any other desired modifications to the template, then click :guilabel:`Save & Close` to save the template and return to the :guilabel:`Refuse Reasons` list. The new template appears in the new refuse reason :guilabel:`Email Template` field." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:591 -msgid "To make any modifications to a refuse reason, click on the line, and make any desired changes." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:594 -msgid "New applicant" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:596 -msgid "An applicant card can be manually added if needed. If an applicant needs to be added to the list of prospective candidates and an applicant card has not been created yet (they have not applied for the job online) an applicant card can be easily added from the job position Kanban view in one of two ways, using either the :ref:`quick add ` button or the :ref:`New ` button." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:605 -msgid "Quick add" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:607 -msgid "Quickly add a new applicant using the *quick add* button. If not already in the job position Kanban view, navigate to the main recruitment dashboard by going to :menuselection:`Recruitment app --> Applications --> By Job Positions`. Click the :guilabel:`(#) New Applications` button on the job position card that the applicant should be added to. Then, click on the small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-right of the :guilabel:`New` stage to quickly add a new applicant." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:614 -msgid "Enter the following information on the card:" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:616 -msgid ":guilabel:`Subject/Application`: Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - HR Manager`. This field is not visible in the Kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the Kanban view." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:621 -#: ../../content/applications/hr/recruitment.rst:670 -msgid ":guilabel:`Applicant's Name`: enter the applicant's name." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:622 -#: ../../content/applications/hr/recruitment.rst:671 -msgid ":guilabel:`Email`: enter the applicant's email address." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:623 -msgid ":guilabel:`Applied Job`: the current job position populates this field. If needed, the job position can be changed by selecting a different position from the drop-down menu. If a different job position is selected, after the card is created, the card appears in the selected job position." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:628 -msgid "After the information is entered, click :guilabel:`Add`. The applicant appears in the list, and a new blank applicant card appears. Click either the :icon:`fa-trash-o` :guilabel:`delete` icon or anywhere on the screen to close the card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:632 -msgid "If preferred, after entering the applicant name, click :guilabel:`Edit` and a detailed :guilabel:`Applicant Form` loads. :ref:`Enter the information on the form `." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:-1 -msgid "All the fields for a new applicant form entered when using the Quick Add option." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:645 -msgid "Add a new applicant including all the relevant information using the *New* button. If not already in the Kanban view for the job position to add an applicant to, navigate to the main recruitment dashboard by going to :menuselection:`Recruitment app --> Applications --> By Job Positions`. Then, click the :guilabel:`New` button in the top-left of the Kanban view and a blank applicant form loads." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:651 -msgid "Certain fields on the applicant card may be pre-populated, depending on how the job position is configured. Typically, the :guilabel:`Job` section, as well as the :guilabel:`Recruiter` field, are all pre-populated." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:655 -msgid "Enter the following information on the new applicant form. Note that not all fields listed below may be visible. Depending on installed applications and configurations, some fields may not be displayed." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:662 -msgid "Applicant section" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:664 -msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `John Smith - Experienced Developer`. This field is not visible in the Kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the Kanban view." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:672 -msgid ":guilabel:`Phone`: enter the applicant's phone number." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:673 -msgid ":guilabel:`Mobile`: enter the applicant's mobile number." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:674 -msgid ":guilabel:`LinkedIn Profile`: enter the web address for the applicant's personal profile on LinkedIn." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:676 -msgid ":guilabel:`Degree`: select the applicant's highest level of education earned from the drop-down menu. Options are :guilabel:`Graduate`, :guilabel:`Bachelor Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The :guilabel:`Graduate` option indicates graduating the highest level of school before a Bachelor's degree, such as a high school or secondary school diploma, depending on the country." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:681 -msgid ":guilabel:`Interviewers`: using the drop-down menu, select the people who will conduct the interview(s). The selected people must have either *recruiter* or *officer* rights configured for the Recruitment application to appear in the drop-down list." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:684 -msgid ":guilabel:`Recruiter`: select the person responsible for the entire recruitment process for the job position. Only *users* can be selected, and all users are presented in the drop-down to select from." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:687 -msgid ":guilabel:`Evaluation`: click on one of the stars to select a rating for the applicant. One star indicates :guilabel:`Good`, two stars indicates :guilabel:`Very Good`, and three stars indicates :guilabel:`Excellent.`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:690 -msgid ":guilabel:`Source`: using the drop-down menu, select where the applicant learned about the job position. The following options come pre-configured in Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, :guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`Twitter`, :guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and :guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source, then click :guilabel:`Create \"(new source)\"`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:695 -msgid ":guilabel:`Medium`: using the drop-down menu, select the method, or :guilabel:`Medium`, for the :guilabel:`Source` that the applicant found the job listing with. The pre-configured options are: :guilabel:`Banner`, :guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, :guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, :guilabel:`Television`, :guilabel:`Twitter` (now known as \"X\"), or :guilabel:`Website`. To add a new :guilabel:`Medium`, type in the medium, then click :guilabel:`Create \"(new medium)\"`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:701 -msgid ":guilabel:`Referred By User`: if referral points are to be earned for this job position in the *Referrals* application, select the user who referred the applicant from the drop-down menu. The *Referrals* application must be installed for this field to appear." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:704 -msgid ":guilabel:`Availability`: select the available start date for the applicant. To select a date, click on the field to reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date. If no entry is selected that indicates the applicant is ready to begin work immediately." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:709 -msgid ":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To add a tag that does not exist, type in the tag name, then click :guilabel:`Create \"new tag\"`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:713 -msgid "Job section" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:715 -msgid "The following fields are pre-populated when creating a new applicant, as long as these field are specified on the Job Position. Editing the fields is possible, if desired." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:718 -msgid ":guilabel:`Applied Job`: select the job position the applicant is applying to from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:720 -msgid ":guilabel:`Department`: select the department the job position falls under from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:722 -msgid ":guilabel:`Company`: select the company the job position is for using the drop-down menu. This field only appears when in a multi-company database." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:726 -msgid "Contract section" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:728 -msgid ":guilabel:`Expected Salary`: enter the amount the applicant is requesting for the role in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:731 -msgid ":guilabel:`Extra advantages...`: if any extra advantages are requested by the applicant, enter it in the :guilabel:`Extra advantages...` field to the right of the :guilabel:`Expected Salary` field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:734 -msgid ":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant for the role in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:737 -msgid ":guilabel:`Extra advantages...`: if any extra advantages are offered to the applicant, enter it in the :guilabel:`Extra advantages...` field to the right of the :guilabel:`Proposed Salary` field. This should be short and descriptive, such as `unlimited sick time` or `retirement plan`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:742 -msgid "Application summary tab" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:744 -msgid "Any additional details or notes that should be added to the applicant's card can be typed into this field." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:750 -msgid "Skills can be added to the applicant's card. To add a skill, follow the same steps as outlined in the skills section of the :ref:`Create new employees ` document." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:-1 -msgid "All the fields for a new applicant form entered." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:760 msgid "Initial qualification" msgstr "" -#: ../../content/applications/hr/recruitment.rst:762 +#: ../../content/applications/hr/recruitment.rst:498 msgid "If an applicant seems to be a good potential candidate, they are moved to the :guilabel:`Initial Qualification` stage. This could be for a number of reasons, such as they have the relevant experience, education, or certifications the position requires." msgstr "" -#: ../../content/applications/hr/recruitment.rst:766 +#: ../../content/applications/hr/recruitment.rst:502 msgid "This stage is to quickly sort candidates that have potential, and those that do not meet the requirements. No automatic actions, such as emails, are set for this stage. This stage simply informs the recruitment team to potentially set up a phone call or an interview with the candidate." msgstr "" -#: ../../content/applications/hr/recruitment.rst:773 +#: ../../content/applications/hr/recruitment.rst:509 msgid "First interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:775 +#: ../../content/applications/hr/recruitment.rst:511 msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be moved to the :guilabel:`First Interview` stage in the job position Kanban view. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`First Interview` stage, or click on the :guilabel:`First Interview` stage button at the top of the individual applicant's card." msgstr "" @@ -8857,47 +8686,47 @@ msgstr "" msgid "An applicant's card moves from one stage to another by using the click and drag method." msgstr "" -#: ../../content/applications/hr/recruitment.rst:785 +#: ../../content/applications/hr/recruitment.rst:521 msgid "The :guilabel:`First Interview` stage can be modified so when the applicant's card moves to the :guilabel:`First Interview` stage, an email is automatically sent to the applicant stating an interview is requested. In this pre-configured email template, a link to the recruiting team's calendar appears, allowing the applicant to schedule their interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:790 +#: ../../content/applications/hr/recruitment.rst:526 msgid ":ref:`Edit ` the :guilabel:`First Interview` stage, and select the :guilabel:`Recruitment: Schedule Interview` for the :guilabel:`Email Template` field, to automate this action." msgstr "" -#: ../../content/applications/hr/recruitment.rst:799 +#: ../../content/applications/hr/recruitment.rst:535 msgid "An interview can be scheduled in one of two ways: either manually by the recruitment team, or by the applicant themselves." msgstr "" -#: ../../content/applications/hr/recruitment.rst:802 +#: ../../content/applications/hr/recruitment.rst:538 msgid "If the :guilabel:`First Interview` stage was modified to send the :guilabel:`Recruitment: Schedule Interview` email template when an applicant reaches that stage, the applicant received a link to the recruitment team's calendar, and can schedule the interview on their own. The recruitment team's availability is reflected in the calendar." msgstr "" -#: ../../content/applications/hr/recruitment.rst:807 +#: ../../content/applications/hr/recruitment.rst:543 msgid "If the interview needs to be scheduled by the recruitment team, they should reach out to the applicant for a date and time that works. When a date and time have been agreed upon for both the applicant and interviewer, the interview can be scheduled. To schedule an interview, whether a phone or in-person interview, click the :guilabel:`Meeting` smart button at the top of the applicant's record." msgstr "" -#: ../../content/applications/hr/recruitment.rst:814 +#: ../../content/applications/hr/recruitment.rst:550 msgid "The meeting smart button displays :guilabel:`No Meeting` if no meetings are currently scheduled. For new applicants who are new to the :guilabel:`First Interview` stage, this is the default." msgstr "" -#: ../../content/applications/hr/recruitment.rst:817 +#: ../../content/applications/hr/recruitment.rst:553 msgid "If there is one meeting already scheduled, the smart button displays :guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If more than one meeting is scheduled, the button displays :guilabel:`Next Meeting`, with the date of the first upcoming meeting beneath it." msgstr "" -#: ../../content/applications/hr/recruitment.rst:821 +#: ../../content/applications/hr/recruitment.rst:557 msgid "Doing so loads the *Calendar* application, showing the currently scheduled meetings and events for the user. The meetings and events displayed are for the employees who are listed under the :guilabel:`Attendees` section on the right side of the calendar view. To change the currently loaded meetings and events being displayed, uncheck the person who's calendar events are to be hidden. Only the checked attendees are visible on the calendar." msgstr "" -#: ../../content/applications/hr/recruitment.rst:827 +#: ../../content/applications/hr/recruitment.rst:563 msgid "The default view is the :guilabel:`Week` view. To change the calendar view, click the :guilabel:`Week` button, then select the desired view from the drop-down menu. The other options are either :guilabel:`Day`, :guilabel:`Month`, or :guilabel:`Year`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:831 +#: ../../content/applications/hr/recruitment.rst:567 msgid "An option to display or hide weekends is available. Click the :guilabel:`Week` button, then click :guilabel:`Show weekends` to deactivate it (the default is to show weekends). If a check mark is next to :guilabel:`Show weekends`, weekends are visible. If there is no check mark, weekends are hidden." msgstr "" -#: ../../content/applications/hr/recruitment.rst:836 +#: ../../content/applications/hr/recruitment.rst:572 msgid "To change the displayed date range for the calendar, either use the :icon:`fa-arrow-left` :guilabel:`(left arrow)`, :icon:`fa-arrow-right` :guilabel:`(Right arrow)`, or :guilabel:`Today` buttons above the calendar, or click on a date in the calendar on the right side of the displayed calendar." msgstr "" @@ -8905,107 +8734,107 @@ msgstr "" msgid "The calendar view, highlighting how to change the displayed meetings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:845 +#: ../../content/applications/hr/recruitment.rst:581 msgid "To add a meeting to the calendar when in the day or week view, click on the start time of the meeting and drag to the end time, to select the date, time, and the length of the meeting. A meeting can also be added in this view by clicking on the day *and* the time slot the meeting is to take place." msgstr "" -#: ../../content/applications/hr/recruitment.rst:850 +#: ../../content/applications/hr/recruitment.rst:586 msgid "Both methods cause a :ref:`New Event ` pop up window to appear." msgstr "" -#: ../../content/applications/hr/recruitment.rst:855 +#: ../../content/applications/hr/recruitment.rst:591 msgid "New event pop-up window" msgstr "" -#: ../../content/applications/hr/recruitment.rst:857 +#: ../../content/applications/hr/recruitment.rst:593 msgid "Enter the information on the form. The only required fields to enter are the :guilabel:`Meeting Title`, and the :guilabel:`Start` and :guilabel:`End` fields. Once the card details are entered, click :guilabel:`Save & Close` to save the changes and create the interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:861 +#: ../../content/applications/hr/recruitment.rst:597 msgid "The fields available to populate or modify on the :guilabel:`New Event` card are as follows:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:863 +#: ../../content/applications/hr/recruitment.rst:599 msgid ":guilabel:`Meeting Title`: enter the subject for the meeting. This should clearly indicate the purpose of the meeting. The default subject is the :guilabel:`Subject/Application Name` on the applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:866 +#: ../../content/applications/hr/recruitment.rst:602 msgid ":guilabel:`Start` and :guilabel:`End`: select the start and end date and times for the meeting. Click on one of the fields and a calendar pop-up window appears. Select both the start and end date and times, then click :guilabel:`Apply`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:869 +#: ../../content/applications/hr/recruitment.rst:605 msgid ":guilabel:`All Day`: if the meeting is an all-day interview, check the box. If this box is checked, the :guilabel:`Start` and :guilabel:`End` fields are hidden from view." msgstr "" -#: ../../content/applications/hr/recruitment.rst:871 +#: ../../content/applications/hr/recruitment.rst:607 msgid ":guilabel:`Attendees`: select the people who should be in attendance. The default employee listed is the person who is creating the meeting. Add as many other people as desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:873 +#: ../../content/applications/hr/recruitment.rst:609 msgid ":guilabel:`Videocall URL`: if the meeting is virtual, or if there is a virtual option available, click :guilabel:`+ Odoo meeting` and a URL is automatically created for the meeting and populates the field." msgstr "" -#: ../../content/applications/hr/recruitment.rst:876 +#: ../../content/applications/hr/recruitment.rst:612 msgid ":guilabel:`Description`: enter a brief description in this field. There is an option to enter formatted text, such as numbered lists, headings, tables, as well as links, photos, and more. Use the powerbox feature, by typing a `/`, and a list of options are presented. Scroll through the options and click on the desired item. The item appears in the field and can be modified. Each command presents a different pop-up window. Follow the instructions for each command to complete the entry." msgstr "" -#: ../../content/applications/hr/recruitment.rst:884 +#: ../../content/applications/hr/recruitment.rst:620 msgid "More options" msgstr "" -#: ../../content/applications/hr/recruitment.rst:886 +#: ../../content/applications/hr/recruitment.rst:622 msgid "To add additional information to the meeting, click the :guilabel:`More Options` button in the lower-right corner of the pop-up window. Enter any of the following additional fields:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:889 +#: ../../content/applications/hr/recruitment.rst:625 msgid ":guilabel:`Duration`: this field auto populates based on the :guilabel:`Starting At` and :guilabel:`Ending At` times entered. If the meeting time is adjusted, this field automatically adjusts to the correct duration length. The default length of a meeting is one hour." msgstr "" -#: ../../content/applications/hr/recruitment.rst:892 +#: ../../content/applications/hr/recruitment.rst:628 msgid ":guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a first interview), check the box next to :guilabel:`Recurrent`. Several additional fields appear when this is enabled:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:896 +#: ../../content/applications/hr/recruitment.rst:632 msgid ":guilabel:`Timezone`: using the drop-down menu, select the :guilabel:`Timezone` for the meetings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:898 +#: ../../content/applications/hr/recruitment.rst:634 msgid ":guilabel:`Repeat`: using the drop-down menu, select when the meetings repeat. The available options are :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom`. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` field appears beneath it, along with another time frequency parameter (:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or :guilabel:`Years`). Enter a number in the blank field, then select the time period using the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:904 +#: ../../content/applications/hr/recruitment.rst:640 msgid ":guilabel:`Repeat on`: if :guilabel:`Weekly` is selected for the :guilabel:`Repeat` field, the :guilabel:`Repeat on` field appears. Click on the corresponding day to select it." msgstr "" -#: ../../content/applications/hr/recruitment.rst:906 +#: ../../content/applications/hr/recruitment.rst:642 msgid ":guilabel:`Day of Month`: if :guilabel:`Monthly` is selected for the :guilabel:`Repeat` field, the :guilabel:`Day of Month` field appears. Using the drop-down menu, select either :guilabel:`Date of month` or :guilabel:`Day of month`. If :guilabel:`Date of month` is selected, enter the date the meeting repeats. If :guilabel:`Day of month` is selected, use the drop-down menus to determine the frequency. Select either :guilabel:`First`, :guilabel:`Second`, :guilabel:`Third`, :guilabel:`Fourth`, or :guilabel:`Last` for the first drop-down menu, then select the day (:guilabel:`Monday`, :guilabel:`Tuesday`, etc.) in the second drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:913 +#: ../../content/applications/hr/recruitment.rst:649 msgid ":guilabel:`Until`: using the drop-down menu, select when the meetings stop repeating. The available options are :guilabel:`Number of repetitions`, :guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of repetitions` is selected, enter the number of total meetings to occur in the blank field. If :guilabel:`End date` is selected, specify the date using the calendar pop-up window, or type in a date in a XX/XX/XXXX format. :guilabel:`Forever` schedules meetings indefinitely." msgstr "" -#: ../../content/applications/hr/recruitment.rst:920 +#: ../../content/applications/hr/recruitment.rst:656 msgid ":guilabel:`Location`: enter the location for the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:921 +#: ../../content/applications/hr/recruitment.rst:657 msgid ":guilabel:`Tags`: select any tag(s) for the meeting using the drop-down menu. There is no limit to the number of tags that can be used." msgstr "" -#: ../../content/applications/hr/recruitment.rst:923 +#: ../../content/applications/hr/recruitment.rst:659 msgid ":guilabel:`Appointment`: if an appointment is associated with this meeting, select it form the drop-down menu, or create a new appointment by typing in the appointment name, then click :guilabel:`Create & Edit...`. A :guilabel:`Create Appointment` form loads. Enter the information on the form, then click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:927 +#: ../../content/applications/hr/recruitment.rst:663 msgid ":guilabel:`Privacy`: select if the organizer appears either :guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting, using the drop-down menu. Next, select the visibility of this meeting, using the drop-down menu to the right of the first selection. Options are :guilabel:`Public`, :guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public` allows for everyone to see the meeting, :guilabel:`Private` allows only the attendees listed on the meeting to see the meeting, and :guilabel:`Only internal users` allows anyone logged into the company database to see the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:934 +#: ../../content/applications/hr/recruitment.rst:670 msgid ":guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the drop-down menu to change the selected employee." msgstr "" -#: ../../content/applications/hr/recruitment.rst:936 +#: ../../content/applications/hr/recruitment.rst:672 msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Default options include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a specific time period before the event (hours, days, etc). The reminder chosen alerts the meeting participants of the meeting via the selected option at the specified time. Multiple reminders can be selected in this field." msgstr "" @@ -9013,15 +8842,15 @@ msgstr "" msgid "A new meeting card with all the details populated, and ready to save." msgstr "" -#: ../../content/applications/hr/recruitment.rst:947 +#: ../../content/applications/hr/recruitment.rst:683 msgid "Send meeting to attendees" msgstr "" -#: ../../content/applications/hr/recruitment.rst:949 +#: ../../content/applications/hr/recruitment.rst:685 msgid "Once changes have been entered and the meeting details are correct, the meeting can be sent to the attendees via email or text message from the expanded :guilabel:`Event Form` (what is seen when the :guilabel:`More Options` button is clicked on in the event pop-up window)." msgstr "" -#: ../../content/applications/hr/recruitment.rst:953 +#: ../../content/applications/hr/recruitment.rst:689 msgid "To send the meeting via email, click the :icon:`fa-envelope` :guilabel:`Email` button next to the list of attendees. A :guilabel:`Contact Attendees` email configurator pop-up window appears. A pre-formatted email using the default :guilabel:`Calendar: Event Update` email template populates the email body field. The followers of the document (job application), as well as the user who created the meeting are added as :guilabel:`Recipients` by default. Add the applicant's email address to the list to send the email to the applicant as well. Make any other desired changes to the email. If an attachment is needed, click the :guilabel:`Attachments` button, navigate to the file, then click :guilabel:`Open`. Once the email is ready to be sent, click :guilabel:`Send`." msgstr "" @@ -9029,19 +8858,19 @@ msgstr "" msgid "Enter the information to send the event via email." msgstr "" -#: ../../content/applications/hr/recruitment.rst:966 +#: ../../content/applications/hr/recruitment.rst:702 msgid "To send the meeting via text message, click the :icon:`fa-mobile` :guilabel:`SMS` button next to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up appears." msgstr "" -#: ../../content/applications/hr/recruitment.rst:969 +#: ../../content/applications/hr/recruitment.rst:705 msgid "At the top, a blue box appears if any attendees do not have valid mobile numbers, and lists how many records are invalid. If a contact does not have a valid mobile number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." msgstr "" -#: ../../content/applications/hr/recruitment.rst:973 +#: ../../content/applications/hr/recruitment.rst:709 msgid "When no warning message appears, type in the message to be sent to the attendees in the :guilabel:`Message` field. to add any emojis to the message, click the :guilabel:`Add Emoji` icon on the right-side of the pop-up window." msgstr "" -#: ../../content/applications/hr/recruitment.rst:977 +#: ../../content/applications/hr/recruitment.rst:713 msgid "Beneath the message field, the number of characters, as well as the amount of text messages required to send the message (according to GSM7 criteria) appears. Click :guilabel:`Put In Queue` to have the text sent later, after any other messages are scheduled, or click :guilabel:`Send Now` to send the message immediately." msgstr "" @@ -9049,95 +8878,95 @@ msgstr "" msgid "Send a text message to the attendees of the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:987 +#: ../../content/applications/hr/recruitment.rst:723 msgid "Sending text messages is not a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../essentials/in_app_purchase` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:994 +#: ../../content/applications/hr/recruitment.rst:730 msgid "Second interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:996 +#: ../../content/applications/hr/recruitment.rst:732 msgid "After an applicant has passed the :guilabel:`First Interview` stage, they can be moved to the :guilabel:`Second Interview` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Second Interview` stage, or click on the :guilabel:`Second Interview` stage button at the top of the individual applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1001 +#: ../../content/applications/hr/recruitment.rst:737 msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as the first interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1009 +#: ../../content/applications/hr/recruitment.rst:745 msgid "Contract proposal" msgstr "" -#: ../../content/applications/hr/recruitment.rst:1011 +#: ../../content/applications/hr/recruitment.rst:747 msgid "When the applicant has passed the interview stages and an offer is ready to be sent, they can be moved to the :guilabel:`Contract Proposal` stage. Drag and drop the applicant's card to the :guilabel:`Contract Proposal` stage, or click on the :guilabel:`Contract Proposal` stage button at the top-right of the individual applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1016 +#: ../../content/applications/hr/recruitment.rst:752 msgid "The next step is to send an offer to the applicant. On the applicant's card, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up appears. Most fields are pre-populated with information from the job position. If any necessary fields are blank, enter the relevant information in the fields." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1022 +#: ../../content/applications/hr/recruitment.rst:758 msgid "Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-up. Depending on the localization setting for the company and the applications installed, some fields may not appear. For example if the *Fleet* application is not installed, any fields related to vehicles do not appear on the pop-up window." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1028 +#: ../../content/applications/hr/recruitment.rst:764 msgid "Universal fields" msgstr "" -#: ../../content/applications/hr/recruitment.rst:1030 +#: ../../content/applications/hr/recruitment.rst:766 msgid "The following fields appear for all offers sent to applicants regardless of localization settings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1032 +#: ../../content/applications/hr/recruitment.rst:768 msgid ":guilabel:`Contract Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up window. To modify the template, click the :guilabel:`Internal link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save & Close`. A different :guilabel:`Contract Template` can be selected using the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1037 +#: ../../content/applications/hr/recruitment.rst:773 msgid ":guilabel:`Job Position`: the name of the :guilabel:`Job Position` being offered to the applicant. The selections available in the drop-down menu correspond to the :guilabel:`Job Positions` configured on the main *Recruitment* dashboard." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1040 +#: ../../content/applications/hr/recruitment.rst:776 msgid ":guilabel:`Job Title`: the specific name of the position being offered to the applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1041 +#: ../../content/applications/hr/recruitment.rst:777 msgid ":guilabel:`Department`: the :guilabel:`Department` the job position falls under." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1042 +#: ../../content/applications/hr/recruitment.rst:778 msgid ":guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the current date. To modify the date, click the drop-down to reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1046 +#: ../../content/applications/hr/recruitment.rst:782 msgid ":guilabel:`Yearly Cost`: the annual salary being offered." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1047 +#: ../../content/applications/hr/recruitment.rst:783 msgid ":guilabel:`Link Expiration Date`: job offers are only valid for a specific period of time. The default expiration date is 30 days. Modify the expiration date, if desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1051 +#: ../../content/applications/hr/recruitment.rst:787 msgid "Send offer" msgstr "" -#: ../../content/applications/hr/recruitment.rst:1053 +#: ../../content/applications/hr/recruitment.rst:789 msgid "When the information is all updated, click :guilabel:`Send By Email` to send the offer to the applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1056 +#: ../../content/applications/hr/recruitment.rst:792 msgid "If the applicant does not have an email address listed on their applicant card, a warning appears in a red box at the bottom of the :guilabel:`Generate a Simulation Link` pop-up window, stating :guilabel:`The applicant does not have a valid email set. The Offer Link won't be able to be completed.` Click :guilabel:`Discard`, enter an email on the applicant's card, then click the :guilabel:`Generate Offer` button again." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1062 +#: ../../content/applications/hr/recruitment.rst:798 msgid "An email pop-up window loads. The default :guilabel:`Recruitment: Your Salary Package` email template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1070 +#: ../../content/applications/hr/recruitment.rst:806 msgid "Once the email is ready to send, click :guilabel:`Send`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1073 +#: ../../content/applications/hr/recruitment.rst:809 msgid "To send an offer, ensure the *Sign* application is installed. This is necessary so the offer can be sent to the applicant by the recruiter. The applicant does not need any software installed." msgstr "" @@ -9145,39 +8974,39 @@ msgstr "" msgid "Send an email to the applicant with a link to the offered salary." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1081 +#: ../../content/applications/hr/recruitment.rst:817 msgid "Configure your package" msgstr "" -#: ../../content/applications/hr/recruitment.rst:1083 +#: ../../content/applications/hr/recruitment.rst:819 msgid "The email template includes a :guilabel:`Configure your package` button. This link takes the applicant to a webpage where they can modify the proposed salary package, and enter their personal information." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1087 +#: ../../content/applications/hr/recruitment.rst:823 msgid "Once the applicant is hired, the personal information entered on the webpage is imported to their employee record, when created." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1090 +#: ../../content/applications/hr/recruitment.rst:826 msgid "If applicable, the applicant can modify their salary package. This option is not available for all localizations. Depending on where the company is located, this option may not be available." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1093 +#: ../../content/applications/hr/recruitment.rst:829 msgid "Once all the information is completed, the applicant accepts the offer by clicking the :guilabel:`Review Contract & Sign` button to accept the contract and sign it using the *Sign* application." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1100 +#: ../../content/applications/hr/recruitment.rst:836 msgid "Contract signed" msgstr "" -#: ../../content/applications/hr/recruitment.rst:1102 +#: ../../content/applications/hr/recruitment.rst:838 msgid "Once the applicant has accepted the offer and signed the contract, the next step is to move the applicant to the :guilabel:`Contract Signed` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Contract Signed` stage, or click the :guilabel:`More` button at the top of the applicant's card to reveal the :guilabel:`Contract Signed` stage button at the top of the individual applicant's card, and click :guilabel:`Contract Signed`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1109 +#: ../../content/applications/hr/recruitment.rst:845 msgid "The :guilabel:`Contract Signed` stage is folded in the Kanban view, but the card may still be dragged and dropped into that stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1112 +#: ../../content/applications/hr/recruitment.rst:848 msgid "Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a green :guilabel:`HIRED` banner appears in the top-right of the applicant's card." msgstr "" @@ -9185,18 +9014,215 @@ msgstr "" msgid "Hired banner in the top right corner of applicant card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1120 +#: ../../content/applications/hr/recruitment.rst:856 msgid "Create employee" msgstr "" -#: ../../content/applications/hr/recruitment.rst:1122 +#: ../../content/applications/hr/recruitment.rst:858 msgid "Once the applicant has been hired, the next step is to create an employee record of them. On the applicant's card, click the :guilabel:`Create Employee` button in the top-left. An employee form appears, and any information from the applicant's card that can be imported into the employee card appears in the form." msgstr "" -#: ../../content/applications/hr/recruitment.rst:1127 +#: ../../content/applications/hr/recruitment.rst:863 msgid "Fill out the rest of the form. For detailed information on the fields, refer to the :doc:`employees/new_employee` documentation. When done, the employee record is saved in the *Employees* app." msgstr "" +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "Once an applicant submits an application, either using the online application, or emailing a job position alias, an applicant card is automatically created in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "However, in some instances, applicants may need to be created manually in the database. This could be necessary if, for example, a company accepts paper applications in the mail, or is meeting prospective applicants at an in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "To view current applicants, navigate to the :menuselection:`Recruitment` app, then click the desired job position card. Doing so reveals the :guilabel:`Applications` page, which displays all applicants for that specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "Add new applicants from a job position's :guilabel:`Applications` page by using either: the :ref:`New ` button or the :ref:`quick add ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "On the :guilabel:`Applications` page, click the on the quick add button, represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-right corner of each stage to quickly add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid ":guilabel:`Subject/Application`: enter the title for the card. Typically, this is the applicant's name, and job position being applied to. For example: `Laura Smith - HR Manager`. The text entered in this field is **not** visible in the Kanban view of the :guilabel:`Applications` page, unless the :guilabel:`Applicant's Name` field is left blank." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid ":guilabel:`Applicant's Name`: enter the applicant's name. Displays as the card title in the Kanban view of the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:37 +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid ":guilabel:`Email`: enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:38 +msgid ":guilabel:`Applied Job`: the current job position populates this field. If needed, the job position can be changed by selecting a different position from the drop-down menu. If a different job position is selected, after the card is created, the card appears on the :guilabel:`Applications` page for that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "After the information is entered, click :guilabel:`Add`. The applicant appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:46 +msgid "If preferred, after entering the :guilabel:`Applicant's Name` in the Kanban card that appears, click :guilabel:`Edit`, and a detailed applicant form loads. Refer to the :ref:`New applicant form ` section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:50 +msgid "When doing a quick add, clicking away from an empty card, or clicking the :icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields for a new applicant form entered when using the Quick Add option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:60 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:62 +msgid "On the new applicant form, the :guilabel:`Subject / Application` field is populated with the pre-selected job position, by default. Certain fields on the applicant card may also be pre-populated, depending on how the job position is configured. Typically, the :guilabel:`Job` section, as well as the :guilabel:`Recruiter` field, are pre-populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:67 +msgid "Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:70 +msgid "Depending on installed applications and configurations, some fields may **not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:79 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:81 +msgid ":guilabel:`Subject/Application Name`: this is the **only** required field. Enter the title for the card in this field. Typically, this is the applicant's name, and the job position being applied to. For example: `John Smith - Experienced Developer`. This field is **not** visible in the Kanban view of the :guilabel:`Applications` page, unless the :guilabel:`Applicant's Name` is left blank." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid ":guilabel:`Applicant's Name`: enter the applicant's name. This field is displayed as the card title in the Kanban view of the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:88 +msgid ":guilabel:`Phone`: enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid ":guilabel:`Mobile`: enter the applicant's mobile number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:90 +msgid ":guilabel:`LinkedIn Profile`: enter the web address for the applicant's personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:92 +msgid ":guilabel:`Degree`: select the applicant's highest level of education from the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The :guilabel:`Graduate` option indicates the applicant graduated at the highest level of school before a Bachelor's degree, such as a high school or secondary school diploma, depending on the country." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:97 +msgid ":guilabel:`Interviewers`: using the drop-down menu, select the people to conduct the interviews. The selected people **must** have either *recruiter* or *officer* rights configured for the *Recruitment* application to appear in the drop-down list. Refer to the :doc:`Access rights <../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:101 +msgid ":guilabel:`Recruiter`: select the user responsible for the entire recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid ":guilabel:`Evaluation`: represents a rating for the applicant: one star (:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is :guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:107 +msgid ":guilabel:`Source`: using the drop-down menu, select where the applicant learned about the job position. The following options come pre-configured in Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, :guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`Twitter`, :guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and :guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source, then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:112 +msgid ":guilabel:`Medium`: using the drop-down menu, specify how the job listing was found. The pre-configured options are: :guilabel:`Banner`, :guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, :guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, :guilabel:`Television`, :guilabel:`Twitter` (now known as \"X\"), or :guilabel:`Website`. To add a new :guilabel:`Medium`, type in the medium, then click :guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:117 +msgid ":guilabel:`Referred By User`: if referral points are to be earned for this job position in the *Referrals* application, select the user who referred the applicant from the drop-down menu. The *Referrals* application **must** be installed for this field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:120 +msgid ":guilabel:`Availability`: select the available start date for the applicant. To select a date, click on the field to reveal a popover calendar. Use the :icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` :guilabel:`(right)` arrows on either side of the month to navigate to the desired month, then click the desired date. Leaving this field blank indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:125 +msgid ":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To add a tag that does not exist, type in the tag name, then click :guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "The following fields are pre-populated when creating a new applicant, as long as these field are specified on the job position form. Editing the fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid ":guilabel:`Applied Job`: select the job position the applicant is applying to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:137 +msgid ":guilabel:`Department`: select the department the job position falls under from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:139 +msgid ":guilabel:`Company`: select the company the job position is for using the drop-down menu. This field **only** appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:143 +msgid "Contract section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:145 +msgid ":guilabel:`Expected Salary`: enter the amount the applicant is requesting in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:149 +msgid ":guilabel:`Extra advantages...`: if any extra advantages are requested by the applicant, enter it in the :guilabel:`Extra advantages...` field to the right of the :guilabel:`Expected Salary` field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid ":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant for the role in this field. The number should be in a `XX,XXX.XX` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:156 +msgid ":guilabel:`Extra advantages...`: if any extra advantages are offered to the applicant, enter it in the :guilabel:`Extra advantages...` field to the right of the :guilabel:`Proposed Salary` field. This should be short and descriptive, such as `unlimited sick time` or `retirement plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "Application Summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:163 +msgid "Any additional details or notes that should be added to the applicant's card can be typed into this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:169 +msgid "Skills can be added to the applicant's card. For details on adding skills, refer to the :ref:`Create new employees ` document." +msgstr "" + #: ../../content/applications/hr/recruitment/new_job.rst:5 msgid "In Odoo *Recruitment*, all job positions are shown on the default dashboard in the *Recruitment* app. This includes positions that are being actively recruited for, as well as inactive positions." msgstr "" @@ -9369,6 +9395,202 @@ msgstr "" msgid "Proceed to fill out the modal interview form as a typical survey. For specific directions on how to create a survey, refer to the :doc:`survey essentials <../../marketing/surveys/create>` document, which provides step-by-step instructions on how to create and configure a survey." msgstr "" +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "At any point in the recruitment process, an applicant can be refused for a job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "To refuse an applicant, start by navigating to the applicant's card in the *Recruitment* app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "Navigate to :menuselection:`Recruitment app --> Applications --> All Applications`. In the :guilabel:`Applications` list, click anywhere on the desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "Navigate to the main *ob Positions* dashboard by navigating to :menuselection:`Recruitment app --> Applications --> By Job Position`. Next, click on the desired job position card, then click on the individual applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "At the top of the applicant's card, there are several buttons. Click the one labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "*Refuse reasons* allow recruiters to document why an applicant was not a good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "Clicking :guilabel:`Refuse` on an applicant's form makes the :guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "The default refuse reasons in Odoo, and their corresponding email templates, are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Doesn't fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Language issues`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Role already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:45 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by Applicant: don't like job`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by Applicant: better offer`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by Applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:50 +msgid "Additional refusal reasons :ref:`can be created, and existing ones can be modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:53 +msgid "Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:60 +msgid "To view and configure refuse reasons, navigate to :menuselection:`Recruitment app --> Configuration --> Applications: Refuse Reasons`. Doing so reveals the :guilabel:`Refuse Reasons` page, where all the existing refuse reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:64 +msgid "To create a new refuse reason from the :guilabel:`Refuse Reasons` page, click the :guilabel:`New` button in the top-left corner. A blank line appears at the bottom of the list, with an empty field present in the :guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:68 +msgid "Type in the new refuse reason in the field. It is recommended to enter a reason that is short and concise, such as `Offer expired` or `Withdrew application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:71 +msgid "Then, in the :guilabel:`Email Template` field, click on the field to reveal a drop-down menu. Select an :guilabel:`Email Template` from the list to be used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:74 +msgid "If a new :guilabel:`Email Template` is desired, type in the name for the new template in the field. Then, click :guilabel:`Create and edit...`, and a :guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:78 +msgid "In the :guilabel:`Create Email Template` pop-up window, enter a :guilabel:`Name` for the form, and an email :guilabel:`Subject` in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:81 +msgid "Enter the desired email content in the :guilabel:`Content` tab. Proceed to make any other modifications to the template in the :guilabel:`Email Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & Close` to save the template. Upon clicking that, Odoo returns to the :guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:86 +msgid "The new template appears in the new refuse reason :guilabel:`Email Template` field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:89 +msgid "Pre-configured recruitment refusal email templates in Odoo use dynamic placeholders, which are personalized placeholders that populate data from the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:92 +msgid "For example, if the applicant's name is a used in a dynamic placeholder, the applicant's name appears anytime that dynamic placeholder appears on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:95 +msgid "For more detailed information on email templates, refer to the :doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:103 +msgid "After clicking the :guilabel:`Refuse` button on an applicant form, a :ref:`Refuse Reason ` can be selected from the :guilabel:`refuse reason` pop-up window. Then, two fields appear below the selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "The applicant's email address automatically populates the :guilabel:`Send Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:115 +msgid "If an email should **not** be sent to the applicant, uncheck the :guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:117 +msgid "The email template associated with the refusal reason populates the :guilabel:`Email Template` field. If a different email template is desired, select a different template from the :guilabel:`Email Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:121 +msgid "To send the refusal email to the applicant, ensure the :guilabel:`Send Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to the applicant, and a red :guilabel:`Refused` banner appears on the applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "An applicant's card with the refused banner appearing in the top-right corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:131 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:133 +msgid "After refusal, the applicant's card is no longer visible in the job position's Kanban view. However, it is still possible to view applicants who have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:136 +msgid "To view only the refused applicants, go to :menuselection:`Recruitment app --> Applications --> By Job Positions`, or :menuselection:`Recruitment app --> Applications --> All Applications`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:139 +msgid "On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` :guilabel:`(caret down)` button in the :guilabel:`Search...` bar, then click :guilabel:`Refused`, located under the :guilabel:`Filters` section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:143 +msgid "All applicants that have been refused for the job position appear on the :guilabel:`Applications` page for that position, organized by the stage they were in when they were refused." +msgstr "" + #: ../../content/applications/hr/referrals.rst:5 msgid "Referrals" msgstr "" @@ -9378,7 +9600,7 @@ msgid "Odoo's *Referrals* application is a centralized place where all informati msgstr "" #: ../../content/applications/hr/referrals.rst:14 -msgid "The only configurations needed for the *Referrals* application *after* installation are related to the :ref:`rewards `; everything else is pre-configured when Odoo *Referrals* is installed." +msgid "The only configurations needed for the *Referrals* application *after* it has been installed, are related to the :doc:`rewards `; everything else is pre-configured when Odoo *Referrals* is installed." msgstr "" #: ../../content/applications/hr/referrals.rst:18 @@ -9519,7 +9741,7 @@ msgid "A friend form in edit mode." msgstr "" #: ../../content/applications/hr/referrals.rst:163 -#: ../../content/applications/hr/referrals.rst:358 +#: ../../content/applications/hr/referrals.rst:293 msgid "It is not advised to edit the images. An image file must have a transparent background in order for it to render properly. Only users with knowledge about transparent images should attempt adjusting any images in the *Referrals* application." msgstr "" @@ -9612,111 +9834,42 @@ msgid "The total points earned for a referral that is hired is 85 points. Modifi msgstr "" #: ../../content/applications/hr/referrals.rst:244 -msgid "Rewards" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:247 -msgid "Create rewards" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:249 -msgid "The rewards are the only configurations needed when setting up the *Referrals* application. Only users with :guilabel:`Administrator` rights for the *Recruitment* application can create or modify rewards. To add rewards, navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the following information on the form:" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:254 -msgid ":guilabel:`Product Name`: enter the name as it should appear for the reward." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:255 -msgid ":guilabel:`Cost`: enter the amount of points required to redeem the reward." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:256 -msgid ":guilabel:`Company`: using the drop-down menu, select the company the reward appears for. If a reward is to be used for several companies, each company needs to have a record of the reward, with the company listed on the form. This field only appears if in a multi-company environment." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:259 -msgid ":guilabel:`Gift Responsible`: select the person who will be responsible for procuring and delivering the reward to the recipient, using the drop-down menu. This person is alerted when the reward is bought in the *Referrals* application, so they know when to deliver the reward to the recipient." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:263 -msgid ":guilabel:`Description`: type in the description for the reward. This will be visible on the reward card, beneath the title." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:265 -msgid ":guilabel:`Photo`: add a photo of the reward, which appears on the rewards page. Hover over the image square, and two icons appear, a :guilabel:`✏️ (pencil)` and a :guilabel:`🗑️ (garbage can)`. Click the :guilabel:`✏️ (pencil)` icon, and a file explorer appears. Navigate to the photo file, then click :guilabel:`Open` to select it." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:270 -msgid "The only required fields are the :guilabel:`Product Name`, :guilabel:`Company` (if applicable), and :guilabel:`Description`." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "A filled out reward form with all details entered." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:278 -msgid "It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a cost is not entered, the default cost will be listed as zero, which would list the reward as free in the reward shop. If a photo is not selected, a placeholder icon will be displayed on the rewards page." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:283 -msgid "Redeem rewards" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:285 -msgid "To redeem points for a reward, click the :guilabel:`Rewards` button on the main Referrals dashboard. All the configured rewards are listed in individual reward cards. The points required to purchase the reward is listed in the top-right corner of the card. If the user has enough points to purchase a reward, a :guilabel:`🧺 (basket) Buy` button appears at the bottom of the reward card. If they do not have enough points for a reward, the reward card displays :guilabel:`You need another (x) points to buy this` instead of a buy button." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:292 -msgid "Click the :guilabel:`🧺 (basket) Buy` button on a reward to purchase it. A :guilabel:`Confirmation` pop-up window appears, asking if the user is sure they want to purchase the reward. Click :guilabel:`OK` to purchase the item, or :guilabel:`Cancel` to close the window and cancel the purchase." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:297 -msgid "After :guilabel:`OK` is clicked, the pop-up window closes, and the points used to purchase the reward are subtracted from the user's available points. The rewards presented are now updated to reflect the user's current available points." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "Buy button appears below a mug and backpack reward, while the bicycle reward states how\n" -"many more reward points are needed to redeem." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:309 msgid "Levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:311 +#: ../../content/applications/hr/referrals.rst:246 msgid "The *Referrals* application has pre-configured levels that are reflected in the user's avatar on the Referrals dashboard. As a user refers potential employees and earns points, they can *level up*, much like in a video game." msgstr "" -#: ../../content/applications/hr/referrals.rst:315 +#: ../../content/applications/hr/referrals.rst:250 msgid "Levels have no functional impact on the performance of the application. They are solely used for the purpose of adding achievement tiers for participants to aim for, gamifying referrals for the user." msgstr "" -#: ../../content/applications/hr/referrals.rst:318 +#: ../../content/applications/hr/referrals.rst:253 msgid "The user's current level is displayed at the top of the main *Referrals* application dashboard, directly beneath their photo, in a :guilabel:`Level: X` format. In addition, a colored ring appears around the user's photo, indicating how many points the user currently has, and how many additional points they need to level up. The cyan colored portion of the ring represents points earned, while the white colored portion represents the points still needed before they can level up." msgstr "" -#: ../../content/applications/hr/referrals.rst:325 +#: ../../content/applications/hr/referrals.rst:260 msgid "Modify levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:327 +#: ../../content/applications/hr/referrals.rst:262 msgid "Only users with :guilabel:`Administrator` rights for the *Recruitment* application can modify levels. The pre-configured levels can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Levels`. Each avatar appears in the :guilabel:`Image` column, and the corresponding level number appears in the :guilabel:`Level Name` column. The default images are of Odoo superheroes, and each level adds an additional element to their avatar, such as capes and shields." msgstr "" -#: ../../content/applications/hr/referrals.rst:334 +#: ../../content/applications/hr/referrals.rst:269 msgid "To modify a level's image, name, or points required to reach the level, click on an individual level in the list to open the level form, then make modifications." msgstr "" -#: ../../content/applications/hr/referrals.rst:337 +#: ../../content/applications/hr/referrals.rst:272 msgid "Type in the name (or number) of the level in the :guilabel:`Level Name` field. What is entered is displayed beneath the user's photo on the main dashboard when they reach that level. Enter the number of referral points needed to reach that level in the :guilabel:`Requirements` field. The points needed to level up are the total accumulated points earned over the lifetime of the employee, not additional points from the previous level that must be earned." msgstr "" -#: ../../content/applications/hr/referrals.rst:343 +#: ../../content/applications/hr/referrals.rst:278 msgid "If desired, the :guilabel:`Image` can also be modified. Hover over the image to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon, and a file explorer window appears. Navigate to the desired image file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:348 +#: ../../content/applications/hr/referrals.rst:283 msgid "The level form saves automatically, but can be saved manually at any time by clicking the *save manually* option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner. To cancel any changes made, click the :guilabel:`✖️ (Discard all changes)` icon to delete any changes, and revert to the original content." msgstr "" @@ -9724,23 +9877,23 @@ msgstr "" msgid "A level form in edit mode." msgstr "" -#: ../../content/applications/hr/referrals.rst:362 +#: ../../content/applications/hr/referrals.rst:297 msgid "Once an image is changed and the level is saved, it is **not possible** to revert to the original image. To revert to the original image, the *Referrals* application must be *uninstalled then reinstalled.*" msgstr "" -#: ../../content/applications/hr/referrals.rst:367 +#: ../../content/applications/hr/referrals.rst:302 msgid "Level up" msgstr "" -#: ../../content/applications/hr/referrals.rst:369 +#: ../../content/applications/hr/referrals.rst:304 msgid "Once enough points have been accumulated to level up, the circle around the user's photo is completely filled in with a cyan color, a large image stating :guilabel:`Level up!` appears above the photo, and the phrase :guilabel:`Click to level up!` appears beneath the user's photo and current level." msgstr "" -#: ../../content/applications/hr/referrals.rst:374 +#: ../../content/applications/hr/referrals.rst:309 msgid "Click on either the :guilabel:`LEVEL UP!` graphic, the user's photo, or the text :guilabel:`Click to level up!` beneath the user's photo to level up the user. The user's avatar changes to the current level, and the ring around the photo is updated to indicate the current amount of points." msgstr "" -#: ../../content/applications/hr/referrals.rst:378 +#: ../../content/applications/hr/referrals.rst:313 msgid "Leveling up does not cost the user any points, the user simply needs to earn the specified amount of points required." msgstr "" @@ -9749,94 +9902,219 @@ msgid "A 'Click to level up!' appears beneath the user's image, and a large 'Lev "above their image." msgstr "" -#: ../../content/applications/hr/referrals.rst:387 +#: ../../content/applications/hr/referrals.rst:322 msgid "Once a user has reached the highest configured level, they will continue to accrue points that can be redeemed for rewards, but they are no longer able to level up. The ring around their photo remains solid cyan." msgstr "" -#: ../../content/applications/hr/referrals.rst:394 -msgid "In the *Referrals* application, it is possible to post a message, also referred to as an *alert*, at the top of the dashboard to share important information with users. These alerts appear as a thin semi-transparent banner, with the word :guilabel:`New!` appearing on the far left. The text for the alert is in the center of the banner, and on the far right side is an :guilabel:`X`." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:399 -msgid "Alerts appear on the main dashboard for the specified time configured on the individual alert. If a user does not wish to see a specific alert again, click the :guilabel:`X` in the far right side of the alert. This removes the alert from the dashboard and will not appear again, even when opening the *Referrals* application for the first time in a new session." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "Two alert banners appear above the user's photo." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:409 -msgid "Create an alert" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:411 -msgid "Only users with :guilabel:`Administrator` rights for the *Recruitment* application can create alerts. To add a new alert, navigate to the :menuselection:`Referrals application --> Configuration --> Alerts`." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:415 -msgid "Click :guilabel:`Create` and a blank alert form loads. Enter the following information on the form:" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:417 -msgid ":guilabel:`Date From`: the date the alert starts. On this date, the alert will be visible on the dashboard." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:419 -msgid ":guilabel:`Date To`: the date the alert ends. After this date, the alert will be hidden from view." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:420 -msgid ":guilabel:`Company`: the current company populates this field by default. To modify the company the alert should be displayed for, select the company from the drop-down menu. If this field remains blank, the alert is visible to everyone with access to the *Referrals* application. If a company is specified, only user's within that company (who also have access to the *Referrals* application) will see the alert. This field only appears when in a multi-company database." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:425 -msgid ":guilabel:`Alert`: enter the text for the alert. This message appears inside the alert banner on the main dashboard." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:427 -msgid ":guilabel:`On Click`: there are three options for the alert. Click the radio button next to the desired selection. The options are:" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:430 -msgid ":guilabel:`Not Clickable`: the alert only displays text, there is no link to click." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:431 -msgid ":guilabel:`Go to All Jobs`: the alert contains a link that when clicked, navigates to the website with all the currently posted job positions." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:433 -msgid ":guilabel:`Specify URL`: the alert contains a link to a specific URL, that when clicked, navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On Click` section. Enter the URL in the field." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "An alert form completely filled in with all selections entered." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:446 +#: ../../content/applications/hr/referrals.rst:331 msgid "Only users with :guilabel:`Administrator` rights for the *Recruitment* application have access to the Reporting feature in *Referrals*. To access the reports, click :menuselection:`Referrals application --> Reporting`. The main view is the Reporting Dashboard view, which contains three sections." msgstr "" -#: ../../content/applications/hr/referrals.rst:451 +#: ../../content/applications/hr/referrals.rst:336 msgid "In the top portion of the window, the report displays a bar chart of how many referred candidates are hired, and how many are still in the hiring pipeline. The candidates are further divided by channel, showing specifically where the referral came from, such as a direct referral, Facebook, etc. If a channel does not appear on the report, that indicates there are no referrals from that particular channel." msgstr "" -#: ../../content/applications/hr/referrals.rst:457 +#: ../../content/applications/hr/referrals.rst:342 msgid "The middle third provides all the specific data that has been tracked. This includes how many total points have been earned across all referrals, how many applicants were referred, hired, or refused, how many applicants the current logged-in user referred, how many total points were earned, and how many points were given for refused applicants." msgstr "" -#: ../../content/applications/hr/referrals.rst:462 +#: ../../content/applications/hr/referrals.rst:347 msgid "The bottom third displays a pivot table. This table can be inserted into a new or existing spreadsheet. To do so, click the :guilabel:`Insert in Spreadsheet` button right above the chart. A pop-up appears, asking which spreadsheet to insert the pivot chart into. Select the desired spreadsheet from the drop-down menu, or select :guilabel:`New Spreadsheet`. Click :guilabel:`Confirm` and the selected spreadsheet loads, with the new table in it." msgstr "" -#: ../../content/applications/hr/referrals.rst:469 +#: ../../content/applications/hr/referrals.rst:354 msgid "The spreadsheet is stored in the *Documents* application. This application needs to be installed to use the :guilabel:`Insert in Spreadsheet` option." msgstr "" -#: ../../content/applications/hr/referrals.rst:473 +#: ../../content/applications/hr/referrals.rst:358 msgid ":doc:`referrals/share_jobs`" msgstr "" +#: ../../content/applications/hr/referrals.rst:359 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:360 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +msgid "In the *Referrals* application, it is possible to post a message, also referred to as an *alert*, at the top of the dashboard to share important information with users." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "Alerts remain on the main *Referrals* dashboard for the specified amount of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:16 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:18 +msgid "Only users with *Administrator* access rights for the *Recruitment* application can create alerts. To add a new alert, navigate to the :menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:21 +msgid "Click :guilabel:`New` to open a blank alert form. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:23 +msgid ":guilabel:`Date From`: the date the alert starts. On this date, the alert is visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:25 +msgid ":guilabel:`Date To`: the date the alert ends. After this date, the alert is hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid ":guilabel:`Company`: the current company populates this field, by default. To modify the company the alert should be displayed for, select the desired company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:30 +msgid "If this field remains blank, the alert is visible to everyone with access to the *Referrals* application." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:33 +msgid "If a company is specified, only users within that company (who also have access to the *Referrals* application) see the alert. This field **only** appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:35 +msgid ":guilabel:`Alert`: enter the text for the alert. This message appears inside the alert banner on the main *Referrals* dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:37 +msgid ":guilabel:`On Click`: there are three options for the alert. Click the radio button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:40 +msgid ":guilabel:`Not Clickable`: the alert only displays text, there is no link to click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:41 +msgid ":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, navigates to the website with all the job positions that are currently posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:43 +msgid ":guilabel:`Specify URL`: the alert contains a link to a specific URL that, when clicked, navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On Click` section. Enter the desired URL in that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "It is possible to dismiss an alert, if a user does not wish to see a specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:56 +msgid "To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on the far-right side of the alert to remove the alert from the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:59 +msgid "This prevents the alert from appearing again, even when opening the *Referrals* application for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "After employees have successfully earned referral points, they can exchange their points by purchasing rewards in Odoo's *Referrals* application. Rewards **must** be :ref:`created and configured ` before employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "Rewards are the only configurations needed when setting up the *Referrals* application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "Only users with :guilabel:`Administrator` rights for the *Recruitment* application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:20 +msgid "To add rewards, navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid ":guilabel:`Product Name`: enter the name as it should appear for the reward. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:25 +msgid ":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid ":guilabel:`Company`: using the drop-down menu, select the company the reward is configured for. If a reward is available for multiple companies, each company **must** configure a reward for their specific company. This field **only** appears if in a multi-company environment; if this field appears, it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:32 +msgid "A corporation with three different companies offers a gift card as a reward. In the database, there are three separate rewards listed for a gift card, one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid ":guilabel:`Gift Responsible`: using the drop-down menu, select the person responsible for procuring and delivering the reward to the recipient. This person is alerted when the reward is bought in the *Referrals* application, so they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid ":guilabel:`Photo`: add a photo of the reward, which appears on the rewards page. Hover over the image box in the top-right corner (a square with a camera and plus sign inside it), and a :icon:`fa-pencil` :guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` :guilabel:`(pencil)` icon to select and add a photo to the reward form. Once a photo is added, hovering over the image reveals two icons instead of one: a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` :guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:45 +msgid ":guilabel:`Description` tab: type in the description for the reward. This is visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:53 +msgid "It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a cost is not entered, the default cost is listed as zero, which would list the reward as free in the reward shop. If a photo is not selected, a placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:60 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "In order to redeem a reward, points must be earned. These points can then be used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:65 +msgid "To purchase a reward, click the :guilabel:`Rewards` button on the main :guilabel:`Referrals` dashboard. All the configured rewards are listed in individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:68 +msgid "The required point amount needed to purchase a reward is listed in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "If the user has enough points to purchase a reward, a :icon:`fa-shopping-basket` :guilabel:`Buy` button appears at the bottom of the reward card. If they do not have enough points for a reward, the reward card displays :guilabel:`You need another (x) points to buy this`, instead of a :icon:`fa-shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:75 +msgid "Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to purchase it. A :guilabel:`Confirmation` pop-up window appears, asking if the user is sure they want to purchase the reward. Click :guilabel:`OK` to purchase the item, or :guilabel:`Cancel` to close the window, and cancel the purchase." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:80 +msgid "After :guilabel:`OK` is clicked, the pop-up window closes, and the points used to purchase the reward are subtracted from the user's available points. The rewards presented are now updated to reflect the user's current available points." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "Buy button appears below a mug and backpack reward, while the bicycle reward states how\n" +"many more reward points are needed to redeem." +msgstr "" + #: ../../content/applications/hr/referrals/share_jobs.rst:3 msgid "Share job positions" msgstr "" @@ -10340,10 +10618,6 @@ msgstr "" msgid "To create a new rule, click the :guilabel:`New Milestone` button in the gray :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:268 -msgid "Fill out the following fields on the form:" -msgstr "" - #: ../../content/applications/hr/time_off.rst:270 msgid ":guilabel:`Employee accrue`: select the parameters for earned time off in this section." msgstr "" @@ -10696,175 +10970,46 @@ msgid "An allocation request form filled out for an employee requesting an addit msgstr "" #: ../../content/applications/hr/time_off.rst:553 -msgid "Management" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:555 -msgid "Time off and allocation requests typically undergo an approval process before being granted. Requests either need one or two approvals, if any, depending on how the specific type of time off is configured. These are all housed under the :guilabel:`Management` section of the *Time Off* application." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:560 -msgid "Only users who can approve allocation and time off requests have the :guilabel:`Management` section visible in the *Time Off* application." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:566 -msgid "Manage time off" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:568 -msgid "To view time off requests that need approval, navigate to :menuselection:`Time Off app --> Management --> Time Off`. The only time off requests visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:573 -msgid "The default filter in the :guilabel:`Time Off` list is `Waiting For Me`. This only presents time off requests that need to be approved for current employees on the user's team, with a status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:577 -msgid "The left side of the screen has various grouping options to narrow down the presented time off requests. Since only time off requests that need to be approved are shown, the only status options are :guilabel:`All`, :guilabel:`To Approve`, and :guilabel:`Second Approval`. The various departments the user is a member of, and manages employees under, also appear on the left side of the screen, under :guilabel:`Departments`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:584 -msgid "If there are no requests that fall under one of the status options or departments, that status or department is **not** visible on the left-side menu." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:587 -msgid "To display time off requests for specific departments only, click on the :guilabel:`Department` on the left-hand side. Only requests within the selected department are then presented." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:590 -#: ../../content/applications/hr/time_off.rst:657 -msgid "The status column displays the status of each request, with the status highlighted in a specific color." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:593 -msgid "The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are highlighted in yellow and are the only ones that appear in the list by default. If the `Waiting For Me` filter is removed, then all statuses appear. :guilabel:`Approved` requests are highlighted in green, :guilabel:`To Submit` (drafts) requests are highlighted in blue, and the :guilabel:`Refused` requests are highlighted in gray." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:599 -msgid "To approve a time off request, click the :guilabel:`👍 Approve` button at the end of the line. To validate a time off request that has already been approved, and is waiting on a second approval, click the :guilabel:`✔️ Validate` button at the end of the line. To refuse a request, click the :guilabel:`✖️ Refuse` button at the far end of the line." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:-1 -msgid "Time off requests with the filter, groupings, and status sections highlighted." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:608 -msgid "For more details, click anywhere on the time off request line (except for the :guilabel:`👍 Approve`, :guilabel:`✔️ Validate`, and :guilabel:`✖️ Refuse` buttons) to load the time off request form. Depending on the rights of the user, changes can be made." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:612 -msgid "To modify the request, make any desired changes to the form. All changes are automatically saved." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:614 -msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button to refuse the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:620 -msgid "Manage allocations" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:622 -msgid "To view allocations that need approval, navigate to :menuselection:`Time Off app --> Management --> Allocations`. The only allocations visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:627 -msgid "The default filters that are configured to be in place when navigating to the :guilabel:`Allocations` list are :guilabel:`My Team` and :guilabel:`Active Employee`. This *only* presents employees on the user's team (who they manage) and active employees. Inactive users are not shown." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:632 -msgid "The left side of the screen has various grouping options to narrow down the presented allocation requests." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:635 -msgid "The :guilabel:`Status` options are :guilabel:`To Approve`, :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific :guilabel:`Status` to view only requests with that status. To view all allocation requests, click :guilabel:`All`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:639 -msgid "It is also possible to display allocation requests by department. Click on the :guilabel:`Department` in the left side of the screen to only present allocations for that specific department." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:644 -msgid "The groupings on the left side only present allocation requests that fall under the default filters of :guilabel:`My Team` and :guilabel:`Active Employee`. Only the statuses for allocation requests that fall under those filters are presented on the left side." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:648 -msgid "For example, if there are no requests with a status of :guilabel:`To Submit`, that status option does not appear in the left-hand side." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:651 -msgid "All departments for the user's employees appear in the list. If there are no allocation requests that fall under that department matching the pre-configured filters, the list is blank." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:654 -msgid "It is always possible to remove any of the pre-configured filters, by clicking the :guilabel:`✖️ (remove)` icon on the specific filter to remove it." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:660 -msgid "The :guilabel:`To Approve` requests are highlighted in yellow, :guilabel:`Approved` requests are highlighted in green, and the :guilabel:`Refused` requests are highlighted in gray." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:663 -msgid "To approve an allocation request, click the :guilabel:`✔ Validate` button at the end of the line. To refuse a request, click the :guilabel:`✖️ Refuse` button." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:-1 -msgid "Allocations with the filter, groupings, and status sections highlighted." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:670 -msgid "If more details are needed, click anywhere on the allocation request line (except for the :guilabel:`✔ Validate` and :guilabel:`✖️ Refuse` buttons) to view the request in detail." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:673 -msgid "Depending on the rights of the user, changes can be made to the allocation request form that appears. To modify the request, make any desired changes to the form. All changes are automatically saved." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:677 -msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Validate` button to approve, or the :guilabel:`Refuse` button to refuse the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:683 msgid "To view a color-coded schedule of the user's time off, and/or of the team managed by them, navigate to :menuselection:`Time Off app --> Overview`. This presents a calendar with the default filter of `My Team`, in a month view." msgstr "" -#: ../../content/applications/hr/time_off.rst:687 +#: ../../content/applications/hr/time_off.rst:557 msgid "To change the time period displayed, click on the :guilabel:`Month` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Year` to present the calendar in that corresponding view." msgstr "" -#: ../../content/applications/hr/time_off.rst:691 +#: ../../content/applications/hr/time_off.rst:561 msgid "To navigate forward or backward in time, in the selected increment (:guilabel:`Month`, :guilabel:`Week`, etc.), click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` to move either forward or backward in that specified amount of time." msgstr "" -#: ../../content/applications/hr/time_off.rst:695 +#: ../../content/applications/hr/time_off.rst:565 msgid "For example, if :guilabel:`Month` is selected, the arrows adjust the view by one month." msgstr "" -#: ../../content/applications/hr/time_off.rst:697 +#: ../../content/applications/hr/time_off.rst:567 msgid "To return to a view containing the current day, click the :guilabel:`Today` button at any time." msgstr "" -#: ../../content/applications/hr/time_off.rst:699 +#: ../../content/applications/hr/time_off.rst:569 msgid "Team members are listed alphabetically on individual lines, and their requested time off, regardless of the status (*validated* or *to approve*), is visible on the calendar." msgstr "" -#: ../../content/applications/hr/time_off.rst:702 +#: ../../content/applications/hr/time_off.rst:572 msgid "Each employee is color-coded. The employee's color is selected at random, and does *not* correspond to the type of time off they requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:705 +#: ../../content/applications/hr/time_off.rst:575 msgid "The status of the time off is represented by the color detail of the request, either appearing solid (*validated*) or striped (*to approve*)." msgstr "" -#: ../../content/applications/hr/time_off.rst:708 +#: ../../content/applications/hr/time_off.rst:578 msgid "The number of days or hours requested is written on the request (if there is enough space)." msgstr "" -#: ../../content/applications/hr/time_off.rst:710 +#: ../../content/applications/hr/time_off.rst:580 msgid "At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph shows how many people are projected to be out on any given day. The number on each individual bar represents the number of employees out for those highlighted days." msgstr "" -#: ../../content/applications/hr/time_off.rst:714 +#: ../../content/applications/hr/time_off.rst:584 msgid "Click on a time off entry to view the details for the specific time off entry. The total number of hours or days are listed, along with the start and end time of the time off. To view the details of the time off request in a modal, click the :guilabel:`View` button." msgstr "" @@ -10872,139 +11017,31 @@ msgstr "" msgid "Overview of the user's team, with time off requests shown." msgstr "" -#: ../../content/applications/hr/time_off.rst:723 -msgid "My time" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:725 -msgid "The :guilabel:`My Time` section of the *Time Off* application contains the time off dashboard, as well as the user's time off requests and allocations." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:731 -msgid "Dashboard" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:733 -msgid "All users have access to the time off dashboard, which is the default view in the *Time Off* application. The dashboard can also be accessed at any point in the application by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:737 -msgid "The current year is displayed, and the current day is highlighted in red." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:739 -msgid "To change the view, click on the :guilabel:`Year` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month` to present the calendar in that corresponding view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:743 -msgid "To change the presented dates, click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` icons to the left of the :guilabel:`Year` button. The calendar view adjusts in increments of the presented view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:747 -msgid "For example, if :guilabel:`Year` is selected, the arrows adjust the view by one year." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:749 -msgid "To change the view at any point to a view that includes the current date, click the :guilabel:`Today` button." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:752 -msgid "Above the calendar view is a summary of the user's time off balances. Every time off type that has been allocated appears in its own summary box. Each summary lists the type of time off, the corresponding icon, the current available balance (in hours or days), and an expiration date (if applicable)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:757 -msgid "To view the full details of a time off balance, click the :guilabel:`? (question mark)` icon at the end of the :guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete details are presented in a popover window, including the :guilabel:`Allocated` time, future :guilabel:`Accrual` time, :guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and the currently :guilabel:`Available` time off." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:-1 -msgid "A view of the complete time off balance details in the popover window." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:767 -msgid "A user is also able to see how much time off they will have accrued in the future. On the right side of the time off summary blocks, there is a :guilabel:`Balance at the (date)` field. Click on the date, and a calendar selector popover appears." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:771 -msgid "The current date is the default date selected. Navigate to the desired date, and Odoo displays the time off balances the user will have on that date. This takes into account all time off currently planned and approved. To return to the current date, click the :guilabel:`Today` button to the right of the date field." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:776 -msgid "On the right side of the calendar, the various time off types are displayed, with their corresponding colors. The :guilabel:`Legend` explains how the various statuses for time off requests are presented." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:780 -msgid "Time off that has been validated appears in a solid color (in the color specified in the :guilabel:`Time Off Type` section above the :guilabel:`Legend`). Time off requests that still need to be approved appear with white stripes in the color. Refused time off requests have a colored line through the dates." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:785 -msgid "New time off requests can be made from the :guilabel:`Dashboard`. Click the :guilabel:`New` button at the top of the dashboard, and a :doc:`New Time Off <../hr/time_off/request_time_off>` pop-up window appears." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:789 -msgid "New allocation requests can also be made from the :guilabel:`Dashboard`. Click the :guilabel:`New Allocation Request` button at the top of the :guilabel:`Dashboard` to request more time off, and a :ref:`New Allocation ` modal appears." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:-1 -msgid "Time off dashboard view with the legend, time off summaries, and view buttons highlighted." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:800 -msgid "My time off" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:802 -msgid "To view a list of all the user's time off requests, navigate to :menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time off requests, both past and present, appear in a list view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:805 -msgid "The list includes the following information for each request: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Duration`, and the :guilabel:`Status`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:809 -msgid "A new time off request can be made from this view. Click the :guilabel:`New` button to :doc:`request time off <../hr/time_off/request_time_off>`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:815 -msgid "My allocations" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:817 -msgid "To view a list of all the user's allocations, navigate to :menuselection:`Time Off app --> My Time --> My Allocations`. All allocations and requested allocations appear in a list view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:820 -msgid "The information presented on the :guilabel:`My Allocations` page includes: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Amount`, :guilabel:`Allocation Type`, and :guilabel:`Status`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:824 -msgid "A new allocation request can be made from this view, as well. Click the :guilabel:`New` button to :ref:`request an allocation `." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:832 +#: ../../content/applications/hr/time_off.rst:597 msgid "The reporting feature allows users to view time off for their team, either by employee or type of time off. This allows users to see which employees are taking time off, how much time off they are taking, and what time off types are being used." msgstr "" -#: ../../content/applications/hr/time_off.rst:836 +#: ../../content/applications/hr/time_off.rst:601 msgid "Any report can be added to a spreadsheet through the *Insert in Spreadsheet* button that appears in the top-left of a report. If the *Documents* application is installed, an option to add the report to a spreadsheet appears. If not, the report can be added to a *Dashboard*." msgstr "" -#: ../../content/applications/hr/time_off.rst:841 +#: ../../content/applications/hr/time_off.rst:606 msgid "By employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:843 +#: ../../content/applications/hr/time_off.rst:608 msgid "To view a report of employee time off requests, navigate to :menuselection:`Time Off app --> Reporting --> by Employee`." msgstr "" -#: ../../content/applications/hr/time_off.rst:846 +#: ../../content/applications/hr/time_off.rst:611 msgid "The default report presents the current year's data in a list view, displaying all the employees in alphabetical order. Each employee's line is collapsed by default. To expand a line, click anywhere on the line." msgstr "" -#: ../../content/applications/hr/time_off.rst:850 +#: ../../content/applications/hr/time_off.rst:615 msgid "The view expands, and has the time off requests organized by time off type. Click anywhere on a time off type line to expand it, and view all the individual time off requests that fall under that type." msgstr "" -#: ../../content/applications/hr/time_off.rst:853 +#: ../../content/applications/hr/time_off.rst:618 msgid "The information shown in the list includes: the :guilabel:`Employee` name, :guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." msgstr "" @@ -11012,7 +11049,7 @@ msgstr "" msgid "Report of time off, shown by each employee in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:861 +#: ../../content/applications/hr/time_off.rst:626 msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that specific way. The various options are a :guilabel:`List` (the default view), :guilabel:`Graph`, :guilabel:`Pivot` table, or :guilabel:`Calendar` view." msgstr "" @@ -11020,19 +11057,19 @@ msgstr "" msgid "The various other views highlighted, for the employee time off report." msgstr "" -#: ../../content/applications/hr/time_off.rst:870 +#: ../../content/applications/hr/time_off.rst:635 msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." msgstr "" -#: ../../content/applications/hr/time_off.rst:875 +#: ../../content/applications/hr/time_off.rst:640 msgid "By type" msgstr "" -#: ../../content/applications/hr/time_off.rst:877 +#: ../../content/applications/hr/time_off.rst:642 msgid "To view a list of all time off, organized by time off type, navigate to :menuselection:`Time Off app --> Reporting --> by Type`. This shows all time off requests in a default bar chart." msgstr "" -#: ../../content/applications/hr/time_off.rst:880 +#: ../../content/applications/hr/time_off.rst:645 msgid "Hover over a bar to view the :guilabel:`Duration (Days)` of that specific time off type." msgstr "" @@ -11041,26 +11078,323 @@ msgid "The various time off types, and how many days requested, in a bar chart. "highlighted in a red box." msgstr "" -#: ../../content/applications/hr/time_off.rst:887 +#: ../../content/applications/hr/time_off.rst:652 msgid "Click on a bar to go to a detailed list view of all the time off requests for that time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:889 +#: ../../content/applications/hr/time_off.rst:654 msgid "Each request is listed, with the following information displayed: the :guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the :guilabel:`Description`." msgstr "" -#: ../../content/applications/hr/time_off.rst:893 +#: ../../content/applications/hr/time_off.rst:658 msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that way. The various options are a :guilabel:`Graph` (the default view), :guilabel:`List`, or :guilabel:`Pivot` table." msgstr "" -#: ../../content/applications/hr/time_off.rst:897 +#: ../../content/applications/hr/time_off.rst:662 msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports, and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." msgstr "" -#: ../../content/applications/hr/time_off.rst:902 +#: ../../content/applications/hr/time_off.rst:667 msgid ":doc:`time_off/request_time_off`" msgstr "" +#: ../../content/applications/hr/time_off.rst:668 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:669 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "Time off and allocation requests undergo an approval process before being granted. Requests either need one or two approvals, if any, depending on how the specific type of time off is configured. All these configurations can be found under the *Management* section of the *Time Off* application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "Only people who can approve allocation and time off requests have the :guilabel:`Management` section visible in the *Time Off* application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "To view time off requests that need approval, navigate to :menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "The only time off requests that are visible on this page belong to employees the user either has :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "The default filter on the :guilabel:`All Time Off` page is `Waiting For Me`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:28 +msgid "This filter only presents time off requests that need to be approved for current employees on the user's team, with a status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:31 +msgid "On the left side of the :guilabel:`All Time Off` page, there are various grouping options that can be used to narrow down the presented time off requests, located beneath the :guilabel:`Status` and :guilabel:`Department` headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:35 +msgid "Since only time off requests that need to be approved are shown, the only :guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:38 +msgid "The various departments the user is a member of, and manages employees under, also appear on the left side of the page, under :guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:42 +msgid "If there are no requests that fall under one of the status options or departments, that status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:45 +msgid "To only display time off requests for specific departments, click on the :guilabel:`Department` on the left-hand side of the page. Only requests within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:48 +#: ../../content/applications/hr/time_off/management.rst:127 +msgid "The status column displays the status of each request, with the status highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:51 +msgid "The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are highlighted in yellow, and are the only ones that appear in the list by default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:54 +msgid "If the `Waiting For Me` filter is removed, all statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:56 +msgid ":guilabel:`Approved` requests are highlighted in green, :guilabel:`To Submit` (drafts) requests are highlighted in blue, and the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:59 +msgid "To approve a time off request, click the :icon:`fa-thumbs-up` :guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:62 +msgid "To validate a time off request that has already been approved, and is waiting on a second approval, click the :icon:`fa-check` :guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:65 +msgid "To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "Time off requests with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:72 +msgid "For more details, click anywhere on the time off request line (except for the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` :guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons). Doing so loads that specific time off request form. Depending on the rights of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "To modify the request, make any desired changes to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:79 +msgid "It is also possible to approve, validate, or refuse the request from this form. Click the :guilabel:`Approve` button to approve, the :guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:88 +msgid "To view allocations that need approval, navigate to :menuselection:`Time Off app --> Management --> Allocations`. Doing so reveals the :guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:91 +msgid "The user is only presented with allocations for employees they have either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:94 +msgid "The default filters configured on the :guilabel:`Allocations` page are :guilabel:`My Team` and :guilabel:`Active Employee`. These default filters *only* present employees on the user's team (who they manage) and active employees. Inactive records are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:98 +msgid "The left side of the :guilabel:`Allocations` page has various grouping options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:101 +msgid "The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`, :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific :guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:105 +msgid "To view all allocation requests, regardless of status, click :guilabel:`All` under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:108 +msgid "It is also possible to display allocation requests by department. Click on the desired :guilabel:`Department` on the left side of the :guilabel:`Allocations` page, to only present allocations for that specific department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:113 +msgid "The groupings on the left side **only** present allocation requests that fall under the default filters of :guilabel:`My Team` and :guilabel:`Active Employee`, if those default filters are not removed from the :guilabel:`Search...` bar. Only the statuses for allocation requests that fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:118 +msgid "For example, if there are no requests with a status of :guilabel:`To Submit`, that status option does not appear in the left-hand side of the :guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:121 +msgid "All departments for the user's employees appear in the list. If there are no allocation requests that fall under that department matching the preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:124 +msgid "It is always possible to remove any of the preconfigured filters, by clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "The :guilabel:`To Approve` requests are highlighted in yellow, :guilabel:`Approved` requests are highlighted in green, and the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:133 +msgid "To approve an allocation request, click the :icon:`fa-check` :guilabel:`Validate` button at the end of the line. To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "If more details are needed, click anywhere on the allocation request line (except for the :icon:`fa-check` :guilabel:`Validate` or :icon:`fa-times` :guilabel:`Refuse` buttons) to view the specific request in detail, via the allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "Depending on the rights of the user, changes can be made to the allocation request form that appears. To modify the request, make any desired changes to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:148 +msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Validate` button to approve, or the :guilabel:`Refuse` button to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "The *My Time* menu of the *Time Off* application houses all the various time off information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "This includes the main *Time Off* dashboard, which displays an overview of the various time off balances, as well as time-off requests and allocations." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:14 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:16 +msgid "All users have access to the *Time Off* :guilabel:`Dashboard`, which is the first page that appears when the *Time Off* application is opened. The :guilabel:`Dashboard` can also be accessed at any point in the application, by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:20 +msgid "The current year is displayed, and the current day is highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:22 +msgid "To change the view, click on the :guilabel:`Year` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:27 +msgid "To change the displayed dates, click the :icon:`fa-arrow-left` :guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)` icons to the left of the :guilabel:`Year` button. The calendar view adjusts in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:31 +msgid "For example, if :guilabel:`Year` is selected, the arrows adjust the view by one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "To reset the view, so it includes the current date, click the :guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "Above the calendar view is a summary of the user's time off balances. Every time off type that has been allocated appears in its own summary box. Each summary lists the type of time off, the corresponding icon, the current available balance (in hours or days), and an expiration date (if applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:40 +msgid "To view the full details of a time off balance, click the :icon:`fa-question-circle-o` :guilabel:`(question mark)` icon at the end of the :guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete details are presented in a popover window, including the :guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, :guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:50 +msgid "A user can also select a future date to see an estimate of how much time they should accrue by that point. On the right side of the time off summary blocks, there is a :guilabel:`Balance at the (date)` field. Click on the date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:55 +msgid "The :guilabel:`Balance at the (date)` field **only** appears if the user is accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:58 +msgid "The current date is the default date selected. Navigate to the desired date, and Odoo displays the time off balances the user should have on that date. This takes into account all time off currently planned and approved. To return to the current date, click the :guilabel:`Today` button to the right of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:63 +msgid "On the right side of the calendar, the various time off types are displayed, each with their own corresponding color. The :guilabel:`Legend` explains how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:67 +msgid "Time off that has been validated appears in a solid color. Time off requests that still are still in the :guilabel:`To Approve` stage, appear with white stripes in the color. :guilabel:`Refused` time off requests have a line through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:71 +msgid "The color for each request corresponds to the specified color set with the various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:74 +msgid "New time off requests can be made from the :guilabel:`Dashboard`. Click the :guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off ` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:77 +msgid "New allocation requests can also be made from the :guilabel:`Dashboard`. Click the :guilabel:`New Allocation Request` button to request more time off, and a :ref:`New Allocation ` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "Time off dashboard view with the legend, time off summaries, and view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "To view a list of all the time off requests, navigate to :menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time off requests, both past and present, appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:93 +msgid "The list includes the following information for each request: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:97 +msgid "A new time off request can be made from this view. Click the :guilabel:`New` button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:103 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:105 +msgid "To view a list of all allocations, navigate to :menuselection:`Time Off app --> My Time --> My Allocations`. All allocations and requested allocations appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:108 +msgid "The information presented on the :guilabel:`My Allocations` page includes: :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Amount`, :guilabel:`Allocation Type`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "A new allocation request can be made from this view, as well. Click the :guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + #: ../../content/applications/hr/time_off/request_time_off.rst:3 msgid "Request time off" msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 6ad767252..2827ee95f 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1142,9 +1142,8 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:35 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:38 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:17 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:22 @@ -1155,6 +1154,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:17 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:19 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:104 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:49 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:22 @@ -1170,7 +1170,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:46 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:20 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:38 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:45 #: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:13 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:52 @@ -1180,11 +1180,14 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:23 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:41 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:21 #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:11 #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:15 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:26 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 #: ../../content/applications/inventory_and_mrp/purchase/products/temporary_reordering.rst:31 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:19 msgid "Configuration" msgstr "" @@ -2436,31 +2439,31 @@ msgstr "" msgid "Reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:7 -msgid "Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:9 +msgid "*Reordering rules* are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:13 msgid "Reordering rules can be configured for each product based on the route used to replenish it. If a product uses the *Buy* route, then a Request for Quotation (RFQ) is created when the reordering rule is triggered. If a product uses the *Manufacture* route, then a Manufacturing Order (MO) is created instead. This is the case regardless of the selected replenishment route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:19 msgid "`Odoo Tutorials: Automatic Reordering Rules `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:20 msgid "`Odoo Tutorials: Manual Reordering Rules `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:23 msgid "Configure products for reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:25 msgid "In order to use reordering rules for a product, it must first be correctly configured. Begin by navigating to :menuselection:`Inventory app --> Products --> Products`, then select an existing product, or create a new one by clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:29 msgid "On the product form, under the :guilabel:`General Information` tab, make sure the :guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is necessary because Odoo only tracks stock quantities for storable products, and this number is used to trigger reordering rules." msgstr "" @@ -2468,7 +2471,7 @@ msgstr "" msgid "Set the Product Type as Storable." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:37 msgid "Next, click on the :guilabel:`Inventory` tab and select one or more routes from the :guilabel:`Routes` section. Doing so tells Odoo which route to use to replenish the product." msgstr "" @@ -2476,7 +2479,7 @@ msgstr "" msgid "Select one or more routes on the Inventory tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:44 msgid "If the product is reordered using the :guilabel:`Buy` route, confirm that the :guilabel:`Can be Purchased` checkbox is enabled under the product name. This makes the :guilabel:`Purchase` tab appear. Click on the :guilabel:`Purchase` tab, and specify at least one vendor, and the price that they sell the product for, so that Odoo knows which company the product should be purchased from." msgstr "" @@ -2484,11 +2487,11 @@ msgstr "" msgid "Specify a vendor and price on the Purchase tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:53 msgid "If the product is replenished using the :guilabel:`Manufacture` route, it needs to have at least one Bill of Materials (BoM) associated with it. This is necessary because Odoo only creates manufacturing orders for products with a :abbr:`BoM (Bill of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:57 msgid "If a :abbr:`BoM (Bill of Materials)` does not already exist for the product, select the :guilabel:`Bill of Materials` smart button at the top of the product form, then click :guilabel:`New` to configure a new :abbr:`BoM (Bill of Materials)`." msgstr "" @@ -2496,35 +2499,35 @@ msgstr "" msgid "The Bill of Materials smart button on a product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:66 msgid "Create new reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:68 msgid "To create a new reordering rule, navigate to :menuselection:`Inventory app --> Configuration --> Reordering Rules`, then click :guilabel:`New`, and fill out the new line as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:71 msgid ":guilabel:`Product`: The product that is replenished by the rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:72 msgid ":guilabel:`Location`: The location where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:73 msgid ":guilabel:`Min Quantity`: The minimum quantity that can be forecasted without the rule being triggered. When forecasted stock falls below this number, a replenishment order for the product is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:76 msgid ":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:77 msgid ":guilabel:`Multiple Quantity`: Specify if the product should be replenished in batches of a certain quantity (e.g., a product could be replenished in batches of 20)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:79 msgid ":guilabel:`UoM`: The unit of measure used for reordering the product. This value can simply be `Units` or a specific unit of measurement for weight, length, etc." msgstr "" @@ -2532,47 +2535,115 @@ msgstr "" msgid "The form for creating a new reordering rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:87 msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product. Then, click the :guilabel:`Reordering Rules` smart button, and click :guilabel:`New` to fill out the new line, as detailed above." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:92 msgid "For advanced usage of reordering rules, learn about the following reordering rule fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:94 msgid ":ref:`Trigger `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:95 msgid ":ref:`Visibility days `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:96 msgid ":ref:`Route `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:99 -msgid "Trigger" +msgid "0/0/1 reordering rule" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:101 -msgid "When stock falls below the reordering rule's minimum, set the reordering rule's *trigger* to *automatic* to automatically create purchase or manufacturing orders to replenish stock." +msgid "The *0/0/1* reordering rule is a specialty rule used to replenish a product that is not kept on-hand, each time a sales order (SO) is confirmed for that product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:104 -msgid "Alternatively, setting the reordering rule's trigger to *manual* displays the product and forecasted stock on the *replenishment dashboard*, where the procurement manager can review the stock levels, lead times, and forecasted dates of arrival." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:105 +msgid "The 0/0/1 reordering rule is similar to the *Replenish on Order (MTO)* route, in that both workflows are used to replenish a product upon confirmation of an |SO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:109 -msgid ":doc:`strategies`" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:108 +msgid "The main difference between the two methods is that the *Replenish on Order* route automatically reserves the product for the |SO| that caused it to be replenished. This means the product **cannot** be used for a different |SO|." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:112 -msgid "The replenishment dashboard is accessible by going to :menuselection:`Inventory app --> Operations --> Replenishment`." +msgid "The 0/0/1 reordering rule does not have this limitation. A product replenished using the rule is not reserved for any specific |SO|, and can be used as needed." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:115 +msgid "Another key difference is that replenishment orders created by the *Replenish on Order* route are linked to the original |SO| by a smart button at the top of the order. When using the 0/0/1 reordering rule, a replenishment order is created, but is not linked to the original |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:119 +msgid "See the :doc:`Replenish on Order (MTO) ` documentation for a full overview of the MTO route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:121 +msgid "To create a 0/0/1 reordering rule, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:124 +msgid "At the top of the product's page, click the :icon:`fa-refresh` :guilabel:`Reordering Rules` smart button to open the :guilabel:`Reordering Rules` page for the product. On the resulting page, click :guilabel:`New` to begin configuring a new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:128 +msgid "In the :guilabel:`Location` field of the new reordering rule, select the location in which replenished products should be stored. By default, this location is set to :guilabel:`WH/Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:131 +msgid "In the :guilabel:`Route` field, select the route the rule should use to replenish the item. For example, if the product should be purchased from a vendor, select the :guilabel:`Buy` route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:134 +msgid "In the :guilabel:`Min Quantity` field and :guilabel:`Max Quantity` field, leave the values set to `0.00`. In the :guilabel:`To Order` field, enter a value of `1.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 +msgid "A 0/0/1 reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:141 +msgid "With the reordering rule configured using these values, each time an |SO| causes the forecasted quantity of the product to fall below the :guilabel:`Min Quantity` of `0.00`, the selected :guilabel:`Route` is used to replenish the product in one-unit increments, back up to the :guilabel:`Max Quantity` of `0.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:147 +msgid "A picture frame is configured with a 0/0/1 reordering rule that uses the *Buy* route. Zero units of the picture frame are kept on-hand at any given time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:150 +msgid "An |SO| is confirmed for one unit of the picture frame, which causes the forecasted quantity to drop to `-1.00`. This triggers the reordering rule, which automatically creates a |PO| for one unit of the picture frame." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:154 +msgid "Once the product is received from the vendor, the forecasted quantity of the picture frame returns to `0.00`. There is now one picture frame on-hand, but it is not reserved for the |SO| which triggered its purchase. It can be used to fulfill that |SO|, or reserved for a different order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:162 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:164 +msgid "When stock falls below the reordering rule's minimum, set the reordering rule's *trigger* to *automatic* to automatically create purchase or manufacturing orders to replenish stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:167 +msgid "Alternatively, setting the reordering rule's trigger to *manual* displays the product and forecasted stock on the *replenishment dashboard*, where the procurement manager can review the stock levels, lead times, and forecasted dates of arrival." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:172 +msgid ":doc:`strategies`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:175 +msgid "The replenishment dashboard is accessible by going to :menuselection:`Inventory app --> Operations --> Replenishment`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:178 msgid "To enable the :guilabel:`Trigger` field, go to :menuselection:`Inventory app --> Configuration --> Reordering Rules`. Then, click the :guilabel:`(slider)` icon, located to the far-right of the column titles, and enable the :guilabel:`Trigger` option from the additional options drop-down menu that appears." msgstr "" @@ -2580,39 +2651,39 @@ msgstr "" msgid "Enable the Trigger field by toggling it in the additional options menu" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:187 msgid "In the :guilabel:`Trigger` column, select :guilabel:`Auto` or :guilabel:`Manual`. Refer to the sections below to learn about the different types of reordering rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:191 msgid "Auto" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:193 msgid "Automatic reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Auto`, generates purchase or manufacturing orders when:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:196 msgid "the scheduler runs, and the *On Hand* quantity is below the minimum" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:134 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:197 msgid "a sales order is confirmed, and lowers the *Forecasted* quantity of the product below the minimum" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:201 msgid "The scheduler is set to run once a day, by default." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:203 msgid "To manually trigger a reordering rule before the scheduler runs, ensure :ref:`developer mode ` is enabled, and select :menuselection:`Inventory app --> Operations --> Run Scheduler`. Then, click the purple :guilabel:`Run Scheduler` button on the pop-up window that appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:145 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:208 msgid "Be aware that this also triggers any other scheduled actions." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:148 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:211 msgid "The product, `Office Lamp`, has an automatic reordering rule set to trigger when the forecasted quantity falls below the :guilabel:`Min Quantity` of `5.00`. Since the current :guilabel:`Forecast` is `55.00`, the reordering rule is **not** triggered." msgstr "" @@ -2620,37 +2691,37 @@ msgstr "" msgid "Show automatic reordering rule from the Reordering Rule page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:219 msgid "If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for Quotation)`, navigate to :menuselection:`Purchase app --> Orders --> Requests for Quotation`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:160 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:223 msgid "If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO (Manufacturing Order)` is generated. To view and manage :abbr:`MOs (Manufacturing Orders)`, navigate to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:164 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:227 msgid "When no route is selected, Odoo selects the :guilabel:`Route` specified in the :guilabel:`Inventory` tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:170 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:163 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:182 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:233 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:228 msgid "Manual" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:172 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:235 msgid "Manual reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Manual`, lists a product on the replenishment dashboard when the forecasted quantity falls below a specified minimum. Products on this dashboard are called *needs*, because they are needed to fulfill upcoming sales orders, but the forecasted quantity is not enough." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:240 msgid "The replenishment dashboard, accessible by navigating to :menuselection:`Inventory app --> Operations --> Replenishment`, considers sales order deadlines, forecasted stock levels, and vendor lead times. It displays needs **only** when it is time to reorder items." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:182 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:245 msgid "If the one-day window for ordering products is too short, skip to the :ref:`visibility days ` section to make the need appear on the replenishment dashboard a specified number of days in advance." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:186 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:249 msgid "When a product appears on the replenishment dashboard, clicking the :guilabel:`Order Once` button generates the purchase or manufacturing order with the specified amounts :guilabel:`To Order`." msgstr "" @@ -2658,31 +2729,31 @@ msgstr "" msgid "Click the Order Once button on the replenishment dashboard to replenish stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:196 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:259 msgid "Visibility days" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:199 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:262 msgid "Ensure :doc:`lead times <../../shipping_receiving/advanced_operations_shipping/scheduled_dates>` are understood before proceeding with this section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:202 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:265 msgid "When :ref:`manual reordering rules ` are assigned to a product, *visibility days* make the product appear on the replenishment dashboard (:menuselection:`Inventory app --> Operations --> Replenishment`) a certain number of days in advance." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:208 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:271 msgid "A product has a manual reordering rule set to trigger when the stock level falls below four units. The current on-hand quantity is ten units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:274 msgid "The current date is February 20th, and the *delivery date* on a sales order (in the :guilabel:`Other Info` tab) is March 3rd — twelve days from the current date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:214 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:277 msgid "The :ref:`vendor lead time ` is four days, and the :ref:`purchase security lead time ` is one day." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:218 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:281 msgid "When the :guilabel:`Visibility Days` field of the reordering rule is set to zero, the product appears on the replenishment dashboard five days before the delivery date, which, in this case, is February 27th." msgstr "" @@ -2690,27 +2761,27 @@ msgstr "" msgid "Graphic representing when the need appears on the replenishment dashboard: Feb 27th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:226 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:289 msgid "To see the product on the replenishment dashboard for the current date, February 20, set the :guilabel:`Visibility Days` to `7.00`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:229 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:292 msgid "To determine the amount of visibility days needed to see a product on the replenishment dashboard, subtract *today's date* from the *date the need appears* on the replenishment dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:232 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:295 msgid "Visibility~days = Need~appears~date - Today's~date" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:237 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:300 msgid "Referring to the example above, today's date is February 20th, and the need for the product appears on February 27th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:240 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:303 msgid "(February 27 - February 20 = 7 days)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:242 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:305 msgid "Incorrectly setting the :guilabel:`Visibility Days` fewer than seven days in this case results in the need **not** appearing on the replenishment dashboard." msgstr "" @@ -2718,27 +2789,27 @@ msgstr "" msgid "Show the replenishment dashboard with the correct and incorrect visibility days set." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:252 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:315 msgid "Route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:254 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:317 msgid "Odoo allows for multiple routes to be selected under the :guilabel:`Inventory` tab on each product form. For instance, it is possible to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling the functionality of both routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:258 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:321 msgid "Odoo also enables users to set a preferred route for a product's reordering rule. This is the route that the rule defaults to, if multiple are selected. To select a preferred route, begin by navigating to :menuselection:`Inventory app --> Configuration --> Reordering Rules`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:262 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:325 msgid "By default, the :guilabel:`Route` column is hidden on the :guilabel:`Reordering Rules` page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:264 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:327 msgid "Reveal the :guilabel:`Route` column by selecting the :guilabel:`(slider)` icon to the far-right of the column titles, and checking the :guilabel:`Route` option from the drop-down menu that appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:267 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:330 msgid "Click inside of the column on the row of a reordering rule, and a drop-down menu shows all available routes for that rule. Select one to set it as the preferred route." msgstr "" @@ -2746,7 +2817,7 @@ msgstr "" msgid "Select a preferred route from the drop-down." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:275 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:338 msgid "If multiple routes are enabled for a product but no preferred route is set for its reordering rule, the product is reordered using the selected route that is listed first on the :guilabel:`Inventory` tab of the product form." msgstr "" @@ -5109,7 +5180,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:163 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:56 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:81 msgid "Create purchase order" msgstr "" @@ -5313,32 +5384,30 @@ msgid "After cancelling the shipping request, you can change the carrier you wan msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:50 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:160 msgid ":doc:`invoicing`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:51 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:161 msgid ":doc:`multipack`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:3 -msgid "Use dropshipping to ship directly from suppliers to customers" +msgid "Dropshipping" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:7 msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:14 msgid "Configure products to be dropshipped" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:16 msgid "To use dropshipping as a fulfillment strategy, navigate to the :menuselection:`Purchase` app and select :menuselection:`Configuration --> Settings`. Under the :guilabel:`Logistics` heading, click the :guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:20 msgid "Next, go to the :menuselection:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the :guilabel:`Product` page, make sure that the :guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are enabled." msgstr "" @@ -5346,7 +5415,7 @@ msgstr "" msgid "Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:29 msgid "Click on the :guilabel:`Purchase` tab and specify a vendor and the price that they sell the product for. Multiple vendors can be added, but the vendor at the top of the list will be the one automatically selected for purchase orders." msgstr "" @@ -5354,7 +5423,7 @@ msgstr "" msgid "The product form with a vendor specified." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:37 msgid "Finally, select the :guilabel:`Inventory` tab and enable the :guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." msgstr "" @@ -5362,39 +5431,39 @@ msgstr "" msgid "Enable the Dropship option in the product inventory tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:45 +msgid "While it is not necessary to enable the :guilabel:`Buy` route in addition to the :guilabel:`Dropship` route, enabling both provides the option of dropshipping the product or purchasing it directly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:50 msgid "Fulfill orders using dropshipping" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:45 -msgid "When a customer completes an online purchase for a dropshipped product, a sales order will be automatically created with an associated request for quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:52 -msgid "Dropship sales orders can also be created manually through the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for dropshipping." +msgid "When a sales order is created for a dropshipped product, an associated request for quotation (RfQ) is automatically generated to purchase the product from the vendor. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 msgid "A dropship sales order with the Purchase smart button in the top right corner." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:60 -msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Receipt` smart button in the top right corner of the purchase order form." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:62 +msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order, and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Dropship` smart button in the top-right corner of the purchase order form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 msgid "A dropship purchase order with the Receipt smart button in the top right corner." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:68 -msgid "The dropship receipt will list the supplier in the :guilabel:`Receive From` section and the customer in the :guilabel:`Destination Location` section. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top left of the dropship receipt to confirm the delivered quantity." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:70 +msgid "The dropship receipt displays :guilabel:`Partners/Vendors` in the :guilabel:`Source Location` field, and :guilabel:`Partners/Customers` in the :guilabel:`Destination Location` field. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top-left of the dropship receipt to confirm the delivered quantity." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 msgid "Validate the dropship receipt after delivery." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:79 msgid "To view all dropship orders, simply navigate to the :menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." msgstr "" @@ -5406,23 +5475,23 @@ msgstr "" msgid "Shipping cost invoicing" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:5 msgid "Invoicing customers for shipping after delivery ensures accurate charges based on real-time shipping factors like distance, weight, and method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:10 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:8 msgid "In Odoo, shipping costs can be invoiced in two ways:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:10 msgid "Agree with the customer on a fixed cost and :ref:`include it in the sale order. `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:13 msgid ":ref:`Invoice shipping costs to the customer post-delivery `, reflecting the actual expenses incurred by the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:19 msgid "To set prices to delivery methods, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Shipping` section, enable the :guilabel:`Delivery Methods` feature. Then, click :guilabel:`Save`." msgstr "" @@ -5430,58 +5499,58 @@ msgstr "" msgid "Enable the \"Delivery Methods\" feature in Settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:28 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 msgid "Add shipping method" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:30 msgid "Next, configure the the price of each delivery method by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods` and click the :guilabel:`Create` button. Doing so opens a form to provide details about the shipping provider, including:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:34 msgid ":guilabel:`Shipping Method` (*required*) the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:36 msgid ":guilabel:`Provider` (*required*): choose the delivery service, like FedEx, if using a third-party carrier Ensure the integration with the shipping carrier is properly installed and select the provider from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:43 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:124 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:27 msgid ":doc:`../setup_configuration/third_party_shipper`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:43 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:121 msgid ":guilabel:`Company`: if the shipping method should apply to a specific company, select it from the drop-down menu. Leave the field blank to apply the method to all companies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:46 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 msgid ":guilabel:`Website`: configure shipping methods for an e-commerce page. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:49 msgid ":guilabel:`Delivery Product` (*required*): the product listed on the :ref:`sales order line ` as the delivery charge." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:51 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 msgid ":guilabel:`Free if order amount is above`: checking this box enables free shipping if the customer spends above the specified amount." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:57 msgid "Invoice cost on sales order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:59 msgid "To invoice shipping costs on the sales order, before the item is delivered, go to the :menuselection:`Sales app` and select the desired sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:62 msgid "On the sales order, click the :guilabel:`Add Shipping` button at the bottom-right corner." msgstr "" @@ -5489,15 +5558,15 @@ msgstr "" msgid "Click \"Add Shipping\" button at the bottom right, near the total." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:68 msgid "In the :guilabel:`Add a shipping method` pop-up window, choose the intended carrier in the :guilabel:`Shipping Method` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:71 msgid "Then, click the :guilabel:`Get Rate` button to the calculate shipping price based on real-time shipping data Odoo's shipping carrier integration." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:74 msgid "The :guilabel:`Cost` is automatically calculated using the weight of the items in the order. Finally, click the :guilabel:`Add` button to close the window." msgstr "" @@ -5505,7 +5574,7 @@ msgstr "" msgid "Calculate shipping by selecting a shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:83 msgid "On the sales order, the delivery product appears in the :guilabel:`Order Lines` tab, with the :guilabel:`Unit Price` set as the shipping cost calculated in the :guilabel:`Add a shipping method` pop-up window." msgstr "" @@ -5513,7 +5582,7 @@ msgstr "" msgid "Show delivery product on the sales order line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:91 msgid "Finally, after the product is delivered, click the :guilabel:`Create invoice` button, and an invoice is created that includes the shipping cost that was added earlier." msgstr "" @@ -5521,7 +5590,7 @@ msgstr "" msgid "Show \"Create Invoice\" button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:98 msgid "Then, click the :guilabel:`Create and View Invoice` button, and a draft invoice is generated, with the shipping cost included in the :guilabel:`Invoice Lines` tab." msgstr "" @@ -5529,15 +5598,15 @@ msgstr "" msgid "Show delivery product in the invoice line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:108 msgid "Invoice real shipping costs" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:110 msgid "To modify the invoice to reflect the real cost of shipping, follow the steps :ref:`above ` to create an invoice with a delivery product with a :guilabel:`Unit Price` of zero." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:114 msgid "Then, on a draft invoice, modify the :guilabel:`Unit Price` to reflect the real shipping cost. Finally, invoice the customer the adjusted shipping cost by clicking :guilabel:`Confirm`." msgstr "" @@ -5545,8 +5614,8 @@ msgstr "" msgid "Show delivery product on the invoice line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:125 -msgid ":doc:`labels`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:123 +msgid ":doc:`../setup_configuration/labels`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:3 @@ -5626,143 +5695,6 @@ msgstr "" msgid "Half page letter size FedEx shipping label." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:3 -msgid "Print shipping labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:8 -msgid "Integrate Odoo with :doc:`third-party shipping carriers <../setup_configuration/third_party_shipper>` to automatically generate shipping labels that includes prices, destination addresses, tracking numbers, and barcodes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:15 -msgid "To generate labels for a third-party shipping carrier, first :doc:`install the third-party shipping connector <../setup_configuration/third_party_shipper>`. Then, configure and activate the :ref:`delivery method `, being sure to set the :guilabel:`Integration Level` to :guilabel:`Get Rate and Create Shipment` to generate shipping labels. Finally, provide the company's :ref:`source address ` and :ref:`product weights `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 -msgid "Set the \"Get Rate and Create Shipment\" option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:33 -msgid "Labels for multi-step" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:35 -msgid "For companies using :doc:`two <../daily_operations/receipts_delivery_two_steps>` or :doc:`three step delivery <../daily_operations/delivery_three_steps>`, labels can be triggered to print after validating the picking or packing operation. To do that, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and choose the desired operation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:40 -msgid "On the :guilabel:`Operation Type` configuration page, tick the :guilabel:`Print Label` checkbox. Enabling this feature ensures that the third-party shipping label is printed upon validating this operation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:45 -msgid "For :doc:`two-step delivery <../daily_operations/receipts_delivery_two_steps>`, where products are placed directly in packages during picking, companies can print shipping labels during picking instead of delivery. Odoo allows users to enable the :guilabel:`Print Label` feature on the `Pick` operation itself to achieve this flexibility." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:0 -msgid "Enable the \"Print Label\" feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:55 -msgid "Print tracking labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:57 -msgid "Tracking labels are printed when specific operations are validated. By default, validating a delivery order (DO) generates a tracking label in the chatter." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:61 -msgid "For companies using two or three step delivery, refer to the :ref:`printing labels for multi-step delivery ` section to learn how to print the label after validating a picking or packing operation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:65 -msgid "When both the *Sales* and *Inventory* apps are installed, begin in the :menuselection:`Sales` app, and proceed to the desired quotation or sales order (SO). There, and :ref:`add the shipping cost ` to the order. Then, navigate to the linked |DO| — or another operation type when using multi-step delivery — to validate the operation and print the label." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:71 -msgid "If only the *Inventory* app is installed, create :abbr:`DOs (Delivery Orders)` directly in the :menuselection:`Inventory` app, :ref:`add the third-party carrier ` in the :guilabel:`Carrier` field, and validate the |DO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:79 -msgid "Add shipping on quotation" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:81 -msgid "To generate a tracking label for an order, begin by creating a quotation in :menuselection:`Sales app --> Orders --> Quotations`, clicking :guilabel:`New`, and filling out the quotation form. Then, click the :guilabel:`Add Shipping` button in the bottom-right corner of the quotation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 -msgid "Show the \"Add Shipping\" button on the quotation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:89 -msgid "In the resulting pop-up window, select the intended carrier from the :guilabel:`Shipping Method` drop-down menu. The :guilabel:`Total Order Weight` field is automatically populated, based on the :ref:`weight of products in the order `. Modify this field to overwrite the predicted weight, and use this weight to estimate the cost of shipping." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:94 -msgid "Next, click :guilabel:`Get Rate` to display the shipping cost for the customer, via the third-party carrier in the :guilabel:`Cost` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:98 -msgid "If clicking :guilabel:`Get Rate` results in an error, ensure the :ref:`warehouse's address ` and :ref:`weight of products in the order ` are properly configured." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:102 -msgid "Click :guilabel:`Add` to add the cost to the quotation, which is listed as the :ref:`configured delivery product `. Finally, click :guilabel:`Confirm` on the quotation, and click the :guilabel:`Delivery` smart button to access the |DO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 -msgid "Show \"Get rate\" pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:112 -msgid "For users who do not have the *Sales* app installed, specify the :guilabel:`Carrier` by going to the :menuselection:`Inventory` app, navigating to the |DO|, and going to the :guilabel:`Additional Info` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:0 -msgid "Show the \"Additional Info\" tab of a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:123 -msgid "Validate delivery order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:125 -msgid "On a delivery order form, navigate to the :guilabel:`Additional Info` tab to ensure the third-party shipping carrier has been added to the :guilabel:`Carrier` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:129 -msgid "If the *Sales* app is not installed, the third-party carrier is set in the :guilabel:`Carrier` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:132 -msgid "After the items in the order have been packed, click :guilabel:`Validate` to get the shipping carrier's tracking number, and generate the shipping label." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:136 -msgid "Create or select an existing delivery order by going to the :menuselection:`Inventory` app, and selecting the :guilabel:`Delivery Orders` card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:139 -msgid "The :guilabel:`Tracking Reference` number is generated in the :guilabel:`Additional Info` tab of the delivery order. Click the :guilabel:`Tracking` smart button to access the tracking link from the shipping carrier's website." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:143 -msgid "The tracking label is found in PDF format in the chatter." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 -msgid "Show generated shipping label in the chatter." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:150 -msgid "For multi-package shipping, one label is generated per package. Each label appears in the chatter." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:157 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:157 -msgid "Sample label generated from Odoo's shipping connector with FedEx." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:3 msgid "Multi-package shipments" msgstr "" @@ -5904,19 +5836,19 @@ msgid ":ref:`Lot and serial number labels `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:16 -msgid "Export documents" +msgid ":ref:`Export documents `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:17 -msgid "Package Content" +msgid ":ref:`Package content `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:18 -msgid "Package label" +msgid ":ref:`Package label `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:22 @@ -5931,27 +5863,27 @@ msgstr "" msgid "Show the *Print on Validation* option in the \"Pick\" *Operation Type*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:37 msgid "Delivery slip" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:39 msgid "A *delivery slip* contains recipient and package details, usually placed inside (or attached to) the package." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:43 msgid ":ref:`Picking list `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:43 -msgid ":doc:`Tracking label `" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:44 +msgid ":doc:`Tracking label <../setup_configuration/labels>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:46 msgid "After :ref:`enabling the Delivery Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the delivery slip." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:50 msgid "The delivery slip shows products, quantities, the delivery order reference number, and the total order weight." msgstr "" @@ -5959,19 +5891,19 @@ msgstr "" msgid "Example delivery slip." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:60 msgid "Return slip" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:62 msgid "Print a *return slip* to include in a delivery for customer return packages. It identifies the return, links to the sales order, and includes item details and customer information. It can also include specific return instructions for the customer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:66 msgid "After :ref:`enabling the Return Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the return slip." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:70 msgid "The return slip displays the company's return address, along with barcodes for both the order and the return operation." msgstr "" @@ -5979,24 +5911,24 @@ msgstr "" msgid "Example return slip." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:80 msgid "Product labels" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:82 msgid "Print *product labels* to affix to items in an order, providing essential information, such as product name, barcode, and price." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:85 msgid "After navigating to the intended operation type (:menuselection:`Inventory app --> Configuration --> Operations Types`), in the :guilabel:`Hardware` tab, tick the :guilabel:`Product Labels` option." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:85 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:141 msgid "Doing so makes the :guilabel:`Print label as:` drop-down menu visible, where each product label can be printed as:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:91 msgid ":guilabel:`2 x 7 with price`: PDF displays product name, barcode, and price, fitting two rows and seven columns of product labels per page." msgstr "" @@ -6004,7 +5936,7 @@ msgstr "" msgid "Example 2 x 7 with price." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:100 msgid ":guilabel:`4 x 7 with price`: displays product name, barcode, and price, fitting four rows and seven columns of product labels per page." msgstr "" @@ -6012,7 +5944,7 @@ msgstr "" msgid "Example 4 x 7 with price." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:109 msgid ":guilabel:`4 x 12`: displays product name and barcode. Fits four rows and twelve columns of product labels per page." msgstr "" @@ -6020,35 +5952,35 @@ msgstr "" msgid "Example 4 x 12." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:118 msgid ":guilabel:`4 x 12 with price`: displays product name, barcode, and price. Fits four rows and twelve columns of product labels per page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:120 msgid ":guilabel:`ZPL Labels`: prints labels in the Zebra Programming Language (ZPL) containing the product name and barcode. Readable for Zebra printers to automatically print labels." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:122 msgid ":guilabel:`ZPL Labels with price`: prints labels in the :abbr:`ZPL (Zebra Programming Language)` containing the product name, barcode, and price." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:126 msgid "Product labels can be manually printed from any delivery order, by clicking the :guilabel:`Print Labels` button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:132 msgid "Lot/SN Labels" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:134 msgid "Print *lot/SN labels* to affix to items in an order, providing essential information, such as product name, lot or serial number, and the barcode." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:137 msgid "To automatically print this PDF, navigate to the intended operation type's options page (:menuselection:`Inventory app --> Configuration --> Operations Types`). Then, in the :guilabel:`Hardware` tab, tick the :guilabel:`Lot/SN Labels` option." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:144 msgid ":guilabel:`4 x 12 - One per lot/SN`: PDF with labels for unique lot/serial numbers in the order, including product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." msgstr "" @@ -6056,22 +5988,209 @@ msgstr "" msgid "Order with only one unique set of lot/serial numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:150 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:154 msgid "Labels for an order with only one unique set of lot/serial numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:152 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:156 msgid ":guilabel:`4 x 12 - One per unit`: PDF with labels matching the quantity of items, displaying the product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:158 msgid ":guilabel:`ZPL Labels - One per lot/SN`: prints labels in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:160 msgid ":guilabel:`ZPL Labels - One per unit`: prints labels with the quantity of items in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:166 +msgid "Carrier labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:168 +msgid "To automatically print a *carrier label* with the recipient address, tracking number, and carrier details for specific third-party shipping carriers, complete the following setup:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:171 +msgid "Tick the :guilabel:`Carrier Labels` checkbox in the :ref:`operation type settings `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:258 +msgid ":doc:`Connect a printer <../../../../general/iot/devices/printer>` to Odoo's *IoT* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:174 +msgid ":ref:`Assign the carrier label to the printer `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:175 +msgid "Configure the shipping method's :ref:`label type `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:262 +msgid "Assign printer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:182 +msgid "Refer to the :doc:`Connect a printer <../../../../general/iot/devices/printer>` documentation for details on connecting a printer to Odoo's *IoT* app. Upon completion, assign the carrier label to the printer, by navigating to :menuselection:`IoT app --> Devices`, and selecting the desired printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 +msgid "Show a list of IoT devices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:191 +msgid "In the printer configuration form, go to the :guilabel:`Printer Reports` tab to configure the types of documents the printer automatically prints. Click :guilabel:`Add a line` to open the :guilabel:`Add: Reports` pop-up window. In the :guilabel:`Search...` bar, type `Shipping`, and select :guilabel:`Shipping Labels`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:197 +msgid "The :guilabel:`Shipping Documents` report is for :ref:`export documents `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 +msgid "Show carrier label report added to the *Printer Reports*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:204 +msgid "After adding the :guilabel:`Shipping Labels` report in the :guilabel:`Printer Reports` tab, ensure the :guilabel:`Report Type` matches the IoT-connected printer's type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:207 +msgid "For laser printers, set the :guilabel:`Report Type` to :guilabel:`PDF`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:208 +msgid "For Zebra printers, set the :guilabel:`Report Type` to :guilabel:`Text`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:213 +msgid "Shipping carrier label type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:215 +msgid "Next, complete the setup for the :doc:`third-party shipping connector <../setup_configuration/third_party_shipper>`. After that, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`, and select the desired shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:219 +msgid "On the shipping method configuration form, in the :guilabel:`[carrier name] Configuration` tab, ensure the :guilabel:`Label Format` matches the :ref:`report type assigned earlier `:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:223 +msgid "For laser printers, set the :guilabel:`Label Format` to :guilabel:`PDF`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:224 +msgid "For Zebra printers, set the :guilabel:`Label Format` to :guilabel:`ZPL2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 +msgid "Show the *Label Type* field on FedEx's shipping method configuration page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:231 +msgid "Example carrier label" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:233 +msgid "After validating the operation, the carrier label is generated in the chatter, and printed using the IoT-connected printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +msgid "Show an example carrier label for FedEx." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:242 +msgid "Carrier label for FedEx, containing the recipient address, tracking number, barcode, and other shipping information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:246 +msgid ":doc:`Print carrier labels <../setup_configuration/labels>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:251 +msgid "Export document" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:253 +msgid "An *export document*, required by customs to ship packages from one country to another, can be automatically printed in Odoo by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:256 +msgid "Tick the :guilabel:`Export Documents` checkbox in the :ref:`operation type settings `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:259 +msgid "Assign the export document to the printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:264 +msgid "Similar to the :ref:`printer assignment instructions for carrier labels `, after connecting a compatible printer to the Odoo *IoT* app, go to :menuselection:`IoT app --> Devices`, and select the desired printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:268 +msgid "In the printer configuration form, go to the :guilabel:`Printer Reports` tab, and click :guilabel:`Add a line`. In the :guilabel:`Add: Reports` pop-up window that appears, add the :guilabel:`Shipping Documents` report to assign the export document to the printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:278 +msgid "Export document for a shipment from the USA to Belgium." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:283 +msgid "Package content" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:285 +msgid "A *package content* PDF includes the package's barcode, packed date, along with a list of contained products and quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:288 +msgid "To print this form automatically, go to :menuselection:`Inventory app --> Configuration --> Operation Types`, and select the desired operation type. Then, go to the :guilabel:`Hardware` tab, and tick the :guilabel:`Package Contents` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:293 +msgid "If the option is not available, enable the :doc:`Packages <../../product_management/product_tracking/package>` feature, by going to :menuselection:`Inventory app --> Configuration --> Settings`, ticking the :guilabel:`Packages` checkbox, and clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:298 +msgid "After enabling the feature in the :guilabel:`Hardware` tab, validating the operation prints a PDF of the package contents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +msgid "Package contents form showing the package contents, barcode, and pack date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:307 +msgid "Package contents showing the package contents, barcode, and pack date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:312 +msgid "Package label" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:314 +msgid "A *package label* that shows the package's barcode and pack date can be configured to print upon clicking the *Put in Pack* button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:318 +msgid "The :guilabel:`Put in Pack` button is available **only** when the :doc:`Packages <../../product_management/product_tracking/package>` feature is enabled in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:322 +msgid "After it is enabled, the :guilabel:`Put in Pack` button is available on all inventory operations (e.g. receipt, pickings, internal transfers, delivery orders, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:325 +msgid "To automatically print the package label when the :guilabel:`Put in Pack` button is clicked, go to :menuselection:`Inventory app --> Configuration --> Operation Types`. Select the desired operation type, and tick the :guilabel:`Package Label` checkbox in the :guilabel:`Hardware` tab. Labels can be printed in :guilabel:`PDF` or :guilabel:`ZPL` file formats, as defined in the :guilabel:`Print label as` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +msgid "PDF of package barcode and package date." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:3 msgid "Scheduled delivery dates" msgstr "" @@ -7753,6 +7872,157 @@ msgstr "" msgid "Setup and configuration" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:3 +msgid "Bpost integration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:5 +msgid "Set up the *Bpost* shipping connector in Odoo to manage Bpost shipments to clients directly within Odoo. To configure it, complete these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:8 +msgid "Create a Bpost account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:9 +msgid "Get the :ref:`Account ID and passphrase `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:10 +msgid "Set up the shipping method in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:12 +msgid "Upon completion, it is possible to calculate the cost of shipping, based on package size and weight, have the charges applied directly to a Bpost business account, and automatically print Bpost tracking labels through Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:10 +msgid ":doc:`third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:18 +msgid ":doc:`delivery_method`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:19 +msgid ":doc:`dhl_credentials`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:21 +msgid ":doc:`ups_credentials`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:23 +msgid "Bpost account setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:25 +msgid "To begin, go to the `Bpost website `_ to create, or log into, the company's Bpost business account. When creating the Bpost account, have the company's VAT number and mobile phone number ready." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:29 +msgid "Follow the website's steps to complete registration, and sign up for shipping services." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:31 +msgid "After completing the setup, get the Bpost account ID and passphrase, by navigating to the :guilabel:`Shipping Manager` menu item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:36 +msgid "On the :guilabel:`Shipping Manager` page, go to the :guilabel:`Admin` tab, then the :guilabel:`General Settings` tab, to find the :guilabel:`Account ID` and :guilabel:`Passphrase` needed to configure Odoo's shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:-1 +msgid "In the *Admin* tab, show the Account ID and Passphrase." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:45 +msgid "Configure Bpost shipping method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:47 +msgid "With those necessary credentials, configure the Bpost shipping method in Odoo by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:50 +msgid "On the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:52 +msgid "In the :guilabel:`Provider` field, select :guilabel:`Bpost` from the drop-down menu. Doing so reveals the :guilabel:`Bpost Configuration` tab at the bottom of the form, where the Bpost credentials can be entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:56 +msgid "For details on configuring the other fields on the shipping method, such as :guilabel:`Delivery Product`, refer to the :doc:`Configure third-party carrier ` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:60 +msgid "To generate Bpost :doc:`shipping labels ` through Odoo, ensure the :guilabel:`Integration Level` option is set to :guilabel:`Get Rate and Create Shipment`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:63 +msgid "In the :guilabel:`Bpost Configuration` tab, complete the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:65 +msgid ":guilabel:`Bpost Account Number` (required field): enter the company's unique :ref:`account ID ` from the Bpost website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:67 +msgid ":guilabel:`Passphrase` (required field): enter the :ref:`passphrase ` from the Bpost website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:69 +msgid ":guilabel:`Bpost Delivery Nature`: select either :guilabel:`Domestic` or :guilabel:`International` shipping services. Choosing :guilabel:`Domestic` shows the :guilabel:`Options` section, while :guilabel:`International` enables the :guilabel:`Bpost Shipment Type` and :guilabel:`Bpost Parcel Return Instructions` fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:73 +msgid ":guilabel:`Bpost Package Type`: select the type of shipping service from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:75 +msgid "For `domestic delivery `_, the options are: :guilabel:`bpack 24h Pro`, :guilabel:`bpack 24h business`, or :guilabel:`bpack Bus`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:80 +msgid "For `international delivery `_, the options are: :guilabel:`bpack World Express Pro`, :guilabel:`bpack World Business`, or :guilabel:`bpack Europe Business`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:83 +msgid ":guilabel:`Bpost Shipment Type` (required field): for international deliveries, declare the type of goods in the package as :guilabel:`SAMPLE`, :guilabel:`GIFT`, :guilabel:`GOODS`, :guilabel:`DOCUMENTS`, or :guilabel:`OTHER`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:86 +msgid ":guilabel:`Bpost Parcel Return Address`: return address when an international shipment fails to deliver. Select from the drop-down menu: :guilabel:`Destroy`, :guilabel:`Return to sender by air`, or :guilabel:`Return to sender by road`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:89 +msgid ":guilabel:`Label Type`: choose :guilabel:`A6` or :guilabel:`A4` label sizes from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:91 +msgid ":guilabel:`Label Format`: choose :guilabel:`PDF` or :guilabel:`PNG` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:93 +msgid "For domestic deliveries, these features are available in the :guilabel:`Options` section:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:95 +msgid "Enable the :guilabel:`Delivery on Saturday` feature to include Saturdays as possible delivery dates. Depending on the :guilabel:`Bpost Package Type` selected, this option might incur additional costs to the company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:98 +msgid "Enable the :guilabel:`Generate Return Label` feature to automatically print a return label upon validating the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:-1 +msgid "Show Bpost shipping method." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:3 msgid "Delivery methods" msgstr "" @@ -7952,7 +8222,7 @@ msgid "To invoice the customer for the shipping cost to the pickup location, cho msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:172 -msgid ":ref:`Invoice cost of shipping `" +msgid ":doc:`Invoice cost of shipping <../advanced_operations_shipping/invoicing>`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:177 @@ -8036,6 +8306,155 @@ msgstr "" msgid "You need to write to xmlrequests@dhl.com along with your full Account details like account number, region, address, etc. to get API Access." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:3 +msgid "Print shipping labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:8 +msgid "Integrate Odoo with :doc:`third-party shipping carriers <../setup_configuration/third_party_shipper>` to automatically generate shipping labels that includes prices, destination addresses, tracking numbers, and barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:13 +msgid ":ref:`Automatically print shipping carrier labels `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:18 +msgid "To generate labels for a third-party shipping carrier, first :doc:`install the third-party shipping connector <../setup_configuration/third_party_shipper>`. Then, configure and activate the :ref:`delivery method `, being sure to set the :guilabel:`Integration Level` to :guilabel:`Get Rate and Create Shipment` to generate shipping labels. Finally, provide the company's :ref:`source address ` and :ref:`product weights `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:-1 +msgid "Set the \"Get Rate and Create Shipment\" option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:36 +msgid "Labels for multi-step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:38 +msgid "For companies using :doc:`two <../daily_operations/receipts_delivery_two_steps>` or :doc:`three step delivery <../daily_operations/delivery_three_steps>`, labels can be triggered to print after validating the picking or packing operation. To do that, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and choose the desired operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:43 +msgid "On the :guilabel:`Operation Type` configuration page, tick the :guilabel:`Print Label` checkbox. Enabling this feature ensures that the third-party shipping label is printed upon validating this operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:48 +msgid "For :doc:`two-step delivery <../daily_operations/receipts_delivery_two_steps>`, where products are placed directly in packages during picking, companies can print shipping labels during picking instead of delivery. Odoo allows users to enable the :guilabel:`Print Label` feature on the `Pick` operation itself to achieve this flexibility." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:0 +msgid "Enable the \"Print Label\" feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:58 +msgid "Print tracking labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:60 +msgid "Tracking labels are printed when specific operations are validated. By default, validating a delivery order (DO) generates a tracking label in the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:64 +msgid "For companies using two or three step delivery, refer to the :ref:`printing labels for multi-step delivery ` section to learn how to print the label after validating a picking or packing operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:68 +msgid "When both the *Sales* and *Inventory* apps are installed, begin in the :menuselection:`Sales` app, and proceed to the desired quotation or sales order (SO). There, and :ref:`add the shipping cost ` to the order. Then, navigate to the linked |DO| — or another operation type when using multi-step delivery — to validate the operation and print the label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:74 +msgid "If only the *Inventory* app is installed, create :abbr:`DOs (Delivery Orders)` directly in the :menuselection:`Inventory` app, :ref:`add the third-party carrier ` in the :guilabel:`Carrier` field, and validate the |DO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:82 +msgid "Add shipping on quotation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:84 +msgid "To generate a tracking label for an order, begin by creating a quotation in :menuselection:`Sales app --> Orders --> Quotations`, clicking :guilabel:`New`, and filling out the quotation form. Then, click the :guilabel:`Add Shipping` button in the bottom-right corner of the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:-1 +msgid "Show the \"Add Shipping\" button on the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:92 +msgid "In the resulting pop-up window, select the intended carrier from the :guilabel:`Shipping Method` drop-down menu. The :guilabel:`Total Order Weight` field is automatically populated, based on the :ref:`weight of products in the order `. Modify this field to overwrite the predicted weight, and use this weight to estimate the cost of shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:97 +msgid "Next, click :guilabel:`Get Rate` to display the shipping cost for the customer, via the third-party carrier in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:101 +msgid "If clicking :guilabel:`Get Rate` results in an error, ensure the :ref:`warehouse's address ` and :ref:`weight of products in the order ` are properly configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:105 +msgid "Click :guilabel:`Add` to add the cost to the quotation, which is listed as the :ref:`configured delivery product `. Finally, click :guilabel:`Confirm` on the quotation, and click the :guilabel:`Delivery` smart button to access the |DO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:-1 +msgid "Show \"Get rate\" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:115 +msgid "For users who do not have the *Sales* app installed, specify the :guilabel:`Carrier` by going to the :menuselection:`Inventory` app, navigating to the |DO|, and going to the :guilabel:`Additional Info` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:0 +msgid "Show the \"Additional Info\" tab of a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:126 +msgid "Validate delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:128 +msgid "On a delivery order form, navigate to the :guilabel:`Additional Info` tab to ensure the third-party shipping carrier has been added to the :guilabel:`Carrier` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:132 +msgid "If the *Sales* app is not installed, the third-party carrier is set in the :guilabel:`Carrier` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:135 +msgid "After the items in the order have been packed, click :guilabel:`Validate` to get the shipping carrier's tracking number, and generate the shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:139 +msgid "Create or select an existing delivery order by going to the :menuselection:`Inventory` app, and selecting the :guilabel:`Delivery Orders` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:142 +msgid "The :guilabel:`Tracking Reference` number is generated in the :guilabel:`Additional Info` tab of the delivery order. Click the :guilabel:`Tracking` smart button to access the tracking link from the shipping carrier's website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:146 +msgid "The tracking label is found in PDF format in the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:-1 +msgid "Show generated shipping label in the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:153 +msgid "For multi-package shipping, one label is generated per package. Each label appears in the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:160 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:160 +msgid "Sample label generated from Odoo's shipping connector with FedEx." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:163 +msgid ":doc:`../advanced_operations_shipping/invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:164 +msgid ":doc:`../advanced_operations_shipping/multipack`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:3 msgid "Sendcloud configuration" msgstr "" @@ -8733,25 +9152,17 @@ msgid "Third-party shipping carriers" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:10 -msgid "Users can link third-party shipping carriers to Odoo databases, in order to verify carriers' delivery to specific addresses, :doc:`automatically calculate shipping costs `, and :doc:`generate shipping labels <../advanced_operations_shipping/labels>`." +msgid "Users can link third-party shipping carriers to Odoo databases, in order to verify carriers' delivery to specific addresses, :doc:`automatically calculate shipping costs `, and :doc:`generate shipping labels `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:14 msgid "In Odoo, shipping carriers can be applied to a sales order (SO), invoice, or delivery order. For tips on resolving common issues when configuring shipping connectors, skip to the :ref:`Troubleshooting ` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:19 -msgid ":doc:`dhl_credentials`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:20 msgid ":doc:`sendcloud_shipping`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:21 -msgid ":doc:`ups_credentials`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:23 msgid "The following is a list of available shipping connectors in Odoo:" msgstr "" @@ -8911,7 +9322,7 @@ msgid ":guilabel:`Integration Level`: choose :guilabel:`Get Rate` to simply get msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:118 -msgid "Select :guilabel:`Get Rate and Create Shipment` to also :doc:`generate shipping labels <../advanced_operations_shipping/labels>`." +msgid "Select :guilabel:`Get Rate and Create Shipment` to also :doc:`generate shipping labels `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:123 @@ -9063,7 +9474,7 @@ msgid "In the :guilabel:`Additional info` tab, set the :guilabel:`Carrier` field msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:269 -msgid ":doc:`Generate shipping labels <../advanced_operations_shipping/labels>`" +msgid ":doc:`Generate shipping labels `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 @@ -9135,11 +9546,7 @@ msgid "UPS integration" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:5 -msgid "UPS is a shipping carrier service that integrates with Odoo to coordinate shipping to all regions. Once integrated, users can create shipping methods that estimate shipping costs and :doc:`generate labels <../advanced_operations_shipping/labels>`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:10 -msgid ":doc:`third_party_shipper`" +msgid "UPS is a shipping carrier service that integrates with Odoo to coordinate shipping to all regions. Once integrated, users can create shipping methods that estimate shipping costs and :doc:`generate labels `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:12 @@ -12274,7 +12681,6 @@ msgid "New warehouse location creation form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation.rst:5 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:123 msgid "Inventory valuation" msgstr "" @@ -12363,46 +12769,46 @@ msgid "When creating new vendor bills, this product can be added as an invoice l msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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|, and its *Costing Method* set to |AVCO|." +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 ` or :doc:`automatic `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:91 msgid "Create vendor bill" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:102 -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 :guilabel:`Save manually (cloud with arrow)` icon to update the draft bill." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 msgid "Landed Costs column checkboxes for product and landed cost." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:116 msgid "Additionally, at the top of the form, a :guilabel:`Create Landed Costs` button appears." msgstr "" @@ -12410,19 +12816,19 @@ msgstr "" msgid "Create Landed Costs button on vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:123 msgid "Add landed cost" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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 "" @@ -12430,43 +12836,43 @@ msgstr "" msgid "Landed cost form with selected receipt transfer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:141 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:151 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:159 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:169 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/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 "" @@ -12475,7 +12881,8 @@ msgid "Journal Entry form for landed cost created from vendor bill." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:3 -msgid "Inventory valuation configuration" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:15 +msgid "Automatic inventory valuation" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:7 @@ -12483,136 +12890,192 @@ msgid "All of a company's stock on-hand contributes to the valuation of its inve msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:11 -msgid "By default, Odoo uses a periodic inventory valuation (also known as manual inventory valuation). This method implies that the accounting team posts journal entries based on the physical inventory of the company, and that warehouse employees take the time to count the stock. In Odoo, this method is reflected inside each product category, where the :guilabel:`Costing Method` field will be set to `Standard Price` by default, and the :guilabel:`Inventory Valuation` field will be set to `Manual`." +msgid "By default, Odoo uses a periodic inventory valuation (also known as manual inventory valuation). This method implies that the accounting team manually posts journal entries, based on the physical inventory of the company, and warehouse employees take the time to count the stock. In Odoo, each product category reflects this, with the :guilabel:`Costing Method` set to :guilabel:`Standard Price`, and the :guilabel:`Inventory Valuation` (not visible by default) set to :guilabel:`Manual`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 -msgid "The Inventory Valuation fields are located on the Product Categories form." +msgid "The Costing Method field is located on the Product Categories form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:21 -msgid "Alternatively, automated inventory valuation is an integrated valuation method that updates the inventory value in real-time by creating journal entries whenever there are stock moves initiated between locations in a company's inventory." +msgid "Alternatively, perpetual (automatic) inventory valuation creates real-time *journal entries* in the *Accounting* app whenever stock enters or leaves the company's warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:26 -msgid "Automated inventory valuation is a method recommended for expert accountants, given the extra steps involved in journal entry configuration. Even after the initial setup, the method will need to be periodically checked to ensure accuracy, and adjustments may be needed on an ongoing basis depending on the needs and priorities of the business." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:24 +msgid "This document is focused on the proper setup of automatic inventory valuation, which is an integrated valuation method that ensures journal entries in the *Accounting* app match stock valuation updates in the *Inventory* app. For an introduction of inventory valuation in Odoo, refer to the :doc:`using_inventory_valuation` documentation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:34 -msgid "Types of accounting" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:30 +msgid "Switching to automatic inventory valuation **does not** create journal entries for existing stock, potentially leading to discrepancies between stock valuation and accounting journals." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:36 -msgid "Accounting entries will depend on the accounting mode: *Continental* or *Anglo-Saxon*." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:33 +msgid "To manually post journal entries for existing stock, navigate to :menuselection:`Inventory app --> Reporting --> Valuation` for a list of current stock and its value. Then, :doc:`post a journal entry <../../../../finance/accounting/vendor_bills>` for each existing item." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:39 -msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting app --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:40 +msgid "To properly set up automatic inventory valuation, follow these steps in Odoo:" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:42 -msgid "Then, in the search bar, look for :guilabel:`Anglo-Saxon Accounting`, to see if the feature is enabled. If it is **not** enabled, Continental accounting mode is in use." +msgid ":ref:`Install Accounting app and enable specific settings `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:44 +msgid ":ref:`Set Automatic inventory valuation on product categories `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:46 +msgid ":ref:`Set costing method `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:51 +msgid "Accounting setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:53 +msgid "To use automatic inventory valuation, install the *Accounting* app. Next, go to :menuselection:`Accounting app --> Configuration --> Settings`, and in the :guilabel:`Stock Valuation` section, tick the :guilabel:`Automatic Accounting` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:59 +msgid "Enabling :guilabel:`Automatic Accounting` shows the previously invisible *Inventory Valuation* field on a product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 +msgid "Automatic Accounting feature in Stock Valuation section of Settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:66 +msgid "Refer to the :ref:`Expense ` and :ref:`Stock input/output ` sections of documentation for details on configuring the accounting journals shown." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:73 +msgid "Product category setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:75 +msgid "After :ref:`enabling inventory valuation `, the next step is to set the product category to use automatic inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:78 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select the desired product category. In the :guilabel:`Inventory Valuation` section, set the :guilabel:`Inventory Valuation` field to :guilabel:`Automated`. Repeat this step for every product category intending to use automatic inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:84 +msgid "After enabling automatic accounting, each new stock move layer (SVL), that is created during inventory valuation updates, generates a journal entry." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 +msgid "Inventory Valuation field on the product category, with its various stock accounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:94 +msgid "Costing method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:96 +msgid "After :ref:`enabling inventory valuation `, the *costing method* for calculating and recording inventory costs is defined on the product category in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:100 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category. In the :guilabel:`Inventory Valuation` section, select the appropriate :guilabel:`Costing Method`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:104 +msgid ":guilabel:`Standard Price`: the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 +msgid ":guilabel:`Average Cost (AVCO)`: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:113 +msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:119 +msgid ":guilabel:`First In First Out (FIFO)`: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it is highly sensitive to input data and human error." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:127 +msgid "Changing the costing method greatly impacts inventory valuation. It is highly recommended to consult an accountant first before making any adjustments here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:131 +msgid ":doc:`using_inventory_valuation`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:133 +msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo generates a corresponding record in the *Inventory Valuation* report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:140 +msgid "It is possible to use different valuation settings for different product categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:145 +msgid "Types of accounting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:147 +msgid "With automated inventory valuation set up, the generated journal entries depend on the chosen accounting mode: *Continental* or *Anglo-Saxon*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:151 +msgid "Verify the accounting mode by activating the :ref:`developer-mode`, and navigating to :menuselection:`Accounting app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:154 +msgid "Then, in the :guilabel:`Search...` bar, look for `Anglo-Saxon Accounting`, to see if the feature is enabled. If it is **not** enabled, *Continental* accounting mode is in use." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 msgid "Show the Anglo-Saxon accounting mode feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:49 -msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. So for **manual** valuation method, set the :guilabel:`Expense Account` to `Stock Valuation` for the current asset type; for **automatic** valuation method, set the the :guilabel:`Expense Account` to an *Expenses* or a *Cost of Revenue* type (e.g. `Cost of Production`, `Cost of Goods Sold`, etc.)." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:161 +msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means the cost of a good is only recorded as an expense when a customer is invoiced for a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:56 -msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Because of this, the :guilabel:`Expense Account` can be set to **either** *Expenses* or a *Cost of Revenue* type, however, it is more commonly set to an *Expenses* account." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:165 +msgid "So, for **manual** valuation method, set the *Expense Account* to *Stock Valuation* for the current asset type; for **automatic** valuation method, set the *Expense Account* to an *Expenses* or a *Cost of Revenue* type (e.g. *Cost of Production*, *Cost of Goods Sold*, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:61 -msgid ":ref:`Details about configuring Expense and Stock accounts `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:169 +msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Because of this, the *Expense Account* can be set to **either** *Expenses* or a *Cost of Revenue* type, however, it is more commonly set to an *Expenses* account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:67 -msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory app --> Configuration --> Product Categories`. In the :guilabel:`Inventory Valuation` section, select the desired :guilabel:`Costing Method` and :guilabel:`Inventory Valuation` options." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:173 +msgid "Refer to the :ref:`Expense ` and :ref:`Stock input/output ` sections for details on configuring each account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:72 -msgid "It is possible to use different valuation settings for different product categories." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 -msgid "Show inventory valuation configuration options." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:81 -msgid "Costing method" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:83 -msgid "From the product category's configuration page, choose the desired :guilabel:`Costing Method`:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:85 -msgid ":guilabel:`Standard Price`: the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:89 -msgid ":guilabel:`Average Cost (AVCO)`: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:94 -msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:100 -msgid ":guilabel:`First In First Out (FIFO)`: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it is highly sensitive to input data and human error." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 -msgid "Changing the costing method greatly impacts inventory valuation. It is highly recommended to consult an accountant first before making any adjustments here." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:112 -msgid ":doc:`using_inventory_valuation`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 -msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:125 -msgid "Inventory valuation in Odoo can be set to be updated manually or automatically. While *Expense* accounts apply to both, the *Stock Input* and *Stock Output* accounts are only used for automated valuation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:129 -msgid "Refer to the :ref:`Expense ` and :ref:`Stock input/output ` sections for details on configuring each account type." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:180 msgid "Expense account" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:137 -msgid "To configure the *expense account*, go to the :guilabel:`Account Properties` section of the intended product category (:menuselection:`Inventory app --> Configuration --> Product Categories`). Then, choose an existing account from the :guilabel:`Expense Account` drop-down menu." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:182 +msgid "To configure the *expense account*, which is used in both manual and automatic inventory valuation, go to the :guilabel:`Account Properties` section of the intended product category (:menuselection:`Inventory app --> Configuration --> Product Categories`). Then, choose an existing account from the :guilabel:`Expense Account` drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:141 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:187 msgid "To ensure the chosen account is the correct :guilabel:`Type,` click the |right arrow| icon to the right of the account. Then, set the account type based on the information below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:146 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:214 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:192 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:260 msgid "Anglo-Saxon" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:150 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:196 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:223 msgid "Automated" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:152 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:198 msgid "In Anglo-Saxon accounting for automated inventory valuation, set the :guilabel:`Expense Account` to the `Expenses` account. Then, click the |right arrow| icon to the right of the account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:202 msgid "In the pop-up window, choose :guilabel:`Expenses` or :guilabel:`Cost of Revenue` from the :guilabel:`Type` drop-down menu." msgstr "" @@ -12620,7 +13083,7 @@ msgstr "" msgid "Show **Expense Account** field, and external link icon." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:211 msgid "To configure the :guilabel:`Expense Account`, choose :guilabel:`Stock Valuation` from the field's drop-down menu. Verify the account's type by clicking the |right arrow| icon, and then ensure the :guilabel:`Type` is :guilabel:`Current Assets`." msgstr "" @@ -12628,49 +13091,49 @@ msgstr "" msgid "Show the **Expense Account** field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:173 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:232 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:219 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:278 msgid "Continental" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:179 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:184 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:230 msgid "Set the :guilabel:`Expense Account` to the :guilabel:`Expenses` or :guilabel:`Cost of Revenue` account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:190 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:236 msgid "Stock input/output (automated only)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:192 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:238 msgid "To configure the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account`, go to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:196 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:242 msgid "In the :guilabel:`Inventory Valuation` field, select :guilabel:`Automated`. Doing so makes the :guilabel:`Account Stock Properties` section appear. These accounts are defined as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:199 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:245 msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:201 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:247 msgid ":guilabel:`Stock Journal`: accounting journal where entries are automatically posted when a product's inventory valuation changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:203 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:249 msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:253 msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:216 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:262 msgid "In Anglo-Saxon accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to *different* :guilabel:`Current Assets` accounts. This way, delivering products and invoicing the customer balance the *Stock Output* account, while receiving products and billing vendors balance the *Stock Input* account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:221 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:267 msgid "To modify the account type, go to the click the |right arrow| icon to the right of the stock input/output account. In the pop-up window, choose :guilabel:`Current Assets` from the :guilabel:`Type` drop-down menu." msgstr "" @@ -12678,15 +13141,15 @@ msgstr "" msgid "Display account setup page, highlighting the **Type** field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:229 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:275 msgid "The *Stock Input* account is set to `Stock Interim (Received)`, a *Current Asset* account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:234 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:280 msgid "In Continental accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to **the same** :guilabel:`Current Assets` account. That way, one account can be balanced when items are bought and sold." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:239 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:285 msgid "The stock input and output accounts are both set to `Stock Interim (Received)`, a :guilabel:`Current Assets` account type. They can also be set to the `Stock Interim (Delivered)`, as long as the input and output accounts are assigned to the **same** account." msgstr "" @@ -12694,30 +13157,42 @@ msgstr "" msgid "Show the Stock Input and Output accounts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:249 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:295 msgid "Inventory valuation reporting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:251 -msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:297 +msgid "To start, go to :menuselection:`Accounting app --> Reporting --> Balance Sheet`. Click the :guilabel:`Current Assets` line item to unfold the drop-down menu, and look for the nested :guilabel:`Stock Valuation`, :guilabel:`Stock Interim (Received)`, and :guilabel:`Stock Interim (Delivered)` lines." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:257 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:303 +msgid "At the top of the dashboard, click the :guilabel:`As of [date]` button to display accounting records up to a specified date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:307 +msgid ":ref:`Stock accounts and what they do `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:308 msgid ":doc:`../../../../finance/accounting/get_started/cheat_sheet`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:259 -msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:263 -msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 msgid "See the full inventory valuation breakdown in Odoo Accounting app." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:314 +msgid "Access more specific information by clicking the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon to the right of the desired journal. Select :guilabel:`General Ledger` to see a list of all of the journal entries, where each line item's :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon can be clicked to reveal the :guilabel:`View Journal Entry` option to open the individualized journal entry." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:320 +msgid "Additionally, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 +msgid "Show Stock Valuation journals in a list." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:3 msgid "Using inventory valuation" msgstr "" @@ -12730,10 +13205,6 @@ msgstr "" msgid "In Odoo, this process can be conducted manually— by warehouse employees physically counting the products— or automatically through the database." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:15 -msgid "Automatic inventory valuation" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:17 msgid "To use Odoo to automatically generate a trail of inventory valuation entries, first navigate to the :menuselection:`Product Categories` list by going to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category. On the form, set the :guilabel:`Inventory Valuation` as :guilabel:`Automated` and the :guilabel:`Costing Method` to any of the three options." msgstr "" @@ -14353,7 +14824,7 @@ msgid "Include additional product information" msgstr "" #: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:48 -msgid "The :guilabel:`Product Information` tab at the bottom of the form can be used to provide further details about the piece of equipment:" +msgid "The :guilabel:`Product Information` tab at the bottom of the page can be used to provide further details about the piece of equipment:" msgstr "" #: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:51 @@ -14393,31 +14864,35 @@ msgid "Add maintenance details" msgstr "" #: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:67 -msgid "The :guilabel:`Maintenance` tab includes information that can be useful to maintenance teams:" +msgid "The :guilabel:`Maintenance` tab at the bottom of the page provides information about the failure frequency of the piece of equipment:" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:69 -msgid ":guilabel:`Preventive Maintenance Frequency`: specifies how often maintenance should be performed to prevent equipment failure" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:71 -msgid ":guilabel:`Maintenance Duration`: the amount of time required to fix the equipment when it fails" +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:70 +msgid ":guilabel:`Expected Mean Time Between Failure`: the average number of days the equipment is expected to operate between failures. This number can be configured manually." msgstr "" #: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:72 -msgid ":guilabel:`Expected Mean Time Between Failure`: the average amount of time that the equipment is expected to operate before failing" +msgid ":guilabel:`Mean Time Between Failure`: the average number of days the equipment operates between failures. This number is calculated automatically based on previous failures, and cannot be configured manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:75 +msgid ":guilabel:`Estimated Next Failure`: the estimated date the equipment may experience its next failure. This date is calculated automatically based on the data in the :guilabel:`Mean Time Between Failure` and :guilabel:`Latest Failure` fields, and cannot be configured manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:79 +msgid ":guilabel:`Latest Failure`: the most recent date on which the equipment failed. This date is based on the creation date of the equipment's most recent maintenance request, and cannot be configured manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:82 +msgid ":guilabel:`Mean Time To Repair`: the average number of days needed to repair the equipment. This number is calculated automatically based on the duration of previous maintenance requests, and cannot be configured manually." msgstr "" #: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:-1 -msgid "The maintenance tab for the new piece of equipment." +msgid "The maintenance tab for a piece of equipment." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:80 -msgid "The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated automatically based on maintenance requests if any exist." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:86 -msgid "To see the maintenance requests for a piece of equipment, go to the page for the equipment and select :guilabel:`Maintenance` in the top right corner of the form." +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:91 +msgid "To see any open maintenance requests for a piece of equipment, go to the page for the equipment, and click the :guilabel:`Maintenance` smart button at the top of the page." msgstr "" #: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:3 @@ -18327,6 +18802,202 @@ msgstr "" msgid "Workflows" msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:3 +msgid "Allocation reports" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:11 +msgid "When fulfilling sales orders (SOs), or sourcing components for manufacturing orders (MOs), it is sometimes necessary to prioritize one |SO| or |MO| over another. In situations where there is insufficient stock on-hand to fulfill every |SO| or |MO|, ensuring that products and components are reserved for priority orders is essential." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:16 +msgid "In Odoo *Manufacturing*, allocation reports are used on |MOs| to assign products to specific sales orders |SOs|, or components to specific |MOs|. This ensures the products or components are available for those orders, and are not used by mistake." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:23 +msgid "To use allocation reports, the *Allocation Report for Manufacturing Orders* feature **must** be enabled. To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Allocation Report for Manufacturing Orders`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:28 +msgid "For products that are sold, it is also necessary to configure them so they can be included in |SOs|. To do so, begin by navigating to :menuselection:`Inventory --> Products --> Products`, and select a product. Under the :guilabel:`Product Name` field on the product form, make sure that the :guilabel:`Can Be Sold` checkbox is ticked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:34 +msgid "Allocate products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:36 +msgid "To allocate products or components from an |MO| to an |SO|, or to a different |MO|, begin by navigating to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`. Click :guilabel:`New` to create a new |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:40 +msgid "On the |MO| form, select a product in the :guilabel:`Product` field, and specify the quantity to be produced in the :guilabel:`Quantity` field. Finally, click :guilabel:`Confirm` to confirm the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:43 +msgid "The rest of the allocation workflow depends on the current on-hand quantity of the product being manufactured, and whether or not there are any |SOs| or |MOs| which require the product, but have not already been allocated units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:47 +msgid "If there **are** existing |SOs| and |MOs| that require the product, **and** there are too few units of the product on-hand to fulfill those orders, then an :icon:`fa-list` :guilabel:`Allocation` smart button appears at the top of the page as soon as the |MO| is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:51 +msgid "If there **are** existing |SOs| and |MOs| that require the product, **and** there are enough units of the product on-hand to fulfill those orders, then the :icon:`fa-list` :guilabel:`Allocation` smart button only appears at the top of the page once the |MO| has been marked as done, by clicking :guilabel:`Produce All`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 +msgid "The Allocation smart button at the top of an MO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:61 +msgid "If there **are not** any existing |SOs| and |MOs| that require the product, the :icon:`fa-list` :guilabel:`Allocation` smart button does not appear, even when the |MO| has been marked as done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:64 +msgid "Click the :icon:`fa-list` :guilabel:`Allocation` smart button to open the :guilabel:`MRP Reception Report` for the |MO|. This report lists open delivery orders or |MOs|, depending on the type of product produced in the original |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:69 +msgid "Allocate to delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:71 +msgid "If the |MO| contains a finished product, the report lists any open delivery orders for which quantities of the product have yet to be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:75 +msgid "An |MO| is created to produce three units of a *rocking chair*. Clicking the :guilabel:`Allocation` smart button on the |MO| opens an allocation report that lists open delivery orders that require one or more rocking chairs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:79 +msgid "Click the :guilabel:`Assign All` button to the right of a specific order to assign products for each quantity required to fulfill that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:83 +msgid "If an order requires one quantity of four units of the product, and one quantity of one unit of the product, clicking :guilabel:`Assign All` assigns five units of the product to fulfill both quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:87 +msgid "Alternatively, click :guilabel:`Assign` next to a specific quantity to only assign products to that quantity, and not any others in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:91 +msgid "If an order requires one quantity of four units of the product, and one quantity of one unit of the product, clicking :guilabel:`Assign` next to the quantity of one unit assigns a product to that quantity, but leaves the quantity of four units without any products assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 +msgid "The MRP Reception Report for an MO containing finished products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:100 +msgid "Allocate to MO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:102 +msgid "If the |MO| contains a component, the report lists any open |MOs| for which quantities of the component have yet to be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:106 +msgid "An |MO| is created to produce three units of *wood*, which is used as a component for the *rocking chair* product. Clicking the :guilabel:`Allocation` smart button on the |MO| opens an allocation report that lists open rocking chair |MOs| that require one or more pieces of wood." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:110 +msgid "Click the :guilabel:`Assign All` or :guilabel:`Assign` button to the right of a specific |MO| to assign components to that |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 +msgid "The MRP Reception Report for an MO containing components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:118 +msgid "Unassign products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:120 +msgid "After assigning products to a quantity within a delivery order, or components to an |MO|, the :guilabel:`Assign` button turns into an :guilabel:`Unassign` button. Click :guilabel:`Unassign` to unreserve the assigned products from that quantity, making them available for other quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:125 +msgid "Print labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:127 +msgid "After clicking :guilabel:`Assign All` or :guilabel:`Assign`, the :guilabel:`Print Labels` or :guilabel:`Print Label` button to the right of either button becomes selectable. Selecting either button generates and downloads a PDF document with one label for each product that was assigned. These labels are used to designate each product as being reserved for that specific order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 +msgid "The assignment labels generated by clicking Print Labels or Print Label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:3 +msgid "By-Products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:9 +msgid "When manufacturing certain products, it is common to be left with residual materials, in addition to the finished product. These materials are known as *by-products*. By specifying the by-products created during manufacturing on a product's bill of materials (BoM), the quantity of by-products on-hand is tracked by Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:15 +msgid "Manufacturing a *rocking chair* requires ten pieces of wood. During production, five pieces of *scrap wood* are created, in addition to the rocking chair. By designating the scrap wood as a by-product on the rocking chair's |BoM|, Odoo tracks the on-hand count of scrap wood, as well as the quantity of rocking chairs produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:23 +msgid "To specify by-products on a product's |BoM|, the *By-Products* setting **must** be enabled. To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the :guilabel:`By-Products` checkbox, located under the :guilabel:`Operations` heading. Then, click :guilabel:`Save` to apply the change." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:-1 +msgid "The By-Products setting on the Manufacturing app settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:32 +msgid "With the :guilabel:`By-Products` setting enabled, a :guilabel:`By-products` tab appears on product |BoMs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:36 +msgid "Add byproduct to BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:38 +msgid "To add by-products to a |BoM|, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select a |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:41 +msgid "On the |BoM|, select the :guilabel:`By-products` tab. Click :guilabel:`Add a line`, and select the by-product in the :guilabel:`By-product` drop-down field. In the :guilabel:`Quantity` field, enter the quantity of the by-product produced during manufacturing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:45 +msgid "If the by-product is produced during a specific operation of a manufacturing order (MO), select the operation in the :guilabel:`Produced in Operation` field. For example, if a scrap wood by-product is produced during an *Assemble* operation, select that operation in the :guilabel:`Produced in Operation` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:-1 +msgid "The By-Products tab on a BoM, configured with a \"Scrap Wood\" by-product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:55 +msgid "Manufacture by-product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:57 +msgid "When an |MO| is completed and marked as *Done*, Odoo registers the quantity of by-products created during the manufacturing process. To create a new |MO|, navigate to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:61 +msgid "In the :guilabel:`Bill of Material` field, select a |BoM| on which by-products have been specified. After doing so, the :guilabel:`Product` field auto-populates with the corresponding product. Click :guilabel:`Confirm` to confirm the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:65 +msgid "When manufacturing is completed, click the :guilabel:`Produce All` button at the top of the |MO|. After doing so, inventory counts update to reflect the quantity of by-product(s) produced, as well as the quantity of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:69 +msgid "Click the :guilabel:`Product Moves` smart button at the top of the |MO| page to see the movements of components and products. Each by-product is listed on the resulting :guilabel:`Inventory Moves` page, with the :guilabel:`From` column displaying the virtual production location, and the :guilabel:`To` column displaying the location where the by-product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:-1 +msgid "The Product Moves page for an MO with by-products." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:3 msgid "Manufacturing backorders" msgstr "" @@ -20807,7 +21478,7 @@ msgid ":doc:`blanket_orders`" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:15 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:20 msgid "Bill control policies" msgstr "" @@ -20848,7 +21519,7 @@ msgid "To do that, navigate to :menuselection:`Purchase app --> Products --> Pro msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:48 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:46 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51 msgid "3-way matching" msgstr "" @@ -21004,115 +21675,130 @@ msgstr "" msgid "Manage vendor bills" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:7 -msgid "A *vendor bill* is an invoice received for products and/or services that a company purchases from a vendor. Vendor bills record payables as they arrive from vendors, and can include amounts owed for the goods and/or services purchased, sales taxes, freight and delivery charges, and more." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:12 +msgid "A *vendor bill* is an invoice received for products and/or services purchased by a company from a vendor. Vendor bills record payables as they arrive from vendors, and can include amounts owed for the goods and/or services purchased, sales taxes, freight and delivery charges, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:11 -msgid "In Odoo, a vendor bill can be created at different points in the purchasing process, depending on the *bill control* policy chosen in the *Purchase* app settings." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:16 +msgid "In Odoo, a vendor bill can be created at different points in the purchasing process, depending on the *bill control* policy chosen in the *Purchase* app's settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:17 -msgid "To view and edit the default bill control policy and make changes to it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:22 +msgid "To configure the default bill control policy, navigate to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll to the :guilabel:`Invoicing` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:21 -msgid "Here, there are two :guilabel:`Bill Control` policy options: :guilabel:`Ordered quantities` and :guilabel:`Received quantities`. After a policy is selected, click :guilabel:`Save` to save changes." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:25 +msgid "The :guilabel:`Bill Control` feature lists two policy options: :guilabel:`Ordered quantities` and :guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 +msgid "The policy selected acts as the default for any new product created. Each policy acts as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:30 +msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:32 +msgid ":guilabel:`Received quantities`: a bill is only created **after** all (or part) of the total order has been received. The products and quantities received are used to generate a draft bill." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 msgid "Bill control policies in purchase app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 -msgid "The policy selected will be the default for any new product created. The definition of each policy is as follows:" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:39 +msgid "Once a policy is selected, click :guilabel:`Save` to save the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 -msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:42 +msgid "If a product needs a different control policy than the one set in the *Purchase* app settings, that product's control policy can be overridden by going to the :guilabel:`Purchase` tab on a product form, and selecting the desired policy in the :guilabel:`Control Policy` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:33 -msgid ":guilabel:`Received quantities`: a bill is only created **after** part of the total order has been received. The products and quantities **received** are used to generate a draft bill." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:37 -msgid "If a product needs a different control policy, the default bill control policy can be overridden by going to the :guilabel:`Purchase` tab in a product's template, and modifying its :guilabel:`Control Policy` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 msgid "Control policy field on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:48 -msgid "*3-way matching* ensures vendor bills are only paid once some (or all) of the products included in the purchase order have actually been received." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51 -msgid "To activate it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, tick the checkbox next to :guilabel:`3-way matching`, and click :guilabel:`Save` to save changes." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:53 +msgid "The *3-way matching* policy ensures vendor bills are only paid once all (or some) products in a purchase order (PO) have been received." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:56 -msgid ":guilabel:`3-way matching` is **only** intended to work with the :guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." +msgid "To activate 3-way matching, navigate to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll to the :guilabel:`Invoicing` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:60 -msgid "Create and manage vendor bills on receipts" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:59 +msgid "Tick the checkbox next to :guilabel:`3-way matching`, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:62 -msgid "When products are received into a company's warehouse, receipts are created. Once the company processes the received quantities, they can choose to create a vendor bill directly from the warehouse receipt form. Depending on the bill control policy chosen in the settings, vendor bill creation is completed at different steps of the procurement process." +msgid "The :guilabel:`3-way matching` feature is **only** intended to work with the :guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:66 +msgid "Create and manage vendor bills on receipts" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:68 -msgid "With the bill control policy set to ordered quantities" +msgid "When products are received into a company's warehouse, receipts are created. Once the company processes the received quantities, they can choose to create a vendor bill directly from the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:70 -msgid "To create and manage vendor bills on receipts using the *ordered quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Ordered quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:72 +msgid "Depending on the bill control policy chosen in the settings, vendor bill creation is completed at different steps of the procurement process." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:75 -msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new request for quotation (RFQ). Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:76 +msgid "Ordered quantities" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:78 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140 -msgid "On the blank detail form, add a vendor to the :abbr:`RFQ (request for quotation)` in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgid "To create and manage vendor bills for receipts with the *Bill Control* policy set to *Ordered Quantities*, first navigate to the :menuselection:`Purchase app`, and click :guilabel:`New` from the :guilabel:`Requests for Quotation` dashboard." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:82 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144 -msgid "Then, confirm the :abbr:`RFQ (request for quotation)` by clicking the :guilabel:`Confirm Order` button above the detail form. Doing so turns the :abbr:`RFQ (request for quotation)` into a purchase order." +msgid "Doing so opens a new :guilabel:`Request for Quotation` (RfQ) form. On the blank |RfQ| form, add a :guilabel:`Vendor`, and click :guilabel:`Add a line` under the :guilabel:`Product` tab to add products to the order." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86 -msgid "Then, click the :guilabel:`Create Bill` button to create a vendor bill for the purchase order." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:126 +msgid "On the product line, select a product from the drop-down menu in the :guilabel:`Product` field, and enter the quantity to order in the :guilabel:`Quantity` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:88 -msgid "Clicking the :guilabel:`Create Bill` button reveals the :guilabel:`Draft Bill` page for the purchase order." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:89 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:129 +msgid "Once ready, click :guilabel:`Confirm Order` to confirm the |RfQ| into a |PO|." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:91 -msgid "On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button to modify the bill, and add a bill date in the :guilabel:`Bill Date` field. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line` in the :guilabel:`Invoice Lines` tab." +msgid "Then, click :guilabel:`Create Bill` to create a vendor bill. This opens a :guilabel:`Vendor Bill` form in the :guilabel:`Draft` state. From here, add a billing date in the :guilabel:`Bill Date` field." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95 -msgid "Next, confirm the bill by clicking the :guilabel:`Confirm` button on the :guilabel:`Draft Bill` page." +msgid "Once ready, confirm the bill by clicking :guilabel:`Confirm` on the :guilabel:`Vendor Bill` page." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99 -msgid "Since the bill control policy is set to *ordered quantities*, the draft bill can be confirmed as soon as it is created, before any products have been received." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:98 +msgid "Since the bill control policy is set to *Ordered quantities*, the draft bill can be confirmed as soon as it is created, before any products have been received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:102 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:175 -msgid "On the new :guilabel:`Vendor Bill`, add a :guilabel:`Bill Reference` number, which can be used to match the bill with additional documents (such as the :abbr:`PO (purchase order)`). Then, click :menuselection:`Confirm --> Register Payment`. Doing so causes a pop-up to appear, wherein a payment :guilabel:`Journal` can be chosen; a :guilabel:`Payment Method` selected; and a :guilabel:`Recipient Bank Account` can be selected from a drop-down menu." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:101 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:152 +msgid "Once a payment has been received, click :guilabel:`Register Payment` at the top of the bill to record it." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:108 -msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the :guilabel:`Vendor Bill`. Doing so causes a green :guilabel:`In Payment` banner to display on the :abbr:`RFQ (request for quotation)` form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:104 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:155 +msgid "Doing so causes a :guilabel:`Register Payment` pop-up window to appear, wherein a payment :guilabel:`Journal` can be chosen, and a :guilabel:`Payment Method` selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:107 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:158 +msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be edited from this pop-up window, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:110 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:161 +msgid "Once ready, click :guilabel:`Create Payment` to finish creating the :guilabel:`Vendor Bill`. Doing so displays a green :guilabel:`Paid` banner on the |RfQ| form." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 @@ -21120,126 +21806,138 @@ msgid "Vendor bill form for ordered quantities control policy." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:118 -msgid "Each vendor bill provides the option to either :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note`. A *credit note* is typically issued when a vendor or supplier of goods get some quantity of products back from the customer to whom they were sold, while *debit notes* are reserved for goods returned from the customer/buyer to the vendor or supplier." +msgid "Received quantities" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:124 -msgid "With the bill control policy set to received quantities" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:120 +msgid "To create and manage vendor bills for receipts with the bill control policy set to *Received quantities*, first navigate to the :menuselection:`Purchase` app, and click :guilabel:`New`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:127 -msgid "If the creation of a vendor bill is attempted without receiving any quantities of a product (while using the *received quantities* bill control policy), an error message appears, and settings must be changed before proceeding." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:123 +msgid "Doing so opens a new |RfQ| form. On the blank |RfQ| form, add a :guilabel:`Vendor`, and click :guilabel:`Add a line` under the :guilabel:`Product` tab to add products to the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131 -msgid "To create and manage vendor bills on receipts using the *received quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Received quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:132 +msgid "When using the *Received quantities* control policy, clicking :guilabel:`Create Bill` before any products are received causes an :guilabel:`Invalid Operation` pop-up window to appear." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:136 -msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new :abbr:`RFQ (request for quotation)`. Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 -msgid "Finally, click the :guilabel:`Create Bill` button to create a bill for the purchase order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:151 -msgid "Clicking :guilabel:`Create Bill` before any products have been received will cause a :guilabel:`User Error` pop-up message to appear. The :guilabel:`Purchase Order` requires the receipt of at least partial quantity of the items included on the order to create a vendor bill." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:135 +msgid "Odoo requires at least partial quantities of the items included in the |PO| to be received in order to create a vendor bill." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 msgid "User error pop-up for received quantities control policy." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:159 -msgid "Next, click the :guilabel:`Receipt` smart button to view the warehouse receipt form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:142 +msgid "On the |PO|, click the :guilabel:`Receipt` smart button to view the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:161 -msgid "On the warehouse receipt form, click :menuselection:`Validate --> Apply` to mark the :guilabel:`Done` quantities. Then, navigate back to the :menuselection:`Purchase Order` (via the breadcrumbs), and click the :guilabel:`Create Bill` button on the purchase order form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144 +msgid "From here, click :guilabel:`Validate` to register the :guilabel:`Done` (received) quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:146 +msgid "Then, navigate back to the |PO|, via the breadcrumb, and click :guilabel:`Create Bill`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 +msgid "This opens a :guilabel:`Vendor Bill` form in the :guilabel:`Draft` state. From here, add a billing date in the :guilabel:`Bill Date` field. Once ready, confirm the bill by clicking :guilabel:`Confirm` at the top of the draft." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165 -msgid "Doing so reveals the :guilabel:`Draft Bill` for the purchase order. On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button, and add a :guilabel:`Bill Date`. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgid "Manage vendor bills in Accounting" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169 -msgid "Next, click the :guilabel:`Confirm` button to confirm the :guilabel:`Draft Bill`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:167 +msgid "Vendor bills can also be created directly from the *Accounting* app, without having to create a purchase order first." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:172 -msgid "Since the bill control policy is set to *received quantities*, the draft bill can **only** be confirmed when at least some of the quantities are received." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:170 +msgid "Navigate to :menuselection:`Accounting app --> Vendors --> Bills`, and click :guilabel:`New`. Doing so reveals a blank :guilabel:`Vendor Bill` form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:181 -msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the vendor bill. Doing so causes a green **In Payment** banner to display on the :abbr:`RFQ (request for quotation)` form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:173 +msgid "Add a vendor in the :guilabel:`Vendor` field. Then, in the :guilabel:`Invoice Lines` tab, click :guilabel:`Add a line` to add products." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:187 -msgid "Create and manage vendor bills in Accounting" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:176 +msgid "Select a product from the drop-down menu in the :guilabel:`Product` field, and enter the quantity to order in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:179 +msgid "Select a :guilabel:`Bill Date`, and configure any other necessary information. Finally, click :guilabel:`Confirm` to confirm the bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:182 +msgid "Once confirmed, click the :guilabel:`Journal Items` tab to view the :guilabel:`Account` journals. These journals are populated based on the configuration on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:186 +msgid "If necessary, click :guilabel:`Credit Note` to add a credit note to the bill. Additionally, a :guilabel:`Bill Reference` number can be added." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:189 -msgid "Vendor bills can also be created directly from the *Accounting* app, **without** having to create a purchase order first. To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`, and click :guilabel:`Create`. Doing so reveals a blank vendor bill detail form." +msgid "Once ready, click :guilabel:`Register Payment`, followed by :guilabel:`Create Payment`, to complete the :guilabel:`Vendor Bill`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193 -msgid "On this blank vendor bill detail form, add a vendor in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines (under the :guilabel:`Invoice Lines` tab), by clicking :guilabel:`Add a line`. Then, add a bill date in the :guilabel:`Bill Date` field, and any other necessary information. Finally, click :guilabel:`Confirm` to confirm the bill." +msgid "To link a draft bill to an existing purchase order, click the drop-down menu next to :guilabel:`Auto-Complete` *before* clicking :guilabel:`Confirm`, and select a |PO| from the menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:198 -msgid "From here, click the :guilabel:`Journal Items` tab to view (or change) the :guilabel:`Account` journals that were populated based on the configuration on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202 -msgid "Then, click :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note` to add credit or debit notes to the bill. Or, add a :guilabel:`Bill Reference` number (while in :guilabel:`Edit` mode)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:205 -msgid "Then, when ready, click :menuselection:`Register Payment --> Create Payment` to complete the :guilabel:`Vendor Bill`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209 -msgid "To tie the draft bill to an existing purchase order, click the drop-down menu next to :guilabel:`Auto-Complete`, and select a :abbr:`PO (purchase order)` from the menu. The bill will auto-populate with the information from the :abbr:`PO (purchase order)`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:196 +msgid "The bill auto-populates with the information from the chosen |PO|." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 msgid "Auto-complete drop-down list on draft vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:218 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:203 msgid "Batch billing" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:220 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:205 msgid "Vendor bills can be processed and managed in batches in the *Accounting* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222 -msgid "To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`. Then, click the :guilabel:`checkbox` at the top left of the page, beside the :guilabel:`Number` column, under the :guilabel:`Create` button. This selects all existing vendor bills with a :guilabel:`Posted` or :guilabel:`Draft` :guilabel:`Status`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:207 +msgid "Navigate to :menuselection:`Accounting app --> Vendors --> Bills`. Then, click the :guilabel:`checkbox` in the top-left corner, beside the :guilabel:`Number` column, under the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:211 +msgid "This selects all existing vendor bills with a :guilabel:`Status` of :guilabel:`Posted` or :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:214 +msgid "Click the :icon:`fa-print` :guilabel:`Print` button to print the selected invoices or bills." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:216 +msgid "Click :guilabel:`Register Payment` to create and process payments for multiple vendor bills at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:219 +msgid "Only payments with their :guilabel:`Status` listed as :guilabel:`Posted` can be billed in batches. Payments in the :guilabel:`Draft` stage **must** be posted before they can be included in a batch billing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:223 +msgid "Clicking :guilabel:`Register Payment` opens a :guilabel:`Register Payment` pop-up window. From the pop-up window, select the :guilabel:`Journal` the bills should post to, choose a :guilabel:`Payment Date`, and select a :guilabel:`Payment Method`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:227 -msgid "From here, click the :guilabel:`Action` gear icon to export, delete, or send & print the bills; click the :guilabel:`Print` icon to print the invoices or bills; or click :guilabel:`Register Payment` to create and process payments for multiple vendor bills at once." +msgid "There is also the option to :guilabel:`Group Payments` together from this pop-up window, as well. If this checkbox is ticked, only one payment is created, instead of one per bill. This option only appears if the *Batch Payments* feature is enabled in the settings of the :menuselection:`Accounting` app." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231 -msgid "When :guilabel:`Register Payment` is selected, a pop-up appears. In this pop-up window, select the appropriate journal in the :guilabel:`Journal` field, choose a payment date in the :guilabel:`Payment Date` field, and choose a :guilabel:`Payment Method`. There is also the option to :guilabel:`Group Payments` on this pop-up, as well." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:236 -msgid "When ready, click the :guilabel:`Create Payment` button, which creates a list of journal entries on a separate page. This list of journal entries are all tied to their appropriate vendor bills." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:232 +msgid "Once ready, click the :guilabel:`Create Payment` button. This creates a list of journal entries on a separate page. The journal entries on this list are all tied to their corresponding vendor bills." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 msgid "Batch billing register payment pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:244 -msgid "The :guilabel:`Register Payment` option for vendor bills in batches will only work for journal entries whose :guilabel:`Status` is set to :guilabel:`Posted`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:240 msgid ":doc:`control_bills`" msgstr "" @@ -22207,6 +22905,106 @@ msgstr "" msgid "Quality control basics" msgstr "" +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:3 +msgid "Failure locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:8 +msgid "In Odoo, *quality control points* (QCPs) are used to create *quality checks*, which prompt employees to confirm the quality of products, when they are included in certain operations. By setting one or more *failure locations* on a |QCP|, products that fail the quality checks it creates can be sent to one of the specified locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:14 +msgid "The *Failure Location* feature was added in version 17.0 of Odoo, and does **not** appear in any previous version. To upgrade an Odoo database to a more recent version, see the documentation on :doc:`database upgrades <../../../../administration/upgrade>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:21 +msgid "To use failure locations, the *Storage Locations* setting **must** be enabled in the settings of the *Inventory* app. This setting allows for the creation of sub-locations within a warehouse, including failure locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:25 +msgid "To enable the *Storage Locations* setting, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Storage Locations`, under the :guilabel:`Warehouses` heading. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:-1 +msgid "The Storage Locations setting on the Inventory app settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:34 +msgid "Failure locations are most effective when used for products configured as *storable products*. This is because inventory counts are only tracked for storable products, versus *consumable* products, for which exact counts are not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:38 +msgid "Quality checks can still be created for consumable products, and those products can be sent to a failure location if they fail a check. However, Odoo does not track the exact quantity of a consumable product stored at a failure location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:42 +msgid "To configure a product as storable, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product. In the :guilabel:`Product Type` field on the :guilabel:`General Information` tab, make sure that :guilabel:`Storable Product` is selected from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:48 +msgid "Add failure location to QCP" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:50 +msgid "To add a failure location to a |QCP|, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`. Select an existing |QCP| from the list, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:55 +msgid "The following instructions only detail the configuration settings necessary for adding a failure location to a |QCP|. For a full overview of |QCPs| and all of the options available when configuring them, see the documentation on :doc:`quality control points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:60 +msgid "In the :guilabel:`Control Per` field on the |QCP| form, select the :guilabel:`Quantity` option. Doing so causes a :guilabel:`Failure Locations` field to appear on the form. This field is only available when the :guilabel:`Quantity` option is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:64 +msgid "In the :guilabel:`Failure Locations` field, select one or more locations from the drop-down menu. To create a new location, type the desired location name into the field, and then select :guilabel:`Create \"[name]\"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:-1 +msgid "A QCP form in the Quality app, configured with a failure location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:73 +msgid "Send products to failure location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:75 +msgid "Once a |QCP| has been configured with one or more failure locations, products that fail a check created by the |QCP| can be routed to one of the locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:78 +msgid "To do so, open an order that requires a quality check created by a |QCP| configured with a failure location. For example, navigate to :menuselection:`Inventory app --> Operations --> Receipts`, and select a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:82 +msgid "At the top of the selected order, click the :guilabel:`Quality Checks` button to open a pop-up window, from which the quality check can be processed. At the bottom of the pop-up window, click the :guilabel:`Fail` button to fail the quality check, which opens a second pop-up window, titled :guilabel:`Quality Check Failed for [Product]`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:87 +msgid "In the :guilabel:`Quantity Failed` field, enter the quantity of the product that failed to pass the quality check. In the :guilabel:`Failure Location` field, select a location to which the failed quantity should be sent. Then, click :guilabel:`Confirm` at the bottom of the pop-up window to close it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:-1 +msgid "The pop-up window that appears after a quality check fails." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:96 +msgid "Finally, on the order, click the :guilabel:`Validate` button at the top of the page. Doing so confirms the products that failed the quality check were sent to the failure location, while products that passed it were sent to their normal storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:101 +msgid "View failure location inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:103 +msgid "To view the product quantities stored in a failure location, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. Select a failure location from the list. Then, click the :guilabel:`Current Stock` smart button on the location's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:107 +msgid "A failure location's page lists all of the products stored within the location, along with the quantity of each." +msgstr "" + #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:3 msgid "Quality alerts" msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index cc93a5e48..c7cff8f52 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -355,6 +355,7 @@ msgid "When all desired options are configured, click :guilabel:`Save` to save t msgstr "" #: ../../content/applications/marketing/email_marketing.rst:274 +#: ../../content/applications/marketing/events.rst:79 msgid "Settings" msgstr "" @@ -533,7 +534,6 @@ msgid "The number of :guilabel:`records` in the database that match the configur msgstr "" #: ../../content/applications/marketing/email_marketing.rst:427 -#: ../../content/applications/marketing/events/event_essentials.rst:191 msgid "Some sub-menu options in the first rule field allow for a second choice to provide even more specificity." msgstr "" @@ -2008,14 +2008,206 @@ msgstr "" msgid "Events" msgstr "" -#: ../../content/applications/marketing/events.rst:8 +#: ../../content/applications/marketing/events.rst:7 +msgid "Explore the various aspects of the Odoo *Events* detailed dashboard, and useful settings, that can be utilized to generate and gather valuable data about events (and their attendees), which can then be used to improve decision-making and event-planning." +msgstr "" + +#: ../../content/applications/marketing/events.rst:12 msgid "`Odoo Tutorials: Events `_" msgstr "" +#: ../../content/applications/marketing/events.rst:37 +msgid "Events dashboard" +msgstr "" + +#: ../../content/applications/marketing/events.rst:39 +msgid "When the *Events* application is opened, Odoo reveals the main :guilabel:`Events` dashboard, which can be viewed in a number of different ways. Those different view options are accessible from the :guilabel:`Events` dashboard in the upper-right corner, via a series of view-related icon buttons." +msgstr "" + +#: ../../content/applications/marketing/events.rst:43 +msgid "By default, the :guilabel:`Events` dashboard is displayed in the :icon:`oi-view-kanban` :guilabel:`Kanban` view, which is populated with a variety of pipeline stages." +msgstr "" + +#: ../../content/applications/marketing/events.rst:-1 +msgid "Overview of events setting with the kanban view in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events.rst:50 +msgid "This view showcases all the events in the database in their respective stages. By default, the stages are: :guilabel:`New`, :guilabel:`Booked`, :guilabel:`Announced`, :guilabel:`Ended`, and :guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/marketing/events.rst:55 +msgid "The :guilabel:`Ended` and :guilabel:`Cancelled` stages are folded, by default, and located to the right of the other stages." +msgstr "" + +#: ../../content/applications/marketing/events.rst:58 +msgid "On each event card, find the scheduled date of the event, the name of the event, the location, the number of expected :guilabel:`Attendees`, any scheduled activities related to the event, the status of the event, and the person responsible for the event." +msgstr "" + +#: ../../content/applications/marketing/events.rst:62 +msgid "To quickly add a new event to a pipeline, click the :icon:`fa-plus` :guilabel:`(plus)` icon at the top of the stage to which the event should be added to reveal a blank Kanban card to fill out." +msgstr "" + +#: ../../content/applications/marketing/events.rst:-1 +msgid "Typical blank kanban card to fill out in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events.rst:69 +msgid "In this blank Kanban card, enter the name of :guilabel:`Event`, along with the start and end :guilabel:`Date` and time." +msgstr "" + +#: ../../content/applications/marketing/events.rst:72 +msgid "Then, either click :guilabel:`Add` to add it to the stage and edit it later, or click :guilabel:`Edit` to add the event to stage and edit its configurations on a separate page." +msgstr "" + +#: ../../content/applications/marketing/events.rst:75 +msgid "Each event card can be dragged-and-dropped into any stage on the Kanban pipeline, providing easy organizational access." +msgstr "" + +#: ../../content/applications/marketing/events.rst:81 +msgid "To access the event settings and feature options in Odoo *Events*, navigate to :menuselection:`Events app --> Configuration --> Settings`. From here, tick the checkboxes beside the desired settings and/or features, and click :guilabel:`Save` to activate them." +msgstr "" + +#: ../../content/applications/marketing/events.rst:86 +msgid "Events section" +msgstr "" + +#: ../../content/applications/marketing/events.rst:88 +msgid "In the :guilabel:`Events` section of the :guilabel:`Settings` page, there are selectable features that can be enabled to add various elements to events created with the Odoo *Events* application." +msgstr "" + +#: ../../content/applications/marketing/events.rst:-1 +msgid "The Events section on the Odoo Events settings page in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events.rst:95 +msgid "The :guilabel:`Schedule & Tracks` feature allows users to manage and publish a schedule with tracks for events. *Tracks* is a catch-all term that refers to talks, lectures, demonstrations, presentations, and other similar elements that users may choose to include as part of an event." +msgstr "" + +#: ../../content/applications/marketing/events.rst:99 +msgid "When the :guilabel:`Schedule & Tracks` feature is enabled, two additional fields appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event Gamification`." +msgstr "" + +#: ../../content/applications/marketing/events.rst:102 +msgid "The :guilabel:`Live Broadcast` feature lets users air tracks online, via a *YouTube* integration." +msgstr "" + +#: ../../content/applications/marketing/events.rst:104 +msgid "The :guilabel:`Event Gamification` feature lets users share a quiz after any event track, in order for attendees to gauge how much they learned from the track they just saw/heard. Companies can also benefit from this feature, in that the subsequent responses and results of the quizzes can help determine where a company's strengths and weaknesses are, when it comes to their presentations." +msgstr "" + +#: ../../content/applications/marketing/events.rst:109 +msgid "Next, is the :guilabel:`Online Exhibitors` feature. This feature allows users to display sponsors and exhibitors on event pages, which can serve as a valuable incentive to encourage partners and businesses to participate in the event." +msgstr "" + +#: ../../content/applications/marketing/events.rst:113 +msgid "The :guilabel:`Jitsi Server Domain` field represents an external conferencing service that is integrated with Odoo. It is what is used to create and host virtual conferences, community rooms, and other similar elements for events." +msgstr "" + +#: ../../content/applications/marketing/events.rst:117 +msgid "The :guilabel:`Community Chat Rooms` feature allows users to create virtual conference rooms for event attendees, providing them with a centralized place to meet and discuss anything related to the event." +msgstr "" + +#: ../../content/applications/marketing/events.rst:121 +msgid "Lastly, there is the :guilabel:`Booth Management` feature. This feature provides users with the ability to create and manage event booths and booth reservations. When enabled, users can create different booth tiers, with individual price points, and sell them to interested parties." +msgstr "" + +#: ../../content/applications/marketing/events.rst:126 +msgid "Registration section" +msgstr "" + +#: ../../content/applications/marketing/events.rst:128 +msgid "The :guilabel:`Registration` section of the :guilabel:`Settings` page provides selectable settings that are directly related to event registration." +msgstr "" + +#: ../../content/applications/marketing/events.rst:-1 +msgid "The Registration section in the Odoo Events settings page in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events.rst:135 +msgid "The :guilabel:`Tickets` setting allows users to sell event tickets, via standard sales orders." +msgstr "" + +#: ../../content/applications/marketing/events.rst:137 +msgid "The :guilabel:`Online Ticketing` setting creates a selectable *Event Ticket* product type on product forms, which provides users with the ability to sell event tickets online, via their website/eCommerce store." +msgstr "" + +#: ../../content/applications/marketing/events.rst:142 +msgid "Attendance section" +msgstr "" + +#: ../../content/applications/marketing/events.rst:144 +msgid "In the :guilabel:`Attendance` section of the :guilabel:`Settings` page, there is a selectable setting that is directly related to how attendees can attend/enter the event." +msgstr "" + +#: ../../content/applications/marketing/events.rst:-1 +msgid "The Attendance section in the Odoo Events Settings page in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events.rst:151 +msgid "The :guilabel:`Use Event Barcode` setting, when activated, enables barcode (and QR code) scanning for attendees to enter the event. This provides attendees with quick access, and helps Odoo users easily track, manage, and analyze all event attendees." +msgstr "" + +#: ../../content/applications/marketing/events.rst:155 +msgid "The :guilabel:`Barcode Nomenclature` field, beneath the :guilabel:`Use Event Barcode` setting, is set to :guilabel:`Default Nomenclature`, by default, but can be changed at any time." +msgstr "" + +#: ../../content/applications/marketing/events.rst:159 #: ../../content/applications/marketing/events/create_events.rst:3 msgid "Create events" msgstr "" +#: ../../content/applications/marketing/events.rst:161 +msgid "With Odoo *Events*, events can be manually created from scratch or built off of pre-made templates. Once launched, the *Events* application then integrates with the *Website* app for the front-end promotion and registration of the event for attendees, the *Sales* app for the purchasing ability of paid tickets, and the *CRM* application through customizable lead generation rules." +msgstr "" + +#: ../../content/applications/marketing/events.rst:167 +msgid ":doc:`events/create_events`" +msgstr "" + +#: ../../content/applications/marketing/events.rst:170 +#: ../../content/applications/marketing/events/sell_tickets.rst:3 +msgid "Sell event tickets" +msgstr "" + +#: ../../content/applications/marketing/events.rst:172 +msgid "Create custom ticket tiers (with various price points) for potential event attendees to choose from, directly on the event template form, under the *Tickets* tab." +msgstr "" + +#: ../../content/applications/marketing/events.rst:175 +msgid "Odoo simplifies the ticket-purchasing process by providing plenty of payment method options, as well." +msgstr "" + +#: ../../content/applications/marketing/events.rst:179 +msgid ":doc:`events/sell_tickets`" +msgstr "" + +#: ../../content/applications/marketing/events.rst:182 +#: ../../content/applications/marketing/events/track_manage_talks.rst:3 +msgid "Track and manage talks" +msgstr "" + +#: ../../content/applications/marketing/events.rst:184 +msgid "Discover how to access various event tracks (talks, presentations, etc.), view entire agendas, and learn how attendees can propose talks for the event." +msgstr "" + +#: ../../content/applications/marketing/events.rst:188 +msgid ":doc:`events/track_manage_talks`" +msgstr "" + +#: ../../content/applications/marketing/events.rst:191 +#: ../../content/applications/marketing/events/event_templates.rst:3 +msgid "Event templates" +msgstr "" + +#: ../../content/applications/marketing/events.rst:193 +msgid "Discover the process to customize and configure event templates, which can be used to expedite the event-creation process." +msgstr "" + +#: ../../content/applications/marketing/events.rst:197 +msgid ":doc:`events/event_templates`" +msgstr "" + #: ../../content/applications/marketing/events/create_events.rst:5 msgid "With the *Events* application, event organizers can create and configure in-person or online-only events in Odoo. Each new event contains a number of customizable options that are geared around specific event logistics, as needed per event, such as ticket sales and registration desk, booths, tracks, sponsors, rooms, and more." msgstr "" @@ -2057,38 +2249,50 @@ msgid "At the top of the event form are a series of smart buttons related to var msgstr "" #: ../../content/applications/marketing/events/create_events.rst:46 -msgid "Beneath the smart buttons is the event form, which contains various fields and clickable tabs that serve to configure the initial, necessary details of the event." +msgid "Primarily, these smart buttons are used as logistical portals to perform specific actions for the event. The numeric displays are primarily for quick reference points." msgstr "" #: ../../content/applications/marketing/events/create_events.rst:49 -msgid "The following are fields found on an event form:" -msgstr "" - -#: ../../content/applications/marketing/events/create_events.rst:51 -msgid ":guilabel:`Event Name`: the title of the event. This field is **required**." +msgid "While those visual metrics are useful, they can still be clicked, and used to navigate to specific event-related pages to modify and/or perform any desired actions." msgstr "" #: ../../content/applications/marketing/events/create_events.rst:52 +msgid "Beneath the smart buttons is the event form, which contains various fields and clickable tabs that serve to configure the initial, necessary details of the event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:55 +msgid "The following are fields found on an event form:" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:57 +msgid ":guilabel:`Event Name`: the title of the event. This field is **required**." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:60 +msgid "To the right of the entered :guilabel:`Event Name`, there is a language tooltip, represented by an abbreviated language indicator (e.g. `EN`). When clicked, a :guilabel:`Translate: name` pop-up window appears, displaying various pre-configured language translation options available in the database." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:65 msgid ":guilabel:`Date`: when the event is scheduled to take place. This field is auto-populated, but modifiable, and is **required**." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:54 +#: ../../content/applications/marketing/events/create_events.rst:67 msgid ":guilabel:`Timezone`: the corresponding timezone related to the event. This field is auto-populated, but modifiable, and is **required**." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:56 +#: ../../content/applications/marketing/events/create_events.rst:69 msgid ":guilabel:`Language`: designate a specific language for all event communications to be translated into, if necessary. This field is blank, by default, so if event-related communications are being sent to recipients who speak a different language, be sure to configure this field properly." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:59 +#: ../../content/applications/marketing/events/create_events.rst:72 msgid ":guilabel:`Twitter Wall`: creates a separate page on the event website to feature specific social posts on X (formerly Twitter) that contain pre-determined desired elements." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:63 +#: ../../content/applications/marketing/events/create_events.rst:76 msgid "To create and customize a :guilabel:`Twitter Wall`, type the name of the desired wall into the field, and select :guilabel:`Create and edit...` from the resulting drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:66 +#: ../../content/applications/marketing/events/create_events.rst:79 msgid "Doing so reveals :guilabel:`Create Twitter Wall` pop-up window." msgstr "" @@ -2096,107 +2300,107 @@ msgstr "" msgid "The Twitter Wall pop-up window in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:72 +#: ../../content/applications/marketing/events/create_events.rst:85 msgid "From this window, enter a :guilabel:`Wall Name`. Then, select a certain word or hashtag for Odoo to search for on X, like `#WoodWorkingExpo24`, for example." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:75 +#: ../../content/applications/marketing/events/create_events.rst:88 msgid "Next, determine the :guilabel:`Type of tweets` Odoo should showcase with that predetermined criteria. The choices in this field are: :guilabel:`Recent`, :guilabel:`Popular`, or :guilabel:`Mixed`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:79 +#: ../../content/applications/marketing/events/create_events.rst:92 msgid "Users also have the option to add a brief :guilabel:`Description` to the wall, as well." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:81 +#: ../../content/applications/marketing/events/create_events.rst:94 msgid "Lastly, the greyed-out, non-modifiable :guilabel:`Website URL` field will autopopulate with the full URL needed to access the document through the event website." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:84 +#: ../../content/applications/marketing/events/create_events.rst:97 msgid "An image can also be added to the wall by clicking the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :guilabel:`(camera)` placeholder image in the upper-right corner of the pop-up window." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:88 +#: ../../content/applications/marketing/events/create_events.rst:101 msgid "Then, from the resulting file explorer window, select the desired image to be added to the wall." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:91 +#: ../../content/applications/marketing/events/create_events.rst:104 msgid "This :guilabel:`Twitter Wall` field **only** appears on the event form if the *Social Marketing* app is installed, and an X account has been added as a stream on the application. To learn more, check out the :doc:`Social marketing essentials <../social_marketing/essentials/social_essentials>` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:96 +#: ../../content/applications/marketing/events/create_events.rst:109 msgid ":guilabel:`Template`: choose a pre-configured event template from the resulting drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:98 +#: ../../content/applications/marketing/events/create_events.rst:111 msgid "Or, create a new one directly from this field, by typing in the name of the new template, and selecting either:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:101 +#: ../../content/applications/marketing/events/create_events.rst:114 msgid ":guilabel:`Create` (which creates the template, and can be edited later) or" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:102 +#: ../../content/applications/marketing/events/create_events.rst:115 msgid ":guilabel:`Create and edit...` (which creates the template, and reveals a separate template page to configure the template in greater detail)." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:105 +#: ../../content/applications/marketing/events/create_events.rst:118 msgid ":guilabel:`Tags`: add any corresponding tags to briefly describe the event (e.g. `Online`, `Conference`, etc.). Multiple tags can be added per event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:109 +#: ../../content/applications/marketing/events/create_events.rst:122 msgid "Tags can be displayed on events that are listed on the website by enabling the *Show on Website* checkbox from :menuselection:`Events app --> Configuration --> Event Tag Categories`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:112 +#: ../../content/applications/marketing/events/create_events.rst:125 msgid ":guilabel:`Organizer`: designate the organizer of the event (a company, contact, or employee)." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:113 +#: ../../content/applications/marketing/events/create_events.rst:126 msgid ":guilabel:`Responsible`: designate a user in the database to be responsible for this event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:114 +#: ../../content/applications/marketing/events/create_events.rst:127 msgid ":guilabel:`Company`: designate which company in the database to which this event is related. This field **only** appears if working in a multi-company environment. This field is auto-populated, but modifiable, and is **required**." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:117 +#: ../../content/applications/marketing/events/create_events.rst:130 msgid ":guilabel:`Website`: choose to restrict the publishing of this event to a specific website created in Odoo. If this field is left blank, the event can be published on *all* websites in the database. To learn more, refer to the :doc:`Multiple websites <../../websites/website/configuration/multi_website>` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:121 -msgid ":guilabel:`Venue`: enter the pertinent event venue details in this field." +#: ../../content/applications/marketing/events/create_events.rst:134 +msgid ":guilabel:`Venue`: enter event venue details. This field pulls pertinent information from the *Contacts* application. Alternatively, :guilabel:`Venue` information can be manually added in this field, as well. At the very least, there **must** be a venue name, address, city, zip code/region, and country entered." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:122 +#: ../../content/applications/marketing/events/create_events.rst:138 msgid ":guilabel:`Exhibition Map`: if desired, click the :guilabel:`Upload your file` button to upload an image of the event venue map." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:124 +#: ../../content/applications/marketing/events/create_events.rst:140 msgid ":guilabel:`Limit Registrations`: if this checkbox is ticked, a limit to the amount of registrations is added to the event, and that desired limit amount **must** be entered in the blank field before :guilabel:`Attendees`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:127 +#: ../../content/applications/marketing/events/create_events.rst:143 msgid ":guilabel:`Badge Dimension`: select a desired paper format dimension for event badges. The options are: :guilabel:`A4 foldable`, :guilabel:`A6`, or :guilabel:`4 per sheet`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:129 +#: ../../content/applications/marketing/events/create_events.rst:145 msgid ":guilabel:`Badge Background`: if desired, click the :guilabel:`Upload your file` button to upload a custom background image for event badges." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:132 +#: ../../content/applications/marketing/events/create_events.rst:148 msgid "When the above fields in the event form have been adequately filled in, move on to the four tabs at the bottom of the event form for further customization." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:135 +#: ../../content/applications/marketing/events/create_events.rst:151 msgid "Those tabs are: :ref:`Tickets `, :ref:`Communication `, :ref:`Questions `, and :ref:`Notes `." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:142 +#: ../../content/applications/marketing/events/create_events.rst:158 msgid "Tickets tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:144 +#: ../../content/applications/marketing/events/create_events.rst:160 msgid "Create custom tickets (and ticket tiers) for events in the :guilabel:`Tickets` tab of an event form." msgstr "" @@ -2204,67 +2408,67 @@ msgstr "" msgid "A typical tickets tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:150 +#: ../../content/applications/marketing/events/create_events.rst:166 msgid "To create a ticket, click :guilabel:`Add a line` in the :guilabel:`Tickets` tab. Then, enter a name for the ticket (e.g. `Basic Ticket` or `VIP`) in the :guilabel:`Name` field." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:153 +#: ../../content/applications/marketing/events/create_events.rst:169 msgid "In the :guilabel:`Product` field, either select the pre-configured :guilabel:`Event Registration` product, or create a new one by typing in the name of the new event registration product, and then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the resulting drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:159 +#: ../../content/applications/marketing/events/create_events.rst:175 msgid "Upon installing Odoo *Events*, a new product type, *Event Ticket*, becomes available on product forms (:menuselection:`Sales --> Products --> Products`). In order for an event registration product to be selectable in the *Tickets* tab, the event registration :guilabel:`Product Type` **must** be set to :guilabel:`Event Ticket`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:165 +#: ../../content/applications/marketing/events/create_events.rst:181 msgid "Existing event registration products can be modified directly from this field, as well, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon, located beside the event registration product. Doing so reveals that product's form. If the *Inventory* application is installed, additional choices are available to customize for the product." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:170 +#: ../../content/applications/marketing/events/create_events.rst:186 msgid "Next, set the registration cost of the ticket in the :guilabel:`Price` field." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:173 +#: ../../content/applications/marketing/events/create_events.rst:189 msgid "The *Sales Price* defined on the event registration product's product form sets the default cost of a ticket. Modifying the :guilabel:`Price` of a ticket in the :guilabel:`Tickets` tab, sets a new registration cost of the ticket for that event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:177 +#: ../../content/applications/marketing/events/create_events.rst:193 msgid "Next, determine a :guilabel:`Sales Start` and :guilabel:`Sales End` date in their respective fields. To do that, click into the blank field to reveal a calendar popover. From there, select the desired date and time, then click :icon:`fa-check` :guilabel:`Apply`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:181 +#: ../../content/applications/marketing/events/create_events.rst:197 msgid "Then, if desired, designate a :guilabel:`Maximum` amount of that specific ticket that can be sold." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:183 +#: ../../content/applications/marketing/events/create_events.rst:199 msgid "The :guilabel:`Taken` column populates with the number of tickets that are sold." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:185 +#: ../../content/applications/marketing/events/create_events.rst:201 msgid "Optionally, in the :guilabel:`Color` column, add a custom color to differentiate ticket badges. The selected color displays on ticket badges when printed." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:188 +#: ../../content/applications/marketing/events/create_events.rst:204 msgid "To delete any tickets from the :guilabel:`Tickets` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding line for the ticket that should be deleted." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:192 +#: ../../content/applications/marketing/events/create_events.rst:208 msgid "To add an optional :guilabel:`Description` column to the :guilabel:`Tickets` tab, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` drop-down menu, located to the far-right of the column titles." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:196 +#: ../../content/applications/marketing/events/create_events.rst:212 msgid "Then, tick the checkbox beside :guilabel:`Description` from the resulting drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:198 +#: ../../content/applications/marketing/events/create_events.rst:214 msgid "When added, the option to add brief descriptions for each event ticket appears, which can be used to inform attendees of any perks or amenities that may coincide with specific ticket purchases." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:204 +#: ../../content/applications/marketing/events/create_events.rst:220 msgid "Communication tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:206 +#: ../../content/applications/marketing/events/create_events.rst:222 msgid "In the :guilabel:`Communication` tab of an event form, create various marketing communications that can be scheduled to be sent at specific intervals leading up to, and following, the event." msgstr "" @@ -2272,93 +2476,93 @@ msgstr "" msgid "Typical communication tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:214 +#: ../../content/applications/marketing/events/create_events.rst:230 msgid "By default, Odoo provides three separate pre-configured communications on every new event form. One is an email sent after each registration to confirm the purchase with the attendee. The other two are email event reminders that are scheduled to be sent at different time intervals leading up to the event to remind the recipient of the upcoming event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:219 +#: ../../content/applications/marketing/events/create_events.rst:235 msgid "To add a communication in the :guilabel:`Communication` tab, click :guilabel:`Add a line`. Then, select the desired type of communication in the :guilabel:`Send` field. The options are: :guilabel:`Mail`, :guilabel:`SMS`, :guilabel:`Social Post`, or :guilabel:`WhatsApp`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:223 +#: ../../content/applications/marketing/events/create_events.rst:239 msgid "There is no limit to the number of communications that can be added in the :guilabel:`Communication` tab of an event form." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:226 +#: ../../content/applications/marketing/events/create_events.rst:242 msgid "To delete a communication from the :guilabel:`Communication` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding communication line. Doing so removes the communication from the event entirely." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:231 +#: ../../content/applications/marketing/events/create_events.rst:247 msgid "The :guilabel:`Social Post` option **only** appears if the *Social Marketing* application is installed. The :guilabel:`WhatsApp` option **only** appears if the *WhatsApp Integration* module is installed." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:235 +#: ../../content/applications/marketing/events/create_events.rst:251 msgid ":doc:`WhatsApp <../../productivity/whatsapp>` templates **cannot** be edited during active configuration. A separate approval from *Meta* is required." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:239 +#: ../../content/applications/marketing/events/create_events.rst:255 msgid "Mail" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:241 +#: ../../content/applications/marketing/events/create_events.rst:257 msgid "Select an existing email template from the :guilabel:`Template` drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:243 +#: ../../content/applications/marketing/events/create_events.rst:259 msgid "Next, define the :guilabel:`Interval`, :guilabel:`Unit`, and :guilabel:`Trigger` from their respective drop-down fields, letting Odoo know when the communication should be sent." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:246 +#: ../../content/applications/marketing/events/create_events.rst:262 msgid "The :guilabel:`Unit` options are: :guilabel:`Immediately`, :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and :guilabel:`Months`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:249 +#: ../../content/applications/marketing/events/create_events.rst:265 msgid "Then, select an option from the :guilabel:`Trigger` drop-down menu. The options are: :guilabel:`After each registration`, :guilabel:`Before the event`, and :guilabel:`After the event`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:252 +#: ../../content/applications/marketing/events/create_events.rst:268 msgid "The :guilabel:`Sent` column populates with the number of sent communications. And, beside the number are different icons that appear, depending on the status of that particular communication." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:255 +#: ../../content/applications/marketing/events/create_events.rst:271 msgid "The status of *Running* is represented by a :icon:`fa-cogs` :guilabel:`(three gears)` icon. The status of *Sent* is represented by a :icon:`fa-check` :guilabel:`(checkmark)` icon. And, the status of *Scheduled* is represented by an :icon:`fa-hourglass-half` :guilabel:`(hourglass)` icon." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:260 +#: ../../content/applications/marketing/events/create_events.rst:276 msgid "To send a confirmation email an hour after an attendee registers for an event, configure the following communication:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:263 +#: ../../content/applications/marketing/events/create_events.rst:279 msgid ":guilabel:`Interval`: `1`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:264 +#: ../../content/applications/marketing/events/create_events.rst:280 msgid ":guilabel:`Unit`: :guilabel:`Hours`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:265 +#: ../../content/applications/marketing/events/create_events.rst:281 msgid ":guilabel:`Trigger`: :guilabel:`After each registration`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:268 +#: ../../content/applications/marketing/events/create_events.rst:284 msgid "Existing email templates can be modified directly from the :guilabel:`Template` drop-down menu, if necessary, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon next to the template name. Doing so reveals a separate page where users can edit the :guilabel:`Content`, :guilabel:`Email Configuration`, and :guilabel:`Settings` of that particular email template." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:273 +#: ../../content/applications/marketing/events/create_events.rst:289 msgid "To view and manage all email templates, activate :ref:`developer-mode` and navigate to :menuselection:`Settings --> Technical --> Email: Email Templates`. Modify with caution as email templates effect all communications where the template is used." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:280 +#: ../../content/applications/marketing/events/create_events.rst:296 #: ../../content/applications/marketing/surveys/create.rst:50 -#: ../../content/applications/marketing/surveys/time_random.rst:20 +#: ../../content/applications/marketing/surveys/questions.rst:20 msgid "Questions tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:282 +#: ../../content/applications/marketing/events/create_events.rst:298 msgid "In the :guilabel:`Questions` tab of an event form, users can create brief questionnaires for registrants to interact with, and respond to, after they register for the event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:285 +#: ../../content/applications/marketing/events/create_events.rst:301 msgid "These questions can be focused on gathering basic information about the attendee, learning about their preferences, expectations, and other things of that nature. This information can also be used to create more detailed reporting metrics, in addition to being utilized to create specific lead generation rules." msgstr "" @@ -2366,15 +2570,15 @@ msgstr "" msgid "Typical questions tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:295 +#: ../../content/applications/marketing/events/create_events.rst:311 msgid "By default, Odoo provides three questions in the :guilabel:`Questions` tab for every event form. The default questions require the registrant(s) to provide their :guilabel:`Name` and :guilabel:`Email`, and make it optional to include their :guilabel:`Phone` number, as well." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:299 +#: ../../content/applications/marketing/events/create_events.rst:315 msgid "The information gathered from the :guilabel:`Questions` tab can be found on the :guilabel:`Attendees` dashboard, accessible via the :icon:`fa-users` :guilabel:`Attendees` smart button. Odoo populates individual records that contain basic information about the registrant(s), as well as their preferences." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:304 +#: ../../content/applications/marketing/events/create_events.rst:320 msgid "To add a question in the :guilabel:`Questions` tab, click :guilabel:`Add a line`. Doing so reveals a :guilabel:`Create Question` pop-up window. From here, users can create and configure their question." msgstr "" @@ -2382,91 +2586,91 @@ msgstr "" msgid "The Create Question pop-up window that appears in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:311 +#: ../../content/applications/marketing/events/create_events.rst:327 msgid "First, enter the question in the field at the top of the form. Then, decide if the question should require a :guilabel:`Mandatory Answer` and/or if Odoo should :guilabel:`Ask once per order`, by ticking their respective boxes, if desired." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:315 +#: ../../content/applications/marketing/events/create_events.rst:331 msgid "If the :guilabel:`Ask once per order` checkbox is ticked, the question will only be asked once, and its value is propogated to every attendee in the order (if multiple tickets are purchased at once). If the checkbox is *not* ticked for this setting, Odoo will present the question for every attendee that is connected to that registration." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:320 +#: ../../content/applications/marketing/events/create_events.rst:336 msgid "Next, select a :guilabel:`Question Type` option:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:322 +#: ../../content/applications/marketing/events/create_events.rst:338 msgid ":guilabel:`Selection`: provide answer options to the question for registrants to choose from. Selectable answer options can be managed in the :guilabel:`Answers` column at the bottom of the pop-up window." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:325 +#: ../../content/applications/marketing/events/create_events.rst:341 msgid ":guilabel:`Text Input`: lets the users enter a custom response to the question in a text field." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:326 +#: ../../content/applications/marketing/events/create_events.rst:342 msgid ":guilabel:`Name`: provides registrants with a field for them to enter their name." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:327 +#: ../../content/applications/marketing/events/create_events.rst:343 msgid ":guilabel:`Email`: provides registrants with a field for them to enter their email address." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:328 +#: ../../content/applications/marketing/events/create_events.rst:344 msgid ":guilabel:`Phone`: provides registrants with a field for them to enter their phone number." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:329 +#: ../../content/applications/marketing/events/create_events.rst:345 msgid ":guilabel:`Company`: provides registrants with a field for them to enter a company they are associated with." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:332 +#: ../../content/applications/marketing/events/create_events.rst:348 msgid "Once all the desired configurations have been entered, either click :guilabel:`Save & Close` to save the question, and return to the :guilabel:`Questions` tab on the event form, or click :guilabel:`Save & New` to save the question and immediately create a new question on a new :guilabel:`Create Question` pop-up window." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:337 +#: ../../content/applications/marketing/events/create_events.rst:353 msgid "As questions are added to the :guilabel:`Questions` tab, the informative columns showcase the configurations of each question." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:340 +#: ../../content/applications/marketing/events/create_events.rst:356 msgid "The informative columns are the following:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:342 +#: ../../content/applications/marketing/events/create_events.rst:358 msgid ":guilabel:`Title`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:343 +#: ../../content/applications/marketing/events/create_events.rst:359 msgid ":guilabel:`Mandatory`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:344 +#: ../../content/applications/marketing/events/create_events.rst:360 msgid ":guilabel:`Once per Order`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:345 +#: ../../content/applications/marketing/events/create_events.rst:361 msgid ":guilabel:`Type`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:346 +#: ../../content/applications/marketing/events/create_events.rst:362 msgid ":guilabel:`Answers` (if applicable)" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:348 +#: ../../content/applications/marketing/events/create_events.rst:364 msgid "For :guilabel:`Selection` and :guilabel:`Text Input` types, a :icon:`fa-bar-chart` :guilabel:`Stats` button appears on the right side of the question line. When clicked, Odoo reveals a separate page, showcasing the response metrics to that specific question." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:352 +#: ../../content/applications/marketing/events/create_events.rst:368 msgid "To delete any question from the :guilabel:`Questions` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding question line." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:355 +#: ../../content/applications/marketing/events/create_events.rst:371 msgid "There is no limit to the number of questions that can be added in the :guilabel:`Questions` tab of an event form." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:361 +#: ../../content/applications/marketing/events/create_events.rst:377 msgid "Notes tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:363 +#: ../../content/applications/marketing/events/create_events.rst:379 msgid "In the :guilabel:`Notes` tab of an event form, users can leave detailed internal notes and/or event-related instructions/information for attendees." msgstr "" @@ -2474,372 +2678,58 @@ msgstr "" msgid "Typical notes tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:370 +#: ../../content/applications/marketing/events/create_events.rst:386 msgid "In the :guilabel:`Note` field of the :guilabel:`Notes` tab, users can leave internal notes for other event employees, like \"to-do\" lists, contact information, instructions, and so on." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:373 +#: ../../content/applications/marketing/events/create_events.rst:389 msgid "In the :guilabel:`Ticket Instructions` field of the :guilabel:`Notes` tab, users can leave specific instructions for people attending the event that appear on the attendees ticket." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:377 -#: ../../content/applications/marketing/events/event_essentials.rst:266 +#: ../../content/applications/marketing/events/create_events.rst:393 msgid "Publish events" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:379 +#: ../../content/applications/marketing/events/create_events.rst:395 msgid "Once all configurations and modifications are complete on the event form, it is time to publish the event on the website. Doing so makes the event visible to website visitors, and makes it possible for people to register for the event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:383 +#: ../../content/applications/marketing/events/create_events.rst:399 msgid "To publish an event after all the customizations are complete, click the :icon:`fa-globe` :guilabel:`Go to Website` smart button at the top of the event form. Doing so reveals the event's web page, which can be customized like any other web page on the site, via the :guilabel:`Edit` button." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:388 +#: ../../content/applications/marketing/events/create_events.rst:404 msgid "To learn more about website design functionality and options, consult the :doc:`Building block <../../websites/website/web_design/building_blocks>` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:391 +#: ../../content/applications/marketing/events/create_events.rst:407 msgid "Once the event website is ready to be shared, click the red :guilabel:`Unpublished` toggle switch in the header menu, changing it to a green :guilabel:`Published` switch. At this point, the event web page is published, and viewable/accessible by all website visitors." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:396 +#: ../../content/applications/marketing/events/create_events.rst:412 msgid "Send event invites" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:398 +#: ../../content/applications/marketing/events/create_events.rst:414 msgid "To send event invites to potential attendees, navigate to the desired event form, via :menuselection:`Events app --> Events`, and click into the desired event. Following this, click the :guilabel:`Invite` button in the upper-left corner of the event form." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:402 +#: ../../content/applications/marketing/events/create_events.rst:418 msgid "Doing so reveals a blank email form to fill out, as desired. To learn more about how to create and customize emails like this, refer to the :ref:`Create an email ` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:406 +#: ../../content/applications/marketing/events/create_events.rst:422 msgid "Proceed to create and customize an email message to send as an invite to potential attendees. Remember to include a link to the registration page on the event website, allowing interested recipients to quickly register." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:411 +#: ../../content/applications/marketing/events/create_events.rst:427 msgid "Sending emails from Odoo is subject to a daily limit, which, by default, is 200. To learn more about daily limits, visit the :ref:`email_communication/daily_limit_mail` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:415 -#: ../../content/applications/marketing/events/event_templates.rst:217 -msgid ":doc:`event_essentials`" -msgstr "" - -#: ../../content/applications/marketing/events/create_events.rst:416 +#: ../../content/applications/marketing/events/create_events.rst:431 msgid ":doc:`track_manage_talks`" msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:3 -msgid "Event essentials" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:5 -msgid "Odoo Events provides event coordinators with an arsenal of planning, communications, and reporting tools to create immersive and engaging experiences for customers. Namely, staff can create and publish events on their website, sell tickets online, scan tickets with Odoo barcode, send out automated emails, and generate rich reporting data once the event accepts registrations." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:11 -msgid "Kanban concepts and organization" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:13 -msgid "To get started, click on the :guilabel:`Events` application on the home dashboard, which then leads to the kanban view populated with a variety of pipeline stages. Key information is listed on each event card, such as the date/time of the event, along with the number of expected (and confirmed) attendees." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:18 -msgid "To create a new stage, click :guilabel:`Add a Column` and provide a befitting title to reflect the purpose of that stage." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:21 -msgid "To reorganize the stages, just drag-and-drop them until they are in the correct order. Stages can also be “folded” in the kanban for a cleaner presentation, via the :guilabel:`Settings` menu to the right of each stage's title, which is represented by a gear icon." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:26 -msgid "The gear icon, by default, is hidden and will appear next to the :guilabel:`+` icon when moused over." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:29 -msgid "When clicked, a drop-down menu of settings will appear." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "Overview of events setting with the kanban view in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:36 -msgid "Create a new event" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:38 -msgid "To create an event, click :guilabel:`Create` from the Events dashboard. Odoo will then direct the page to a blank event template form." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:41 -msgid "From the event form, fill out the necessary fields, either by choosing from existing data in the Odoo database or by creating and editing new field data. Key information to enter for the event includes:" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:45 -msgid ":guilabel:`Event Name`: give the event a title." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:46 -msgid ":guilabel:`Date`: includes the start and end dates/times for the event." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:47 -msgid ":guilabel:`Timezone`: covers the timezone for when the event is taking place." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:48 -msgid ":guilabel:`Template`: choose from a pre-built event template or build a custom one and connect it here." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:50 -msgid ":guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. `tradeshow`). Tags help better organize event cards in the kanban and are useful when using search filters during reporting periods." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:53 -msgid ":guilabel:`Organizer`: detail the organizer(s) for the event. This field is usually the company that owns the Odoo database, or a vendor." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:55 -msgid ":guilabel:`Responsible`: name the point person who is responsible for organizing the event." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:56 -msgid ":guilabel:`Website`: indicate which Odoo website(s) the event event should be published to." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:57 -msgid ":guilabel:`Venue`: list the venue details here if it's a new record, or choose from an existing location." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:59 -msgid ":guilabel:`Limit Registrations`: when enabled, this setting caps the attendee registrations to a specified amount" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:61 -msgid ":guilabel:`Autoconfirmation`: when enabled, this setting skips the confirmation request that gets sent by email to event registrants, and automatically confirms their registration." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:64 -msgid "Once the fields in the event form are set, move on to the :guilabel:`Tickets` and :guilabel:`Communication` tabs, and optionally the :guilabel:`Questions` tab if registrations should require additional information." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:69 -msgid "Add and sell event tickets" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:71 -msgid "Under the :guilabel:`Tickets` tab, add line items for each type of ticket the event plans to offer. Here, determine the ticket price, start/end dates for registrations, as well as the maximum number of tickets that can be sold." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:75 -msgid "If selling tickets isn't necessary for the event, a simple :guilabel:`Registration` button will be displayed on the event's page by default." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "View of the ticket tab in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:83 -msgid "Send automated emails, text, and social posts to event attendees" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:85 -msgid "Under the :guilabel:`Communication` tab, configure personalized email, SMS, or social post messages to keep in touch with event attendees. For each communication, click :guilabel:`Add a line` in the :guilabel:`Communication` tab form, and then choose (or create) a communications template using the drop-down menu under the :guilabel:`Template` column." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:90 -msgid "Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how often the communication should be sent; use these time fields to specify the frequency of :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months` communications should be sent. There is also the option to send communications `Immediately` after a specified :guilabel:`Trigger` is activated." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:96 -msgid "In the last column, determine the :guilabel:`Trigger` which controls how and when the communication is sent. For this action, choose between: :guilabel:`Before the event`, :guilabel:`After each registration`, or :guilabel:`After the event`." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "View of the communication tab in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:105 -msgid "Attach a questionnaire to event registrations" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:107 -msgid "Implementing a questionnaire during event sign up is an effective way to gauge the wants, needs, and interests of the event's attendees ahead of time. Questionnaires also act as informative analytics tools for reporting periods before (or after) events take place." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:111 -msgid "To create a questionnaire, from the :guilabel:`Events` application, navigate to :menuselection:`Configuration --> Settings` and then enable the :guilabel:`Questions` setting." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:114 -msgid "With the setting enabled, questions and answers can now be added (and recorded) under the the :guilabel:`Questions` tab back on the event form. For each question, specify if it should only be asked once with the :guilabel:`Ask once per order` checkbox, or if the question requires a :guilabel:`Mandatory Answer`, which will make the question required for registration." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:120 -msgid "If the :guilabel:`Once per order` checkbox is enabled, then a single registration for 3 event attendees will show the questionnaire only once." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:123 -msgid "There are two :guilabel:`Question Types` to choose from: :guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` type, allows attendees to select an answer from pre-configured options, which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text Input` type allows attendees to write in their own answer to the question in a text box." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "View of an event form, open the questions tab, and add a question." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:133 -msgid "Log internal notes or add ticket instructions" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:135 -msgid "In the :guilabel:`Notes` tab, there is the option to add a :guilabel:`Note` and/or :guilabel:`Ticket instructions`." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:138 -msgid "Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, contact information, etc.) for event staff to reference. In the :guilabel:`Ticket instructions` field, helpful information for staff and attendees can be shared (like, directions to the venue, opening/closing times, etc.)" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:144 -msgid "Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These options provide various formatting options to ensure vital internal information is organized for event staff to review." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "View of the Notes tab in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:153 -msgid "Invite attendees to the event" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:155 -msgid "To invite people to an event, click the :guilabel:`Invite` button located in the top left corner of the event form." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:158 -msgid "Inside the invite template form, are options to sent email or SMS invites. Each message can be fully customized, and recipients can be added." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:161 -msgid "Adding a :guilabel:`Subject` line for the invite message is required, but the :guilabel:`Preview Text` field is optional. The :guilabel:`Preview Text` is a catchy preview sentence meant to encourage recipients to open the email." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:166 -msgid "In most cases, the :guilabel:`Preview Text` is displayed next to the subject. Keep this field empty to ensure the first characters of the email content appear, instead." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:170 -msgid "Select invitees and configure recipient filters" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:172 -msgid "In the middle of the invitation form, find and click the :guilabel:`Recipients` field, to reveal a drop-down menu of recipient options. These choices represent where Odoo will find the desired recipients' information." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:176 -msgid "Once an option from this menu is selected (e.g. :guilabel:`Applicant`, :guilabel:`Contact`, :guilabel:`Event Registration`, :guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all recipients who match that initial rule. Additional rules can be added to narrow down the target recipients, by clicking :guilabel:`Add Filter`." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "View of the add filter button beneath the recipients field in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:185 -msgid "Clicking :guilabel:`Add Filter` reveals three fields, formatted like an equation. To reveal the sub-menu options, click each field, and make the desired selections, until the preferred configuration has been acheived. The number of :guilabel:`Records` that match the rule(s) are indicated to the right of the :guilabel:`Recipients` field, in green." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:194 -msgid "To the right of each rule, are :guilabel:`x`, :guilabel:`+`, and :guilabel:`...` icons. The :guilabel:`x` icon deletes a specific node (line) of the rule. The :guilabel:`+` icon adds a node (line) to the rule. And, the :guilabel:`...` icon adds a branch to the node. A branch means two additional, indented sub-nodes are added to the rule, providing even more specificity to the line above it." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:201 -msgid "Build a custom event invite" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:203 -msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from. Select the desired template, and modify every element of its design details with Odoo's drag-and-drop web builder, located on the right sidebar." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "View of the drag and drop building blocks used to customize event invite emails." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:212 -msgid "To build an email event invite from scratch, select the :guilabel:`Plain Text` template, and Odoo will provide a blank email canvas, which can be customized either by using the frontend rich text editor that accepts slash (`/`) commands, or the XML code editor when :ref:`developer mode ` is engaged and the :guilabel:`` icon is pressed." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:218 -msgid "The :guilabel:`Mail Body` tab (and template options), are only available if the event invite :guilabel:`Mailing Type` is designated as an :guilabel:`Email`. If :guilabel:`SMS` is the :guilabel:`Mailing Type`, a :guilabel:`SMS Content` tab (consisting of a blank text space), is available, instead." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:224 -msgid "Modify event invite settings" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:226 -msgid "The options under the :guilabel:`Settings` tab are different, depending on the specified :guilabel:`Mailing Type`." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:229 -msgid "If the :guilabel:`Email` option is selected as the :guilabel:`Mailing Type`, an employee can be designated as the :guilabel:`Responsible`, meaning that person is the one responsible for this particular invite message. :guilabel:`Send From` and :guilabel:`Reply To` email aliases can be designated here, as well." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:234 -msgid "Also, if any specific documents are required (or helpful) for this event invite, they can be sent along with this email, by clicking :guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:238 -msgid "If the :guilabel:`SMS` option is selected as the :guilabel:`Mailing Type`, a :guilabel:`Responsible` can be designated, and the option to :guilabel:`Include an opt-out link` is available." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:242 -msgid "Send event invitations to recipients" -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:244 -msgid "If the selected :guilabel:`Mailing Type` is :guilabel:`Email`, there are three options to send the invite: :guilabel:`Send`, :guilabel:`Schedule`, and :guilabel:`Test`." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:247 -msgid "The :guilabel:`Send` option sends the invite right away. The :guilabel:`Schedule` option reveals a pop-up, in which a scheduled date/time can be selected for the email to be sent. The :guilabel:`Test` option reveals a :guilabel:`Test Mailing` pop-up, where specific recipient email addresses can be entered for Odoo to send them the current version of the mailing for review before officially sending it out to prospective event attendees." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:253 -msgid "If the selected :guilabel:`Mailing Type` is :guilabel:`SMS`, there are four options to send the invite: :guilabel:`Put in Queue`, :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test`." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:256 -msgid "The :guilabel:`Put in Queue` option schedules an SMS message to all recipients (that match the designated rules, if any) in the near future. Clicking :guilabel:`Put in Queue` reveals a pop-up, requiring confirmation. When confirmed, a blue banner appears on the event invite template form, indicating that the SMS will be sent later that day." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:262 -msgid "The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options all function the same way for both :guilabel:`Mailing Type` options." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:268 -msgid "Until an event is published, it will remain hidden from public view on the website and registering for it will not be possible. To publish an event, navigate to it either from the backend of Odoo through the :guilabel:`Events` application, or access the hidden event page through the frontend as either a priveliged user or administrator." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:273 -msgid "If navigating from the backend, go to the event form, and click the :guilabel:`Go to Website` smart button to reach the event page on the website (on the frontend). If starting from the frontend , simply navigate to the event page that needs to be published." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:277 -msgid "No matter the route, an event page can only be published from the frontend. In the upper right corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished` status to the green :guilabel:`Published` status. Doing so instantly makes the event page accessible to the public on the website." -msgstr "" - -#: ../../content/applications/marketing/events/event_essentials.rst:-1 -msgid "View of a website page and the option to publish the event in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/event_templates.rst:3 -msgid "Event templates" -msgstr "" - #: ../../content/applications/marketing/events/event_templates.rst:5 msgid "The Odoo *Events* application provides the ability to customize and configure event templates, which can be used to expedite the event-creation process." msgstr "" @@ -3092,91 +2982,159 @@ msgstr "" msgid "Any of these pre-configured settings related to the selected event template chosen in the :guilabel:`Template` field on an event form can be modified, as desired." msgstr "" -#: ../../content/applications/marketing/events/event_templates.rst:218 +#: ../../content/applications/marketing/events/event_templates.rst:217 +#: ../../content/applications/marketing/events/sell_tickets.rst:143 msgid ":doc:`create_events`" msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:3 -msgid "Sell tickets" -msgstr "" - #: ../../content/applications/marketing/events/sell_tickets.rst:5 -msgid "Create custom ticket tiers (with various price points) for potential attendees to choose from, directly on the event template form, under the :guilabel:`Tickets` tab. Odoo simplifies the ticket-purchasing process by providing plenty of payment method options." +msgid "Odoo *Events* provides users with the ability to create custom event tickets (and ticket tiers), with various price points." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:10 +#: ../../content/applications/marketing/events/sell_tickets.rst:8 +msgid "It *also* allows them to sell event tickets in two different ways: via standard sales orders, and online through an integrated website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:11 +msgid "Odoo also simplifies the ticket-purchasing process by providing plenty of payment method options." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:14 +msgid "To learn more about how to create custom tickets (and ticket tiers) for events, check out the :doc:`create_events` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:18 #: ../../content/applications/marketing/events/track_manage_talks.rst:9 #: ../../content/applications/marketing/marketing_automation.rst:44 msgid "Configuration" msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:12 -msgid "First, in order to enable the creation (and selling of) event tickets, go to :menuselection:`Configuration --> Settings`, then enable the :guilabel:`Tickets` and :guilabel:`Online Ticketing` features." +#: ../../content/applications/marketing/events/sell_tickets.rst:20 +msgid "In order to sell event tickets in Odoo, some settings must first be enabled." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:16 -msgid "The :guilabel:`Tickets` feature allows tickets to be sold for an event." +#: ../../content/applications/marketing/events/sell_tickets.rst:22 +msgid "First, navigate to :menuselection:`Events app --> Configuration --> Settings`. In the :guilabel:`Registration` section, there are two different settings: :guilabel:`Tickets` and :guilabel:`Online Ticketing`." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:18 -msgid "The :guilabel:`Online Tickets` feature allows for the sale of tickets to occur through the website." +#: ../../content/applications/marketing/events/sell_tickets.rst:26 +msgid "The :guilabel:`Tickets` setting allows users to sell event tickets with standard sales orders." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:21 -msgid "If these options are *not* enabled, a default :guilabel:`Register` button will be available for free registrations." +#: ../../content/applications/marketing/events/sell_tickets.rst:28 +msgid "The :guilabel:`Online Ticketing` setting allows users to sell event tickets online through their integrated Odoo website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:31 +msgid "To activate a setting, tick the checkbox beside the desired feature's label, and click :guilabel:`Save` to finish enabling it." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:35 +msgid "If these options are *not* enabled, a default :guilabel:`Register` button becomes available for visitors to interact with and procure free registrations to the event." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:-1 msgid "View of the settings page for Odoo Events." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:29 -msgid "Sell tickets through sales orders" +#: ../../content/applications/marketing/events/sell_tickets.rst:42 +msgid "With those settings enabled, Odoo automatically creates a new *Product Type* called, *Event Ticket*, which is accessible on every product form. Odoo also creates three event registration products (with the *Product Type* set to *Event Ticket*) that can be used or modified for event tickets." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:31 -msgid "In the :guilabel:`Sales` application, choose a previously-created Event Registration (as if it were a product), and add it as a product line. Upon adding the registration, a pop-up appears, which allows for the selection of a specific event (and ticket tier). That specific event ticket is then attached to the sales order." +#: ../../content/applications/marketing/events/sell_tickets.rst:47 +msgid "When creating a new event registration product, the *Product Type* **must** be set to *Event Ticket* on the product form, in order for it to be selected in the *Product* column under the *Tickets* tab on an event form." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:-1 -msgid "View of a sales order and option to choose the specific event in Odoo Events." +#: ../../content/applications/marketing/events/sell_tickets.rst:0 +msgid "View of an event form highlighting the column product under the tickets tab in Odoo." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:40 -msgid "Events with tickets sold online or through sales orders have a :guilabel:`Sales Smart Button` shortcut, located at the top of the event template form (in the :guilabel:`Events` application)." -msgstr "" - -#: ../../content/applications/marketing/events/sell_tickets.rst:43 -msgid "Clicking the :guilabel:`Sales Smart Button` reveals a page with all the sales orders related to that event." +#: ../../content/applications/marketing/events/sell_tickets.rst:56 +msgid "Any event with paid tickets sold, features a :icon:`fa-dollar` :guilabel:`Sales` smart button at the top of the event form, where the respective sales orders attributed to those ticket sales become available." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:-1 msgid "View of an event's form and the sales smart button in Odoo Events." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:-1 -msgid "View of an event form highlighting the column product under the tickets tab in Odoo\n" -"Events." +#: ../../content/applications/marketing/events/sell_tickets.rst:64 +msgid "Clicking the :icon:`fa-dollar` :guilabel:`Sales` smart button reveals a separate page, showcasing all the sales orders (standard and/or online) related to tickets that have been sold for that specific event." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:56 -msgid "Sell tickets through the website" +#: ../../content/applications/marketing/events/sell_tickets.rst:69 +msgid "Sell event tickets with the Sales app" msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:58 -msgid "With tickets purchased through the website, the process is similar to creating a :guilabel:`Sales Order` with a specific :guilabel:`Registration` product. Here, tickets are added to a virtual cart, and the transaction can be completed as usual - utilizing any of the pre-configured payment methods options that have been set up on the website." +#: ../../content/applications/marketing/events/sell_tickets.rst:71 +msgid "To sell event tickets with sales orders, start by navigating to the :menuselection:`Sales` app. Then, click :guilabel:`New` to open a new quotation form." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:63 -msgid "The completed purchase is automatically produced in a :guilabel:`Sales Order`, which can be easily accessed in the back end of the database." +#: ../../content/applications/marketing/events/sell_tickets.rst:74 +msgid "After filling out the top portion of the form with the appropriate customer information, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Then, in the :guilabel:`Product` column, select (or create) an event registration product configured with its :guilabel:`Product Type` set to :guilabel:`Event Ticket` on its product form." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:79 +msgid "Once an event registration product is selected, a :guilabel:`Configure an event` pop-up window appears." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:-1 -msgid "View of website transaction for Odoo Events." +msgid "Standard 'Configure an event' pop-up window that appears on an event ticket sales order." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:3 -msgid "Track and manage talks" +#: ../../content/applications/marketing/events/sell_tickets.rst:86 +msgid "From the :guilabel:`Configure an event` pop-up window, select to which event this ticket purchase is related to in the :guilabel:`Event` field drop-down menu. Then, in the :guilabel:`Event Ticket` drop-down menu, select which ticket tier the customer wishes to purchase, if there are multiple tiers configured for that event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:91 +msgid "When all the desired configurations are complete, click :guilabel:`Ok`. Doing so returns the user to the sales order, with the event registration ticket product now present in the :guilabel:`Order Lines` tab. The user can proceed to confirm and close the sale, per the usual process." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:96 +msgid "To re-open the *Configure an event* pop-up window, hover over the event registration product name in the :guilabel:`Order Lines` tab, and click on the :icon:`fa-pencil` :guilabel:`(pencil)` icon." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:100 +msgid "Sell event tickets through the Website app" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:102 +msgid "When a visitor arrives on the register page of the event website, they can click the :guilabel:`Register` button to purchase a ticket to the event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:106 +msgid "If the visitor is *not* already on the register page of the event website, clicking :guilabel:`Register` on the event website's submenu redirects them to the proper register page. From there, they can click the :guilabel:`Register` button to begin the ticket purchasing process." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:111 +msgid "If different ticket tiers are configured for the event, the visitor is presented with a :guilabel:`Tickets` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:-1 +msgid "The tickets pop-up window that appears on the event's website when 'Register' is clicked." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:118 +msgid "From here, visitors select which ticket tier they would like to purchase, along with a quantity, using the numerical drop-down menu available to the right of their desired ticket. Once the desired selections have been entered, the visitor then clicks the :guilabel:`Register` button." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:122 +msgid "Then, an :guilabel:`Attendees` pop-up window appears, containing all the questions that have been configured in the *Questions* tab of the event form for this particular event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:-1 +msgid "The attendees pop-up window that appears on the event's website when 'Ok' is clicked." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:129 +msgid "If multiple tickets are being purchased at once, there are numbered sections for each individual ticket registrant, each containing the same questions. However, if any question has been configured with the *Ask once per order* setting, that question is only asked once -- and **not** for every attendee making the reservation in the order." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:134 +msgid "With all necessary information entered, the visitor can then click the :guilabel:`Go to Payment` button. Doing so first takes the visitor to a :guilabel:`Billing` confirmation page, followed by a :guilabel:`Payment` confirmation page, where they can utilize any configured payment method set up in the database to complete the order." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:139 +msgid "Then, once the purchase is complete on the front-end of the website, the subsequent sales order is instantly accessible in the back-end of the database." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:5 @@ -3423,6 +3381,7 @@ msgid "To create a campaign, navigate to the :menuselection:`Marketing Automatio msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:81 +#: ../../content/applications/marketing/marketing_automation/campaign_templates.rst:5 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:82 msgid "Campaign templates" msgstr "" @@ -3432,7 +3391,7 @@ msgid "Odoo provides six campaign templates to help users get started. The campa msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:88 -msgid "To get started with a template, navigate to the :menuselection:`Marketing Automation` application, from the main Odoo dashboard, to open the :guilabel:`Campaigns` dashboard, which displays six campaign template cards:" +msgid "To get started with a template, navigate to the :menuselection:`Marketing Automation` application, from the main Odoo dashboard, to open the :guilabel:`Campaigns` dashboard, which displays six :doc:`campaign template ` cards:" msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:0 @@ -3452,7 +3411,7 @@ msgid ":guilabel:`Send a welcome email to new subscribers, remove the address th msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:0 -msgid ":guilabel:`☑️ Double Opt-in`" +msgid ":icon:`fa-check-square` :doc:`Double Opt-in `" msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:0 @@ -3487,147 +3446,336 @@ msgstr "" msgid "Six campaign template cards on the Campaigns dashboard of the Marketing Automation app." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:109 +#: ../../content/applications/marketing/marketing_automation.rst:110 msgid "These templates are designed to be used as starting points for creating new campaigns. Click one of the template cards to open the campaign form." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:113 +#: ../../content/applications/marketing/marketing_automation.rst:114 msgid "To display the campaign template cards again after a campaign has been created, type the name of a campaign that does **not** exist in the database into the :guilabel:`Search...` bar, then press :kbd:`Enter`." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:117 +#: ../../content/applications/marketing/marketing_automation.rst:118 +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:33 msgid "For example, searching for `empty` displays the campaign template cards again, as long as there is not a campaign with the name \"empty\" in the database." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:121 +#: ../../content/applications/marketing/marketing_automation.rst:122 msgid "Targets and filters" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:123 +#: ../../content/applications/marketing/marketing_automation.rst:124 msgid "On the campaign form, the :guilabel:`Target` and :guilabel:`Filter` section, also referred to as the domain, contains the fields used to define the target audience for the campaign's reach (i.e., the unique contact records in the database)." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:127 +#: ../../content/applications/marketing/marketing_automation.rst:128 msgid "The target audience specifies the type of records available for use in the campaign, such as *Lead/Opportunity*, *Event Registration*, *Contact*, and more." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:131 +#: ../../content/applications/marketing/marketing_automation.rst:132 msgid "Records" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:133 +#: ../../content/applications/marketing/marketing_automation.rst:134 msgid "The contacts in the system that fit the specified criteria for a campaign are referred to as *records*." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:136 +#: ../../content/applications/marketing/marketing_automation.rst:137 msgid "The number of records that are displayed next to the campaign :guilabel:`Filter` represent the total number of records the campaign is targeting." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:140 +#: ../../content/applications/marketing/marketing_automation.rst:141 #: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:157 msgid "Participants" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:142 +#: ../../content/applications/marketing/marketing_automation.rst:143 msgid "The records that are engaged by the campaign are referred to as *participants*." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:144 +#: ../../content/applications/marketing/marketing_automation.rst:145 msgid "The number of participants engaged in a test run are shown in the *Tests* smart button, which displays on the top of the campaign form after a test has been run." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:147 +#: ../../content/applications/marketing/marketing_automation.rst:148 msgid "The number of participants engaged in a running, or stopped, campaign are shown in the *Participants* smart button at the top of the campaign form." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:151 +#: ../../content/applications/marketing/marketing_automation.rst:152 msgid ":doc:`Audience targeting `" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:154 +#: ../../content/applications/marketing/marketing_automation.rst:155 msgid "Workflow" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:156 +#: ../../content/applications/marketing/marketing_automation.rst:157 msgid "A *workflow* consists of an activity, many activities, or a sequence of activities organized in a campaign. A campaign's workflow is defined in the :guilabel:`Workflow` section of the campaign form." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:160 +#: ../../content/applications/marketing/marketing_automation.rst:161 #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:19 msgid "Activities" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:162 +#: ../../content/applications/marketing/marketing_automation.rst:163 msgid "*Activities* are the methods of communication or server actions, organized in a workflow, that are executed within a campaign. Once running, each activity displays the number of participants that are engaged by the activity as *Success* and *Rejected* counts." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:166 +#: ../../content/applications/marketing/marketing_automation.rst:167 msgid "To create one of the following activities, click :guilabel:`Add new activity` in the :guilabel:`Workflow` section of the campaign form:" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:169 +#: ../../content/applications/marketing/marketing_automation.rst:170 #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:53 msgid ":ref:`Email `: an email that is sent to the target audience." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:171 +#: ../../content/applications/marketing/marketing_automation.rst:172 #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:55 msgid ":ref:`Server action `: an internal action within the database that is executed." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:173 +#: ../../content/applications/marketing/marketing_automation.rst:174 #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:57 msgid ":ref:`SMS `: a text message that is sent to the target audience." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:177 +#: ../../content/applications/marketing/marketing_automation.rst:178 msgid ":doc:`marketing_automation/workflow_activities`" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:180 +#: ../../content/applications/marketing/marketing_automation.rst:181 msgid "Testing and running" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:182 +#: ../../content/applications/marketing/marketing_automation.rst:183 msgid "Once a campaign has been created, it can be tested to ensure the workflow is functioning as expected, to check for errors, and correct any mistakes before it reaches its target audience." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:185 +#: ../../content/applications/marketing/marketing_automation.rst:186 msgid "After testing, the campaign can be launched to start engaging the target audience. The campaign can also be launched *without* testing, if the user is confident in the workflow." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:189 +#: ../../content/applications/marketing/marketing_automation.rst:190 msgid ":doc:`marketing_automation/testing_running`" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:192 +#: ../../content/applications/marketing/marketing_automation.rst:193 msgid "Reporting" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:194 +#: ../../content/applications/marketing/marketing_automation.rst:195 msgid "A range of reporting metrics are available to measure the success of each campaign. Navigate to :menuselection:`Marketing Automation app --> Reporting` to access the following menu options:" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:197 +#: ../../content/applications/marketing/marketing_automation.rst:198 msgid ":guilabel:`Link Tracker`: displays the metrics of links to track the number of clicks." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:198 +#: ../../content/applications/marketing/marketing_automation.rst:199 msgid ":guilabel:`Traces`: displays the results of all activities from all campaigns." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:199 +#: ../../content/applications/marketing/marketing_automation.rst:200 msgid ":guilabel:`Participants`: displays an overview of the participants of all campaigns." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:201 +#: ../../content/applications/marketing/marketing_automation.rst:202 msgid "Additionally, each activity within the workflow of a campaign displays its engagement metrics." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:204 +#: ../../content/applications/marketing/marketing_automation.rst:205 msgid ":doc:`marketing_automation/understanding_metrics`" msgstr "" +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:3 +msgid "Double Opt-in" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:5 +msgid "A *double opt-in*, also referred to as a *confirmed opt-in*, may be required in some countries for marketing communications, due to anti-SPAM laws. Confirming consent has several other benefits, as well: it validates email addresses, avoids spam/robo subscribers, keeps mailing lists clean, and only includes engaged contacts in the mailing list." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:10 +msgid "When the *Double Opt-in* campaign template is used, a new mailing list titled, *Confirmed contacts* is created in the *Email Marketing* app, and any new mailing list contacts that are added to the default *Newsletter* mailing list are sent a confirmation email to double opt-in. The contacts that click on the confirmation link in the email are automatically added to the *Confirmed contacts* mailing list in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:17 +msgid "When using the *Double Opt-in* campaign template, only the contacts in the *Confirmed contacts mailing* list are considered to have confirmed their consent." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:23 +msgid "Use the Double Opt-in campaign template" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:25 +msgid "Open the :menuselection:`Marketing Automation` app, and select the :guilabel:`Double Opt-in` campaign template to create a new campaign for confirming consent." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:29 +msgid "The campaign templates do **not** display, by default, when there are existing *Marketing Automation* campaigns. To display the campaign templates, type the name of a campaign (that does not exist in the database) into the :guilabel:`Search...` bar, then press :kbd:`Enter`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:37 +msgid "Campaign configuration" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:39 +msgid "Upon creation of the campaign, the campaign form loads with a new preconfigured campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:41 +msgid "The :guilabel:`Target` and :guilabel:`Filter` configurations of the campaign are as follows:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:43 +msgid ":guilabel:`Name`: `Double Opt-in`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:44 +msgid ":guilabel:`Responsible`\\*: The user who created the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:45 +msgid ":guilabel:`Target`: :guilabel:`Mailing Contact`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:46 +msgid ":guilabel:`Unicity based on`: :guilabel:`Email (Mailing Contact)`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:47 +msgid ":guilabel:`Filter`:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:49 +msgid ":guilabel:`Email` :guilabel:`is set`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:50 +msgid ":guilabel:`Blacklist` :guilabel:`is not` :guilabel:`set`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:51 +msgid ":guilabel:`Mailing lists` :guilabel:`contains` `Newsletter`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:53 +msgid "\\* The :guilabel:`Responsible` field is only visible with :ref:`developer-mode` activated." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:56 +msgid "The :guilabel:`Target` model of the campaign should **not** be modified. Changing the :guilabel:`Target` model with activities in the :guilabel:`Workflow` invalidates the existing activities in the :guilabel:`Workflow`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:60 +msgid "The *Double Opt-in* campaign template is intended to **only** use the :guilabel:`Mailing Contact` model." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:63 +msgid "The campaign loads two activities in the :guilabel:`Workflow` section of the campaign: an email activity, with a child server action activity that triggers *on click*." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:66 +msgid "By default, the `Confirmation` email activity is set to trigger :guilabel:`1 Hours` after the beginning of the workflow. In other words, the email is sent 1 hour after a new contact is added to the *Newsletter* mailing list." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:70 +msgid "The email activity uses the preconfigured *Confirmation* email template, which contains a button for the contact to click to confirm their consent." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:73 +msgid "To modify the email template, select the :icon:`fa-envelope-o` :guilabel:`Templates` smart button at the top of the campaign form. Then, in the list of templates, select the `Confirmation` email template." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:77 +msgid "Be sure to personalize the contents of the email template; however, it is recommended to keep the contents of double opt-in confirmation emails short and to-the-point." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:80 +msgid "The default confirmation button, in the body of the template, links directly to the database's website homepage. Click on the button to edit the button text and URL." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:84 +msgid "To provide a streamlined experience for the contact, consider :doc:`creating a page on the website <../../../websites/website/pages>` that expresses gratitude to the contact for confirming their subscription to the mailing list. Add the link to that page in the URL of the confirmation button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:90 +msgid "The email template should only include a single call-to-action link for confirmation, other than an unsubscribe link." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:93 +msgid "Any click on a link (or button) included in the confirmation email, besides the unsubscribe button, triggers the *Add to list* server action." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:96 +msgid "The child activity *Add to list* server action's *On click* trigger cannot differentiate between multiple URLs in an email, besides the `/unsubscribe_from_list` unsubscribe button that is included in any one of the footer blocks." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:100 +msgid "The `Add to list` server action activity triggers immediately after a click in the parent `Confirmation` email activity is detected." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:103 +msgid "When triggered, the `Add to list` activity executes the *Add To Confirmed List* server action, automatically adding the contact to the *Confirmed contacts* mailing list, if they are not already in the mailing list." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:107 +msgid "To modify the server action, select the title of the activity to open the :guilabel:`Open: Activities` pop-up window and edit the server action activities configuration." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:111 +msgid "Consider setting an :guilabel:`Expiry Duration` to prevent executing the activity after a specific amount of time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:115 +msgid "It is not recommended to modify the preconfigured Python code in the :guilabel:`Add To Confirmed List` server action, as doing so may trigger a change in the database's pricing plan." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:118 +msgid "Once the campaign configuration is complete, consider :doc:`launching a test <../testing_running>` to verify the campaign executes as expected. If the campaign testing is successful, :guilabel:`Start` the campaign to begin sending double opt-in confirmation emails to *Newsletter* mailing list contacts, and fill the *Confirmed contacts* mailing list with engaged contacts." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:126 +msgid "Double Opt-in use-case" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:129 +msgid "To prepare for sending newsletter marketing emails on an Odoo database, a mailing contact list must be procured. One way of collecting subscribers is through a sign-up form on the website that adds contacts to the *Newsletter* mailing list on the form submission." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:-1 +msgid "Newsletter sign-up form on Odoo website footer." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:137 +msgid "Before sending any marketing emails, :ref:`use the Double Opt-in campaign template ` in the *Marketing Automation* app to confirm marketing email consent from the contacts in the *Newsletter* mailing list." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:141 +msgid "After launching the *Double Opt-in* campaign, view the contacts that have double opt-in in the *Confirmed contacts* mailing list (:menuselection:`Email Marketing app --> Mailing Lists --> Mailing Lists`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:-1 +msgid "Activity metrics on the campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:149 +msgid "Now, the *Confirmed contacts* mailing list is ready to be used for sending newsletter marketing emails from an Odoo database." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:153 +msgid ":doc:`../understanding_metrics`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:154 +msgid ":doc:`../../email_marketing/mailing_lists`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:155 +msgid ":doc:`../../email_marketing`" +msgstr "" + #: ../../content/applications/marketing/marketing_automation/target_audience.rst:3 msgid "Audience targeting" msgstr "" @@ -6209,7 +6357,7 @@ msgid ":guilabel:`Attachments` can be added to the email, as well as an :guilabe msgstr "" #: ../../content/applications/marketing/surveys.rst:84 -#: ../../content/applications/marketing/surveys/create.rst:296 +#: ../../content/applications/marketing/surveys/create.rst:299 msgid "Once modifications are complete, click :guilabel:`Send` to send that email invite to all the email addresses/contacts listed in the :guilabel:`Recipients` field." msgstr "" @@ -6640,7 +6788,7 @@ msgid ":doc:`create`" msgstr "" #: ../../content/applications/marketing/surveys/analysis.rst:258 -#: ../../content/applications/marketing/surveys/create.rst:331 +#: ../../content/applications/marketing/surveys/create.rst:334 #: ../../content/applications/marketing/surveys/live_session.rst:221 msgid ":doc:`scoring`" msgstr "" @@ -6714,12 +6862,12 @@ msgid "View, access, add, and/or delete questions and sections to the survey in msgstr "" #: ../../content/applications/marketing/surveys/create.rst:55 -#: ../../content/applications/marketing/surveys/time_random.rst:25 +#: ../../content/applications/marketing/surveys/questions.rst:25 msgid "By default, two columns are present in the :guilabel:`Questions` tab: :guilabel:`Title` (i.e. the question) and :guilabel:`Question Type`." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:58 -#: ../../content/applications/marketing/surveys/time_random.rst:28 +#: ../../content/applications/marketing/surveys/questions.rst:28 msgid "If the :guilabel:`Randomized per Section` option is enabled in the :guilabel:`Options` tab of the survey form, a column titled, :guilabel:`# Questions Randomly Picked` appears in the :guilabel:`Questions` tab." msgstr "" @@ -6740,11 +6888,11 @@ msgid "To add a question to a survey, click :guilabel:`Add a question` in the :g msgstr "" #: ../../content/applications/marketing/surveys/create.rst:76 -msgid "To learn how to create and customize questions, refer to the :doc:`create questions ` documentation." +msgid "To learn how to create and customize questions, refer to the :doc:`create questions ` documentation." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:80 -#: ../../content/applications/marketing/surveys/time_random.rst:73 +#: ../../content/applications/marketing/surveys/questions.rst:73 msgid "There **must** be a survey title entered in order for the :guilabel:`Create Sections and Questions` pop-up window to appear. If no title is entered for the survey, an error pop-up message appears in the upper-right corner, instructing the user to enter a survey title." msgstr "" @@ -6753,12 +6901,12 @@ msgid "Add a section" msgstr "" #: ../../content/applications/marketing/surveys/create.rst:87 -#: ../../content/applications/marketing/surveys/time_random.rst:43 +#: ../../content/applications/marketing/surveys/questions.rst:43 msgid "A *section* divides the survey into organized parts, in order to visually group similar questions together. To make a section, click :guilabel:`Add a section` at the bottom of the :guilabel:`Questions` tab, proceed to type in a desired name for the section, then either press :kbd:`Enter` or click away." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:92 -#: ../../content/applications/marketing/surveys/time_random.rst:48 +#: ../../content/applications/marketing/surveys/questions.rst:48 msgid "The section line appears in dark gray in the :guilabel:`Questions` tab." msgstr "" @@ -6767,18 +6915,18 @@ msgid "Then, drag-and-drop desired questions beneath a section, or drag-and-drop msgstr "" #: ../../content/applications/marketing/surveys/create.rst:98 -#: ../../content/applications/marketing/surveys/time_random.rst:54 +#: ../../content/applications/marketing/surveys/questions.rst:54 msgid "If the :guilabel:`Randomized per Section` option is enabled in the :guilabel:`Options` tab of the survey form, the number `1` appears, by default, on the section line, beneath the :guilabel:`# Questions Randomly Picked` column." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:102 -#: ../../content/applications/marketing/surveys/time_random.rst:58 +#: ../../content/applications/marketing/surveys/questions.rst:58 msgid "This indicates that `1` question from that section will be picked at random for each participant taking the survey, bypassing every other, non-chosen question from that section. To change that number, select that figure, and type in the desired number in its place. Then, either press :kbd:`Enter`, or click away." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:108 #: ../../content/applications/marketing/surveys/live_session.rst:57 -#: ../../content/applications/marketing/surveys/time_random.rst:207 +#: ../../content/applications/marketing/surveys/questions.rst:207 msgid "Options tab" msgstr "" @@ -6947,27 +7095,31 @@ msgid "Lastly, in the :guilabel:`Live Session` section, there is the option to : msgstr "" #: ../../content/applications/marketing/surveys/create.rst:255 -#: ../../content/applications/marketing/surveys/time_random.rst:198 +msgid ":doc:`live_session`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:258 +#: ../../content/applications/marketing/surveys/questions.rst:198 msgid "Description tab" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:257 +#: ../../content/applications/marketing/surveys/create.rst:260 msgid "In this non-required tab, users can enter a custom description about the survey, along with any explanations or guidance that a survey participant may need in order to properly participate (and complete) the survey." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:262 +#: ../../content/applications/marketing/surveys/create.rst:265 msgid "End Message tab" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:264 +#: ../../content/applications/marketing/surveys/create.rst:267 msgid "In this non-required tab, users can enter a custom message that participants see upon completing the survey." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:268 +#: ../../content/applications/marketing/surveys/create.rst:271 msgid "Survey form buttons" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:270 +#: ../../content/applications/marketing/surveys/create.rst:273 msgid "Once the survey has been configured properly, and questions have been added, the user can utilize any of the available buttons in the upper-left corner of the survey form." msgstr "" @@ -6975,11 +7127,11 @@ msgstr "" msgid "The various buttons on a survey form in Odoo Surveys." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:277 +#: ../../content/applications/marketing/surveys/create.rst:280 msgid "Those buttons are the following:" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:279 +#: ../../content/applications/marketing/surveys/create.rst:282 msgid ":guilabel:`Share`: click to reveal a :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey — complete with a :guilabel:`Survey Link` that can be copied and sent to potential participants, and a :guilabel:`Send by Email` toggle switch." msgstr "" @@ -6987,50 +7139,50 @@ msgstr "" msgid "The 'Share a Survey' pop-up window that appears in the Odoo Surveys application." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:287 +#: ../../content/applications/marketing/surveys/create.rst:290 msgid "When the :guilabel:`Send by Email` toggle is in the 'on' position, indicated by a green switch, additional fields appear, in which :guilabel:`Recipients` and a :guilabel:`Subject` can be added to the email. Below that, a dynamic email template, complete with a :guilabel:`Start Certification` button appears, which can also be modified." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:298 +#: ../../content/applications/marketing/surveys/create.rst:301 msgid ":guilabel:`See results`: this button **only** appears if there has been at least one participant who has completed the survey. Clicking :guilabel:`See results` reveals a separate tab containing a visual analysis of the survey questions and responses. For more information, check out the :doc:`scoring surveys ` documentation." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:302 +#: ../../content/applications/marketing/surveys/create.rst:305 msgid ":guilabel:`Create Live Session`: clicking this button opens the *Session Manager* in a separate tab. It also allows participants to access the live session, but the actual survey does **not** begin until the user hosting the live session survey clicks the :guilabel:`Start` button on the *Session Manager* window." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:307 +#: ../../content/applications/marketing/surveys/create.rst:310 msgid "Additionally, when :guilabel:`Create Live Session` has been clicked, and the *Session Manager* tab has been opened, the :guilabel:`Create Live Session` button on the survey form is replaced with two new buttons: :guilabel:`Open Session Manager` and :guilabel:`Close Live Session`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:311 +#: ../../content/applications/marketing/surveys/create.rst:314 msgid "Clicking :guilabel:`Open Session Manager` opens another separate tab to the *Session Manager*, and clicking :guilabel:`Close Live Session` closes, and subsequently ends, the live session." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:313 +#: ../../content/applications/marketing/surveys/create.rst:316 msgid ":guilabel:`Test`: clicking this button opens a new tab to a test version of the survey, in order for the user to check for errors or inconsistencies, from the point-of-view of a participant. Users can tell if they are in a test version of the survey if there is a blue banner at the top of the screen, reading: `This is a Test Survey --> Edit Survey`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:318 +#: ../../content/applications/marketing/surveys/create.rst:321 msgid "If the link in the blue banner is clicked, Odoo returns the user to the survey form." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:319 +#: ../../content/applications/marketing/surveys/create.rst:322 msgid ":guilabel:`Print`: clicking this button opens a new tab to a printable version of the survey that the user can proceed to print for their records." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:321 +#: ../../content/applications/marketing/surveys/create.rst:324 msgid ":guilabel:`Close`: clicking this button closes the survey (i.e. archives it), which is represented by a red :guilabel:`Archived` banner across the top-right corner of the survey form." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:324 +#: ../../content/applications/marketing/surveys/create.rst:327 msgid "When this button is clicked, and the survey is closed, a single button appears in the upper-right corner of the survey form, titled: :guilabel:`Reopen`. When :guilabel:`Reopen` is clicked the survey is reopened (i.e. unarchived), and the :guilabel:`Archived` banner is removed from the survey form." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:330 +#: ../../content/applications/marketing/surveys/create.rst:333 #: ../../content/applications/marketing/surveys/live_session.rst:220 #: ../../content/applications/marketing/surveys/scoring.rst:56 -msgid ":doc:`time_random`" +msgid ":doc:`questions`" msgstr "" #: ../../content/applications/marketing/surveys/live_session.rst:3 @@ -7078,7 +7230,7 @@ msgid "If the :guilabel:`Is a Certification` option is enabled in the :guilabel: msgstr "" #: ../../content/applications/marketing/surveys/live_session.rst:41 -msgid "With the desired survey radio button option selected, proceed to :doc:`create a survey <../surveys/create>` with :doc:`questions and sections <../surveys/time_random>`." +msgid "With the desired survey radio button option selected, proceed to :doc:`create a survey <../surveys/create>` with :doc:`questions and sections <../surveys/questions>`." msgstr "" #: ../../content/applications/marketing/surveys/live_session.rst:44 @@ -7237,6 +7389,356 @@ msgstr "" msgid "Repeat this process until the survey is complete." msgstr "" +#: ../../content/applications/marketing/surveys/questions.rst:3 +#: ../../content/applications/marketing/surveys/questions.rst:64 +msgid "Create questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:5 +msgid "In Odoo *Surveys*, crafting and tailoring survey questions is crucial for :doc:`creating and customizing surveys <../surveys/create>`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:8 +msgid "Fortunately, Odoo provides numerous ways to configure tailored questions for any kind of survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:10 +msgid "To access a list of *all* the questions that have been created in the database, navigate to :menuselection:`Surveys app --> Questions & Answers --> Questions`. There, users can view and modify any question from any survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:14 +msgid "However, there is only one place in the Odoo *Surveys* application where survey questions can be created. To do that, navigate to a survey form, by going to :menuselection:`Surveys app --> New`, or by selecting any pre-existing survey from the :guilabel:`Surveys` page (:menuselection:`Surveys app --> Surveys`)." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:22 +msgid "On a survey form, users can view, access, add, and/or delete questions (and sections) in the :guilabel:`Questions` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:32 +msgid "To reveal the :guilabel:`Mandatory Answer` column on the :guilabel:`Questions` tab, which indicates if questions require a mandatory answer or not, click the :guilabel:`(optional columns)` icon located to the far-right of the column titles." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The slider drop-down menu showing the Mandatory Answer option in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:41 +msgid "Create sections" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:50 +msgid "Then, drag-and-drop desired questions beneath a section, or drag-and-drop a section title on top of (i.e. *before*) the desired question(s) in the survey, in order to populate the section with specific questions that fit the theme of the section." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:66 +msgid "To create questions for the survey, click :guilabel:`Add a question` in the :guilabel:`Questions` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:69 +msgid "Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and Questions` pop-up window, in which a survey question can be created." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:77 +msgid "When all desired configurations are complete click either :guilabel:`Save & Close` to save the question and return to the survey form, or :guilabel:`Save & New` to save the question and create a new one right away in a fresh :guilabel:`Create Sections and Questions` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:81 +msgid "Click :guilabel:`Discard` to discard the question entirely." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:84 +msgid "Create Sections and Questions pop-up window" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The Create Sections and Questions pop-up form in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:90 +msgid "In the :guilabel:`Create Sections and Questions` pop-up window, start by typing the question into the :guilabel:`Question` field, located at the top of the pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:93 +msgid "Then, choose the desired :guilabel:`Question Type`. A preview of each :guilabel:`Question Type` is to the right of the :guilabel:`Question Type` field, when a :guilabel:`Question Type` is selected." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:96 +msgid "Choose from the following :guilabel:`Question Types`:" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:98 +msgid ":guilabel:`Multiple choice: only one answer`: a multiple choice question, where only one answer is permitted." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:100 +msgid ":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice question, where more than answer is permitted." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:102 +msgid ":guilabel:`Multiple Lines Text Box`: an open-ended question, where participants can type in a multiple line response." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:104 +msgid ":guilabel:`Single Line Text Box`: an open-ended question, where participants can type in a single line response." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:106 +msgid ":guilabel:`Numerical Value`: a number-based question, where participants must enter a number as a response." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:108 +msgid ":guilabel:`Date`: a date-based question, where participants must enter a date (year-month-day) as a response." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:110 +msgid ":guilabel:`Datetime`: a date-based question, where participants must enter a date *and* time (year-month-day, hour-minute-second) as a response." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:112 +msgid ":guilabel:`Matrix`: a multiple-choice, multiple question, in a table/chart layout, where participants are presented with different questions on each row, and different answer options on each column." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:117 +msgid "Different features appear in the :guilabel:`Answers` and :guilabel:`Options` tabs, depending on the chosen :guilabel:`Question Type`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:120 +msgid "However, the :guilabel:`Description` tab **always** remains the same, regardless of the question type chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:123 +msgid "Once a :guilabel:`Question Type` has been selected, there are three possible tabs where information can be customized for the question. These include the :guilabel:`Answers` tab (if applicable for the chosen :guilabel:`Question Type`), the :guilabel:`Description` tab, and the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:127 +msgid "Each tab offers a variety of different features, depending on what :guilabel:`Question Type` was chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:131 +msgid "Answers tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:133 +msgid "The :guilabel:`Answers` tab **only** appears if the selected :guilabel:`Question Type` provides answer options to the participant." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:136 +msgid "However, if a custom response is required to answer the selected :guilabel:`Question Type`, like a :guilabel:`Multiple Lines Text Box`, for example. Or, if the answer to the :guilabel:`Question Type` is a number, date, or datetime, the :guilabel:`Answers` tab disappears completely." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:140 +msgid "If the :guilabel:`Single Line Text Box` is selected as the :guilabel:`Question Type`, the :guilabel:`Answers` tab remains, although it only provides two checkbox options: :guilabel:`Input must be an email` and :guilabel:`Save as user nickname`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The Single Line Text box question type answers tab in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:148 +msgid "If the :guilabel:`Input must be an email` option is enabled, a new field, :guilabel:`Save as user email` appears. If that box is ticked, Odoo saves the participant's answer to that specific question as their email address." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:152 +msgid "If the :guilabel:`Save as user nickname` option is enabled, Odoo saves the participant's answer as its nickname." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:155 +msgid "For all other applicable :guilabel:`Question Type` options that provide answer options to the participant, the :guilabel:`Answers` tab appears the same." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The answer tab with a multiple choice answer option selected in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:162 +msgid "From here, users can add answer options by clicking :guilabel:`Add a line`, and typing in the various answer options for that question. Then, either press :kbd:`Enter` to lock in that answer option and immediately add another one. Or, click away to simply lock in that answer option." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:166 +msgid "The entered answer options appear in the :guilabel:`Choices` column of the :guilabel:`Answers` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:168 +msgid "If any *Scoring* option is enabled in the :guilabel:`Options` tab of the survey form, the :guilabel:`Correct` and :guilabel:`Score` columns appear to the right of the :guilabel:`Choices` column." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:172 +msgid "To mark an answer option as correct, tick the box beneath the :guilabel:`Correct` column for the respective question. If :guilabel:`Multiple choice: multiple answers allowed` is set as the :guilabel:`Question Type`, multiple answers in the :guilabel:`Choices` column can be marked as :guilabel:`Correct`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:177 +msgid "In the :guilabel:`Score` column, designate how many points (if any) should be rewarded to the participant for entering that specific answer. It is possible to enter a negative amount as the :guilabel:`Score` to take points away for an incorrect response." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:181 +msgid "The option to upload a corresponding image to accompany the answer options is available on the question line, beneath the :guilabel:`Image` column, by clicking :guilabel:`Upload your file`, and uploading the desired image." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:185 +msgid "To delete any answer option, click the :guilabel:`🗑️ (trash can)` icon to the far-right of the question line." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:188 +msgid "An exception to that is if the :guilabel:`Matrix` option is selected as the :guilabel:`Question Type`. If that's chosen, the :guilabel:`Answers` tab remains, but below the typical :guilabel:`Choices` section, there is a :guilabel:`Rows` section. That's because the :guilabel:`Matrix` option provides an answer table for participants to fill out." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The answer tab with a matrix question type selected in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:200 +msgid "In the :guilabel:`Description` tab of the :guilabel:`Create Sections and Questions` pop-up window is used to provide any kind of guidelines, instructions, or any other type of supplemental material deemed necessary to help participants answer/understand the question." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:204 +msgid "Entering a description is **not** required." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:209 +msgid "In the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window, there are four available sections: :guilabel:`Answers`, :guilabel:`Constraints`, :guilabel:`Conditional Display`, and :guilabel:`Live Sessions`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:214 +msgid "Answers section" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:217 +msgid "Fields in the :guilabel:`Answers` section in the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window vary, depending on the selected :guilabel:`Question Type` and overall :guilabel:`Options` configured on the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:222 +msgid "Multiple Choice question types" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:224 +msgid "If the selected :guilabel:`Question Type` is either :guilabel:`Multiple choice: only one answer` or :guilabel:`Multiple choice: multiple answers allowed`, there is a :guilabel:`Show Comments Field` present in the :guilabel:`Answers` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:228 +msgid "When enabled, two additional fields appear: :guilabel:`Comment Message` and :guilabel:`Comment is an answer`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The answers section of the options tab when a multiple choice question type is selected." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:235 +msgid "In the :guilabel:`Comment Message` field, type in a guiding message to help participants know what is expected of them (e.g. `If other, please specify`)." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:238 +msgid "If the :guilabel:`Comment is an answer` option is enabled, Odoo takes the participant's commented response as an answer, and not just commentary on the question. This is best utilized in surveys where there is no scoring option enabled." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:243 +msgid "Multiple Lines Text Box question type" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:245 +msgid "If the selected :guilabel:`Question Type` is :guilabel:`Multiple Lines Text Box`, a :guilabel:`Placeholder` field appears in the :guilabel:`Answers` section of the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The placeholder field when a multiple lines text box option is chosen in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:253 +#: ../../content/applications/marketing/surveys/questions.rst:276 +msgid "In the :guilabel:`Placeholder` field, enter a guiding direction to help participants know what they should write in the :guilabel:`Multiple Lines Text Box` presented to them." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:257 +msgid "Single Line Text Box, Numerical Value, Date, Datetime question types" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:259 +msgid "If the selected :guilabel:`Question Type` is :guilabel:`Single Line Text Box`, :guilabel:`Numerical Value`, :guilabel:`Date`, or :guilabel:`Datetime`, two options appear in the :guilabel:`Answers` section of the :guilabel:`Options` tab: :guilabel:`Validate Entry` and :guilabel:`Placeholder`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:263 +msgid "If the :guilabel:`Validate Entry` option is enabled, two additional fields appear beneath: :guilabel:`Min/Max Limits` and :guilabel:`Validation Error`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The answers section of the option tab when a single line text box question type is chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:270 +msgid "In the :guilabel:`Min/Max Limits` field, designate the minimum and maximum allowed quantities for that specific question." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:273 +msgid "In the :guilabel:`Validation Error` field, enter a custom message that Odoo displays when an answer is not valid." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:280 +msgid "Constraints section" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:282 +msgid "The :guilabel:`Constraints` section in the :guilabel:`Options` tab is the same, regardless of the selected :guilabel:`Question Type`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The Constraints section in the options tab in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:289 +msgid "In the :guilabel:`Constraints` section, there is one option available: :guilabel:`Mandatory Answer`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:291 +msgid "When :guilabel:`Mandatory Answer` is enabled, that means that specific question requires an answer from the participant before they can move on. Also, when :guilabel:`Mandatory Answer` is enabled, that reveals an additional field: :guilabel:`Error Message`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:295 +msgid "In the :guilabel:`Error Message` field, enter a custom error message prompting the participant to provide an answer for this question." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:299 +msgid "Conditional Display section" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:301 +msgid ":guilabel:`Conditional Display` means the question is **only** displayed if a specified conditional answer(s) (i.e. :guilabel:`Triggering Answers`) has been selected in a previous question(s)." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:305 +msgid "The :guilabel:`Conditional Display` section of the :guilabel:`Options` tab is **not** available when questions are randomly picked." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:308 +msgid "There is only one field in the :guilabel:`Conditional Display` section: :guilabel:`Triggering Answers`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The Conditional Display section of the options tab in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:315 +msgid "In the :guilabel:`Triggering Answers` field, select specific responses from previous questions that would trigger this question. More than one answer can be selected. Leave the field empty if the question should always be displayed." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:320 +msgid "Live Sessions section" +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:322 +msgid "The option in the :guilabel:`Live Sessions` section of the :guilabel:`Options` tab are **only** supported by *Live Session* surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:325 +msgid "There is only one option available in the :guilabel:`Live Sessions` section: :guilabel:`Question Time Limit`." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:-1 +msgid "The Live Sessions section of the Option tab in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/questions.rst:332 +msgid "When the :guilabel:`Question Time Limit` option is enabled, designate how much time (in :guilabel:`seconds`) participants have to answer the question during a *Live Session* survey." +msgstr "" + #: ../../content/applications/marketing/surveys/scoring.rst:3 msgid "Scoring surveys" msgstr "" @@ -7288,353 +7790,3 @@ msgstr "" #: ../../content/applications/marketing/surveys/scoring.rst:-1 msgid "Example of how a badge looks on the eLearning portion of the website." msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:3 -#: ../../content/applications/marketing/surveys/time_random.rst:64 -msgid "Create questions" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:5 -msgid "In Odoo *Surveys*, crafting and tailoring survey questions is crucial for :doc:`creating and customizing surveys <../surveys/create>`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:8 -msgid "Fortunately, Odoo provides numerous ways to configure tailored questions for any kind of survey." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:10 -msgid "To access a list of *all* the questions that have been created in the database, navigate to :menuselection:`Surveys app --> Questions & Answers --> Questions`. There, users can view and modify any question from any survey." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:14 -msgid "However, there is only one place in the Odoo *Surveys* application where survey questions can be created. To do that, navigate to a survey form, by going to :menuselection:`Surveys app --> New`, or by selecting any pre-existing survey from the :guilabel:`Surveys` page (:menuselection:`Surveys app --> Surveys`)." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:22 -msgid "On a survey form, users can view, access, add, and/or delete questions (and sections) in the :guilabel:`Questions` tab." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:32 -msgid "To reveal the :guilabel:`Mandatory Answer` column on the :guilabel:`Questions` tab, which indicates if questions require a mandatory answer or not, click the :guilabel:`(optional columns)` icon located to the far-right of the column titles." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The slider drop-down menu showing the Mandatory Answer option in Odoo Surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:41 -msgid "Create sections" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:50 -msgid "Then, drag-and-drop desired questions beneath a section, or drag-and-drop a section title on top of (i.e. *before*) the desired question(s) in the survey, in order to populate the section with specific questions that fit the theme of the section." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:66 -msgid "To create questions for the survey, click :guilabel:`Add a question` in the :guilabel:`Questions` tab." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:69 -msgid "Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and Questions` pop-up window, in which a survey question can be created." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:77 -msgid "When all desired configurations are complete click either :guilabel:`Save & Close` to save the question and return to the survey form, or :guilabel:`Save & New` to save the question and create a new one right away in a fresh :guilabel:`Create Sections and Questions` pop-up window." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:81 -msgid "Click :guilabel:`Discard` to discard the question entirely." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:84 -msgid "Create Sections and Questions pop-up window" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The Create Sections and Questions pop-up form in Odoo Surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:90 -msgid "In the :guilabel:`Create Sections and Questions` pop-up window, start by typing the question into the :guilabel:`Question` field, located at the top of the pop-up window." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:93 -msgid "Then, choose the desired :guilabel:`Question Type`. A preview of each :guilabel:`Question Type` is to the right of the :guilabel:`Question Type` field, when a :guilabel:`Question Type` is selected." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:96 -msgid "Choose from the following :guilabel:`Question Types`:" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:98 -msgid ":guilabel:`Multiple choice: only one answer`: a multiple choice question, where only one answer is permitted." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:100 -msgid ":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice question, where more than answer is permitted." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:102 -msgid ":guilabel:`Multiple Lines Text Box`: an open-ended question, where participants can type in a multiple line response." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:104 -msgid ":guilabel:`Single Line Text Box`: an open-ended question, where participants can type in a single line response." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:106 -msgid ":guilabel:`Numerical Value`: a number-based question, where participants must enter a number as a response." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:108 -msgid ":guilabel:`Date`: a date-based question, where participants must enter a date (year-month-day) as a response." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:110 -msgid ":guilabel:`Datetime`: a date-based question, where participants must enter a date *and* time (year-month-day, hour-minute-second) as a response." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:112 -msgid ":guilabel:`Matrix`: a multiple-choice, multiple question, in a table/chart layout, where participants are presented with different questions on each row, and different answer options on each column." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:117 -msgid "Different features appear in the :guilabel:`Answers` and :guilabel:`Options` tabs, depending on the chosen :guilabel:`Question Type`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:120 -msgid "However, the :guilabel:`Description` tab **always** remains the same, regardless of the question type chosen." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:123 -msgid "Once a :guilabel:`Question Type` has been selected, there are three possible tabs where information can be customized for the question. These include the :guilabel:`Answers` tab (if applicable for the chosen :guilabel:`Question Type`), the :guilabel:`Description` tab, and the :guilabel:`Options` tab." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:127 -msgid "Each tab offers a variety of different features, depending on what :guilabel:`Question Type` was chosen." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:131 -msgid "Answers tab" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:133 -msgid "The :guilabel:`Answers` tab **only** appears if the selected :guilabel:`Question Type` provides answer options to the participant." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:136 -msgid "However, if a custom response is required to answer the selected :guilabel:`Question Type`, like a :guilabel:`Multiple Lines Text Box`, for example. Or, if the answer to the :guilabel:`Question Type` is a number, date, or datetime, the :guilabel:`Answers` tab disappears completely." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:140 -msgid "If the :guilabel:`Single Line Text Box` is selected as the :guilabel:`Question Type`, the :guilabel:`Answers` tab remains, although it only provides two checkbox options: :guilabel:`Input must be an email` and :guilabel:`Save as user nickname`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The Single Line Text box question type answers tab in Odoo Surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:148 -msgid "If the :guilabel:`Input must be an email` option is enabled, a new field, :guilabel:`Save as user email` appears. If that box is ticked, Odoo saves the participant's answer to that specific question as their email address." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:152 -msgid "If the :guilabel:`Save as user nickname` option is enabled, Odoo saves the participant's answer as its nickname." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:155 -msgid "For all other applicable :guilabel:`Question Type` options that provide answer options to the participant, the :guilabel:`Answers` tab appears the same." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The answer tab with a multiple choice answer option selected in Odoo Surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:162 -msgid "From here, users can add answer options by clicking :guilabel:`Add a line`, and typing in the various answer options for that question. Then, either press :kbd:`Enter` to lock in that answer option and immediately add another one. Or, click away to simply lock in that answer option." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:166 -msgid "The entered answer options appear in the :guilabel:`Choices` column of the :guilabel:`Answers` tab." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:168 -msgid "If any *Scoring* option is enabled in the :guilabel:`Options` tab of the survey form, the :guilabel:`Correct` and :guilabel:`Score` columns appear to the right of the :guilabel:`Choices` column." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:172 -msgid "To mark an answer option as correct, tick the box beneath the :guilabel:`Correct` column for the respective question. If :guilabel:`Multiple choice: multiple answers allowed` is set as the :guilabel:`Question Type`, multiple answers in the :guilabel:`Choices` column can be marked as :guilabel:`Correct`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:177 -msgid "In the :guilabel:`Score` column, designate how many points (if any) should be rewarded to the participant for entering that specific answer. It is possible to enter a negative amount as the :guilabel:`Score` to take points away for an incorrect response." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:181 -msgid "The option to upload a corresponding image to accompany the answer options is available on the question line, beneath the :guilabel:`Image` column, by clicking :guilabel:`Upload your file`, and uploading the desired image." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:185 -msgid "To delete any answer option, click the :guilabel:`🗑️ (trash can)` icon to the far-right of the question line." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:188 -msgid "An exception to that is if the :guilabel:`Matrix` option is selected as the :guilabel:`Question Type`. If that's chosen, the :guilabel:`Answers` tab remains, but below the typical :guilabel:`Choices` section, there is a :guilabel:`Rows` section. That's because the :guilabel:`Matrix` option provides an answer table for participants to fill out." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The answer tab with a matrix question type selected in Odoo Surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:200 -msgid "In the :guilabel:`Description` tab of the :guilabel:`Create Sections and Questions` pop-up window is used to provide any kind of guidelines, instructions, or any other type of supplemental material deemed necessary to help participants answer/understand the question." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:204 -msgid "Entering a description is **not** required." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:209 -msgid "In the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window, there are four available sections: :guilabel:`Answers`, :guilabel:`Constraints`, :guilabel:`Conditional Display`, and :guilabel:`Live Sessions`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:214 -msgid "Answers section" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:217 -msgid "Fields in the :guilabel:`Answers` section in the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window vary, depending on the selected :guilabel:`Question Type` and overall :guilabel:`Options` configured on the survey form." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:222 -msgid "Multiple Choice question types" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:224 -msgid "If the selected :guilabel:`Question Type` is either :guilabel:`Multiple choice: only one answer` or :guilabel:`Multiple choice: multiple answers allowed`, there is a :guilabel:`Show Comments Field` present in the :guilabel:`Answers` section." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:228 -msgid "When enabled, two additional fields appear: :guilabel:`Comment Message` and :guilabel:`Comment is an answer`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The answers section of the options tab when a multiple choice question type is selected." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:235 -msgid "In the :guilabel:`Comment Message` field, type in a guiding message to help participants know what is expected of them (e.g. `If other, please specify`)." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:238 -msgid "If the :guilabel:`Comment is an answer` option is enabled, Odoo takes the participant's commented response as an answer, and not just commentary on the question. This is best utilized in surveys where there is no scoring option enabled." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:243 -msgid "Multiple Lines Text Box question type" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:245 -msgid "If the selected :guilabel:`Question Type` is :guilabel:`Multiple Lines Text Box`, a :guilabel:`Placeholder` field appears in the :guilabel:`Answers` section of the :guilabel:`Options` tab." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The placeholder field when a multiple lines text box option is chosen in Odoo Surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:253 -#: ../../content/applications/marketing/surveys/time_random.rst:276 -msgid "In the :guilabel:`Placeholder` field, enter a guiding direction to help participants know what they should write in the :guilabel:`Multiple Lines Text Box` presented to them." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:257 -msgid "Single Line Text Box, Numerical Value, Date, Datetime question types" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:259 -msgid "If the selected :guilabel:`Question Type` is :guilabel:`Single Line Text Box`, :guilabel:`Numerical Value`, :guilabel:`Date`, or :guilabel:`Datetime`, two options appear in the :guilabel:`Answers` section of the :guilabel:`Options` tab: :guilabel:`Validate Entry` and :guilabel:`Placeholder`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:263 -msgid "If the :guilabel:`Validate Entry` option is enabled, two additional fields appear beneath: :guilabel:`Min/Max Limits` and :guilabel:`Validation Error`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The answers section of the option tab when a single line text box question type is chosen." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:270 -msgid "In the :guilabel:`Min/Max Limits` field, designate the minimum and maximum allowed quantities for that specific question." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:273 -msgid "In the :guilabel:`Validation Error` field, enter a custom message that Odoo displays when an answer is not valid." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:280 -msgid "Constraints section" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:282 -msgid "The :guilabel:`Constraints` section in the :guilabel:`Options` tab is the same, regardless of the selected :guilabel:`Question Type`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The Constraints section in the options tab in Odoo Surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:289 -msgid "In the :guilabel:`Constraints` section, there is one option available: :guilabel:`Mandatory Answer`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:291 -msgid "When :guilabel:`Mandatory Answer` is enabled, that means that specific question requires an answer from the participant before they can move on. Also, when :guilabel:`Mandatory Answer` is enabled, that reveals an additional field: :guilabel:`Error Message`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:295 -msgid "In the :guilabel:`Error Message` field, enter a custom error message prompting the participant to provide an answer for this question." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:299 -msgid "Conditional Display section" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:301 -msgid ":guilabel:`Conditional Display` means the question is **only** displayed if a specified conditional answer(s) (i.e. :guilabel:`Triggering Answers`) has been selected in a previous question(s)." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:305 -msgid "The :guilabel:`Conditional Display` section of the :guilabel:`Options` tab is **not** available when questions are randomly picked." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:308 -msgid "There is only one field in the :guilabel:`Conditional Display` section: :guilabel:`Triggering Answers`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The Conditional Display section of the options tab in the Odoo Surveys application." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:315 -msgid "In the :guilabel:`Triggering Answers` field, select specific responses from previous questions that would trigger this question. More than one answer can be selected. Leave the field empty if the question should always be displayed." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:320 -msgid "Live Sessions section" -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:322 -msgid "The option in the :guilabel:`Live Sessions` section of the :guilabel:`Options` tab are **only** supported by *Live Session* surveys." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:325 -msgid "There is only one option available in the :guilabel:`Live Sessions` section: :guilabel:`Question Time Limit`." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "The Live Sessions section of the Option tab in the Odoo Surveys application." -msgstr "" - -#: ../../content/applications/marketing/surveys/time_random.rst:332 -msgid "When the :guilabel:`Question Time Limit` option is enabled, designate how much time (in :guilabel:`seconds`) participants have to answer the question during a *Live Session* survey." -msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 56d75d48e..e742fdb4d 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -762,35 +762,35 @@ msgstr "" msgid "Chatter" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:5 +#: ../../content/applications/productivity/discuss/chatter.rst:8 msgid "The *Chatter* feature is integrated throughout Odoo to streamline communication, maintain traceability, and provide accountability among team members. Chatter windows, known as *composers*, are located on almost every record within the database, and allow users to communicate with both internal users and external contacts." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:10 +#: ../../content/applications/productivity/discuss/chatter.rst:13 msgid "Chatter composers also enable users to log notes, upload files, and schedule activities." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:13 +#: ../../content/applications/productivity/discuss/chatter.rst:16 msgid "Chatter thread" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:15 +#: ../../content/applications/productivity/discuss/chatter.rst:18 msgid "A *chatter thread* can be found on most pages in the database, and serves as a record of the updates and edits made to a record. A note is logged in the chatter thread when a change is made. The note includes details of the change, and a time stamp." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:20 +#: ../../content/applications/productivity/discuss/chatter.rst:23 msgid "A user, Mitchell Admin, needs to update the email address of a contact. After they save the changes to the contact record, a note is logged in the chatter of the contact record with the following information:" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:24 +#: ../../content/applications/productivity/discuss/chatter.rst:27 msgid "The date when the change occurred." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:25 +#: ../../content/applications/productivity/discuss/chatter.rst:28 msgid "The email address as it was previously listed." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:26 +#: ../../content/applications/productivity/discuss/chatter.rst:29 msgid "The updated email address." msgstr "" @@ -798,7 +798,7 @@ msgstr "" msgid "A close up of a chatter thread with an update to a contact record." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:32 +#: ../../content/applications/productivity/discuss/chatter.rst:35 msgid "If a record was created, or edited, via an imported file, or was otherwise updated through an intervention by the system, the chatter thread creates a log note, and credits the change to OdooBot." msgstr "" @@ -806,111 +806,111 @@ msgstr "" msgid "A close up of a chatter thread of an OdooBot created contact record." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:43 +#: ../../content/applications/productivity/discuss/chatter.rst:46 msgid "Add followers" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:45 +#: ../../content/applications/productivity/discuss/chatter.rst:48 msgid "A *follower* is a user or contact that is added to a record and is notified when the record is updated, based on specific :ref:`follower subscription settings `. Followers can add themselves, or can be added by another user." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:50 +#: ../../content/applications/productivity/discuss/chatter.rst:53 msgid "If a user creates, or is assigned to a record, they are automatically added as a follower." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:52 +#: ../../content/applications/productivity/discuss/chatter.rst:55 msgid "To follow a record, navigate to any record with a chatter thread. For example, to open a *Helpdesk* ticket, navigate to :menuselection:`Helpdesk app --> Tickets --> All Tickets`, and select a ticket from the list to open it." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:56 +#: ../../content/applications/productivity/discuss/chatter.rst:59 msgid "At the top-right, above the chatter composer, click :guilabel:`Follow`. Doing this changes the button to read :guilabel:`Following`. Click it again to :guilabel:`Unfollow`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:60 +#: ../../content/applications/productivity/discuss/chatter.rst:63 msgid "Manage followers" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:62 -msgid "To add another user, or contact, as a follower, click the :guilabel:`👤 (user)` icon. This opens a drop-down list of the current followers. Click :guilabel:`Add Followers` to open an :guilabel:`Invite Follower` pop-up window." +#: ../../content/applications/productivity/discuss/chatter.rst:65 +msgid "To add another user, or contact, as a follower, click the |user|. This opens a drop-down list of the current followers. Click :guilabel:`Add Followers` to open an :guilabel:`Invite Follower` pop-up window." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:66 +#: ../../content/applications/productivity/discuss/chatter.rst:69 msgid "Select one or more contacts from the :guilabel:`Recipients` drop-down list. To notify the contacts, tick the :guilabel:`Send Notification` checkbox. Edit the message template as desired, then click :guilabel:`Add Followers`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:70 -msgid "To remove followers, click the :guilabel:`👤 (user)` icon to open the current followers list. Find the name of the follower to be removed, and click the :guilabel:`x` icon." +#: ../../content/applications/productivity/discuss/chatter.rst:73 +msgid "To remove followers, click the |user| to open the current followers list. Find the name of the follower to be removed, and click the :icon:`fa-remove` :guilabel:`(remove)` icon." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:76 +#: ../../content/applications/productivity/discuss/chatter.rst:79 msgid "Edit follower subscription" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:78 -msgid "The updates a follower receives can vary based on their subscription settings. To see the type of updates a follower is subscribed to, and to edit the list, click the :guilabel:`👤 (user)` icon. Find the appropriate follower in the list, then click the :guilabel:`✏️ (pencil)` icon. This opens the :guilabel:`Edit Subscription` pop-up window for the follower." +#: ../../content/applications/productivity/discuss/chatter.rst:81 +msgid "The updates a follower receives can vary based on their subscription settings. To see the type of updates a follower is subscribed to, and to edit the list, click the |user|. Find the appropriate follower in the list, then click the :icon:`fa-pencil` :guilabel:`(pencil)` icon. This opens the :guilabel:`Edit Subscription` pop-up window for the follower." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:83 +#: ../../content/applications/productivity/discuss/chatter.rst:86 msgid "The list of available subscription settings varies depending on the record type. For example, a follower of a *Helpdesk* ticket may be informed when the ticket is rated. This option would not be available for the followers of a *CRM* opportunity." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:87 +#: ../../content/applications/productivity/discuss/chatter.rst:90 msgid "Tick the checkbox for any updates the follower should receive, and clear the checkbox for any updates they should **not** receive. Click :guilabel:`Apply` when finished." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:94 +#: ../../content/applications/productivity/discuss/chatter.rst:97 msgid "The Edit Subscription window on a Helpdesk ticket." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:94 +#: ../../content/applications/productivity/discuss/chatter.rst:97 msgid "The Edit Subscription options vary depending on the record type. These are the options for a Helpdesk ticket." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:100 +#: ../../content/applications/productivity/discuss/chatter.rst:103 msgid "Log notes" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:102 +#: ../../content/applications/productivity/discuss/chatter.rst:105 msgid "The chatter function includes the ability to log internal notes on individual records. These notes are only accessible to internal users, and are available on any records that feature a chatter thread." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:106 +#: ../../content/applications/productivity/discuss/chatter.rst:109 msgid "To log an internal note, first navigate to a record. For example, to open a *CRM* opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, and click on the Kanban card of an opportunity to open it. Then, at the top-right, above the chatter composer, click :guilabel:`Log note`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:111 +#: ../../content/applications/productivity/discuss/chatter.rst:114 msgid "Enter the note in the chatter composer. To tag an internal user, type `@`, and begin typing the name of the person to tag. Then, select a name from the drop-down menu. Depending on their notification settings, the user is notified by email, or through Odoo." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:116 +#: ../../content/applications/productivity/discuss/chatter.rst:119 msgid "Outside contacts can also be tagged in an internal log note. The contact then receives an email with the contents of the note they were tagged in, including any attachments added directly to the note. If they respond to the email, their response is logged in the chatter, and they are added to the record as a follower." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:121 +#: ../../content/applications/productivity/discuss/chatter.rst:124 msgid "Outside contacts are **not** able to log in to view the entire chatter thread, and are only notified of specific updates, based on their :ref:`follower subscription settings `, or when they are tagged directly." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:128 +#: ../../content/applications/productivity/discuss/chatter.rst:131 msgid "Send messages" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:130 +#: ../../content/applications/productivity/discuss/chatter.rst:133 msgid "Chatter composers can send messages to outside contacts, without having to leave the database, or open a different application. This makes it easy to communicate with potential customers in the *Sales* and *CRM* applications, or vendors in the *Purchase* app." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:134 +#: ../../content/applications/productivity/discuss/chatter.rst:137 msgid "To send a message, first navigate to a record. For example, to send a message from a *CRM* opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, and click on the Kanban card of an opportunity to open it. Then, at the top-right, above the chatter composer, click :guilabel:`Send message`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:140 +#: ../../content/applications/productivity/discuss/chatter.rst:143 msgid "Press :command:`Ctrl + Enter` to send a message, instead of using the :guilabel:`Send` button." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:142 +#: ../../content/applications/productivity/discuss/chatter.rst:145 msgid "If any :ref:`followers ` have been added to the record, they are added as recipients of the message." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:146 +#: ../../content/applications/productivity/discuss/chatter.rst:149 msgid ":ref:`Followers ` of a record are added as recipients of a message automatically. If a follower should **not** receive a message, they must be removed as a follower before the message is sent, or a note is logged." msgstr "" @@ -919,167 +919,167 @@ msgid "A chatter composer preparing to send a message to the followers of a CRM "the customer listed on the opportunity record." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:156 +#: ../../content/applications/productivity/discuss/chatter.rst:159 msgid "Expand full composer" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:158 +#: ../../content/applications/productivity/discuss/chatter.rst:161 msgid "The chatter composer can be expanded to a larger pop-up window, allowing for additional customizations." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:161 -msgid "To open the full composer, click the :guilabel:`expand` icon in the bottom-right corner of the composer window." +#: ../../content/applications/productivity/discuss/chatter.rst:164 +msgid "To open the full composer, click the :icon:`fa-expand` :guilabel:`(expand)` icon in the bottom-right corner of the composer window." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:168 +#: ../../content/applications/productivity/discuss/chatter.rst:171 msgid "A chatter composer with emphasis on the expand icon." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:168 +#: ../../content/applications/productivity/discuss/chatter.rst:171 msgid "The expand icon in a chatter composer." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:170 +#: ../../content/applications/productivity/discuss/chatter.rst:173 msgid "Doing this opens a :guilabel:`Compose Email` pop-up window. Confirm or edit the intended :guilabel:`Recipients` of the message, or add additional recipients. The :guilabel:`Subject` field auto-populates based on the title of the record, though it can be edited, if desired." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:174 +#: ../../content/applications/productivity/discuss/chatter.rst:177 msgid "To use an :doc:`email template <../../general/companies/email_template/>` for the message, select it from the drop-down menu in the :guilabel:`Load template` field." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:178 +#: ../../content/applications/productivity/discuss/chatter.rst:181 msgid "The number and type of templates available vary, based on the record the message is created from." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:180 -msgid "Click :guilabel:`📎 Attachments` to add any files to the message, then click :guilabel:`Send`." +#: ../../content/applications/productivity/discuss/chatter.rst:183 +msgid "Click :icon:`fa-paperclip` :guilabel:`(paperclip)` icon to add any files to the message, then click :guilabel:`Send`." msgstr "" #: ../../content/applications/productivity/discuss/chatter.rst:-1 msgid "The expanded full chatter composer in the CRM application." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:187 +#: ../../content/applications/productivity/discuss/chatter.rst:191 msgid "Edit sent messages" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:189 +#: ../../content/applications/productivity/discuss/chatter.rst:193 msgid "Messages can be edited after they are sent, to fix typos, correct mistakes, or add missing information." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:193 +#: ../../content/applications/productivity/discuss/chatter.rst:197 msgid "When messages are edited after they have been sent, an updated message is **not** sent to the recipient." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:196 -msgid "To edit a sent message, click the :guilabel:`... (ellipsis)` icon menu to the right of the message. Then, select :guilabel:`Edit`. Make any necessary adjustments to the message." +#: ../../content/applications/productivity/discuss/chatter.rst:200 +msgid "To edit a sent message, click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon menu to the right of the message. Then, select :guilabel:`Edit`. Make any necessary adjustments to the message." msgstr "" #: ../../content/applications/productivity/discuss/chatter.rst:-1 msgid "The edit message option in a chatter thread." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:203 +#: ../../content/applications/productivity/discuss/chatter.rst:207 msgid "To save the changes, press :command:`Ctrl + Enter`. To discard the changes, press :command:`Escape`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:206 +#: ../../content/applications/productivity/discuss/chatter.rst:210 msgid "Users with Admin-level access rights can edit any sent messages. Users without Admin rights can **only** edit messages they created." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:212 +#: ../../content/applications/productivity/discuss/chatter.rst:216 msgid "Search messages" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:214 +#: ../../content/applications/productivity/discuss/chatter.rst:218 msgid "Chatter threads can become long after a while, because of all the information they contain. To make it easier to find a specific entry, users can search the text of messages and notes for specific keywords." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:218 -msgid "First, select a record with a chatter thread. For example, to search a *CRM* opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, and click on the Kanban card of an opportunity to open it. Then, at the top-right, above the chatter composer, click the :guilabel:`🔍 (magnifying glass)` icon to open the search bar." -msgstr "" - -#: ../../content/applications/productivity/discuss/chatter.rst:223 -msgid "Enter a keyword or phrase into the search bar, then hit :command:`Enter`, or click the :guilabel:`🔍 (magnifying glass)` icon to the right of the search bar. Any messages or notes containing the keyword or phrase entered are listed below the search bar, with the keyword highlighted." +#: ../../content/applications/productivity/discuss/chatter.rst:222 +msgid "First, select a record with a chatter thread. For example, to search a *CRM* opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, and click on the Kanban card of an opportunity to open it. Then, at the top-right, above the chatter composer, click the :icon:`oi-search` :guilabel:`(search)` icon to open the search bar." msgstr "" #: ../../content/applications/productivity/discuss/chatter.rst:227 +msgid "Enter a keyword or phrase into the search bar, then hit :command:`Enter`, or click the :icon:`oi-search` :guilabel:`(search)` icon to the right of the search bar. Any messages or notes containing the keyword or phrase entered are listed below the search bar, with the keyword highlighted." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:232 msgid "To be taken directly to a particular message in the chatter thread, hover over the upper-right corner of the result to reveal a :guilabel:`Jump` button. Click this button to be directed to that message's location in the thread." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:235 +#: ../../content/applications/productivity/discuss/chatter.rst:240 msgid "Search results in a chatter thread emphasising the search icon and the jump button." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:235 +#: ../../content/applications/productivity/discuss/chatter.rst:240 msgid "Search results in a chatter thread. Hover over the upper-right corner of a result to see the **Jump** option. Click it to be taken directly to that message in the chatter thread." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:241 +#: ../../content/applications/productivity/discuss/chatter.rst:246 msgid "Schedule activities" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:243 +#: ../../content/applications/productivity/discuss/chatter.rst:248 msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any database page that contains a chatter thread, Kanban view, list view, or activities view of an application." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:247 +#: ../../content/applications/productivity/discuss/chatter.rst:252 msgid "To schedule an activity through a chatter thread, click the :guilabel:`Activities` button, located at the top of the chatter on any record. On the :guilabel:`Schedule Activity` pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:252 +#: ../../content/applications/productivity/discuss/chatter.rst:257 msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:256 +#: ../../content/applications/productivity/discuss/chatter.rst:261 msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:259 +#: ../../content/applications/productivity/discuss/chatter.rst:264 msgid "Select a name from the :guilabel:`Assigned to` drop-down menu to assign the activity to a different user. Otherwise, the user creating the activity is automatically assigned." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:262 +#: ../../content/applications/productivity/discuss/chatter.rst:267 msgid "Add any additional information in the optional :guilabel:`Log a note...` field." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:265 +#: ../../content/applications/productivity/discuss/chatter.rst:270 msgid "The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up window auto-populates based on the configuration settings for the selected :guilabel:`Activity Type`. However, this date can be changed by selecting a day on the calendar in the :guilabel:`Due Date` field." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:269 +#: ../../content/applications/productivity/discuss/chatter.rst:274 msgid "Lastly, click one of the following buttons:" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:271 +#: ../../content/applications/productivity/discuss/chatter.rst:276 msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:272 +#: ../../content/applications/productivity/discuss/chatter.rst:277 msgid ":guilabel:`Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, it is automatically marked as completed." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:274 +#: ../../content/applications/productivity/discuss/chatter.rst:279 msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:276 +#: ../../content/applications/productivity/discuss/chatter.rst:281 msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:278 +#: ../../content/applications/productivity/discuss/chatter.rst:283 msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`, and are color-coded based on their due date." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:281 +#: ../../content/applications/productivity/discuss/chatter.rst:286 msgid "**Red** icons indicate an overdue activity." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:282 +#: ../../content/applications/productivity/discuss/chatter.rst:287 msgid "**Yellow** icons indicate an activity with a due date scheduled for the current date." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:283 +#: ../../content/applications/productivity/discuss/chatter.rst:288 msgid "**Green** icons indicate an activity with a due date scheduled in the future." msgstr "" @@ -1087,19 +1087,19 @@ msgstr "" msgid "A chatter thread with planned activities with varying due dates." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:290 -msgid "Click the :guilabel:`ℹ️ (info)` icon next to a planned activity to see additional details." +#: ../../content/applications/productivity/discuss/chatter.rst:295 +msgid "Click the :icon:`fa-info-circle` :guilabel:`(info)` icon next to a planned activity to see additional details." msgstr "" #: ../../content/applications/productivity/discuss/chatter.rst:0 msgid "A detailed view of a planned activity." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:296 +#: ../../content/applications/productivity/discuss/chatter.rst:302 msgid "After completing an activity, click :guilabel:`Mark Done` under the activity entry in the chatter. This opens a :guilabel:`Mark Done` pop-up window, where additional notes about the activity can be entered. After adding any comments to the pop-up window, click: :guilabel:`Done \\& Schedule Next`, :guilabel:`Done`, or :guilabel:`Discard`." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:301 +#: ../../content/applications/productivity/discuss/chatter.rst:307 msgid "After the activity is marked complete, an entry with the activity type, title, and any other details that were included in the pop-up window are listed in the chatter." msgstr "" @@ -1107,81 +1107,81 @@ msgstr "" msgid "A chatter thread with a completed activity, included additional details." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:311 +#: ../../content/applications/productivity/discuss/chatter.rst:317 msgid "Attach files" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:313 +#: ../../content/applications/productivity/discuss/chatter.rst:319 msgid "Files can be added as attachments in the chatter, either to send with messages, or to include with a record." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:317 -msgid "After a file has been added to a chatter thread, it can be downloaded by any user with access to the thread. Click the :guilabel:`📎 (paperclip)` icon to make the files header visible, if necessary. Then, click the download icon on the file to download it." +#: ../../content/applications/productivity/discuss/chatter.rst:323 +msgid "After a file has been added to a chatter thread, it can be downloaded by any user with access to the thread. Click the |paperclip| to make the files header visible, if necessary. Then, click the :icon:`fa-download` :guilabel:`(download)` icon the file to download it." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:321 -msgid "To attach a file, click the :guilabel:`📎 (paperclip)` icon located at the top of the chatter composer of any record that contains a chatter thread." +#: ../../content/applications/productivity/discuss/chatter.rst:327 +msgid "To attach a file, click the |paperclip| located at the top of the chatter composer of any record that contains a chatter thread." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:324 +#: ../../content/applications/productivity/discuss/chatter.rst:330 msgid "This opens a file explorer pop-up window. Navigate to the desired file, select it, then click :guilabel:`Open` to add it to the record. Alternatively, files can be dragged and dropped directly onto a chatter thread." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:328 +#: ../../content/applications/productivity/discuss/chatter.rst:334 msgid "After files have been added, they are listed in the chatter thread, under a :guilabel:`Files` heading." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:332 -msgid "After at least one file has been added to a chatter record, a new button labeled :guilabel:`Attach files` appears below the :guilabel:`Files` heading. To attach any additional files, this is the button that **must** be used, instead of the :guilabel:`📎 (paperclip)` icon at the top of the chatter thread." +#: ../../content/applications/productivity/discuss/chatter.rst:338 +msgid "After at least one file has been added to a chatter record, a new button labeled :guilabel:`Attach files` appears below the :guilabel:`Files` heading. To attach any additional files, this is the button that **must** be used, instead of the |paperclip| at the top of the chatter thread." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:337 -msgid "After the :guilabel:`Files` section heading appears in the thread, clicking the :guilabel:`📎 (paperclip)` icon no longer opens a file explorer pop-up window. Instead, clicking the :guilabel:`📎 (paperclip)` icon toggles the :guilabel:`Files` section from visible to invisible in the chatter thread." +#: ../../content/applications/productivity/discuss/chatter.rst:343 +msgid "After the :guilabel:`Files` section heading appears in the thread, clicking the |paperclip| no longer opens a file explorer pop-up window. Instead, clicking the |paperclip| toggles the :guilabel:`Files` section from visible to invisible in the chatter thread." msgstr "" #: ../../content/applications/productivity/discuss/chatter.rst:0 msgid "A chatter thread with a file attached and the Attach files button added." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:349 +#: ../../content/applications/productivity/discuss/chatter.rst:354 msgid "Integrations" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:351 +#: ../../content/applications/productivity/discuss/chatter.rst:356 msgid "Beyond the standard features, additional integrations can be enabled to work with the chatter feature, specifically *WhatsApp* and *Google Translate*." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:355 +#: ../../content/applications/productivity/discuss/chatter.rst:360 msgid "Before the *WhatsApp* and *Google Translate* integrations can be used with the chatter, they **must** be configured. Step-by-step instructions on how to set-up each of these features can be found in the documentation below:" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:359 -#: ../../content/applications/productivity/discuss/chatter.rst:418 +#: ../../content/applications/productivity/discuss/chatter.rst:364 +#: ../../content/applications/productivity/discuss/chatter.rst:424 msgid ":doc:`WhatsApp <../whatsapp>`" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:360 +#: ../../content/applications/productivity/discuss/chatter.rst:365 msgid ":doc:`Google Translate <../../general/integrations/google_translate>`" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:363 +#: ../../content/applications/productivity/discuss/chatter.rst:368 #: ../../content/applications/productivity/whatsapp.rst:3 msgid "WhatsApp" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:365 +#: ../../content/applications/productivity/discuss/chatter.rst:370 msgid "*WhatsApp* is an instant messaging and voice-over-IP app that allows users to send and receive messages, as well as share content." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:369 +#: ../../content/applications/productivity/discuss/chatter.rst:374 msgid "*WhatsApp* is an Odoo Enterprise-only application that does **not** work in the Odoo Community edition. To sign up for an Odoo Enterprise edition, click here: `Odoo Free Trial `_." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:373 +#: ../../content/applications/productivity/discuss/chatter.rst:378 msgid "After *WhatsApp* has been configured and enabled within a database, a :guilabel:`WhatsApp` button is added above the chatter composer on any applicable record. If one or more approved *WhatsApp* templates are found for that model, clicking this button opens a :guilabel:`Send WhatsApp Message` pop-up window." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:379 +#: ../../content/applications/productivity/discuss/chatter.rst:384 msgid "*WhatsApp* templates **must** be approved before they can be used. See :ref:`WhatsApp templates ` for more information." msgstr "" @@ -1189,47 +1189,47 @@ msgstr "" msgid "A send WhatsApp message pop-up window." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:387 +#: ../../content/applications/productivity/discuss/chatter.rst:392 msgid "Google Translate" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:389 +#: ../../content/applications/productivity/discuss/chatter.rst:394 msgid "*Google Translate* can be used to translate user-generated text in the Odoo chatter." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:391 +#: ../../content/applications/productivity/discuss/chatter.rst:396 msgid "To enable *Google Translate* on a database, an *API key* must first :doc:`be created <../../general/integrations/google_translate>` through the `Google API Console `_." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:395 +#: ../../content/applications/productivity/discuss/chatter.rst:400 msgid "After creating the API key, navigate to the :menuselection:`Settings app --> Discuss section` and paste the key in the :guilabel:`Message Translation` field. Click :guilabel:`Save` to save the changes." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:400 +#: ../../content/applications/productivity/discuss/chatter.rst:405 msgid "Translate a chatter message" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:402 -msgid "To translate a user's text from another language, click the :guilabel:`... (ellipsis)` icon menu to the right of the chatter. Then, select :guilabel:`Translate`. The content translates to the language set in the :doc:`user's preferences <../../general/users/language/>`." +#: ../../content/applications/productivity/discuss/chatter.rst:407 +msgid "To translate a user's text from another language, click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` menu to the right of the chatter. Then, select :guilabel:`Translate`. The content translates to the language set in the :doc:`user's preferences <../../general/users/language/>`." msgstr "" #: ../../content/applications/productivity/discuss/chatter.rst:-1 msgid "alt text" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:411 +#: ../../content/applications/productivity/discuss/chatter.rst:417 msgid "Using the *Google Translate* API **requires** a current billing account with `Google `_." msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:415 +#: ../../content/applications/productivity/discuss/chatter.rst:421 msgid ":doc:`Discuss <../discuss>`" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:416 +#: ../../content/applications/productivity/discuss/chatter.rst:422 msgid ":doc:`Discuss Channels <../discuss/team_communication/>`" msgstr "" -#: ../../content/applications/productivity/discuss/chatter.rst:417 +#: ../../content/applications/productivity/discuss/chatter.rst:423 msgid ":doc:`Activities <../../essentials/activities>`" msgstr "" @@ -6114,7 +6114,7 @@ msgid "Odoo VoIP (Voice over Internet Protocol) can be set up to work together w msgstr "" #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:12 -msgid "To use this service, `contact Axivox `_ to open an account. Before doing so, verify that Axivox covers the company's area, along with the areas the company's users wish to call." +msgid "To use this service, `contact Axivox `_ to open an account. Before doing so, verify that Axivox covers the company's area, along with the areas the company's users wish to call." msgstr "" #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:19 diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index a42b67c7e..75e536b0e 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,7 +49,8 @@ msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:13 #: ../../content/applications/sales/crm/optimize/gamification.rst:10 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:27 -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 +#: ../../content/applications/sales/crm/track_leads/resellers.rst:9 #: ../../content/applications/sales/point_of_sale/combos.rst:16 #: ../../content/applications/sales/point_of_sale/configuration.rst:6 #: ../../content/applications/sales/point_of_sale/employee_login.rst:13 @@ -65,7 +66,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:12 -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:53 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:54 #: ../../content/applications/sales/point_of_sale/restaurant.rst:22 #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:22 @@ -1066,7 +1067,7 @@ msgid ":guilabel:`Time to Qualify a Lead`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:132 -msgid ":guilabel:`Days to Close a Dead`" +msgid ":guilabel:`Days to Close a Deal`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:133 @@ -1735,6 +1736,7 @@ msgid "Add Custom Filters pop-up window with custom filters configured for expec msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:118 +#: ../../content/applications/sales/crm/performance/forecast_report.rst:85 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:145 msgid "View results" msgstr "" @@ -1861,6 +1863,118 @@ msgstr "" msgid "Click :guilabel:`Insert in Spreadsheet` to add the pivot view into an editable spreadsheet format within the *Dashboards* app. If the Odoo *Documents* app is installed, the report can be inserted into a blank or existing spreadsheet, and exported." msgstr "" +#: ../../content/applications/sales/crm/performance/forecast_report.rst:3 +msgid "Forecast report" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:9 +msgid "The *Forecast* report in the *CRM* app allows users to view upcoming opportunities and build a forecast of potential sales. Opportunities are grouped by the month of their expected closing date, and can be dragged-and-dropped to adjust the deadline." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:13 +msgid "To access the *Forecast* report, navigate to :menuselection:`CRM app --> Reporting --> Forecast`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:16 +msgid "Navigate the forecast report" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:18 +msgid "The default :guilabel:`Forecast` report includes opportunities assigned to the current user's pipeline, and are expected to close within four months. It also shows opportunities without an assigned expected closing date. The opportunities are grouped by month in a :icon:`oi-view-kanban` :guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:-1 +msgid "A sample version of the Forecast report in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:28 +msgid "Expected closing date" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:30 +msgid "Opportunities are grouped by the date assigned in the *Expected Closing* field on an opportunity form. To change this date directly from the :guilabel:`Forecast` page, select the Kanban card for the desired opportunity, then click and drag the card to the desired column." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:35 +msgid "The default time frame for the forecast is *month*. This can be changed by clicking the |caret| next to the :guilabel:`Search...` bar at the top of the report. Under the :guilabel:`Group By` heading in the resulting drop-down menu, click :guilabel:`Expected Closing` to expand the list of available options, and select a desired amount of time from the list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:40 +msgid "After an opportunity is added to a new month, the *Expected Closing* field on the opportunity form is updated to the *last* date of the new month." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:44 +msgid "The *Expected Closing* field can also be manually updated on the opportunity card. To do that, click on the Kanban card for an opportunity on the :guilabel:`Forecast` page to open the opportunity's detail form. Click in the :guilabel:`Expected Closing` field, and use the calendar popover to select a new closing date." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:50 +msgid "Prorated revenue" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:52 +msgid "At the top of the column for each month on the :guilabel:`Forecast` reporting page, to the right of the progress bar, is a sum of the prorated revenue for that time frame." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:55 +msgid "The prorated revenue is calculated using the formula below:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:57 +msgid "\\text{Expected Revenue} \\times \\text{Probability} = \\text{Prorated Revenue}" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:61 +msgid "As opportunities are moved from one column to another, the column's revenue is automatically updated to reflect the change." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:65 +msgid "A forecast report for June includes two opportunities:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:67 +msgid "The first opportunity, `Global Solutions`, has an expected revenue of `$3,800`, and a probability of `90%`. This results in a prorated revenue of `$3,420`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:70 +msgid "The second opportunity, `Quote for 600 Chairs`, has an expected revenue of `$22,500`, and a probability of `20%`. This results in a prorated revenue of `$4,500`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:73 +msgid "The combined prorated revenue of the opportunities is `$7,920`, which is listed at the top of the column for the month." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:0 +msgid "An example of the prorated revenue for one month of the forecast report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:81 +msgid "For more information on how probability is assigned to opportunities, see :doc:`../track_leads/lead_scoring`" +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:87 +msgid "Click the :icon:`fa-area-chart` :guilabel:`(area chart)` icon to change to graph view. Then, click the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:-1 +msgid "A pie chart view of the Forecast report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:96 +msgid "Click the |pivot| to change to the pivot view, or the |list| to change to the list view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:99 +msgid "The :ref:`pivot view ` can be used to view and analyze data in a more in-depth manner. Multiple measures can be selected, and data can be viewed by month, and by opportunity stage." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:0 +msgid "A sample of the forecast report in the pivot view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/forecast_report.rst:108 +msgid "To save this report as a *favorite*, see :ref:`search/favorites`." +msgstr "" + #: ../../content/applications/sales/crm/performance/win_loss.rst:3 msgid "Pipeline Analysis" msgstr "" @@ -3397,6 +3511,34 @@ msgid "\\begin{equation}\n" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:33 +msgid "Breaking down the equation:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:35 +msgid "P(A|B) = The probability of a successful lead *in this case*" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:36 +msgid "P(A) = The overall probability of a lead being successful regardless of the conditions" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:37 +msgid "P(B|A) = The probability of this being the case given a lead is successful" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:38 +msgid "P(B) = The probability of this being the case" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 +msgid "The term *in this case* refers to the variables that can affect a lead being successful in Odoo. This can include variables such as the assigned Salesperson, the source of the lead, the language of the lead, and other historical and demographic data." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 +msgid "Which variables are considered in this calculation can be :ref:`configured ` to tailor the calculation to each business's needs." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:47 msgid "The probability of success of each opportunity is displayed on the opportunity form, and it updates automatically as the opportunity progresses through the CRM pipeline." msgstr "" @@ -3404,19 +3546,19 @@ msgstr "" msgid "The probability of success displayed on the opportunity form." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:54 msgid "When an opportunity moves to the next stage, its probability of success automatically increases according to the predictive lead scoring algorithm." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:46 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 msgid "Predictive lead scoring is always active in Odoo *CRM*. However, the variables used to calculate the probability of success can be customized in the settings." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 msgid "To customize the variables used by predictive lead scoring, go to :menuselection:`CRM --> Configuration --> Settings`. Under :guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update Probabilities` button." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:69 msgid "Then, click on the drop-down menu to choose which variables the predictive lead scoring feature will take into account." msgstr "" @@ -3424,63 +3566,63 @@ msgstr "" msgid "The Update Probabilities window in the Predictive Lead Scoring settings." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 msgid "Any number of the following variables can be activated:" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:78 msgid ":guilabel:`State`: the geographical state from which the opportunity originates" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:63 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 msgid ":guilabel:`Country`: the geographical country from which the opportunity originates" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:80 msgid ":guilabel:`Phone Quality`: whether or not a phone number is listed for the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:81 msgid ":guilabel:`Email Quality`: whether or not an email address is listed for the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:66 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 msgid ":guilabel:`Source`: the source of an opportunity (e.g. search engine, social media)" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:67 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:83 msgid ":guilabel:`Language`: the spoken language specified on the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 msgid ":guilabel:`Tags`: the tags placed on the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:71 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:87 msgid "The variables `Stage` and `Team` are always in effect. `Stage` refers to the CRM pipeline stage that an opportunity is in. `Team` refers to the sales team that is assigned to an opportunity. Predictive lead scoring *always* takes into account these two variables, regardless of which optional variables are selected." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 msgid "Next, click on the date field next to the option :guilabel:`Consider leads created as of the:` to select the date from which predictive lead scoring will begin its calculations." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:95 msgid "Lastly, click :guilabel:`Confirm` to save changes." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:98 msgid "Change the probability manually" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:100 msgid "An opportunity's probability of success can be changed manually on the opportunity form. Click on the probability number to edit it." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:88 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:104 msgid "Manually changing the probability removes the automatic probability updates for that opportunity. The probability will no longer update automatically as the opportunity moves through each stage of the pipeline." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 msgid "To reactivate automatic probability, click on the gear icon next to the probability percentage." msgstr "" @@ -3488,27 +3630,27 @@ msgstr "" msgid "The gear icon used to reactivate automatic probability on an opportunity form." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:99 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115 msgid "Assign leads based on probability" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:101 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:117 msgid "Odoo *CRM* can assign leads/opportunities to sales teams and salespeople based on specified rules. Create assignment rules based on the leads' probability of success to prioritize those that are more likely to result in deals." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:122 msgid "Configure rule-based assignment" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:124 msgid "To activate *rule-based assignment*, navigate to :menuselection:`CRM --> Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:127 msgid "The rule-based assignment feature can be set to run :guilabel:`Manually`, meaning an Odoo user must manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo will automatically trigger the assignment according to the chosen time period." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:131 msgid "To set up automatic lead assignment, select :guilabel:`Repeatedly` for the :guilabel:`Running` section. Then, customize how often Odoo will trigger the automatic assignment in the :guilabel:`Repeat every` section." msgstr "" @@ -3516,39 +3658,39 @@ msgstr "" msgid "The Rule-Based Assignment setting in CRM settings." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:123 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139 msgid "If rule-based assignment is set to run :guilabel:`Repeatedly`, the assignment can still be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings (or using the :guilabel:`Assign Leads` button on the sales team configuration page)." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:144 msgid "Configure assignment rules" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146 msgid "Next, configure the *assignment rules* for each sales team and/or salesperson. These rules determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM --> Configuration --> Sales Teams`, and select a sales team." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:150 msgid "On the sales team configuration form, under :guilabel:`Assignment Rules`, click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to determine lead assignment for this sales team. The rules can include anything that may be relevant for this company or team, and any number of rules can be added." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:155 msgid "Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :guilabel:`+` sign on the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to remove the line." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:159 msgid "To create an assignment rule based on an opportunity's probability of success, click on the far left drop-down menu of an assignment rule line, and select :guilabel:`Probability`." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:162 msgid "From the middle drop-down menu, select the desired equation symbol—most likely the symbol for *greater than*, *less than*, *greater than or equal to*, or *less than or equal to*." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:165 msgid "In the far right space, enter the desired number value of the probability. Finally, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:153 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:169 msgid "To configure an assignment rule such that a sales team receives leads that have a probability of success of 20% or greater, create a :guilabel:`Domain` line that reads: `Probability >= 20`." msgstr "" @@ -3556,15 +3698,15 @@ msgstr "" msgid "Sales team domain set to probability greater than or equal to twenty percent." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:176 msgid "Separate assignment rules can also be configured for individual team members. From the sales team configuration page, click on a team member in the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:180 msgid "If automatic lead assignment is configured in the settings, both the sales team and individual team members have the option to :guilabel:`Skip auto assignment`. Check this box to omit a particular sales team or salesperson from being assigned leads automatically by Odoo's rule-based assignment feature. If :guilabel:`Skip auto assignment` is activated, the sales team or salesperson can still be assigned leads manually." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:186 msgid "To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top of the sales team configuration page. This will assign any leads that are currently unassigned and match this team's specified domain." msgstr "" @@ -3817,6 +3959,170 @@ msgstr "" msgid "In the drop-down menu, rename the report from the default `Pipeline` label to `Quality Leads`, and click :guilabel:`Save`." msgstr "" +#: ../../content/applications/sales/crm/track_leads/resellers.rst:3 +msgid "Resellers" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:5 +msgid "Within Odoo's *CRM* app, leads can be forwarded to resellers (or partners). Leads can be manually assigned, or automatically assigned, based on the resellers' designated *level* and location." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:11 +msgid "To utilize the reseller features, the *Resellers* module first needs to be installed. Navigate to the :menuselection:`Apps application`, and remove the :guilabel:`Apps` filter from the :guilabel:`Search...` bar. Then, search for `Resellers`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:-1 +msgid "The resellers module in Odoo." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:19 +msgid "Click :guilabel:`Activate` on the :guilabel:`Resellers` module card that appears. Doing so installs the module, and returns to the main Odoo dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:22 +msgid "After the module is installed, navigate to the :menuselection:`CRM app`. Under the :menuselection:`Configuration` menu is a new section, titled :guilabel:`Resellers`, with three options beneath it: :guilabel:`Partner Levels`, :guilabel:`Partner Activations`, and :guilabel:`Commission Plans`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:30 +msgid "Partner levels" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:32 +msgid "Partner *levels* are used to differentiate between various resellers. To view the partner levels, navigate to :menuselection:`CRM app --> Configuration --> Resellers: Partner Levels`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:35 +msgid "On the :guilabel:`Partner Levels` page that appears, there are three default levels:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:37 +msgid ":guilabel:`Gold`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:38 +msgid ":guilabel:`Silver`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:39 +msgid ":guilabel:`Bronze`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:41 +msgid "New levels can be added, as needed, by clicking :guilabel:`New`, and filling out the resulting level form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:44 +msgid "Existing levels can also be edited and renamed, if desired, as well. To modify a level, select it from the list, and proceed to make any desired changes from the level form page that appears." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:47 +msgid "Level weight is used to decide the probability a partner to be assigned a lead or opportunity. On the level form, assign a numerical value (greater than zero) to the :guilabel:`Level Weight` field. If the weight is zero, no leads are assigned." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:52 +msgid "*Level Weight* can be assigned on an individual contact record. The weight assigned on the individual record overwrites the default weight assigned on the level configuration form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:58 +msgid "Partner activations" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:60 +msgid "Partner *activations* are used to identify the status of a partner. Activations are assigned on an individual contact record, and can be used to group or filter the *Partnership Analysis* report (:menuselection:`CRM app --> Reporting --> Partnerships`)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:64 +msgid "To view the partner levels, navigate to :menuselection:`CRM app --> Configuration --> Partner Activations`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:67 +msgid "Three activation types are created by default in the *CRM* app:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:69 +msgid ":guilabel:`Fully Operational`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:70 +msgid ":guilabel:`Ramp-up`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:71 +msgid ":guilabel:`First Contact`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:73 +msgid "New partner activations can be added, as needed, by clicking :guilabel:`New`, and entering a :guilabel:`Name` on the new line that appears. Then, select the desired status in the :guilabel:`Active` column." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:77 +msgid "Existing partner activations can also be edited and renamed, if desired. To rename a status, click the :guilabel:`Name` field of a desired level, and enter a new name." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:80 +msgid "To change the active status of an activation, slide the toggle in the :guilabel:`Active` column of the desired activation to the *inactive* position." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:87 +msgid "The list of default partner activations in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:87 +msgid "The list of default Partner Activations in the CRM app. The toggle for First Contact is in the inactive position, while the rest are active." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:91 +msgid "Partner assignments" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:93 +msgid "After :ref:`partner levels ` and :ref:`partner activations ` configured." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:96 +msgid "To update an individual partner record, navigate to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for the desired partner to open the customer record." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:99 +msgid "On the customer record, click the :guilabel:`Partner Assignment` tab." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:101 +msgid "Click the :guilabel:`Partner Level` field, and select an option from the drop-down menu to assign a level. Click the :guilabel:`Activation` field, and select a partner activation type from the drop-down list, if desired. Then, click the :guilabel:`Level Weight` field to assign a different level weight, if necessary." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:107 +msgid "Publish partners" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:109 +msgid "With the Odoo *Website* and *Resellers* apps installed, a new webpage (`/partners`) is created to display a list of all active partners from the *CRM* app." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:112 +msgid "Next, return to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a partner. From that partner's contact form, click the :guilabel:`Go to Website` smart button at the top of the page to open that partner's webpage." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:116 +msgid "Next, click :guilabel:`Edit` at the top-right of the partner's webpage, and use the :doc:`building blocks <../../../websites/website/web_design/building_blocks>` to add any additional design elements, or information about the partner." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:121 +msgid "A company summary is a useful addition to this page." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:123 +msgid "After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position, if needed." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:126 +msgid "Repeat these steps for all partners." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/resellers.rst:-1 +msgid "An example of the partners webpage, displaying available partners by level and location." +msgstr "" + #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:3 msgid "Unattended leads report" msgstr "" @@ -4377,62 +4683,58 @@ msgid "Epson TM-L90-i" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:35 -msgid "Epson TM-T20II-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:36 msgid "Epson TM-T70-i" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:37 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:36 msgid "Epson TM-T82II-i" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:38 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:37 msgid "Epson TM-T83II-i" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:39 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:38 msgid "Epson TM-U220-i" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:40 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:39 msgid "Epson TM-m10" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:41 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:40 msgid "Epson TM-P20 (Wi-Fi® model)" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:42 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:41 msgid "Epson TM-P60II (Receipt: Wi-Fi® model)" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:43 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:42 msgid "Epson TM-P60II (Peeler: Wi-Fi® model)" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:44 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:43 msgid "Epson TM-P80 (Wi-Fi® model)" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:47 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:46 msgid "ePOS printers with IoT Box integration" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:49 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:48 msgid "The following printers require an :doc:`IoT Box ` to be compatible with Odoo:" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:52 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:51 msgid "Epson TM-T20 family (incompatible ePOS software)" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:53 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:52 msgid "Epson TM-T88 family (incompatible ePOS software)" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:54 +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:53 msgid "Epson TM-U220 family (incompatible ePOS software)" msgstr "" @@ -5068,6 +5370,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:41 #: ../../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/worldline.rst:72 msgid "Configure the payment method" msgstr "" @@ -5084,6 +5387,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:68 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:93 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:41 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:96 msgid "Pay with a payment terminal" msgstr "" @@ -5450,28 +5754,28 @@ msgstr "" msgid "Vantiv card readers should be purchased exclusively from Vantiv, as certain Vantiv terminals bought on Amazon do not include the correct encryption needed to be used with an Odoo database." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 -msgid "Configure the Payment Method" -msgstr "" - #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22 -msgid "First, go in the general settings of the POS app, and activate the Vantiv setting." +msgid "Enable the payment terminal in the :guilabel:`Payment Terminals` section :ref:`of the application settings `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28 -msgid "Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:25 +msgid "Then, go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Vantiv` in the :guilabel:`Use a Payment Terminal` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:29 +msgid "Type the name you want to give to your :guilabel:`Vantiv Credentials` and click :guilabel:`Create and edit`. Enter your :guilabel:`Merchant ID` and :guilabel:`Merchant Password`, then click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:-1 +msgid "Vantiv payment method" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36 -msgid "To create new Vantiv credentials, fill in your merchant ID and password, then save. Make sure the credentials you just created are selected, then save the payment method." +msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings ` and add the payment method under the :guilabel:`Payment` section." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44 -msgid "Pay with a Payment Terminal" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46 -msgid "In your PoS interface, at the moment of the payment, select your Vantiv payment method and… that’s all." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:43 +msgid "When processing a payment, select the related payment method. Check the amount and click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3 @@ -5675,6 +5979,7 @@ msgid "And then scan the discount tag. The discount will be applied and you can msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:321 msgid "Discounts" msgstr "" @@ -6178,7 +6483,7 @@ msgid "Setup form of a multiple prices pricelist" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:321 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:359 msgid "Advanced price rules" msgstr "" @@ -6310,19 +6615,19 @@ msgstr "" msgid "POS receipt" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:21 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:22 msgid ":doc:`restaurant/bill_printing`" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:22 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:23 msgid ":doc:`configuration/epos_printers`" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:25 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26 msgid "Reprint a receipt" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:27 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:28 msgid "From the POS interface, click :guilabel:`Orders`, open the dropdown selection menu next to the search bar, and change the default :guilabel:`All active orders` filter to :guilabel:`Paid`. Then, select the corresponding order and click :guilabel:`Print Receipt`." msgstr "" @@ -6330,23 +6635,23 @@ msgstr "" msgid "Print receipt button from the backend" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:35 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:36 msgid "You can filter the list of orders using the search bar. Type in your reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or :guilabel:`Customer`." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:41 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42 msgid "Invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:43 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:44 msgid "Point of Sale allows you to issue and print invoices for :ref:`registered customers ` upon payment and retrieve all past invoiced orders." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:47 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:48 msgid "An invoice created in a POS creates an entry into the corresponding :ref:`accounting journal `, previously :ref:`set up `." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:55 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:56 msgid "To define what journals will be used for a specific POS, go to the :ref:`POS' settings ` and scroll down to the accounting section. Then, you can determine the accounting journals used by default for orders and invoices in the :guilabel:`Default Journals` section." msgstr "" @@ -6354,35 +6659,35 @@ msgstr "" msgid "accounting section in the POS settings" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:64 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 msgid "Invoice a customer" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:66 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:67 msgid "Upon processing a payment, click :guilabel:`Invoice` underneath the customer's name to issue an invoice for that order." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:69 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:70 msgid "Select the payment method and click :guilabel:`Validate`. The **invoice** is automatically issued and ready to be downloaded and/or printed." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:73 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:74 msgid "To be able to issue an invoice, a :ref:`customer ` must be selected." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:76 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:77 msgid "Retrieve invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:78 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79 msgid "To retrieve invoices from the **POS dashboard**," msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:80 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81 msgid "access all orders made through your POS by going to :menuselection:`Point of Sale --> Orders --> Orders`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:82 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:83 msgid "to access an order's invoice, open the **order form** by selecting the order, then click :guilabel:`Invoice`." msgstr "" @@ -6390,19 +6695,19 @@ msgstr "" msgid "invoice smart button from an order form" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:89 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:90 msgid "**Invoiced orders** can be identified by the :guilabel:`Invoiced` status in the :guilabel:`Status` column." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:91 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:92 msgid "You can filter the list of orders to invoiced orders by clicking :guilabel:`Filters` and :guilabel:`Invoiced`." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:95 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:96 msgid "QR codes to generate invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:97 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:98 msgid "Customers can also request an invoice by scanning the **QR code** printed on their receipt. Upon scanning, they must fill in a form with their billing information and click :guilabel:`Get my invoice`. On the one hand, doing so generates an invoice available for download. On the other hand, the order status goes from :guilabel:`Paid` or :guilabel:`Posted` to :guilabel:`Invoiced` in the Odoo backend." msgstr "" @@ -6410,7 +6715,7 @@ msgstr "" msgid "order status change" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:106 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:107 msgid "To use this feature, you have to enable QR codes on receipts by going to :menuselection:`Point of Sale --> Configuration --> Settings`. Then, select the POS in the :guilabel:`Point of Sale` field, scroll down to the :guilabel:`Bills & Receipts` section and enable :guilabel:`Use QR code on ticket`." msgstr "" @@ -9237,7 +9542,7 @@ msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:97 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:260 -#: ../../content/applications/sales/sales/invoicing/expense.rst:226 +#: ../../content/applications/sales/sales/invoicing/expense.rst:255 #: ../../content/applications/sales/sales/invoicing/milestone.rst:238 #: ../../content/applications/sales/sales/invoicing/proforma.rst:71 #: ../../content/applications/sales/sales/invoicing/time_materials.rst:166 @@ -9626,18 +9931,50 @@ msgid "Upon clicking :guilabel:`Post Journal Entries`, that button disappears, a msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:159 -msgid "Reinvoice expense" +msgid "By default, the :guilabel:`Customer to Reinvoice` field is enabled for the :guilabel:`[TRANS & ACC] Travel & Accommodation`, :guilabel:`[COMM] Communication`, :guilabel:`[FOOD] Meals`, and :guilabel:`[MIL] Mileage` expense category." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:161 -msgid "With those steps completed, it's time to return to the sales order to complete the reinvoice of the expense to the customer." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/expense.rst:164 -msgid "To do that, navigate to :menuselection:`main Odoo dashboard --> Sales app`, and select the appropriate sales order that should be reinvoiced for the expense." +#: ../../content/applications/sales/sales/invoicing/expense.rst:163 +msgid "It should be noted that **not** all of the default expense categories that come installed with the *Expenses* application have reinvoicing policies activated. The setting may have to be manually activated." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:167 +msgid "To do that, navigate to :menuselection:`Expenses app --> Configuration --> Expenses Categories` to view a list of all expense categories in the database." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:170 +msgid "Look in the :guilabel:`Re-Invoice Expenses` column to see which selections have been made for each expense category." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:0 +msgid "The Re-Invoice Expenses column on the Expense Categories page in the Odoo Expenses app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:177 +msgid "To modify an expense category, click the :icon:`fa-arrow-right` :guilabel:`(right arrow)` in the :guilabel:`Category` field, to reveal that specific expense from." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:180 +msgid "Under the :guilabel:`Invoicing` section, in the :guilabel:`Re-Invoice Expenses` field, select either :guilabel:`At cost` or :guilabel:`Sales price`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:0 +msgid "The Re-Invoice Expenses field on an Expense Category form in the Odoo Expenses app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:188 +msgid "Reinvoice expense" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:190 +msgid "With those steps completed, it's time to return to the sales order to complete the reinvoice of the expense to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:193 +msgid "To do that, navigate to :menuselection:`main Odoo dashboard --> Sales app`, and select the appropriate sales order that should be reinvoiced for the expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:196 msgid "On the sales form, the newly-configured expense is now in the :guilabel:`Order Lines` tab, with its :guilabel:`Delivered` column filled in, and ready to be invoiced." msgstr "" @@ -9645,7 +9982,7 @@ msgstr "" msgid "A sales order with the configured expense ready to be invoiced in the Order Lines tab." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:174 +#: ../../content/applications/sales/sales/invoicing/expense.rst:203 msgid "After confirming the details of the expense, click :guilabel:`Create Invoice` at the top of the sales order. When clicked, a :guilabel:`Create invoices` pop-up window appears." msgstr "" @@ -9653,11 +9990,11 @@ msgstr "" msgid "A create invoices pop-up window that appears when the Create Invoice is clicked." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:181 +#: ../../content/applications/sales/sales/invoicing/expense.rst:210 msgid "From this pop-up window, leave the :guilabel:`Create Invoice` field on the default :guilabel:`Regular invoice` option, and click :guilabel:`Create Draft Invoice`." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:184 +#: ../../content/applications/sales/sales/invoicing/expense.rst:213 msgid "Doing so reveals a :guilabel:`Customer Invoice Draft` showing *only* the expense in the :guilabel:`Invoice Lines` tab." msgstr "" @@ -9665,19 +10002,19 @@ msgstr "" msgid "A customer invoice draft with the expense in the Invoice Lines tab of the form." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:191 +#: ../../content/applications/sales/sales/invoicing/expense.rst:220 msgid "If all the information related to the expense is correct, click :guilabel:`Confirm` to confirm the invoice. Doing so moves the status of the invoice from :guilabel:`Draft` to :guilabel:`Posted`." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:194 +#: ../../content/applications/sales/sales/invoicing/expense.rst:223 msgid "To send the invoice to the customer, click :guilabel:`Send \\& Print`. Doing so reveals a :guilabel:`Send` pop-up window, with a preconfigured message and PDF invoice in the body of the message. The message can be reviewed and modified, if needed." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:198 +#: ../../content/applications/sales/sales/invoicing/expense.rst:227 msgid "Once ready, click :guilabel:`Send \\& Print` to send the invoice to the customer. When clicked, the pop-up window disappears, and Odoo sends the message/invoice to the customer. Additionally, a PDF of the invoice is automatically downloaded for record-keeping and/or printing purposes." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:202 +#: ../../content/applications/sales/sales/invoicing/expense.rst:231 msgid "Back on the :guilabel:`Customer Invoice`, click the :guilabel:`Register Payment` button when the customer pays for the invoiced expense." msgstr "" @@ -9685,7 +10022,7 @@ msgstr "" msgid "A customer invoice with the register payment button ready to be clicked." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:209 +#: ../../content/applications/sales/sales/invoicing/expense.rst:238 msgid "When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment` pop-up window appears. In this pop-up window, the necessary fields are auto-populated with the correct information. After reviewing the information, click :guilabel:`Create Payment`." msgstr "" @@ -9694,16 +10031,16 @@ msgstr "" msgid "A register payment pop-up window on a customer invoice in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:217 +#: ../../content/applications/sales/sales/invoicing/expense.rst:246 msgid "Once :guilabel:`Create Payment` is clicked, the pop-up window disappears, and a green :guilabel:`In Payment` banner is in the upper-right corner of the invoice, signifying this invoice is paid for in full. Thus, completing the workflow." msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:227 +#: ../../content/applications/sales/sales/invoicing/expense.rst:256 #: ../../content/applications/sales/sales/invoicing/milestone.rst:236 msgid ":doc:`time_materials`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/expense.rst:228 +#: ../../content/applications/sales/sales/invoicing/expense.rst:257 msgid ":doc:`milestone`" msgstr "" @@ -11329,7 +11666,7 @@ msgid "After activating and saving the :guilabel:`Pricelists` feature, the :guil msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:337 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:375 msgid "Either option reveals the :guilabel:`Pricelists` page, in which pricelists can be created and/or modified at any time." msgstr "" @@ -11622,22 +11959,54 @@ msgid "When a price rule/pricelist is added to a product via the :guilabel:`Extr msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 +msgid "The *Discounts* feature allows the ability to set a discount or increase the price on *individual items* in a sales order. This is calculated as a percentage of that product's sales price." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:326 +msgid "To access discounts, navigate to the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click the :guilabel:`Discounts` checkbox, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "Click the checkbox labeled Discounts to activate Discounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 +msgid "After the setting has been activated, navigate to the desired quotation by going to :menuselection:`Sales app --> Orders --> Quotations` at the top of the page. Once there, click on the desired quote from the list." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:338 +msgid "In the order lines section of the quotation form, a new column heading will appear labeled :guilabel:`Disc.%`. This column is used to set discounts on individual line items. Enter the desired discount for each product line and the new price will automatically be calculated in the quote :guilabel:`Total` at the bottom of the page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:344 +msgid "A discount can also be added directly to a sales order in the same way. Navigate to :menuselection:`Sales app --> Orders --> Orders`, click on the desired sales order, and add the discount to :guilabel:`Disc.%` as described above." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "The Dis.% heading will now appear in Order Lines." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:353 +msgid "Positive values for :guilabel:`Disc.%` will apply a *discount*, while negative values can be used to *increase* the price." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:361 msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:327 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:365 msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:332 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:370 msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:340 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:378 msgid "From the :guilabel:`Pricelists` page, select a desired pricelist to modify, or create a new pricelist by clicking the :guilabel:`New` button." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:381 msgid "On the pricelist form, under the :guilabel:`Price Rules` tab, click :guilabel:`Add a line` to add an advanced price rule. Doing so reveals a :guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule is configured." msgstr "" @@ -11645,35 +12014,35 @@ msgstr "" msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:390 msgid "Price computation" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:392 msgid "On this form, first choose one of the three :guilabel:`Computation` options:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:356 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:394 msgid ":guilabel:`Fixed Price`: the price computation is based on a fixed price." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:357 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:395 msgid ":guilabel:`Discount`: the price computation is based on a discount." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:396 msgid ":guilabel:`Formula`: the price computation is based on a formula." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:361 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:399 msgid "Each :guilabel:`Computation` option reveals its own computation-specific fields on the form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:363 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:401 msgid "If :guilabel:`Fixed Price` is selected, enter the desired price in the :guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, enter the desired discount percentage in the :guilabel:`Discount` field that appears." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:367 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:405 msgid "If :guilabel:`Formula` is selected, a number of configurable options appear." msgstr "" @@ -11681,15 +12050,15 @@ msgstr "" msgid "The various formula computation options present in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:373 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 msgid "To configure the :guilabel:`Formula` computation option, start by selecting an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the advanced price rule formula will be based on." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:377 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:415 msgid "Next, in the :guilabel:`Discount` field, determine how much of a discount should be applied. It should be noted that a mark-up can be applied by setting a negative discount in this field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:381 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:419 msgid "To formulate a 100% markup (or 2 times the cost of the product), with a $5 minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the :guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is often seen in retail situations." msgstr "" @@ -11697,27 +12066,27 @@ msgstr "" msgid "How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:389 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:427 msgid "Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or subtract) to the amount calculated with the discount. After that, enter a desired figure in the :guilabel:`Rounding Method` field. The rounding method sets the price so that it is a multiple of the value in the field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:394 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:432 msgid "Rounding is applied *after* the discount and *before* the surcharge." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:435 msgid "To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10` and the :guilabel:`Extra Fee` to `-0.01`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:400 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 msgid "Lastly, specify the minimum amount of margin over the base price in the :guilabel:`Margins` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:402 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:440 msgid "Once all formula-related configurations are complete, Odoo provides an example of the formula in a blue block to the right of the configurations." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:444 msgid "To apply 20% discounts, with prices rounded up to 9.99, set the :guilabel:`Based on` field to :guilabel:`Sales Price`, the :guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to `-0.01`, and the :guilabel:`Rounding Method` field to `10`." msgstr "" @@ -11725,55 +12094,55 @@ msgstr "" msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:415 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:453 msgid "Conditions" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:455 msgid "At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the :guilabel:`Conditions` section." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:458 msgid "Here, start by selecting one of the options in the :guilabel:`Apply On` field:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:422 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:460 msgid ":guilabel:`All Products`: the advanced pricelist rule will be applied to all products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:423 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:461 msgid ":guilabel:`Product Category`: the advanced pricelist rule will be applied to a specific category of products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:425 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:463 msgid ":guilabel:`Product`: the advanced pricelist rule will be applied to a specific product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:426 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:464 msgid ":guilabel:`Product Variant`: the advanced pricelist rule will be applied to a specific product variant." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:429 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:467 msgid "If any of those options, apart from :guilabel:`All Products`, are selected, a new option-specific field appears, in which the specific :guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product Variant` must be chosen." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:471 msgid "Then, select a minimum quantity to be applied to the advanced pricelist rule in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for the pricelist item validation in the :guilabel:`Validity` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:475 msgid "Once all configurations are complete, either click :guilabel:`Save & Close` to save the advanced pricelist rule, or click :guilabel:`Save & New` to immediately create another advanced pricelist rule on a fresh form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:442 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:480 msgid "If a price rule is set for a particular product, and another one for its product category, Odoo takes the rule of the product itself." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:446 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:484 msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:447 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:485 msgid ":doc:`/applications/websites/ecommerce/managing_products/price_management`" msgstr "" @@ -12052,7 +12421,7 @@ msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:220 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:181 msgid "Product variants" msgstr "" @@ -12353,10 +12722,10 @@ msgid "Before product variants can be set up, attributes **must** be created. To msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:57 -msgid "The order of attributes on the :guilabel:`Attributes` page dictates how they appear on the :guilabel:`Product Configurator`, :guilabel:`Point of Sale` dashboard, and :guilabel:`eCommerce` pages." +msgid "The order of attributes on the :guilabel:`Attributes` page dictates how they appear on the *Product Configurator*, *Point of Sale* dashboard, and *eCommerce* pages." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:61 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:60 msgid "To create a new attribute from the :guilabel:`Attributes` page, click :guilabel:`New`. Doing so reveals a blank attributes form that can be customized and configured in a number of ways." msgstr "" @@ -12364,115 +12733,123 @@ msgstr "" msgid "A blank attribute creation form in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:68 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:67 msgid "First, create an :guilabel:`Attribute Name`, such as `Color` or `Size`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:70 -msgid "Next, in the optional :guilabel:`Category` field, select a category from a drop-down menu to group similar attributes under the same section for added specificity and organization." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:69 +msgid "Next, select one of the options from the :guilabel:`Display Type` field. The :guilabel:`Display Type` determines how this product is shown on the online store, *Point of Sale* dashboard, and *Product Configurator*." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:74 -msgid "To view the details related to the attribute category selected, click the internal link :guilabel:`➡️ (arrow)` icon to the far-right of the :guilabel:`Category` field. Doing so reveals that attribute category's detail form." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 -msgid "A standard attribute category detail page accessible via its internal link arrow icon." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:82 -msgid "Here, the :guilabel:`Category Name` and :guilabel:`Sequence` is displayed at the top. Followed by :guilabel:`Related Attributes` associated with the category. These attributes can be dragged-and-dropped into a desirable order of priority." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:86 -msgid "Attributes can be directly added to the category, as well, by clicking :guilabel:`Add a line`." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:89 -msgid "To create an attribute category directly from this field, start typing the name of the new category, then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:93 -msgid "Clicking :guilabel:`Create` creates the category, which can be modified later. Clicking :guilabel:`Create and edit...` creates the category and reveals a :guilabel:`Create Category` pop-up window, in which the new attribute category can be configured and customized." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:97 -msgid "Beneath the :guilabel:`Category` field are the :guilabel:`Display Type` options. The :guilabel:`Display Type` determines how this product is shown on the online store, :guilabel:`Point of Sale` dashboard, and :guilabel:`Product Configurator`." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:101 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:73 msgid "The :guilabel:`Display Type` options are:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:103 -msgid ":guilabel:`Radio`: options appear in a bullet-style list on the product page of the online store." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:104 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:75 msgid ":guilabel:`Pills`: options appear as selectable buttons on the product page of the online store." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:105 -msgid ":guilabel:`Select`: options appear in a drop-down menu on the product page of the online store." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:76 +msgid ":guilabel:`Color`: options appear as small, colored squares, which reflect any HTML color codes" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:106 -msgid ":guilabel:`Color`: options appear as small, colored squares, which reflect any HTML color codes set, on the product page of the online store." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:77 +msgid ":guilabel:`Radio`: options appear in a bullet-style list on the product page of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:78 +msgid ":guilabel:`Select`: options appear in a drop-down menu on the product page of the online store. set, on the product page of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:80 +msgid ":guilabel:`Multi-checkbox (option)`: options appear as selectable checkboxes on the product page of the online store." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 msgid "Display Types on Product Configurator on the online store in Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:113 -msgid "The :guilabel:`Variants Creation Mode` field informs Odoo when to automatically create a new variant once an attribute is added to a product." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:87 +msgid "The :guilabel:`Variant Creation Mode` field informs Odoo when to automatically create a new variant once an attribute is added to a product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:116 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:91 +msgid "The :guilabel:`Variant Creation Mode` field **must** be set to :guilabel:`Never (option)` in order for the :guilabel:`Multi-checkbox (option)` to work properly as the :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:95 msgid ":guilabel:`Instantly`: creates all possible variants as soon as attributes and values are added to a product template." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:118 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:97 msgid ":guilabel:`Dynamically`: creates variants **only** when corresponding attributes and values are added to a sales order." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:120 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:99 msgid ":guilabel:`Never (option)`: never automatically creates variants." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:123 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:102 msgid "Once added to a product, an attribute's :guilabel:`Variants Creation Mode` cannot be edited." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:125 -msgid "Lastly, the :guilabel:`eCommerce Filter Visibility` field determines whether these attribute options are visible to the customer on the front-end, as they shop on the online store." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:104 +msgid "The :guilabel:`eCommerce Filter Visibility` field determines whether or not these attribute options are visible to the customer on the front-end, as they shop on the online store." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:128 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:107 msgid ":guilabel:`Visible`: the attribute values are visible to customers on the front-end." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:129 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:108 msgid ":guilabel:`Hidden`: the attribute values are hidden from customers on the front-end." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:132 -msgid "Attribute values" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:110 +msgid "Lastly, in the optional :guilabel:`eCommerce Category` field, select a category from a drop-down menu to group similar attributes under the same section for added specificity and organization." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:114 +msgid "To view the details related to the attribute category selected, click the internal link :icon:`fa-arrow-right` :guilabel:`(right arrow)` icon to the far-right of the :guilabel:`eCommerce Category` field, once an option has been selected. Doing so reveals that attribute category's detail form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "A standard attribute category detail page accessible via its internal link arrow icon." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:123 +msgid "Here, the :guilabel:`Category Name` and :guilabel:`Sequence` is displayed at the top. Followed by :guilabel:`Related Attributes` associated with the category. These attributes can be dragged-and-dropped into a desirable order of priority." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:127 +msgid "Attributes can be directly added to the category, as well, by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:130 +msgid "To create an attribute category directly from this field, start typing the name of the new category, then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:134 -msgid "Attribute values should be added to the :guilabel:`Attribute Values` tab. Values can be added to an attribute at any time, if needed." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 -msgid "To add a value, click :guilabel:`Add a line` in the :guilabel:`Attribute Values` tab." +msgid "Clicking :guilabel:`Create` creates the category, which can be modified later. Clicking :guilabel:`Create and edit...` creates the category and reveals a :guilabel:`Create Category` pop-up window, in which the new attribute category can be configured and customized." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:139 -msgid "Then, enter the name of the value in the :guilabel:`Value` column. Next, check the box in the :guilabel:`Is custom value` column, if the value is custom (i.e. the customer gets to provide unique specifications that are specific to this particular value)." +msgid "Attribute values" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:141 +msgid "Attribute values should be added to the :guilabel:`Attribute Values` tab. Values can be added to an attribute at any time, if needed." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:144 +msgid "To add a value, click :guilabel:`Add a line` in the :guilabel:`Attribute Values` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:146 +msgid "Then, enter the name of the value in the :guilabel:`Value` column. Next, check the box in the :guilabel:`Is custom value` column, if the value is custom (i.e. the customer gets to provide unique specifications that are specific to this particular value)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:151 msgid "If the :guilabel:`Display Type` - :guilabel:`Color` option is selected, the option to add an HTML color code will appear to the far-right of the value line, to make it easier for salespeople and customers to know exactly what color option they're choosing." msgstr "" @@ -12480,7 +12857,7 @@ msgstr "" msgid "Attribute values tab when add a line is clicked, showing the custom columns." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:152 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:159 msgid "To choose a color, click the blank circle in the :guilabel:`Color` column, which reveals an HTML color selector pop-up window." msgstr "" @@ -12488,27 +12865,27 @@ msgstr "" msgid "Selecting a color from the HTML color pop-up window that appears on attribute form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:159 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:166 msgid "In this pop-up window, select a specific color by dragging the color slider to a particular hue, and clicking on the color portion directly on the color gradient window." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:162 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169 msgid "Or, choose a specific color by clicking the *dropper* icon, and selecting a desired color that's currently clickable on the screen." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:166 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:173 msgid "Attributes can also be created directly from the product template by adding a new line and typing the name into the :guilabel:`Variants` tab." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:176 msgid "Once an attribute is added to a product, that product is listed and accessible, via the attribute's :guilabel:`Related Products` smart button. That button lists every product in the database currently using that attribute." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:176 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:183 msgid "Once an attribute is created, use the attribute (and its values) to create a product variant. To do that, go to :menuselection:`Sales app --> Products --> Products`, and select an existing product to view that desired product's form. Or, click :guilabel:`Create` to create a new product, to which a product variant can be added." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:181 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:188 msgid "On the product form, click the :guilabel:`Attributes \\& Variants` tab to view, manage, and modify attributes and values for the product." msgstr "" @@ -12516,35 +12893,35 @@ msgstr "" msgid "The attributes and values tab on a typical product form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:188 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:195 msgid "To add an attribute to a product, and subsequent attribute values, click :guilabel:`Add a line` in the :guilabel:`Attributes \\& Variants` tab. Then, choose the desired attribute from the drop-down menu that appears." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:193 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:200 msgid "Attributes can be created directly from the :guilabel:`Attributes \\& Variants` tab of a product form. To do that, start typing the name of the new attribute in the blank field, and select either :guilabel:`Create` or :guilabel:`Create and edit...` from the mini drop-down menu that appears." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:198 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:205 msgid "Clicking :guilabel:`Create` creates the attribute, which can be customized later. Clicking :guilabel:`Create and edit...` creates the attribute, and a :guilabel:`Create Attribute` pop-up form appears. In the pop-up form, proceed to modify the attribute in a number of ways." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:202 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:209 msgid "Once an attribute is selected in the :guilabel:`Attribute` column, proceed to select the specific attribute values to apply to the product, via the drop-down menu available in the :guilabel:`Values` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:207 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:214 msgid "There is no limit to how many values can be added." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:210 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:217 msgid "Similar product variant creation processes are accessible through the Purchase, Inventory, and eCommerce applications." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:214 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:221 msgid "Configure variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:216 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:223 msgid "To the far-right of the attribute line is a :guilabel:`Configure` button. When clicked, Odoo reveals a separate page showcasing those specific :guilabel:`Product Variant Values`." msgstr "" @@ -12552,15 +12929,15 @@ msgstr "" msgid "The Product Variant Values page accessible via the Configure button on a product form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:223 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:230 msgid "Here, the specific :guilabel:`Value` name, :guilabel:`HTML Color Index` (if applicable), and :guilabel:`Value Price Extra` are viewable." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:227 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:234 msgid "The :guilabel:`Value Price Extra` represents the increase in the sales price if the attribute is selected." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:230 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:237 msgid "When a value is clicked on the :guilabel:`Product Variant Values` page, Odoo reveals a separate page, detailing that value's related details." msgstr "" @@ -12568,19 +12945,19 @@ msgstr "" msgid "A Product Variant Values page accessible via the Product Variants Values general page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:237 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:244 msgid "On the specific product variant detail page, the :guilabel:`Value` and :guilabel:`Value Price Extra` fields can be found, along with an :guilabel:`Exclude for` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:240 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:247 msgid "In the :guilabel:`Exclude for` field, different :guilabel:`Product Templates` and specific :guilabel:`Attribute Values` can be added. When added, this specific attribute value will be excluded from those specific products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:245 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:252 msgid "Variants smart button" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:247 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:254 msgid "When a product has attributes and variants configured in its :guilabel:`Attributes \\& Variants` tab, a :guilabel:`Variants` smart button appears at the top of the product form. The :guilabel:`Variants` smart button indicates how many variants are currently configured for that specific product." msgstr "" @@ -12588,7 +12965,7 @@ msgstr "" msgid "The variants smart button at the top of the product form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:255 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:262 msgid "When the :guilabel:`Variants` smart button is clicked, Odoo reveals a separate page showcasing all the specific product variant combinations configured for that specific product." msgstr "" @@ -12596,39 +12973,39 @@ msgstr "" msgid "The variants page accessible via the variants smart button on the product form in Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:263 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:270 msgid "Impact of variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:265 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:272 msgid "In addition to offering more detailed product options to customers, product variants have their own impacts that can be taken advantage of throughout the Odoo database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:268 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:275 msgid ":guilabel:`Barcode`: barcodes are associated with each variant, instead of the product template. Each individual variant can have its own unique barcode/SKU." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:270 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:277 msgid ":guilabel:`Price`: every product variant has its own public price, which is the sum of the product template price *and* any extra charges for particular attributes." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:274 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:281 msgid "A red shirt's sales price is $23 -- because the shirt's template price is $20, plus an additional $3 for the red color variant. Pricelist rules can be configured to apply to the product template, or to the variant." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:278 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:285 msgid ":guilabel:`Inventory`: inventory is counted for each individual product variant. On the product template form, the inventory reflects the sum of all variants, but the actual inventory is computed by individual variants." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:281 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:288 msgid ":guilabel:`Picture`: each product variant can have its own specific picture." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:284 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:291 msgid "Changes to the product template automatically apply to every variant of that product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:287 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:294 msgid ":doc:`import`" msgstr "" @@ -13045,7 +13422,7 @@ msgid ":doc:`quote_template`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:245 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:249 msgid ":doc:`get_signature_to_validate`" msgstr "" @@ -13134,7 +13511,7 @@ msgid "Then, when the quotation is paid and confirmed, a delivery order is autom msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:246 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:250 msgid ":doc:`get_paid_to_validate`" msgstr "" @@ -13147,7 +13524,7 @@ msgid "The use of optional products is a marketing strategy that involves the cr msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:9 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:162 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:166 msgid "For instance, if a customer wants to buy a car, they have the choice to order massaging seats, as well, or ignore the offer and simply buy the car. Presenting the choice to purchase optional products enhances the customer experience." msgstr "" @@ -13168,7 +13545,7 @@ msgid "To add an optional product(s) to a quotation, click :guilabel:`Add a prod msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:27 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:179 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:183 msgid "When clicked, a drop-down menu with products from the database appear. Select the desired product from the drop-down menu to add it as an optional product to the quotation template." msgstr "" @@ -13181,7 +13558,7 @@ msgid "When a product is added, the default :guilabel:`Quantity` is `1`, but tha msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:39 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:182 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:186 msgid "To delete any line item from the :guilabel:`Optional Products` tab, click the :guilabel:`🗑️ (trash can)` icon." msgstr "" @@ -13806,47 +14183,51 @@ msgstr "" msgid "When clicked, a drop-down menu with existing products in the database appear. Select the desired product from the drop-down menu to add it to the quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:127 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:126 msgid "If the desired product isn't readily visible, type the name of the desired product in the :guilabel:`Product` field, and the option appears in the drop-down menu. Products can also be found by clicking :guilabel:`Search More...` from the drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:132 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:131 +msgid "In Odoo 17, it is now possible to add event-related products (booths and registrations) to quotation templates. To do so, click the :guilabel:`Product` field, type in `Event`, and select the desired event-related product from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:136 msgid "When a product is added to a quotation template, the default :guilabel:`Quantity` is `1`, but that can be edited at any time." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:135 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:139 msgid "Then, drag-and-drop the product to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:142 msgid "To add a *section*, which serves as a header to organize the lines of a sales order, click :guilabel:`Add a section` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired name of the section can be typed. When the name has been entered, click away to secure the section name." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:143 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:147 msgid "Then, drag-and-drop the section name to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:146 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:150 msgid "To add a note, which would appear as a piece of text for the customer on the quotation, click :guilabel:`Add a note` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired note can be typed. When the note has been entered, click away to secure the note." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:150 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:154 msgid "Then, drag-and-drop the note to the desired position, via the :guilabel:`six squares` icon." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:152 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:156 msgid "To delete any line item from the :guilabel:`Lines` tab (product, section, and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right side of the line." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:156 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:160 msgid "Optional Products tab" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:158 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:162 msgid "The use of *optional products* is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:166 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:170 msgid "Optional products appear as a section on the bottom of sales orders and eCommerce pages. Customers can immediately add them to their online sales orders themselves, if desired." msgstr "" @@ -13854,55 +14235,55 @@ msgstr "" msgid "Optional products appearing on a typical sales order with Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:173 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:177 msgid "In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each cross-selling product related to the original items in the :guilabel:`Lines` tab, if applicable. The products added here ideally complement the original offering as added value for the prospective buyer." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:177 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:181 msgid "Clicking :guilabel:`Add a line` reveals a blank field in the :guilabel:`Product` column." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:186 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:190 msgid "Optional products are **not** required to create a quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:189 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:193 msgid "Terms \\& Conditions tab" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:191 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:195 msgid "The :guilabel:`Terms \\& Conditions` tab provides the opportunity to add terms and conditions to the quotation template. To add terms and conditions, simply type (or copy/paste) the desired terms and conditions in this tab." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:196 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:200 msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:199 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:203 msgid "Terms and conditions are **not** required to create a quotation template." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:202 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:206 msgid "PDF Quote Builder tab" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:204 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:208 msgid "The :guilabel:`PDF Quote Builder` tab provides options to compose an attractive quotation, with more information and visually-pleasing elements, to highlight products and/or services." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:207 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:211 msgid "To upload customer :guilabel:`Header pages` and :guilabel:`Footer pages`, click the :guilabel:`✏️ (pencil)` icon to the right of the respective pages. Click the :guilabel:`🗑️ (trash)` icon to delete an uploaded PDF." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:212 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:216 msgid ":doc:`/applications/sales/sales/send_quotations/pdf_quote_builder`" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:215 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:219 msgid "Use quotation templates" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:217 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:221 msgid "When creating a quotation (:menuselection:`Sales app --> New`), choose a pre-configured template in the :guilabel:`Quotation Template` field." msgstr "" @@ -13910,7 +14291,7 @@ msgstr "" msgid "Quotation templates field on a standard quotation form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:224 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:228 msgid "To view what the customer will see, click the :guilabel:`Preview` button at the top of the page to see how the quotation template appears on the front-end of the website through Odoo's customer portal." msgstr "" @@ -13918,15 +14299,15 @@ msgstr "" msgid "Customer preview of a quotation template in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:233 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:237 msgid "Quotation template design uses the same methodology and functionality with design building blocks as a typical web page design with Odoo *Website*. Be sure to check out the :doc:`../../../websites/website` documentation to learn more." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:237 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:241 msgid "When all blocks and customizations are complete, click the :guilabel:`Save` button to put those configurations into place." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:240 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:244 msgid "There is also a blue banner at the top of the quotation template design with a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo returns to the quotation form in the back-end of the *Sales* application." msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index a3c1259d4..66e438c58 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -172,6 +172,62 @@ msgstr "" msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk" msgstr "" +#: ../../content/applications/services/field_service/planning_itinerary.rst:3 +msgid "Planning an itinerary" +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:5 +msgid "By default, **Odoo Field Service** shows a static map where all task locations for the day are pinned. To make it more useful for the field service workers, it is possible to display an itinerary on the map using MapBox. To do so, enable the **Map Routes** feature as follows:" +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:9 +msgid "Create or sign in to a MapBox account using the following link: ``_." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:10 +msgid "`Create a token `_." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:11 +msgid "Go to the `Access tokens page on Mapbox `_ and copy your token." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:13 +msgid "In Odoo, go to the :guilabel:`Settings` app and scroll down to the :guilabel:`Integrations` section. Paste your Mapbox access token in the :guilabel:`Token` field under :guilabel:`Map Routes`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:18 +msgid "Displaying your itinerary on a map" +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:21 +msgid "For a field service task to be featured on the map, it needs:" +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:23 +msgid "a :guilabel:`Planned Date`;" +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:24 +msgid "a valid address linked to the customer’s profile." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:26 +msgid "To display your tasks on a map, go to :menuselection:`Field Service --> My Tasks --> Map`. To create your itinerary, Odoo sorts out your field service tasks based on their :guilabel:`Planned Date` to show the way from one location to the next." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:30 +msgid "To open your itinerary on the Google Maps website or app, click :guilabel:`View in Google Maps`. Google Maps includes your current location as a starting point for your itinerary." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:34 +msgid "By default, the map shows today’s tasks. Remove the :guilabel:`Today` filter in the search bar to display all tasks. Your tasks are then sorted by date in the left column." +msgstr "" + +#: ../../content/applications/services/field_service/planning_itinerary.rst:36 +msgid "Click your task in the left column or the map pin to display the task's details. From there, you can :guilabel:`Open` the task or click :guilabel:`Navigate to` to get an itinerary from your current location to this specific task's location." +msgstr "" + #: ../../content/applications/services/helpdesk.rst:7 msgid "Helpdesk" msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index da94da0ce..82dd476a5 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-06-24 07:08+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -548,7 +548,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:14 #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:94 #: ../../content/applications/websites/website/configuration.rst:5 -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:24 +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:15 #: ../../content/applications/websites/website/reporting/link_tracker.rst:10 msgid "Configuration" msgstr "" @@ -622,12 +622,10 @@ msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_ msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35 -#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83 msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36 -#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85 msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`" msgstr "" @@ -643,37 +641,37 @@ msgstr "" msgid "Another solution is to use one of the integrations with an existing shipping provider. The advantage of using an integration is that delivery costs are automatically computed based on each order as well as generating shipping labels." msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`" -msgstr "" - #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`" +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52 -#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels`" +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:53 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:54 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57 #: ../../content/applications/websites/ecommerce/managing_products/products.rst:203 msgid "Website availability" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:59 msgid "Shipping methods can be made available on **specific** websites *only*, if desired. To do so, go to :menuselection:`Website --> Configuration --> Settings --> Shipping Methods`, and select the desired **shipping method**. In the :guilabel:`Website` field, set the website you want the shipping method to be restrained to. Leave the field **empty** for the method to be available on *all* websites." msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:63 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65 msgid "Delivery method at checkout" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:67 msgid "Customers can choose the shipping method at the end of the checkout process, at the :guilabel:`Confirm Order` step." msgstr "" @@ -954,6 +952,14 @@ msgstr "" msgid "If customers are allowed to pay when picking up their order in stores or by wire transfer, the quotation is **not** be confirmed and the stock is **not** be reserved. Orders must be confirmed manually to reserve products in stock." msgstr "" +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`" +msgstr "" + #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:88 msgid "Returns and refunds" msgstr "" @@ -4545,91 +4551,55 @@ msgid "Cookies bar" msgstr "" #: ../../content/applications/websites/website/configuration/cookies_bar.rst:5 -msgid "Cookies are small text files sent to your device when you visit a website. They are processed and stored by your browser and contain information about your visit, such as login data, location, language, etc. There are two main types of cookies:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:9 -msgid "Essential cookies, which are necessary for the website to function properly;" +msgid "**Cookies** are small text files sent to your device when you visit a website. They are processed and stored by your browser and track user information like login details, preferences, and browsing history. **Essential cookies** are necessary for the website to function, while **optional cookies** are used to analyze behavior or display ads." msgstr "" #: ../../content/applications/websites/website/configuration/cookies_bar.rst:10 -msgid "Non-essential or optional cookies, which are used to analyze your behavior or display advertisements." -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:-1 -msgid "Example of a cookies bar with the popup layout." +msgid "Data protection laws require notifying users about data collection methods and purposes. **Cookies bar** fulfill this obligation by informing users on their first visit and allowing them to decide whether to store all or only essential cookies on their device." msgstr "" #: ../../content/applications/websites/website/configuration/cookies_bar.rst:17 -msgid "Notifying users about data collection, as well as its methods and purposes, is required by data protection laws such as `GDPR `_. Cookies bars are commonly used to fulfill this obligation in a user-friendly and transparent manner. They are displayed immediately upon a user's first visit to inform them that the website uses cookies and let them decide whether they want to store non-essential cookies on their device." +msgid "To enable the cookies bar on your website, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Cookies Bar` in the :guilabel:`Privacy` section." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:26 -msgid "To enable the cookies bar on your Odoo website, go to :menuselection:`Website --> Configuration` and enable :guilabel:`Cookies Bar` in the :guilabel:`Privacy` section." +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:21 +msgid "The :ref:`Cookies Policy ` page (/cookie-policy`) is automatically created when you enable the cookies bar." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:29 -msgid "You can :ref:`customize the appearance of your cookies bar ` and :ref:`edit the content of the related Cookie Policy page `." -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:35 +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:27 msgid "Customization" msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:37 -msgid "To adapt the display of the cookies bar, click :guilabel:`Edit` and select the :guilabel:`Cookies Bar` building block in the :guilabel:`Invisible Elements` at the bottom of the panel. Customize it using the options in the :guilabel:`Customize` tab in the edit panel. Three :guilabel:`Layouts` are available:" +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:29 +msgid "To adapt the display of the cookies bar, click :guilabel:`Edit`, go to the :guilabel:`Invisible Elements` section at the bottom of the panel, and click :guilabel:`Cookies Bar`. You can modify the :guilabel:`Layout` and :guilabel:`Size` of the cookies bar, and enable :guilabel:`Backdrop` to gray out the page in the background when the cookies bar is displayed on the screen." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:42 -msgid ":guilabel:`Discrete`: thin bar" +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:35 +msgid "Click anywhere in the building block to further customize the appearance of the cookies bar using :guilabel:`Block`, :guilabel:`Column` and/or :guilabel:`Inline Text` customization options." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:43 -msgid ":guilabel:`Classic`: banner" -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:44 -msgid ":guilabel:`Popup`: you can change the popup's :guilabel:`Position` to the :guilabel:`Top`, :guilabel:`Middle`, or :guilabel:`Bottom` of the screen." -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:47 -msgid "You can also:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:49 -msgid "modify the :guilabel:`Size` of the cookies bar;" -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:50 -msgid "enable :guilabel:`Backdrop` to gray out the page in the background when the cookies bar is displayed on the screen;" -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:52 -msgid "further customize the appearance of the cookies bar using :guilabel:`Block` and/or :guilabel:`Column` customization options, which are available after clicking anywhere in the building block." -msgstr "" - -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:56 +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:38 msgid "To edit the contents of the cookies bar (i.e., the consent message), click directly in the building block." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:-1 -msgid "Odoo Website's edit panel to customize the cookies bar." +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:44 +msgid "Cookies policy" msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:65 -msgid "Cookie policy" +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:46 +msgid "When you enable the cookies bar for your website, Odoo creates the **Cookie Policy** page (`/cookie-policy`) containing a non-exhaustive list of cookies, with their purpose and examples. To access it, click the :guilabel:`Cookie Policy` hyperlink in the cookies bar or open the page from :menuselection:`Website --> Site --> Pages`." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:67 -msgid "When you enable the cookies bar for your website, Odoo creates the **Cookie Policy** page (`/cookie-policy`) with the list of essential and optional cookies. To access it, click the :guilabel:`Cookie Policy` hyperlink in the cookies bar or open the page from :menuselection:`Website --> Site --> Pages`." +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:51 +msgid "To adapt the content of the page according to your needs, click the :guilabel:`Edit` button." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:72 -msgid "The contents of the page can be adapted based on your website's features and characteristics if needed." +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:54 +msgid "You could add a link to this page in your website's footer, for example." msgstr "" -#: ../../content/applications/websites/website/configuration/cookies_bar.rst:76 -msgid "You could add a link providing access to this page, in your website's footer, for example." +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:57 +msgid ":doc:`Pages <../pages>`" msgstr "" #: ../../content/applications/websites/website/configuration/domain_names.rst:3