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

[I18N] Update translation terms from Transifex

Browse Source
This commit is contained in:
Odoo Translation Bot
2024-08-25 01:42:40 +02:00
parent cdd4a16bda
commit 70905915c4
187 changed files with 291268 additions and 198594 deletions
Download Patch File Download Diff File Expand all files Collapse all files
locale/vi/LC_MESSAGES/sales.po
+529 -74
View File
@@ -9,17 +9,17 @@
# Martin Trigaux, 2023
# Hà Trần Thị Minh, 2023
# Võ Văn Khoa, 2023
# Wil Odoo, 2024
# Thi Huong Nguyen, 2024
# Wil Odoo, 2024
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-07-23 10:38+0000\n"
"POT-Creation-Date: 2024-08-21 07:41+0000\n"
"PO-Revision-Date: 2022-10-04 12:54+0000\n"
"Last-Translator: Thi Huong Nguyen, 2024\n"
"Last-Translator: Wil Odoo, 2024\n"
"Language-Team: Vietnamese (https://app.transifex.com/odoo/teams/41243/vi/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -71,7 +71,7 @@ msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10
#: ../../content/applications/sales/crm/optimize/gamification.rst:11
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:27
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60
#: ../../content/applications/sales/point_of_sale/configuration.rst:6
#: ../../content/applications/sales/point_of_sale/employee_login.rst:13
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13
@@ -241,6 +241,7 @@ msgid ""
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:95
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:44
msgid ""
"When merging, Odoo gives priority to whichever lead/opportunity was created "
"in the system first, merging the information into the first created "
@@ -281,6 +282,7 @@ msgid ""
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:116
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:11
msgid ""
"When merging opportunities, no information is lost. Data from the other "
"opportunity is logged in the chatter, and the information fields, for "
@@ -1810,6 +1812,197 @@ msgstr ""
msgid ":doc:`../performance/win_loss`"
msgstr ":doc:`../performance/win_loss`"
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:3
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:41
msgid "Merge similar leads and opportunities"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:5
msgid ""
"Odoo automatically detects similar *leads* and *opportunities* within the "
"**CRM** app. These identified duplicate records can be merged, without "
"losing any information in the process. Doing so keep the pipeline organized,"
" and prevents customers from being contacted by more than one salesperson."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:15
msgid "Identify similar leads and opportunities"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:17
msgid ""
"Similar leads and opportunities are identified by comparing the email "
"address and phone number of the associated contact. If a similar "
"lead/opportunity is found, a *Similar Leads* smart button appears at the top"
" of the lead (or opportunity) record."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst-1
msgid "An opportunity record with emphasis on the Similar Leads smart button."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:26
msgid "Compare similar leads and opportunities"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:28
msgid ""
"To compare the details of similar leads/opportunities, navigate to "
":menuselection:`CRM app --> Sales --> My Pipeline`, or :menuselection:`CRM "
"app --> Leads`. Open a lead or opportunity, and click the :guilabel:`Similar"
" Leads` smart button. Doing so opens an :guilabel:`Opportunities` page, in "
"Kanban view, that only displays similar leads/opportunities. Click on a card"
" to view the details for the lead/opportunity, and confirm if they should be"
" merged."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:35
msgid ""
"*Leads* will not appear in the header menu unless the leads feature has been"
" activated. This can be done by navigating to :guilabel:`CRM app --> "
"Configuration --> Settings` and ticking the checkbox next to "
":guilabel:`Leads`, then clicking :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:49
msgid ""
"After confirming the leads/opportunities should be merged, return to the "
":guilabel:`Opportunities` page, in Kanban view, using the breadcrumb link, "
"or by clicking the :guilabel:`Similar Leads` smart button on the opportunity"
" form. Click the :icon:`oi-view-list` :guilabel:`(list)` icon to change to "
"list view."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:54
msgid ""
"Tick the checkbox on the left of the page for the leads/opportunities to be "
"merged. Then, click the :icon:`fa-cog` :guilabel:`Action` icon at the top of"
" the page, to reveal a drop-down menu. From that drop-down menu, select the "
":guilabel:`Merge` option to merge the selected opportunities or leads."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:59
msgid ""
"When :guilabel:`Merge` is selected from the :icon:`fa-cog` "
":guilabel:`Action` drop-down menu, a :guilabel:`Merge` pop-up modal appears."
" In that pop-up modal, under the :guilabel:`Assign opportunities to` "
"section, optionally select a :guilabel:`Salesperson` and :guilabel:`Sales "
"Team` from the appropriate drop-down menus."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:64
msgid ""
"Below those fields, the leads/opportunities to merge are listed, along with "
"their related information. To add more, click :guilabel:`Add a line`, tick "
"the checkbox next to the desired leads/opportunities from the resulting "
":guilabel:`Add: Leads/Opportunities' pop-up modal, then click the "
":guilabel:`Select` button. The additional selections now appear in the list."
" To merge those selected leads/opportunities, click :guilabel:`Merge`."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:70
msgid ""
"The pop-up window disappears, and the detail card for the merged "
"opportunity/lead appears."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst-1
msgid ""
"List of similar leads and opportunities selected for merge in the CRM app."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:77
msgid ""
"Merging is an irreversible action. Do **not** merge leads/opportunities "
"unless absolutely certain they should be combined."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:81
msgid "When leads/opportunities should not be merged"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:83
msgid ""
"There may be instances where a similar lead or opportunity is identified, "
"but should *not* be merged. These circumstances vary, based on the processes"
" of the sales team and organization. Some potential scenarios are listed "
"below."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:88
msgid "Lost leads"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:90
msgid ""
"If a lead/opportunity has been marked as :doc:`lost <lost_opportunities>`, "
"it can still be merged with an active lead or opportunity. The resulting "
"lead/opportunity is marked active, and added to the pipeline."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:95
msgid "Different contact within an organization"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:97
msgid ""
"Leads/opportunities from the same organization, but with different points of"
" contact, may not have the same needs. In this case, it is beneficial to "
"*not* merge these records, though assigning the same salesperson, or sales "
"team, can prevent duplicated work and miscommunication."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:102
msgid "Duplicates with more than one salesperson"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:104
msgid ""
"If more than one lead/opportunity exists in the database, there may be "
"multiple salespeople assigned to them, who are actively working on them "
"independently. While these leads/opportunities may need to be managed "
"separately, it is recommended that any affected salespeople be tagged in an "
"internal note for visibility."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:110
msgid "Contact information is similar, but not identical"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:112
msgid ""
"Similar leads and opportunities are identified by comparing the email "
"addresses and phone numbers of the associated contacts. However, if the "
"email address is similar, but not identical, they may need to remain "
"independent."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:117
msgid ""
"Three different leads were added to the pipeline, and assigned to different "
"salespeople. They were identified as *Similar Leads*, due to the email "
"addresses of the contacts."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:120
msgid ""
"Two of the leads appear to come from the same individual, `Robin`, and have "
"identical email addresses. These leads should be merged."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:123
msgid ""
"The third lead has the same email domain, but the address is different, as "
"is the contact name. While this lead is most likely from the same "
"organization, it is from a different contact, and should **not** be merged."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:0
msgid ""
"List of similar leads with emphasis on the contact information in the CRM "
"app."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3
msgid "Multiple sales teams"
msgstr ""
@@ -1927,7 +2120,7 @@ msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5
msgid ""
"The Odoo *CRM* app can automatically assign leads/opportunities to sales "
"The Odoo **CRM** app can automatically assign leads/opportunities to sales "
"teams and salespeople. A standard practice is to assign leads based on the "
"probability of winning each lead. Companies can prioritize the leads that "
"are more likely to result in successful deals by quickly assigning them to "
@@ -1947,7 +2140,7 @@ msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:16
msgid ""
"Predictive lead scoring is a machine-learning model that uses historical "
"data from Odoo *CRM* to score open leads/opportunities."
"data from Odoo **CRM** to score open leads/opportunities."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19
@@ -1979,38 +2172,77 @@ msgid ""
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 ":math:`P(A|B)` = probability of a successful lead in this *case*"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:36
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."
":math:`P(A)` = overall probability of a lead being successful, regardless of"
" the conditions"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:37
msgid ""
":math:`P(B|A)` = probability of this being the *case*, given a lead is "
"successful"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:38
msgid ":math:`P(B)` = probability of this being the *case*"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40
msgid ""
"The term *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 ""
"The variables considered in this calculation can be :ref:`configured "
"<lead_scoring/configuration>` 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 for each opportunity is displayed on the "
"opportunity form, and updates automatically, as the opportunity progresses "
"through the CRM pipeline."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1
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."
"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 "
"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 "
":menuselection:`CRM app --> Configuration --> Settings`. Under "
":guilabel:`Predictive Lead Scoring`, click 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."
@@ -2021,49 +2253,49 @@ 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 "
@@ -2072,38 +2304,38 @@ msgid ""
"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."
"for that opportunity. The probability no longer updates 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."
"To reactivate automatic probability, click on the :icon:`fa-cog` "
":guilabel:`(gear) icon next to the :guilabel:`Probability` percentage."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1
@@ -2112,37 +2344,38 @@ msgid ""
"form."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:99
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:116
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:118
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."
"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:123
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:125
msgid ""
"To activate *rule-based assignment*, navigate to :menuselection:`CRM --> "
"Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`."
"To activate *Rule-Based Assignment*, navigate to :menuselection:`CRM app -->"
" Configuration --> Settings`, and tick the :guilabel:`Rule-Based Assignment`"
" checkbox. Then, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128
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."
"The :guilabel:`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:132
msgid ""
"To set up automatic lead assignment, select :guilabel:`Repeatedly` for the "
":guilabel:`Running` section. Then, customize how often Odoo will trigger the"
@@ -2153,63 +2386,63 @@ 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:140
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 "
"If :guilabel:`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:145
msgid "Configure assignment rules"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:147
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."
" To get started, navigate to :menuselection:`CRM app --> 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:151
msgid ""
"On the sales team configuration form, under :guilabel:`Assignment Rules`, "
"click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to "
"click :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:156
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:160
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:163
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:166
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:170
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`"
@@ -2222,7 +2455,7 @@ msgid ""
"percent."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:177
msgid ""
"Separate assignment rules can also be configured for individual team "
"members. From the sales team configuration page, click on a team member in "
@@ -2230,17 +2463,17 @@ msgid ""
" :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:181
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 "
"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:187
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 "
@@ -2248,6 +2481,229 @@ msgid ""
"specified domain."
msgstr ""
#: ../../content/applications/sales/members.rst:3
msgid "Members"
msgstr "Thành viên"
#: ../../content/applications/sales/members.rst:5
msgid ""
"The **Members** application is where all operations related to memberships "
"can be configured and managed. The **Members** app integrates with the "
"**Sales** and **Accounting** applications to sell and invoice memberships "
"directly to customers."
msgstr ""
#: ../../content/applications/sales/members.rst:10
msgid "Membership products"
msgstr "Dịch vụ thẻ thành viên"
#: ../../content/applications/sales/members.rst:12
msgid ""
"To create a new membership product, navigate to :menuselection:`Members app "
"--> Configuration --> Membership Products`, and click :guilabel:`New` to "
"open a blank product form."
msgstr ""
#: ../../content/applications/sales/members.rst:15
msgid ""
"On the new product form, enter a name for the product in the field under "
":guilabel:`Product Name`. Use the two blank fields to the right of "
":guilabel:`Membership Duration` to set a date from which the membership "
"becomes active. Finally, use the :guilabel:`Membership Fee` field to set the"
" price at which the product is sold to customers."
msgstr ""
#: ../../content/applications/sales/members.rst:20
msgid "The following optional fields can also be configured for each product:"
msgstr ""
#: ../../content/applications/sales/members.rst:22
msgid ""
":guilabel:`Internal Reference`: Set an internal reference number for the "
"product."
msgstr ""
#: ../../content/applications/sales/members.rst:23
msgid ":guilabel:`Product Category`: Set a category for the product."
msgstr ""
#: ../../content/applications/sales/members.rst:24
msgid ""
":guilabel:`Company`: Set the company inventory for the product to appear in."
msgstr ""
#: ../../content/applications/sales/members.rst:25
msgid ":guilabel:`Active`: Hide a product without removing it from inventory."
msgstr ""
#: ../../content/applications/sales/members.rst:26
msgid ""
":guilabel:`Visible on current website`: Make the product visible to "
"customers on the current website."
msgstr ""
#: ../../content/applications/sales/members.rst:28
msgid ":guilabel:`Description`: Set an internal product description."
msgstr ""
#: ../../content/applications/sales/members.rst:29
msgid ""
":guilabel:`Sales Description`: Set a product description that is visible on "
"quotations."
msgstr ""
#: ../../content/applications/sales/members.rst:30
msgid ""
":guilabel:`Income Account`: Use a different value than the default from the "
"product category."
msgstr ""
#: ../../content/applications/sales/members.rst:31
msgid ":guilabel:`Taxes`: Set the default tax used when selling this product."
msgstr ""
#: ../../content/applications/sales/members.rst:34
msgid ""
"Membership products require a start and end date, as they are used to "
"determine :ref:`membership status <sales/membership-status>`. Membership "
"products can be sold *before* their active start date."
msgstr ""
#: ../../content/applications/sales/members.rst-1
msgid "A new membership product in the members app."
msgstr ""
#: ../../content/applications/sales/members.rst:42
msgid ""
"Membership products can be added to a sales order, and invoiced as regular "
"products or subscriptions."
msgstr ""
#: ../../content/applications/sales/members.rst:46
msgid "Activate a membership"
msgstr ""
#: ../../content/applications/sales/members.rst:48
msgid ""
"To activate a membership from the **Contacts** application, navigate to the "
":menuselection:`Contacts app`, and click on a contact to open that specific "
"contact form."
msgstr ""
#: ../../content/applications/sales/members.rst:51
msgid ""
"From the contact form, open the :guilabel:`Membership` tab, and click "
":guilabel:`Buy Membership`."
msgstr ""
#: ../../content/applications/sales/members.rst:55
msgid ""
"To successfully buy a membership, both the :guilabel:`Account Receivable` "
"and :guilabel:`Account Payable` lines **must** be configured for that "
"contact. These can be found in the contact form's :guilabel:`Accounting` "
"tab, under the :guilabel:`Accounting entries` section."
msgstr ""
#: ../../content/applications/sales/members.rst:59
msgid ""
"On the :guilabel:`Join Membership` pop-up window that appears, select a "
":guilabel:`Membership` from the drop-down menu. Then, configure a "
":guilabel:`Member Price`."
msgstr ""
#: ../../content/applications/sales/members.rst:62
msgid ""
"Click :guilabel:`Invoice Membership` when both fields are filled in. Doing "
"so reveals a :guilabel:`Membership Invoices` page, wherein invoices can be "
"confirmed and completed."
msgstr ""
#: ../../content/applications/sales/members.rst:65
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/sales/members.rst:71
msgid "Membership status"
msgstr ""
#: ../../content/applications/sales/members.rst:73
msgid ""
"The :guilabel:`Current Membership Status` is listed on the "
":guilabel:`Membership` tab of each contact record:"
msgstr ""
#: ../../content/applications/sales/members.rst:76
msgid ""
":guilabel:`Non Member`: a partner who has **not** applied for membership."
msgstr ""
#: ../../content/applications/sales/members.rst:77
msgid ""
":guilabel:`Cancelled Member`: a member who has cancelled their membership."
msgstr ""
#: ../../content/applications/sales/members.rst:78
msgid ":guilabel:`Old Member`: a member whose membership end date has passed."
msgstr ""
#: ../../content/applications/sales/members.rst:79
msgid ""
":guilabel:`Waiting Member`: a member who has applied for membership, but "
"whose invoice has not yet been created."
msgstr ""
#: ../../content/applications/sales/members.rst:81
msgid ""
":guilabel:`Invoiced Member`: a member whose invoice has been created, but "
"has not been paid."
msgstr ""
#: ../../content/applications/sales/members.rst:82
msgid ":guilabel:`Paid Member`: a member who has paid the membership fee."
msgstr ""
#: ../../content/applications/sales/members.rst:85
msgid "Publish members directory"
msgstr ""
#: ../../content/applications/sales/members.rst:87
msgid ""
"To publish a list of active members on the website, the **Online Members "
"Directory** module must first be :ref:`installed <general/install>`. 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/sales/members.rst-1
msgid "The Online Members directory module in Odoo."
msgstr ""
#: ../../content/applications/sales/members.rst:96
msgid "Publish individual members"
msgstr ""
#: ../../content/applications/sales/members.rst:98
msgid ""
"Navigate to :menuselection:`CRM app --> Sales --> Customers`, and click the "
"Kanban card for a member. From the customer form that appears, click the "
":guilabel:`Go to Website` smart button at the top of the page to open the "
"member's webpage."
msgstr ""
#: ../../content/applications/sales/members.rst:102
msgid ""
"Click the :icon:`fa-pencil` :guilabel:`Edit` button to reveal a sidebar of "
"editing tools. 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/sales/members.rst:106
msgid "Repeat these steps for all desired members."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:6
msgid "Point of Sale"
msgstr "Điểm bán lẻ"
@@ -6068,9 +6524,8 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:28
msgid ""
":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`"
":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration`"
msgstr ""
":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`"
#: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:29
msgid ""
@@ -14526,7 +14981,7 @@ msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:43
msgid "Payment providers"
msgstr ""
msgstr "Nhà cung cấp dịch vụ thanh toán"
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:45
msgid ""