# SOME DESCRIPTIVE TITLE. # Copyright (C) Odoo S.A. # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # # Translators: # jl2035 , 2023 # Jasmina Macur , 2023 # Tadej Lupšina , 2024 # Boris Kodelja , 2024 # Grega Vavtar , 2024 # Katja Deržič, 2024 # Matjaz Mozetic , 2024 # matjaz k , 2024 # Martin Trigaux, 2024 # Gregor Flajs, 2024 # Wil Odoo, 2024 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-09-24 10:43+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" "Last-Translator: Wil Odoo, 2024\n" "Language-Team: Slovenian (https://app.transifex.com/odoo/teams/41243/sl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: sl\n" "Plural-Forms: nplurals=4; plural=(n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3);\n" #: ../../content/applications/sales.rst:5 #: ../../content/applications/sales/sales.rst:8 msgid "Sales" msgstr "Prodaja" #: ../../content/applications/sales/crm.rst:8 msgid "CRM" msgstr "CRM" #: ../../content/applications/sales/crm.rst:10 msgid "" "**Odoo CRM** helps you organize your sales activities: track leads, close " "opportunities and get accurate forecasts. Keep opportunities organized with " "the pipeline and manage your day-to-day activities with meetings and next " "activities." msgstr "" #: ../../content/applications/sales/crm.rst:15 msgid "`Odoo Tutorials: CRM `_" msgstr "" #: ../../content/applications/sales/crm/acquire_leads.rst:5 msgid "Acquire leads" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:3 msgid "Convert leads into opportunities" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 msgid "" "*Leads* act as a qualifying step before an opportunity is created. This " "provides additional time to review its potential, and gauge its viability, " "before the opportunity is assigned to a salesperson." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 #: ../../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: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/configuration.rst:52 #: ../../content/applications/sales/point_of_sale/employee_login.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:20 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:20 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:12 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:19 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:16 #: ../../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: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 #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11 #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:12 #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:10 #: ../../content/applications/sales/sales/invoicing/proforma.rst:14 #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:14 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:34 #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:24 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:14 #: ../../content/applications/sales/subscriptions/closing.rst:9 #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:21 #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:17 msgid "Configuration" msgstr "Nastavitve" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:11 msgid "" "To activate the *Leads* setting, navigate to :menuselection:`CRM app --> " "Configuration --> Settings` and check the box labeled, :guilabel:`Leads`. " "Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 msgid "Leads setting on CRM configuration page." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:18 msgid "" "Activating this feature adds a new menu option, :guilabel:`Leads`, to the " "header bar, located along the top of the screen." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 msgid "Leads menu on CRM application." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:25 msgid "" "Once the *Leads* setting has been activated, it applies to all sales teams " "by default. To turn off leads for a specific team, navigate to " ":menuselection:`CRM app --> Configuration --> Sales Teams`. Then, select a " "team from the list to open that team's configuration page. Clear the " ":guilabel:`Leads` checkbox, located beneath the :guilabel:`Sales Team` " "field, then click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:36 msgid "Convert a lead into an opportunity" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:38 msgid "" "To convert a lead into an *opportunity*, navigate to :menuselection:`CRM app" " --> Leads`, and click on a lead from the list to open it." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:42 msgid "" "If a :guilabel:`Similar Leads` smart button appears at the top of the page " "for the lead, it indicates a similar lead or opportunity already exists in " "the database. Before converting this lead, click the smart button to confirm" " if the lead should be merged." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:0 msgid "Close up of a lead with emphasis on the Similar Leads smart button." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:50 msgid "" "Click the :guilabel:`Convert to Opportunity` button, located at the top-left" " of the page." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 msgid "Create opportunity button on a lead record." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:56 msgid "" "This opens a :guilabel:`Convert to opportunity` pop-up modal. Here, in the " ":guilabel:`Conversion Action` field, select the :guilabel:`Convert to " "opportunity` option." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:60 msgid "" "To merge this lead with an existing similar lead or opportunity, select " ":guilabel:`Merge with existing opportunities` in the :guilabel:`Conversion " "Action` field. This generates a list of the similar leads/opportunities to " "be merged." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:64 #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:38 msgid "" "When merging, Odoo gives priority to whichever lead/opportunity was created " "in the system first, merging the information into the first created " "lead/opportunity. However, if a lead and an opportunity are being merged, " "the resulting record is referred to as an opportunity, regardless of which " "record was created first." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:69 msgid "" "Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which" " the opportunity should be assigned. Neither field is required, though if a " "selection is made in the :guilabel:`Salesperson` field, the :guilabel:`Sales" " Team` field is populated automatically, based on the salesperson's team " "assignments." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:74 msgid "" "If the lead has already been assigned to a salesperson or a team, these " "fields automatically populate with that information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 msgid "Create opportunity pop-up." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:81 msgid "" "Under the :guilabel:`Customer` heading, choose from the following options:" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:83 msgid "" ":guilabel:`Create a new customer`: choose this option to use the information" " in the lead to create a new customer record." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:85 msgid "" ":guilabel:`Link to an existing customer`: choose this option, then select a " "customer from the resulting drop-down menu, to link this opportunity to an " "existing customer record." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:87 msgid "" ":guilabel:`Do not link to a customer`: choose this option to convert the " "lead, but not link it to a new or existing customer." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:90 msgid "" "Lastly, when all configurations are complete, click :guilabel:`Create " "Opportunity`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:92 msgid "" "To view the newly created opportunity, navigate to :menuselection:`CRM app " "--> My Pipeline`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:95 msgid "" "Some filters may need to be removed from the :guilabel:`Search...` bar on " "the top :guilabel:`Pipeline` page to view all opportunities." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:3 msgid "Create leads (from email or manually)" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:8 msgid "" "Leads can be added to the *CRM* app from custom email aliases, and by " "manually creating new records. This is in addition to the leads and " "opportunities created in the app through the :doc:`website contact form " "`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:12 msgid "" "First, ensure the *Leads* feature is enabled in the database by navigating " "to :menuselection:`CRM app --> Configuration --> Settings`. Tick the " ":guilabel:`Leads` checkbox, then click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:19 msgid "Configure email aliases" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:21 msgid "" "Each sales team has the option to create and utilize their own unique email " "alias. When messages are sent to this address, a lead (or opportunity), is " "created with the information from the message." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:25 msgid "" "To create or update a sales teams' email alias, navigate to " ":menuselection:`CRM app --> Configuration --> Sales Teams`. Click on a team " "from the list to open the team's details page." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst-1 msgid "The sales team details page, focused on the email alias section." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:32 msgid "" "In the :guilabel:`Email Alias` field, enter a name for the email alias, or " "edit the existing name. In the :guilabel:`Accept Emails From` field, use the" " drop-down menu to choose who is allowed to send messages to this email " "alias:" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:36 msgid ":guilabel:`Everyone`: messages are accepted from any email address." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:37 msgid "" ":guilabel:`Authenticated Partners`: only accepts messages from email " "addresses associated with a a partner (contact or customer) record." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:39 msgid "" ":guilabel:`Followers only`: only accepts messages from those who are " "following a record related to the team, such as a lead or opportunity. " "Messages are also accepted from team members." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:41 msgid "" ":guilabel:`Authenticated Employees`: only accepts messages from email " "addresses that are connected to a record in the *Employees* app." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:45 msgid "Leads created from email" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:47 msgid "" "Leads created from email alias messages can be viewed by navigating to " ":menuselection:`CRM app --> Leads`. Click a lead from the list to open it, " "and view the details." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:50 msgid "" "The email received by the alias is added to the *chatter* thread for the " "lead. The subject line of the message is added to the title field, and the " ":guilabel:`Email` field is updated with the contact's email address." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst-1 msgid "The chatter thread of a newly created lead in the CRM app." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:59 msgid "" "If the *leads* feature is **not** enabled on the database, messages to the " "email alias are added to the database as opportunities." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:63 msgid ":doc:`../../../general/email_communication`" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:66 msgid "Manually create leads" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:68 msgid "" "Leads can be added directly to the *CRM* app by manually creating a new " "record. Navigate to :menuselection:`CRM app --> Leads` to view a list of " "existing leads." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:72 msgid "" "Leads can also be added via the :doc:`Generate Leads ` button." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:74 msgid "" "At the top-left of the list, click :guilabel:`New` to open a blank " ":guilabel:`Leads` form." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:76 msgid "" "In the first field of the new form, enter a title for the new lead. Next, " "enter a :guilabel:`Contact Name`, and a :guilabel:`Company Name`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:80 msgid "" "If a lead is :doc:`converted to an opportunity `, the " ":guilabel:`Company Name` field is used to either link this opportunity to an" " existing customer, or to create a new customer." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:84 msgid "Manually create opportunities" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:86 msgid "" "To manually create an opportunity, navigate to :menuselection:`CRM app --> " "Sales --> My Pipeline`. At the top-left of the page, click :guilabel:`New` " "to create a new opportunity Kanban card. In the " ":guilabel:`Organization/Contact` field, enter the name of the company the " "opportunity is for." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:90 msgid "" "Choose a name, and enter it in the :guilabel:`Opportunity` field. *This is a" " required field.* When manually creating an opportunity, it is helpful to " "add a name that relates to the details of the opportunity." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:95 msgid "" "In the example below, the opportunity is named `5 VP Chairs`. This " "identifies the product the customer is interested in, as well as the " "potential number of products." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:0 msgid "An example of an opportunity in the CRM pipeline." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:102 msgid "" "Enter the contact information for the opportunity in the :guilabel:`Email` " "and :guilabel:`Phone` fields." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:105 msgid "" "In the :guilabel:`Expected Revenue` field, enter an estimated value for the " "opportunity." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:108 msgid "" "The information in the :guilabel:`Expected Revenue` and priority fields can " "be used to track performance for individual salespeople, and on a team " "basis. See :doc:`../performance/expected_revenue_report` and " ":doc:`../track_leads/lead_scoring` for more information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:113 msgid "Then, use the |st-o| :guilabel:`(star)` icons to assign a priority." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:115 msgid "|st-o| |st-o| |st-o|: low priority" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:116 msgid "|st| |st-o| |st-o|: medium priority" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:117 msgid "|st| |st| |st-o|: high priority" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:118 msgid "|st| |st| |st|: very high priority" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:121 msgid "" "Assigning a priority changes the order of leads in Kanban view, with higher " "priority leads displayed first." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:124 msgid "" "Once all the necessary information has been entered, click :guilabel:`Add`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst-1 msgid "The CRM pipeline with a newly created opportunity." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:3 msgid "Lead mining" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:8 msgid "" "*Lead mining* is a feature that allows *CRM* users to generate new leads " "directly into their Odoo database. To ensure lead qualification, lead mining" " output is determined by a variety of filtering criteria, such as the " "country, the company size, and the industry." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:15 msgid "" "To get started, go to :menuselection:`CRM app --> Configuration --> " "Settings`, and tick the :guilabel:`Lead Mining` checkbox to activate the " "feature. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 msgid "Activate lead mining in Odoo CRM settings." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:23 msgid "Generate leads" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:25 msgid "" "After the *Lead Mining* setting is activated, a new button called *Generate " "Leads* is available to use in the upper-left corner of the *CRM* *Pipeline* " "(:menuselection:`CRM app --> Sales --> My Pipeline`)." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:29 msgid "" "Lead mining requests are also available through :menuselection:`CRM app --> " "Configuration --> Lead Mining Requests`, or through :menuselection:`CRM app " "--> Leads --> Leads`, where the :guilabel:`Generate Leads` button is also " "available." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 msgid "The Generate Leads button to use the lead mining feature." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:37 msgid "" "Click the :guilabel:`Generate Leads` button, and a pop-up window appears, " "offering a variety of criteria by which to generate leads." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 msgid "" "The pop-up window with the selection criteria in order to generate leads in " "Odoo." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44 msgid "" "Choose to generate leads for :guilabel:`Companies` to get company " "information only, or choose |CC| to get company information and individual " "employee contact information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:48 msgid "" "When targeting |CC|, additional options are available to filter contacts " "based on :guilabel:`Role` or :guilabel:`Seniority`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51 msgid "Additional filtering options include the following:" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:53 msgid "" ":guilabel:`Countries`: filter leads based on the country (or countries) they" " are located in." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:54 msgid "" ":guilabel:`States`: further filter leads based on the state in which they " "are located, if applicable." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:56 msgid "" ":guilabel:`Industries`: filter leads based on the specific industry they " "work in." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:57 msgid "" ":guilabel:`Filter on Size`: tick this checkbox to specify the number of " "employees at the company. This generates a field labeled :guilabel:`Size`. " "Fill in the blanks to create a range for the desired company size." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:60 msgid "" ":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned " "to." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61 msgid "" ":guilabel:`Salesperson`: choose which member of the Sales Team the leads " "will be assigned to." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:62 msgid "" ":guilabel:`Default Tags`: choose which tags are applied directly to the " "leads once found." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:65 msgid "" "Make sure to be aware of the latest EU regulations when receiving contact " "information. Get more information about the General Data Protection " "Regulation on `Odoo GDPR `_." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:69 msgid "View leads" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:71 msgid "" "After leads are generated, they are assigned to the designated salesperson " "and team. To view additional information regarding the lead, select one from" " the list, and click to open it." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:74 msgid "" "In the chatter thread for the lead, additional information is provided. This" " can include the number of employees, the technology used by the company, " "the timezone, and direct contact information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 msgid "The chatter thread of a newly generated lead." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:82 msgid "" "If :guilabel:`Leads` are **not** enabled for the database, then leads are " "generated as *opportunities*, and added to the pipeline for the designated " "salesperson." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:85 msgid "" "To enable the :guilabel:`Leads` feature, navigate to :menuselection:`CRM app" " --> Configuration --> Settings`, and tick the :guilabel:`Leads` checkbox. " "Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:89 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:94 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:61 #: ../../content/applications/sales/rental.rst:88 msgid "Pricing" msgstr "Določanje cen" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:91 msgid "" "Lead mining is an *In-App Purchase* feature, and each generated lead costs " "one :ref:`credit `." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:95 msgid "" "Generating |CC| costs one additional credit for each contact generated. See " "here for complete pricing information: `Lead Generation by Odoo IAP " "`_." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:99 msgid "" "To buy credits, navigate to :menuselection:`CRM app --> Configuration --> " "Settings`. In the :guilabel:`Lead Generation` section, under the " ":guilabel:`Lead Mining` feature, click :guilabel:`Buy Credits`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:103 msgid "" "Credits may also be purchased by navigating to the :menuselection:`Settings " "app`. In the :guilabel:`Contacts` section, under the :guilabel:`Odoo IAP` " "feature, click :guilabel:`View My Services`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst-1 msgid "Buy credits in the Odoo IAP settings." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:112 msgid "" "Enterprise Odoo users with a valid subscription get free credits to test " "|IAP| features before purchasing more credits for the database. This " "includes demo/training databases, educational databases, and one-app-free " "databases." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:117 msgid ":doc:`/applications/essentials/in_app_purchase`" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:3 msgid "Create opportunities from web contact forms" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:5 msgid "" "Adding a contact form to a website makes it easy to convert visitors into " "leads and opportunities. After a visitor submits their information, an " "opportunity can be created automatically, and assigned to a designated sales" " team and salesperson." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:12 msgid "Customize contact forms" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:14 msgid "" "By default, the *Contact Us* page on an Odoo website displays a " "preconfigured contact form. This form can be customized, as needed, to suit " "the needs of a specific sales team." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:17 msgid "" "Navigate to :menuselection:`Website app --> Contact Us`, then click " ":guilabel:`Edit` in the top-right of the screen to open the web editor. " "Click on the form building block in the body of the webpage to open the form" " configuration settings on the right sidebar. The following options are " "available to customize the contact form from the :guilabel:`From` section of" " the right sidebar:" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst-1 msgid "The form configuration settings on an Odoo website." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:26 msgid "" ":guilabel:`Action`: the default action for a contact form is :guilabel:`Send" " an Email`. Select :guilabel:`Create an Opportunity` from the drop-down list" " to capture the information in the *CRM* app." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:29 msgid "" ":guilabel:`Sales Team`: choose a sales team from the drop-down menu that the" " opportunities from this form should be assigned to. This field **only** " "appears if the :guilabel:`Action` field is set to :guilabel:`Create an " "Opportunity`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:32 msgid "" ":guilabel:`Salesperson`: if the opportunities should be assigned to a " "specific salesperson, select them from the drop-down menu. If no selection " "is made in this field, the opportunities are assigned based on the team's " "existing rules." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:35 msgid "" ":guilabel:`Marked Fields`: use this field to alter how the form handles " "marked fields. The default option is to treat marked fields as " ":guilabel:`Required`, which is the recommended setting." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:37 msgid "" ":guilabel:`Mark Text`: choose how :guilabel:`Marked Fields` should be " "identified. The default character is an asterisk (`*`)." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:39 msgid "" ":guilabel:`Labels Width`: use this field to alter the pixel width of the " "labels, if desired." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:40 msgid "" ":guilabel:`On Success`: select how the webpage reacts after a customer " "successfully submits a form. :guilabel:`Nothing` keeps the customer on the " "same screen, with the addition of a confirmation message that the form was " "submitted successfully. :guilabel:`Redirect` sends the customer to a new " "webpage, based on the address provided in the :guilabel:`URL` field below. " ":guilabel:`Show Message` replaces the form with a preconfigured message that" " informs the customer someone should respond to them as soon as possible." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:46 msgid "" ":guilabel:`URL`: if :guilabel:`Redirect` is selected in the :guilabel:`On " "Success` field, enter the URL for the webpage, where customers should be " "directed after successfully submitting a form." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:48 msgid "" ":guilabel:`Visibility`: use the drop-down menu to add any visibility " "conditions for this field, if desired." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:52 msgid "" "If *leads* are activated in *CRM* settings, selecting :guilabel:`Create an " "Opportunity` generates a lead instead. To activate leads, navigate to " ":menuselection:`CRM app --> Configuration --> Settings`, and tick the " ":guilabel:`Leads` checkbox. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:57 msgid "Customize contact form fields" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:59 msgid "" "In addition to the settings for the form, the settings for each field can be" " customized, as well. With the web editor menu still open, click into a " "field to open the :guilabel:`Field` configuration settings section on the " "sidebar. The following options are available to customize a field:" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:63 msgid "" ":guilabel:`Type`: choose a custom field option or an existing field type." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:64 msgid "" ":guilabel:`Input Type`: determine the type of information customers should " "input. Available options are :guilabel:`Text`, :guilabel:`Email`, " ":guilabel:`Telephone`, or :guilabel:`Url`. The selection made in this field " "limits the format that customers can use when entering information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:67 msgid ":guilabel:`Label`: enter the name for the field." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:68 msgid "" ":guilabel:`Position`: choose the way the label is aligned with the rest of " "the form. The label can be hidden, above the field, to the left of the " "field, or right adjusted and closer to the field." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:70 msgid "" ":guilabel:`Description`: slide the toggle to add a description for the " "field, which can provide additional instructions to customers. Click under " "the field on the form to add the description." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:72 msgid "" ":guilabel:`Placeholder`: enter an example to help users know how to input " "information where formatting is important, such as a phone number or email " "address." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:74 msgid "" ":guilabel:`Default Value`: enter a value to include in the form, by default," " if the customer does not provide information in the field. *It is not " "recommended to include a default value for required fields*." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:77 msgid "" ":guilabel:`Required`: slide the toggle to mark this field as required if it " "**must** be filled in for every submission." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:79 msgid "" ":guilabel:`Visibility`: select when this field should be visible. Use the " "button on the left to choose whether to show or hide this field on a desktop" " users. Use the button on the right to choose whether to show or hide this " "field to mobile users." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:82 msgid ":guilabel:`Animation`: select if this field should have any animation." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst-1 msgid "The field configuration settings on an Odoo website." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:89 msgid "View opportunities" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:91 msgid "" "After a customer submits a contact form, and an opportunity is created, it " "is assigned based on the :ref:`form settings `. " "To view opportunities, navigate to :menuselection:`CRM app --> Sales --> My " "Pipeline`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:96 msgid "" "If leads are activated on the database, contact form submissions are " "generated as leads, not opportunities. To activate leads, navigate to " ":menuselection:`CRM app --> Configuration --> Settings`, and tick the " ":guilabel:`Leads` checkbox. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:100 msgid "" "Navigate to :menuselection:`CRM app --> Leads` to view the newly-created " "leads." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:102 msgid "" "On the :guilabel:`My Pipeline` dashboard, click on an opportunity card in " "the Kanban view to open the opportunity record. The information submitted by" " the customer is visible on the opportunity record." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:107 msgid "" "As the contact form fields are customizable, the fields on the opportunity " "record, where the form information is stored, varies accordingly." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:110 msgid "" "If the preconfigured contact form is used, the *Subject* field is added to " "the :guilabel:`Title` field, and the content in the :guilabel:`Notes` field," " which is labeled as :guilabel:`Your Question`, is added to the " ":guilabel:`Internal Notes` tab." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:115 msgid ":doc:`../pipeline/manage_sales_teams`" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:116 msgid ":doc:`convert`" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:117 #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:109 msgid ":doc:`../track_leads/lead_scoring`" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:118 msgid ":ref:`Website forms `" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:3 msgid "Create and send quotations" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:5 msgid "" "Once a qualified lead has been converted into an opportunity, the next step " "is to create and deliver a quotation. This process can be easily handled " "through Odoo's *CRM* application." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:9 msgid "Create a new quotation" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:11 msgid "" "To create a new quotation, open the :menuselection:`CRM app`, revealing the " ":guilabel:`Pipeline` page on the main *CRM* dashboard." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:14 msgid "" "From here, click on any opportunity to open it. Review the existing " "information and update any fields, if necessary." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:18 msgid "" "If a quotation has already been created for this opportunity, it can be " "found by clicking on the :guilabel:`Quotations` smart button at the top of " "the top of the form. The number of existing quotations is listed on the " "smart button, as well." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:22 msgid "" "At the top-left of the form, click the :guilabel:`New Quotation` button." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst-1 #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst-1 msgid "Qualified lead form with New Quotation button emphasized." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:29 msgid "" "The **Sales** application **must** be installed for the :guilabel:`New " "Quotation` button to appear." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:33 msgid "" "The :guilabel:`Customer` field is **not** required on the opportunity form." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:35 msgid "" "However, customer information must be added or linked before a quotation can" " be sent. If the :guilabel:`Customer` field is left blank on the " "opportunity, clicking the :guilabel:`New Quotation` button opens a pop-up " "window with the following options:" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:39 msgid "" ":guilabel:`Create a new customer`: creates a new customer record, using any " "available information provided on the opportunity form." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:41 msgid "" ":guilabel:`Link to an existing customer`: opens a drop-down field with " "existing customer names. Select a name to link this new quotation to an " "existing customer record." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:43 msgid "" ":guilabel:`Do not link to a customer`: the quotation will **not** be linked " "to a customer, and no changes are made to the customer information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:46 msgid "" "Once this button is clicked, a new quotation form appears. Confirm the " "information in the top half of the form, and update any missing or incorrect" " fields:" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:49 msgid "" ":guilabel:`Customer`: the company or contact for whom this quotation was " "created." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:50 msgid "" ":guilabel:`Referrer`: if this customer was referred by another customer or " "contact, select it from the drop-down menu in this field." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:52 msgid "" ":guilabel:`Invoice Address`: physical address where the invoice should be " "sent." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:53 msgid "" ":guilabel:`Delivery Address`: physical address where any products should be " "delivered." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:54 msgid "" ":guilabel:`Quotation Template`: if applicable, select a pre-configured " ":doc:`quotation template " "` from this field." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:56 msgid ":guilabel:`Expiration`: date when this quotation is no longer valid." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:57 msgid "" ":guilabel:`Quotation Date`: creation date of draft/sent orders, confirmation" " date of confirmed orders. Note that this field is only visible if " ":doc:`Developer mode (debug mode) ` is" " active." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:60 msgid "" ":guilabel:`Recurring Plan`: if this quotation is for a recurring product or " "subscription, select the recurring plan configuration to be used." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:62 msgid ":guilabel:`Pricelist`: select a pricelist to be applied to this order." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:63 msgid "" ":guilabel:`Payment Terms`: select any applicable payment terms for this " "quotation." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:70 msgid "" "The :guilabel:`Expiration` field automatically populates based on the " "creation date of the quotation, and the default validity time frame." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:73 msgid "" "To update the default validity time frame, navigate to :menuselection:`Sales" " app --> Configuration --> Settings --> Quotations & Orders` and update the " ":guilabel:`Default Quotation Validity` field. To disable automatic " "expiration, enter `0` in this field." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:77 msgid "When the desired changes are complete, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:79 msgid "" "When using a quotation template, the expiration date is based off of the " ":guilabel:`Quotation Validity` field on the template. To alter the validity " "date computation on a template, go to :menuselection:`Sales app --> " "Configuration --> Sales Orders --> Quotation Templates`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:83 msgid "" "Then, click on a template to open it, and update the number in the " ":guilabel:`Quotation Validity` field." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:87 msgid "Order lines" msgstr "Postavke naročila" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:89 msgid "" "After updating the customer, payment, and deadline information on the new " "quotation, the :guilabel:`Order Lines` tab can be updated with the " "appropriate product information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:92 msgid "" "To do that, click :guilabel:`Add a product` in the :guilabel:`Order Lines` " "tab." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:94 msgid "" "Next, type the name of an item into the :guilabel:`Product` field to search " "through the product catalog. Then, select a product from the drop-down menu," " or create a new one by selecting :guilabel:`Create` or :guilabel:`Create " "and Edit`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:98 msgid "" "After selecting a product, update the :guilabel:`Quantity`, if necessary. " "Confirm the information in the remaining fields." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:101 msgid "" "To remove a line from the quotation, click the :icon:`fa-trash-o` " ":guilabel:`(trash can)` icon." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:103 msgid "" "To organize products into sections click :guilabel:`Add a section` and type " "a name for the section. Then, click the :icon:`oi-draggable` " ":guilabel:`(drag)` icon to the left of the name and drag to move the section" " to the appropriate location. Move each product using the same method to " "finish organizing the quotation order lines." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst-1 msgid "" "Categories are used to create separate sections on the order lines of a " "quote." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:113 msgid "Product catalog" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:115 msgid "" "To quickly add numerous products to the quotation, click the " ":guilabel:`Catalog` button to open the product catalog." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:118 msgid "" "All products in the database are listed as cards and can be sorted in the " "left panel by :guilabel:`Product Category` and :guilabel:`Attributes`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst-1 msgid "The product catalog displays all products as cards." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:125 msgid "" "To add a product, click the :icon:`fa-shopping-cart` :guilabel:`Add` button " "on the product card. Set the quantity of the item using the :icon:`fa-plus` " ":guilabel:`(add)` or :icon:`fa-minus` :guilabel:`(subtract)` buttons, or " "type the quantity in the number field between the two buttons. To remove an " "item, click the :icon:`fa-trash` :guilabel:`Remove` button on the product " "card." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst-1 msgid "" "The purple add and subtract buttons are used to set the quantity of an item." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:134 msgid "" "Once all product quantities are set, click the :guilabel:`Back to Quotation`" " button to return to the quotation. The items selected in the product " "catalog now appear in the :guilabel:`Order Lines` tab." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:138 msgid "Preview and send quotation" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:140 msgid "" "To see a preview of the quotation as the customer will see it, click the " ":guilabel:`Preview` button. Doing so opens a preview in the " ":guilabel:`Customer Portal`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:143 msgid "" "After reviewing the customer preview, click :guilabel:`Return to edit mode` " "to return to the quotation form in the backend." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:146 msgid "" "When the quotation is ready to deliver to the customer, click the " ":guilabel:`Send by Email` button." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:148 msgid "" "Doing so opens a pop-up window with a pre-configured email message. " "Information from the quotation, including the contact information, total " "cost, and quotation title are be imported from the quotation." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:152 msgid "A PDF of the quotation is added as an attachment to the email." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:155 msgid "" "A pre-loaded template is used to create the email message. To alter the " "template, click the internal link to the right of the :guilabel:`Load " "template` field, located at the bottom of the email pop-up window." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:159 msgid "" "To select a new template, select an option from the :guilabel:`Load " "template` drop-down menu." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:161 msgid "" "Proceed to make any necessary changes to the email, then click " ":guilabel:`Send`. A copy of the message is added to the *Chatter* of the of " "the record." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:164 msgid "" "After a quotation is sent, the originating opportunity's " ":guilabel:`Quotations` smart button updates with a new count. This " "quotation, and all other quotations can be accessed through this smart " "button at the top of the opportunity in the *CRM* app." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:168 msgid "" "Any quotations attached to the opportunity that are confirmed, and have " "therefore been converted to sales orders, will be deducted from the number " "listed on the :guilabel:`Quotations` smart button. Instead, the value of the" " sales order will appear in the :guilabel:`Orders` smart button located in " "the same control panel." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:174 msgid "Mark an opportunity won or lost" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:176 msgid "" "In order to keep the pipeline up to date and accurate, opportunities need to" " be identified as *won* or *lost* once a customer has responded to a " "quotation." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:179 msgid "" "To mark an opportunity as *won* or *lost*, return to the opportunity using " "the breadcrumbs at the top-left of the quotation form. Or navigate to " ":menuselection:`CRM app --> Sales --> My Pipeline` and click on the correct " "opportunity to open it." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:183 msgid "" "At the top-left of the form, click on either the :guilabel:`Won` or " ":guilabel:`Lost` button." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:185 msgid "" "If the opportunity is marked *won*, a green :guilabel:`Won` banner is added " "to the record, and it is moved to the :guilabel:`Won` stage." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:188 msgid "" "Marking an opportunity as *lost*, via the :guilabel:`Lost` button opens a " ":guilabel:`Mark Lost` pop-up window, where a :guilabel:`Lost Reason` can be " "entered." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:191 msgid "" "From the :guilabel:`Lost Reason` drop-down field, choose an existing lost " "reason. If no applicable reason is available, create a new one by entering " "it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:196 msgid "" "It's best practice to try and use pre-configured :guilabel:`Lost Reason` " "values as much as possible or to limit the creation of new values only to " "sales team leads. Using consistent values for this parameter will make " "pipeline analysis easier and more accurate when filtering for the " ":guilabel:`Lost Reason` parameter." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:201 msgid "" "To set up new values for this field, navigate to :menuselection:`CRM --> " "Configuration --> Lost Reasons`, and click both :guilabel:`New` and " ":guilabel:`Save` for each new entry added to the list." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:205 msgid "" "Additional notes and comments can be added in the :guilabel:`Closing Note` " "field." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:207 #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:34 #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:192 msgid "" "When all the desired information has been entered in the :guilabel:`Mark " "Lost` pop-up window, click :guilabel:`Mark as Lost`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:210 msgid "" "Upon clicking :guilabel:`Mark as Lost`, the pop-up window disappears, and " "Odoo returns to the opportunity form, where a new red :guilabel:`Lost` " "banner is now present in the upper-right corner of the opportunity." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:214 msgid "" "Once an opportunity is marked as *lost*, it is no longer considered active, " "and it is removed from the pipeline." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:217 msgid "" "In order to view a *lost* opportunity from the pipeline, click the " ":guilabel:`down arrow icon` to the right of the search bar, and select " "either :guilabel:`Lost` or :guilabel:`Archived` from the drop-down menu that" " appears." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:222 msgid "" "While opportunities that have been marked as *lost* are considered " "*Archived*, be advised that, in order for an opportunity to be included as " "*lost* in reporting, it **must** be specifically marked as *lost*, not " "*Archived*." msgstr "" #: ../../content/applications/sales/crm/optimize.rst:5 msgid "Optimize your Day-to-Day work" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:3 msgid "CRM Gamification" msgstr "CRM igrifikacija" #: ../../content/applications/sales/crm/optimize/gamification.rst:5 msgid "" "In Odoo's *CRM* app, *gamification tools* provide the opportunity to " "evaluate and motivate users through customizable challenges, goals, and " "rewards. Goals are created to target actions within the *CRM* app, and can " "be tracked and rewarded automatically to participating sales teams." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:12 msgid "" "To install the *CRM Gamification* module, navigate to the " ":menuselection:`Apps` application. Click into the :guilabel:`Search...` bar " "at the top of the page and remove the :guilabel:`Apps` filter. Type `CRM " "Gamification` to search." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:16 msgid "" "On the :guilabel:`CRM Gamification` module, click :guilabel:`Install`. This " "module features goals and challenges related to the *CRM* and *Sales* " "applications." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst-1 msgid "View of the gamification module being installed in Odoo." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:24 msgid "" "If **both** the *CRM* and *Sales* apps are installed, the *CRM Gamification*" " module is automatically installed on the database." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:27 msgid "" "To access the *Gamification Tools* menu, first enable :ref:`developer-mode`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:29 msgid "" "Next, navigate to :menuselection:`Settings app --> Gamification Tools`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst-1 msgid "View if the gamification tools menu in Odoo Settings." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:38 msgid "Create badges" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:40 msgid "" "*Badges* are awarded to users when they have completed a challenge. " "Different badges can be awarded based on the type of task completed, and can" " be issued to more than one user, depending on the time they accomplish the " "goal." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:44 msgid "" "To view the existing badges, or create a new one, navigate to " ":menuselection:`Settings --> Gamification Tools --> Badges`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst-1 msgid "View of the badges page in Odoo." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:52 msgid "" "Some badges can be awarded outside of challenges, as well. Select the Kanban" " card for the desired badge, then click :guilabel:`Grant`. This opens a " ":guilabel:`Grant Badge` pop-up window. Select a user from the :guilabel:`Who" " would you like to reward?` field." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:56 msgid "" "Add any additional information regarding why the user is receiving the " "reward in the field below, then click :guilabel:`Grant Badge`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:59 msgid "" "To create a new badge, click :guilabel:`New` at the top-left of the page to " "open a blank form. Enter a name for the :guilabel:`Badge`, followed by a " "description." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:62 msgid "" "The :guilabel:`Allowance to Grant` field determines when a badge can be " "granted, and by whom:" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:64 msgid ":guilabel:`Everyone`: this badge can be manually granted by any user." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:65 msgid "" ":guilabel:`A selected list of users`: this badge can only be granted by a " "select group of users. If this option is selected, it generates a new field," " :guilabel:`Authorized Users`. Choose the appropriate users from this drop-" "down list." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:68 msgid "" ":guilabel:`People having some badges`: this badge can only be granted by " "users who have already been awarded a specific badge. If this option is " "selected it generates a new field, :guilabel:`Required Badges`. Use this " "drop-down list to select the badge(s) a user must have before they can award" " this badge to others." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:72 msgid "" ":guilabel:`No one, assigned through challenges`: this badge cannot be " "manually granted, it can only be awarded through challenges." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:75 msgid "" "To limit the number of badges a user can send, tick the :guilabel:`Monthly " "Limited Spending` checkbox. This sets a limit on the number of times a user " "can grant this badge. In the :guilabel:`Limitation Number` field, enter the " "maximum number of times this badge can be sent per month, per person." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst-1 msgid "The details page for a new badge." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:87 msgid "Create a challenge" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:89 msgid "" "To create a challenge, navigate to to :menuselection:`Settings --> " "Gamification Tools --> Challenges`. Click :guilabel:`New` in the top-left " "corner to open a blank challenge form." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:92 msgid "At the top of the form, enter a :guilabel:`Challenge Name`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:95 msgid "Create assignment rules" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:97 msgid "" "To assign the challenge to specific users, one or more assignment rules must" " be utilized." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:99 msgid "" "Click into the first field under :guilabel:`Assign Challenge to`, and select" " a parameter from the drop-down list to define the rule. Then, click into " "the next field to define the rule's operator. If necessary, click into the " "third field to further define the parameter." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:104 msgid "" "To include all users with permissions in the *Sales* app, create a rule with" " the following parameters:" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:107 msgid ":guilabel:`Groups`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:108 msgid ":guilabel:`is in`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:109 msgid "`Sales/User: Own Documents Only`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:0 msgid "View of the assignation rules section of a Challenge form." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:115 msgid "" "In the :guilabel:`Periodicity` field, select a time frame for goals to be " "automatically assessed." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:118 msgid "Add goals" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:120 msgid "" "Challenges can be based on a single goal, or can include multiple goals with" " different targets. To add a goal to the challenge, click :guilabel:`Add a " "line` on the :guilabel:`Goals` tab." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:123 msgid "" "In the :guilabel:`Goal Definition` field, choose a goal from the drop-down " "list. The :guilabel:`Condition` field automatically updates to reflect the " "condition set on the goal definition." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:128 msgid "" "The *CRM Gamification* module contains preconfigured goals geared towards " "salesteams:" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:130 msgid ":guilabel:`New Leads`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:131 msgid ":guilabel:`Time to Qualify a Lead`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:132 msgid ":guilabel:`Days to Close a Deal`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:133 msgid ":guilabel:`New Opportunities`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:134 msgid ":guilabel:`New Sales Orders`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:136 msgid "" "Enter a :guilabel:`Target` for the goal based on the :guilabel:`Suffix`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:138 msgid "Repeat these steps for each additional goal." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst-1 msgid "The goals tab of a challenge form." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:145 msgid "Add rewards" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:147 msgid "" "Next, click the :guilabel:`Reward` tab. Choose the :ref:`badges ` to be awarded :guilabel:`For 1st User` and :guilabel:`For Every " "Succeeding User` by selecting them from the drop-down lists." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:152 msgid "" "Badges are granted when a challenge is finished. This is either at the end " "of a running period, at the end date of a challenge, or when the challenge " "is manually closed." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:155 msgid "" "After setup is complete, click the :guilabel:`Start Challenge` button at the" " top-left of the page to begin the challenge." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:3 msgid "Lead enrichment" msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:5 msgid "" "*Lead enrichment* is a service that provides business information for a " "contact attached to a lead. Lead enrichment is an In-App Purchase (IAP) that" " requires credits to use, and is available for existing leads in an Odoo " "database." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:9 msgid "" "The information provided by lead enrichment can include general information " "about the business (including full business name and logo), social media " "accounts, :guilabel:`Company type`, :guilabel:`Founded` information, " ":guilabel:`Sectors` information, the number of :guilabel:`Employees`, " ":guilabel:`Estimated revenue`, :guilabel:`Phone` number, " ":guilabel:`Timezone`, and :guilabel:`Technologies Used`." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:16 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:78 msgid "" "Enterprise Odoo users with a valid subscription get free credits to test " ":abbr:`IAP (In-App Purchase)` features before deciding to purchase more " "credits for the database. This includes demo/training databases, educational" " databases, and one-app-free databases." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:21 msgid "" "The *leads* feature **must** be activated in the *CRM* settings page in " "order to use lead enrichment. To access the *CRM* settings, navigate to " ":menuselection:`CRM app --> Configuration --> Settings`. Under the " ":guilabel:`CRM` section activate the :guilabel:`Leads` option and click " ":guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:27 msgid "Lead enrichment set up" msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:29 msgid "" "To set up lead enrichment in the *CRM* application, navigate to " ":menuselection:`CRM app --> Configuration --> Settings`. Then, under the " ":guilabel:`Lead Generation` section, tick the checkbox next to " ":guilabel:`Lead Enrichment`, and select either :guilabel:`Enrich leads on " "demand only` or :guilabel:`Enrich all leads automatically`. Click the " ":guilabel:`Save` button to activate the changes." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst-1 msgid "" "CRM lead generation settings page, with lead enrichment activation highlighted, and enrich\n" "leads on demand only chosen." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:41 msgid "Enrich leads" msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:43 msgid "" "Enrichment of leads is based on the domain of the email address of the " "customer set on the lead. There are two different ways that a lead can be " "enriched: *automatically* or *manually*." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:47 msgid "Automatically enrich leads" msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:49 msgid "" "During set up, if :guilabel:`Enrich all leads automatically` was selected on" " the *CRM* :guilabel:`Settings` page, then no action needs to be taken by " "the user to enrich the lead. A scheduled action runs automatically, every " "sixty minutes, and enrichment occurs on leads, after a remote database is " "contacted." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:55 msgid "" "To access the cron that runs for the automatic lead enrichment, activate " ":ref:`developer mode `, and navigate to " ":menuselection:`Settings app --> Technical menu --> Automation section --> " "Scheduled Actions`. In the :guilabel:`Search...` bar, type in `CRM`. Click " "into the result labeled :guilabel:`CRM: enrich leads (IAP)`, and make any " "necessary adjustments. In the :guilabel:`Execute Every` field, enter a value" " greater than, or equal to, five minutes." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:62 msgid "" "The following is an example of lead enrichment data that has been " "autocompleted successfully:" msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:0 msgid "Chatter showing lead enrichment data." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:69 msgid "Manually enrich leads" msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:71 msgid "" "If the :guilabel:`Enrich leads on demand only` option was selected on the " "*CRM* :guilabel:`Settings` page, when activating :guilabel:`Lead " "Enrichment`, each lead that a user wishes to enrich **must** be manually " "enriched. This is achieved by clicking the :guilabel:`Enrich` button in the " "top menu of the lead." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:76 msgid "" "The same information will be retrieved at the same :abbr:`IAP (In-App " "Puchase)` credit cost (one per enrichment). This method of enrichment is " "useful when every lead does not need to be enriched, or cost is an issue." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst-1 msgid "Manual enrich button feature highlighted on the CRM lead." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:85 msgid "" "Manually enrich leads in bulk using the *list* view. First, navigate to " ":menuselection:`CRM app --> Leads`, and click the list view button " "(:guilabel:`☰ (three horizontal lines)` icon). Next, tick the checkboxes for" " the leads that should be manually enriched. Finally, click the " ":guilabel:`⚙️ Action` icon, and select :guilabel:`Enrich` from the resulting" " drop-down menu. This can also be achieved from the *My Pipeline* page. To " "do so, simply open the *CRM* app, or navigate to :menuselection:`CRM app -->" " Sales --> My Pipeline`. Either route reveals leads and opportunities on the" " :guilabel:`Pipeline` page." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:96 msgid "" "Lead enrichment is an In-App Purchase (IAP) feature, and each enriched lead " "costs one credit." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:99 msgid "" "See here for full pricing information: `Lead Generation by Odoo IAP " "`_." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:102 msgid "" "To buy credits, navigate to :menuselection:`CRM app --> Configuration --> " "Settings`. In the :guilabel:`Lead Generation` section, under the " ":guilabel:`Lead Enrichment` feature, click on :guilabel:`Buy Credits`." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst-1 msgid "Buy credits from the lead enrichment settings." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:110 msgid "" "Credits and balances may also be purchased by navigating to the " ":menuselection:`Settings app`. In the :guilabel:`Contacts` section, under " "the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`." msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:119 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:83 msgid ":doc:`../../../essentials/in_app_purchase`" msgstr "" #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:122 msgid "" "When collecting a company's contact information, make sure to be aware of " "the latest EU regulations. For more information about General Data " "Protection Regulation, refer to: `Odoo GDPR `__." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:3 msgid "Enrich contacts with partner autocomplete" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:5 msgid "" "*Partner autocomplete* enriches the contacts database with corporate data. " "In any module, enter the new company name into the :guilabel:`Customer` " "field (`partner_id` technical field), and select one of the companies " "suggested in the drop-down menu. Instantly get valuable company information " "full of hard-to-find data for a desired company." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:11 msgid "" "A company **cannot** already be manually entered in the *Contacts* " "application prior to enriching it with data." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:14 msgid "" "The information provided by partner autocomplete can include general " "information about the business (including full business name and logo), " "social media accounts, :guilabel:`Company type`, :guilabel:`Founded` " "information, :guilabel:`Sectors` information, the number of " ":guilabel:`Employees`, :guilabel:`Estimated revenue`, :guilabel:`Phone` " "number, :guilabel:`Timezone`, and :guilabel:`Technologies Used`." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:21 msgid "" "When getting a company's contact information make sure to be aware of the " "latest EU regulations. For more information about General Data Protection " "Regulation refer to: `Odoo GDPR `_. In Odoo, " "individual contact information cannot be searched for with the partner " "autocomplete feature." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:29 msgid "" "Go to :menuselection:`Settings app --> Contacts section`. Then, activate the" " :guilabel:`Partner Autocomplete` feature, by ticking the checkbox beside " "it, and clicking :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 msgid "View of settings page and the activations of the feature in Odoo." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:37 msgid "Enrich contacts with corporate data" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:39 msgid "" "From any module, as the user is typing in the name of a new company contact," " Odoo reveals a large drop-down menu of potential match suggestions. If any " "are selected, the contact is then populated with corporate data related to " "that specific selection." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:43 msgid "For example, after typing `Odoo`, the following information populates:" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 msgid "Creating a new contact in Odoo" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:49 msgid "" "In the chatter, the following information populates about the company, after" " clicking on the desired pre-populated contact:" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 msgid "" "View of the information being shown about odoo with the autocomplete option " "in Odoo" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:57 msgid "" "Partner Autocomplete also works if a :abbr:`VAT (value-added tax)` number is" " entered instead of company name." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:63 msgid "" "*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires" " prepaid credits to be used. Each request consumes one credit." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:66 msgid "" "To buy credits, go to :menuselection:`Settings app --> Contacts section`. " "Then, locate either the :guilabel:`Partner Autocomplete` feature and click " ":guilabel:`Buy credits`, or locate the :guilabel:`Odoo IAP` feature and " "click :guilabel:`View My Services`. From the resulting page, select a " "desired package." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:72 msgid "" "If the database runs out of credits, the only information populated when " "clicking on the suggested company will be the website link and the logo." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:75 msgid "Learn about our `Privacy Policy `_." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:3 msgid "Utilize activities for sales teams" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:5 msgid "" "*Activities* are follow-up tasks tied to a record in an *Odoo* database. " "Activities can be scheduled on any page of the database that contains a " "chatter thread, Kanban view, list view, or activities view of an " "application." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:13 msgid "" "The summary view of activities for leads and opportunities in an Odoo " "database." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:13 msgid "Planned Activities for Leads and Opportunities." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:16 msgid "Activity types" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:18 msgid "" "A set of preconfigured activity types is available in the *CRM* app. To view" " the list of available activity types, navigate to the :menuselection:`CRM " "app --> Configuration --> Activity Types`." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:22 msgid "" "Additional activity types are available within the database, and can be " "utilized through different applications. To access the complete list of " "activity types, go to the :menuselection:`Settings app`, then scroll to the " ":guilabel:`Discuss` section, and click :guilabel:`Activity Types`." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:27 msgid "The preconfigured activity types for the *CRM* app are as follows:" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:29 msgid "" ":guilabel:`Email`: adds a reminder to the chatter that prompts the " "salesperson to send an email." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:30 msgid "" ":guilabel:`Call`: opens a calendar link where the salesperson can schedule " "time to call the contact." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:32 msgid "" ":guilabel:`Meeting`: opens a calendar link where the salesperson can " "schedule time to have a meeting with the contact." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:34 msgid ":guilabel:`To Do`: adds a general reminder task to the chatter." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:35 msgid "" ":guilabel:`Upload Document`: adds a link on the activity where an external " "document can be uploaded. Note that the *Documents* app is **not** required " "to utilize this activity type." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:39 msgid "" "If other applications are installed, such as *Sales* or *Accounting*, other " "activity types are made available in the *CRM* app." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:45 msgid "Create a new activity type" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:47 msgid "" "To create a new activity type, click :guilabel:`New` at the top-left of the " "page to open a blank form." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:50 msgid "" "At the top of the form, start by choosing a :guilabel:`Name` for the new " "activity type." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:53 msgid "Activity settings" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:56 msgid "Action" msgstr "Dejanje" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:58 msgid "" "The *Action* field specifies the intent of the activity. Some actions " "trigger specific behaviors after an activity is scheduled." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:61 msgid "" "If :guilabel:`Upload Document` is selected, a link to upload a document is " "added directly to the planned activity in the chatter." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:63 msgid "" "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users " "have the option to open their calendar to schedule a time for this activity." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:65 msgid "" "If :guilabel:`Request Signature` is selected, a link is added to the planned" " activity in the chatter that opens a signature request pop-up window." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst-1 msgid "" "The Activity settings on a new activity type with emphasis on the Action " "field." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:73 msgid "" "The actions available to select on an activity type vary, depending on the " "applications currently installed in the database." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:77 msgid "Default user" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:79 msgid "" "To automatically assign this activity to a specific user when this activity " "type is scheduled, choose a name from the :guilabel:`Default User` drop-down" " menu. If this field is left blank, the activity is assigned to the user who" " creates the activity." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:84 msgid "Default summary" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:86 msgid "" "To include notes whenever this activity type is created, enter them into the" " :guilabel:`Default Summary` field." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:90 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/sales/crm/optimize/utilize_activities.rst:95 msgid "Next activity" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:97 msgid "" "To automatically suggest, or trigger, a new activity after an activity has " "been marked complete, the :guilabel:`Chaining Type` must be set." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:101 msgid "Suggest next activity" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:103 msgid "" "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next " "Activity`. Upon doing so, the field underneath changes to: " ":guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to " "select any activities to recommend as follow-up tasks to this activity type." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst-1 msgid "The Next Activity section on a new activity type form." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:111 #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:139 msgid "" "In the :guilabel:`Schedule` field, choose a default deadline for these " "activities. To do so, configure a desired number of :guilabel:`Days`, " ":guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur " ":guilabel:`after completion date` or :guilabel:`after previous activity " "deadline`." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:116 #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:144 msgid "" "This :guilabel:`Schedule` field information can be altered before the " "activity is scheduled." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:118 #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:146 msgid "When all configurations are complete, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:121 msgid "" "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest " "Next Activity`, and has activities listed in the :guilabel:`Suggest` field, " "users are presented with recommendations for activities as next steps." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:0 msgid "" "A schedule activity pop-up with emphasis on the recommended activities." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:130 msgid "Trigger next activity" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:132 msgid "" "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` " "immediately launches the next activity once the previous one is completed." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:135 msgid "" "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining " "Type` field, the field beneath changes to: :guilabel:`Trigger`. From the " ":guilabel:`Trigger` field drop-down menu, select the activity that should be" " launched once this activity is completed." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:149 msgid "" "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger" " Next Activity`, marking the activity as *Done* immediately launches the " "next activity listed in the :guilabel:`Trigger` field." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:154 msgid "Activity tracking" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:156 msgid "" "To keep the pipeline up to date with the most accurate view of the status of" " activities, as soon as a lead is interacted with, the associated activity " "should be marked as *Done*. This ensures the next activity can be scheduled " "as needed. It also prevents the pipeline from becoming cluttered with past " "due activities." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:161 msgid "" "The pipeline is most effective when it is kept up-to-date and accurate to " "the interactions it is tracking." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:167 msgid "Activity plans" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:169 msgid "" "*Activity plans* are preconfigured sequences of activities. When an activity" " plan is launched, every activity in the sequence is scheduled " "automatically." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:172 msgid "" "To create a new plan, navigate to :menuselection:`CRM app --> Configuration " "--> Activity Plan`. Click :guilabel:`New` at the top-left of the page to " "open a blank :guilabel:`Lead Plans` form." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:175 msgid "" "Enter a name for the new plan in the :guilabel:`Plan Name` field. On the " ":guilabel:`Activities to Create` tab, click :guilabel:`Add a line` to add a " "new activity." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:178 msgid "" "Select an :guilabel:`Activity Type` from the drop-down menu. Click " ":guilabel:`Search More` to see a complete list of available activity types, " "or to create a :ref:`new one `." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:182 msgid "" "Next, in the :guilabel:`Summary` field, enter any details to describe the " "specifics of the activity, including instructions for the salesperson or " "information due upon the completion of the activity. The contents of this " "field are included with the scheduled activity, and can be edited later." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:186 msgid "" "In the :guilabel:`Assignment` field, select one of the following options:" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:188 msgid "" ":guilabel:`Ask at launch`: activities are assigned to a user when the plan " "is scheduled." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:189 msgid "" ":guilabel:`Default user`: activities are always assigned to a specific user." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:191 msgid "" "If :guilabel:`Default user` is selected in the :guilabel:`Assignment` field," " choose a user in the :guilabel:`Assigned to` field." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:195 msgid "" "Activity plans can feature activities that are assigned to default users and" " users assigned at the plan launch." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:0 msgid "A Lead Plan form with scheduled activities." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:202 msgid "" "Next, configure the timeline for the activity. Activities can be scheduled " "to occur either before the plan date or after. Use the :guilabel:`Interval` " "and :guilabel:`Units` fields to set the deadline for this activity. Lastly, " "in the :guilabel:`Trigger` field, select whether the activity should occur " "before or after the plan date." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:208 msgid "" "An activity plan is created to handle high priority leads. Specifically, " "these leads should be contacted quickly, with a meeting scheduled within two" " days of the initial contact. The plan is configured with the following " "activities:" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:212 msgid "Email two days **before** plan date" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:213 msgid "Meeting zero days **before** plan date" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:214 msgid "Make quote three days **after** plan date" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:215 msgid "Upload document three days **after** plan date" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:216 msgid "Follow-up five days **after** plan date" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:218 msgid "" "This sets the *plan date* as the meeting deadline, which is the objective of" " the plan. Before that date, there is lead time to contact the customer and " "prepare for the meeting. After that date, the salesperson has time to create" " a quote, upload the document, and follow-up." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:222 msgid "Repeat these steps for each activity included in the plan." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:225 msgid "Launch an activity plan" msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:227 msgid "" "To launch an activity plan on a *CRM* opportunity, navigate to " ":menuselection:`CRM app` and click on the Kanban card of an opportunity to " "open it." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:230 msgid "" "At the top-right of the chatter, click :guilabel:`Activities` to open the " ":guilabel:`Schedule Activity` pop-up window." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:233 msgid "" "In the :guilabel:`Plan` field, select the desired activity plan to launch. " "This generates a :guilabel:`Plan summary`, listing out the activities " "included in the plan. Select a :guilabel:`Plan Date` using the calendar " "popover. This updates the :guilabel:`Plan summary` with deadlines based on " "the intervals configured on the :ref:`activity plan `." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:238 msgid "" "Select a user in the :guilabel:`Assigned To` field. This user is assigned to" " any of the activities on the plan were configured with :guilabel:`Ask at " "launch` in the :guilabel:`Assignment` field." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst-1 msgid "The schedule activity pop-up window with an Activity plan selected." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:245 msgid "Click :guilabel:`Schedule`." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:247 msgid "" "The details of the plan are added to the chatter, in addition to each of the" " activities." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst-1 msgid "The chatter thread of a CRM opportunity with a launched activity plan." msgstr "" #: ../../content/applications/sales/crm/optimize/utilize_activities.rst:254 msgid ":doc:`Activities `" msgstr "" #: ../../content/applications/sales/crm/performance.rst:5 msgid "Analyze performance" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:3 msgid "Expected revenue report" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:5 msgid "" "*Expected revenue* is the total cash value of leads that are expected to " "close by a certain date, usually the end of the current month." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:8 msgid "" "An *expected revenue report* compiles all active leads in a sales pipeline " "that have a set expected closing date, and compares how sales teams are " "performing in a given time frame." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst-1 msgid "Close up of the expected closing date on a lead in the CRM app." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:15 msgid "" "By pulling a monthly expected revenue report, sales managers can see which " "team members are reaching their goals, and who may need additional " "assistance to close valuable deals." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:19 msgid "Create an expected revenue report" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:21 msgid "" "To create an expected revenue report, first navigate to :menuselection:`CRM " "app --> Reporting --> Pipeline`. This opens the :guilabel:`Pipeline " "Analysis` dashboard." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:25 msgid "" "The *Pipeline Analysis* dashboard includes several filters in the search bar" " by default. Remove these before adding any additional custom filters." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:28 msgid "" "On the top-left of the report, click :guilabel:`Measures`, then select " ":guilabel:`Expected Revenue` from the drop-down menu." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:31 msgid "" "At the top of the page, click the :guilabel:`🔻(triangle pointed down)` icon " "to the right of the :guilabel:`Search...` bar to open the drop-down menu " "that contains :guilabel:`Filters`, :guilabel:`Group By`, and " ":guilabel:`Favorites` columns. Under the :guilabel:`Filters` column, click " ":guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` " "pop-up window." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:39 #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:53 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:68 msgid "Add custom filters" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:41 msgid "" "In order to generate an expected revenue report, filters need to be created " "for the following conditions:" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:44 msgid "" ":ref:`Expected closing date `: limits " "results to only include leads expected to close within a specific time " "frame." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:46 msgid "" ":ref:`Exclude unassigned leads `: " "excludes leads without an assigned salesperson." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:48 msgid "" ":ref:`Specific sales teams `: limits " "results to only include leads assigned to one or more sales teams. This " "filter is optional and should not be included if the report is intended for " "the entire company." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:55 msgid "Add filter for expected closing date" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:57 msgid "" "On the :guilabel:`Add Custom Filter` pop-up window, click into the first " "field of the new rule. Type `Expected Closing` into the " ":guilabel:`Search...` bar, or scroll to select it from the list. Click in " "the second field and select :guilabel:`is set`. This limits the results to " "only include leads where an estimated closing date is listed." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:62 msgid "" "Next, click the :guilabel:`➕ (plus)` icon to the right of the rule to " "duplicate it." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:65 msgid "" "Using the :guilabel:`➕ (plus)` icon makes it easy to add multiple rules " "based on the same filter." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:68 msgid "" "In the second field of the new rule, select :guilabel:`is between` from the " "drop-down menu. This creates a set time frame during which the expected " "closing date must occur for leads to be included in the results." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:72 msgid "" "Click in each date field, one at a time, and use the calendar popover window" " to add both a start and end date to the rule. This is usually the beginning" " and ending of the current month, or fiscal quarter." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:79 #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:117 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:107 msgid "Exclude unassigned leads" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:81 msgid "" "After filtering for the expected closing date, add a :guilabel:`New Rule`. " "Then, click into the new rule's first field, and type `Salesperson` in the " ":guilabel:`Search...` bar, or scroll through the list to select it. Click in" " the rule's second field and select :guilabel:`is set` from the drop-down " "menu. This excludes any results without an assigned salesperson." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:89 msgid "Add a filter for sales teams" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:92 msgid "" "This filter is optional. To view results for the entire company, do **not** " "add this filter, and continue to :ref:`View results " "`." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:95 #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:103 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:125 msgid "" "To limit the results of the report to one or more sales teams, click " ":guilabel:`New Rule`. Next, click the first field for the new rule, and type" " `Sales Team` in the :guilabel:`Search...` bar, or scroll to search through " "the list to locate it." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:99 msgid "" "In the rule's second field, select :guilabel:`is in` from the drop-down " "menu. Selecting this operator limits results to the sales teams indicated in" " the next field." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:102 msgid "" "Lastly, click into the third field, and either: make a selection from the " "complete list revealed in the popover menu, or type the first few characters" " of the specific sales team's title to quickly find and select it as a " "parameter." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:107 msgid "" "Multiple teams can be added to the `Sales Team` rule, where each parameter " "is treated with an \"or\" (e.g. \"any\") operator in the search logic." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst-1 msgid "" "Add Custom Filters pop-up window with custom filters configured for expected revenue\n" "report." 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 #: ../../content/applications/sales/members/members_analysis.rst:39 msgid "View results" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:120 #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:193 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:147 msgid "" "At the top of the :guilabel:`Add Custom Filter` form, there is an option to " "match :guilabel:`any` or :guilabel:`all` of the rules. In order to properly " "run the report, only records that match **all** of the following filters " "should be included. Before adding the filters, make sure :guilabel:`all` is " "selected in this field." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst-1 msgid "" "Emphasis on the match all filters option on the Add Custom Filter pop-up " "window." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:129 msgid "" "At the bottom of the :guilabel:`Add Custom Filter` form, click " ":guilabel:`Add`." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:132 #: ../../content/applications/sales/crm/performance/win_loss.rst:279 msgid "View options" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:134 msgid "" "The expected revenue report benefits from utilizing multiple views. The " "default graph view can be used to identify which salespeople are expected to" " bring in the most revenue, while the list view and pivot view provide more " "detail on specific deals." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:140 #: ../../content/applications/sales/subscriptions/reports.rst:92 msgid "Graph view" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:142 msgid "" "The *graph view* is used to visualize data, and is beneficial in identifying" " patterns and trends." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:145 msgid "" "*Bar charts* are used to show the distribution of data across several " "categories or among several salespeople." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:148 msgid "" "*Line charts* are useful to show changing trends over a period of time." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:150 msgid "" "*Pie charts* are useful to show the distribution, or comparison, of data " "among a small number of categories or salespeople, specifically how they " "form the meaningful part of a whole picture." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:154 msgid "" "The default view for the expected revenue report is the bar chart, stacked. " "To change to a different graph view, click one of the icons at the top-left " "of the report. While both the line chart and bar chart are available in " "stacked view, the pie chart is not." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 msgid "" "Close up view of the graph icons on the Pipeline analysis report in the CRM " "app." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:162 msgid "Graph view icons in order: bar chart, line chart, pie chart, stacked." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:164 #: ../../content/applications/sales/subscriptions/reports.rst:131 msgid "List view" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:166 msgid "" "The *list view* provides a list of all leads that are expected to close by " "the designated date. Clicking on a lead in list view opens the record for " "detailed analysis, but many insights can be gleaned from the basic view." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:170 msgid "" "To switch to the list view, click the :guilabel:`≣ (list)` icon at the top-" "right of the report." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 msgid "Close up of the list view icon in the CRM app." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:177 msgid "" "To add additional metrics to the report, click the *additional options menu*" " indicated by the :guilabel:`toggle` icon at the top-right of the list." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 msgid "Close up of the toggle icon in the CRM app." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:184 msgid "" "Clicking the toggle icon in *list view* opens the *additional options menu*." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:186 msgid "" "Select any additional metrics from the drop-down menu to add them to the " "list view. Some options that may be useful are :guilabel:`Expected Closing` " "and :guilabel:`Probability`." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:189 #: ../../content/applications/sales/subscriptions/reports.rst:143 msgid "Pivot view" msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:191 msgid "" "The *pivot view* arranges all leads that are expected to close by the " "designated date into a dynamic table." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:194 msgid "" "To switch to the pivot view, click the :guilabel:`Pivot` icon at the top-" "right of the report." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 msgid "Close up of the pivot view icon in the CRM app." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:200 msgid "" "When the pivot view is selected for this report, the X-axis lists the stages" " in the pipeline, while the Y-axis defaults to group the results by their " "creation date. To switch these groupings, click the flip access icon " "(:guilabel:`⇄`) at the top of the report." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:204 msgid "" "To add additional measures to the report, click the :guilabel:`Measures` " "button at the top-left of the report. Select any additional metrics from the" " drop-down menu." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:207 msgid "" "To add a group to a row or column to the pivot view, click the :guilabel:`➕ " "(plus sign)` next to :guilabel:`Total`, and then select one of the groups. " "To remove one, click the :guilabel:`➖ (minus sign)` and de-select the " "appropriate option." msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:211 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 #: ../../content/applications/sales/members/members_analysis.rst:49 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 "Analiza prodajnega toka" #: ../../content/applications/sales/crm/performance/win_loss.rst:5 msgid "" "The *CRM* app manages the sales pipeline as leads/opportunities move from " "stage to stage, origination to sale (**Won**) or archival (**Lost**)." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:8 msgid "" "After organizing the pipeline, use the search options and reports available " "on the *Pipeline Analysis* page to gain insight into the effectiveness of " "the pipeline and its users." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:11 msgid "" "To access the *Pipeline Analysis* page, go to :menuselection:`CRM app --> " "Reporting --> Pipeline`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "Open the CRM app and click on the Reporting tab along the top, then click " "Pipeline." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:20 msgid "Navigate the pipeline analysis page" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:22 msgid "" "Upon accessing the :guilabel:`Pipeline Analysis` page, a bar graph " "showcasing the leads from the past year automatically populates. The bars " "represent the number of leads in each stage of the sales pipeline, color-" "coded to show the month the lead reached that stage." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "The default state of the Pipeline Analysis page is a graph, with many " "options to change it." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:30 msgid "" "The interactive elements of the :guilabel:`Pipeline Analysis` page " "manipulate the graph to report different metrics in several views. From " "left-to-right, top-to-bottom, the elements include:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:33 msgid "" ":guilabel:`Actions`: represented by the :guilabel:`⚙️ (gear)` icon, located " "next to the :guilabel:`Pipeline Analysis` page title. When clicked, a drop-" "down menu appears with three options, each with their own sub-menu: " ":guilabel:`Knowledge`, :guilabel:`Dashboard`, :guilabel:`Spreadsheet`. (See " ":ref:`Save and share reports ` for more information)" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:39 msgid "" "The :guilabel:`Knowledge` option is for linking to or inserting the graph in" " a *Knowledge* app article." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:41 msgid "" "The :guilabel:`Dashboard` option is for adding the graph to a dashboard in " "the *Dashboards* app." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:42 msgid "" "The :guilabel:`Spreadsheet` option is for linking the graph in a spreadsheet" " in the *Documents* app." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:44 msgid "" ":guilabel:`Search...` bar: shows the filters and groupings currently being " "applied to the graph. To add new filters/groups, type them into the search " "bar, or click the :guilabel:`⬇️ (down arrow)` icon, at the end of the bar, " "to open a drop-down menu of options. (See :ref:`Search Options " "` for more information)" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:49 msgid "" "In the upper-right corner, there are view options represented by different " "icons. (See :ref:`View Options ` for more information)" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:52 msgid "" ":guilabel:`Graph` view: displays the data in a bar graph. This is the " "default view." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:53 msgid "" ":guilabel:`Pivot` view: displays the data in a customizable, categorized " "metrics table." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:54 msgid "" ":guilabel:`Cohort` view: displays and organizes the data, based on their " ":guilabel:`Created on` and :guilabel:`Closed Date` week (default), day, " "month, or year." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:56 msgid ":guilabel:`List` view: displays the data in a list." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:58 msgid "" "Located on the far-left side of the page, beneath the :guilabel:`Pipeline " "Analysis` page title, there are more configurable filter and view options." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:61 msgid "" ":guilabel:`Measures`: opens a drop-down menu of different measurement " "options that can be seen in the graph, pivot, or cohort view. The " ":guilabel:`Measure` drop-down menu is not available in the list view. (See " ":ref:`Measurement Options ` for more information)" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:64 msgid "" ":guilabel:`Insert in Spreadsheet`: opens a pop-up window with options for " "adding a graph or pivot table to a spreadsheet in the *Documents* app or a " "dashboard in the *Dashboards* app. This option is not available in the " "cohort or list view." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:68 msgid "With the graph view selected, the following options are available:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:70 msgid ":guilabel:`Bar Chart`: switches the graph to a bar chart." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:71 msgid ":guilabel:`Line Chart`: switches the graph to a line chart." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:72 msgid ":guilabel:`Pie Chart`: switches the graph to a pie chart." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:73 msgid "" ":guilabel:`Stacked`: when selected, the results of each stage of the graph " "are stacked on top of each other. When not selected, the results in each " "stage are shown as individual bars." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:75 msgid "" ":guilabel:`Descending`: re-orders the stages in the graph in descending " "order from left-to-right. Click the icon a second time to deselect it. " "Depending on the search criteria, this option may not be available." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:78 msgid "" ":guilabel:`Ascending`: re-orders the stages in the graph in ascending order " "from left-to-right. Click the icon a second time to deselect it. Depending " "on the search criteria, this option may not be available." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:82 msgid "With the pivot view selected, the following options are available:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:84 #: ../../content/applications/sales/crm/performance/win_loss.rst:326 msgid ":guilabel:`Flip Axis`: flips the X and Y axis for the entire table." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:85 #: ../../content/applications/sales/crm/performance/win_loss.rst:327 msgid "" ":guilabel:`Expand All`: when additional groupings are selected using the " ":guilabel:`➕ (plus sign)` icons, this button opens those groupings under " "every row." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:87 #: ../../content/applications/sales/crm/performance/win_loss.rst:329 msgid ":guilabel:`Download xlsx`: downloads the table as an Excel file." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:92 msgid "Search options" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:94 msgid "" "The :guilabel:`Pipeline Analysis` page can be customized with various " "filters and grouping options." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:96 msgid "" "To add new search criteria, type the desired criteria into the search bar, " "or click the :guilabel:`⬇️ (down arrow)` icon, next to the search bar, to " "open a drop-down menu of all options. See the sections below for more " "information on what each option does." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "Clicking on the down arrow next to the search bar opens a menu of filters " "for the analysis." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:106 msgid "Filters" msgstr "Filtri" #: ../../content/applications/sales/crm/performance/win_loss.rst:108 msgid "" "The :guilabel:`Filters` section allows users to add pre-made and custom " "filters to the search criteria. Multiple filters can be added to a single " "search." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:111 msgid ":guilabel:`My Pipeline`: show leads assigned to the current user." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:112 msgid "" ":guilabel:`Opportunities`: show leads that have been qualified as " "opportunities." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:113 msgid "" ":guilabel:`Leads`: show leads that have yet to be qualified as " "opportunities." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:114 msgid ":guilabel:`Active`: show active leads." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:115 msgid ":guilabel:`Inactive`: show inactive leads." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:116 msgid ":guilabel:`Won`: show leads that have been marked **Won**." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:117 msgid ":guilabel:`Lost`: show leads that have been marked **Lost**." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:118 msgid "" ":guilabel:`Created On`: show leads that were created during a specific " "period of time. By default, this is the past year, but it can be adjusted as" " needed, or removed entirely." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:120 msgid "" ":guilabel:`Expected Closing`: show leads that are expected to close (marked " "**Won**) during a specific period of time." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:122 msgid "" ":guilabel:`Date Closed`: show leads that were closed (marked **Won**) during" " a specific period of time." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:124 msgid "" ":guilabel:`Archived`: show leads that have been archived (marked **Lost**)." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:125 msgid "" ":guilabel:`Add Custom Filter`: allows the user to create a custom filter " "with numerous options. (See :ref:`Add Custom Filters and Groups " "` for more information)" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:129 msgid "Group By" msgstr "Združi po" #: ../../content/applications/sales/crm/performance/win_loss.rst:131 msgid "" "The :guilabel:`Group By` section allows users to add pre-made and custom " "groupings to the search results. Multiple groupings can be added to split " "results into more manageable chunks." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:135 msgid "" "The order that groupings are added affects how the final results are " "displayed. Try selecting the same combinations in a different order to see " "what works best for each use case." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:139 msgid "" ":guilabel:`Salesperson`: groups the results by the Salesperson to whom a " "lead is assigned." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:140 msgid "" ":guilabel:`Sales Team`: groups the results by the Sales Team to whom a lead " "is assigned." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:141 msgid "" ":guilabel:`City`: groups the results by the city from which a lead " "originated." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:142 msgid "" ":guilabel:`Country`: groups the results by the country from which a lead " "originated." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:143 msgid "" ":guilabel:`Company`: groups the results by the company to which a lead " "belongs (if multiple companies are activated in the database)." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:145 msgid "" ":guilabel:`Stage`: groups the results by the stages of the sales pipeline." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:146 msgid "" ":guilabel:`Campaign`: groups the results by the marketing campaign from " "which a lead originated." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:148 msgid "" ":guilabel:`Medium`: groups the results by the medium (Email, Google Adwords," " Website, etc.) from which a lead originated." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:150 msgid "" ":guilabel:`Source`: groups the results by the source (Search engine, Lead " "Recall, Newsletter, etc.) from which a lead originated." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:152 msgid "" ":guilabel:`Creation Date`: groups the results by the date a lead was added " "to the database." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:153 msgid "" ":guilabel:`Conversion Date`: groups the results by the date a lead was " "converted to an opportunity." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:155 msgid "" ":guilabel:`Expected Closing`: groups the results by the date a lead is " "expected to close (marked \"Won\")." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:157 msgid "" ":guilabel:`Closed Date`: groups the results by the date a lead was " "closed(marked \"Won\")." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:158 msgid "" ":guilabel:`Lost Reason`: groups the results by the reason selected when a " "lead was marked \"Lost.\"" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:160 msgid "" ":guilabel:`Add Custom Group`: allows the user to create a custom group with " "numerous options. (See :ref:`Adding Custom Filters and Groups " "` for more information)" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:164 msgid "Comparison" msgstr "Primerjava" #: ../../content/applications/sales/crm/performance/win_loss.rst:166 msgid "" "The :guilabel:`Comparison` section allows users to add comparisons to the " "same search criteria over another period of time." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:169 msgid "" "This option is only available if the search includes time-based filters, " "such as :guilabel:`Created On`, :guilabel:`Expected Closing`, or " ":guilabel:`Date Closed`. While multiple time-based filters can be added at " "once, only one comparison can be selected at a time." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:174 msgid "" ":guilabel:`Previous Period`: adds a comparison to the same search criteria " "from the previous period." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:176 msgid "" ":guilabel:`Previous Year`: adds a comparison to the same search criteria " "from the previous year." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:179 msgid "Favorites" msgstr "Priljubljene" #: ../../content/applications/sales/crm/performance/win_loss.rst:181 msgid "" "The :guilabel:`Favorites` section allows users to save a search for later, " "so it does not need to be recreated every time." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:184 msgid "" "Multiple searches can be saved, shared with others, or even set as the " "default for whenever the :guilabel:`Pipeline Analysis` page is opened." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:187 msgid "" ":guilabel:`Save current search`: save the current search criteria for later." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:189 msgid "" ":guilabel:`Default filter`: when saving a search, check this box to make it " "the default search filter when the :guilabel:`Pipeline Analysis` page is " "opened." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:191 msgid "" ":guilabel:`Shared`: when saving a search, check this box to make it " "available to other users." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:197 msgid "Add custom filters and groups" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:199 msgid "" "In addition to the pre-made options in the search bar, the " ":guilabel:`Pipeline Analysis` page can also utilize custom filters and " "groups." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:202 msgid "" "Custom filters are complex rules that further customize the search results, " "while custom groups display the information in a more organized fashion." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:205 msgid "**To add a custom filter:**" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:207 msgid "" "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`down arrow` " "icon next to the :guilabel:`Search...` bar." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:209 msgid "In the drop-down menu, click :guilabel:`Add Custom Filter`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:210 msgid "" "The :guilabel:`Add Custom Filter` pop-up window appears with a default rule " "(:guilabel:`Country is in _____`) comprised of three unique fields. These " "fields can be edited to make a custom rule, and multiple rules can be added " "to a single custom filter." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:213 msgid "" "To edit a rule, start by clicking the first field (:guilabel:`Country`), and" " select an option from the drop-down menu. The first field determines the " "primary subject of the rule." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:215 msgid "" "Next, click the second field, and select an option from the drop-down menu. " "The second field determines the relationship of the first and third fields, " "and is usually an **is** or **is not** statement, but can also be **greater " "than or less than** statements, and more." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:218 msgid "" "Finally, click the third field, and select an option from the drop-down " "menu. The third field determines the secondary subject of the rule." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:220 msgid "With all three fields selected, the rule is complete." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:222 msgid "" "**To add more rules:** click :guilabel:`New Rule` and repeat steps 4-7, as " "needed." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:223 msgid "" "**To delete a rule:** click the :guilabel:`🗑️ (trash)` icon to the right of " "the rule." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:224 msgid "" "**To duplicate an existing rule:** click the :guilabel:`➕ (plus sign)` icon " "to the right of the rule." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:226 msgid "" "**To create more complex rules:** click the :guilabel:`Add branch` icon to " "the right of the rule. This adds another modifier below the rule for adding " "an \"all of\" or \"any of\" statement." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "The add branch feature allows the creation of more complex all or any " "statements for rules." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:233 msgid "" "Once all rules have been added, click :guilabel:`Add` to add the custom " "filter to the search criteria." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:236 msgid "" "**To remove a custom filter:** click the :guilabel:`✖️ (x)` icon beside the " "filter in the search bar." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:239 msgid "**To add a custom group:**" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:241 msgid "" "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`down arrow` " "icon next to the search bar." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:243 msgid "" "In the drop-down menu that appears, click :guilabel:`Add Custom Group`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:244 msgid "" "Scroll through the options in the drop-down menu, and select one or more " "groups." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:246 msgid "" "**To remove a custom group:** click the :guilabel:`✖️ (x)` icon beside the " "custom group in the search bar." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:252 msgid "Measurement options" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:254 msgid "" "By default, the :guilabel:`Pipeline Analysis` page measures the total " ":guilabel:`Count` of leads that match the search criteria, but can be " "changed to measure other items of interest." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:257 msgid "" "To change the selected measurement, click the :guilabel:`Measures` button on" " the top-left of the page, and select one of the following options from the " "drop-down menu:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:260 msgid "" ":guilabel:`Days to Assign`: measures the number of days it took a lead to be" " assigned after creation." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:262 msgid "" ":guilabel:`Days to Close`: measures the number of days it took a lead to be " "closed (marked **Won**)." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:264 msgid "" ":guilabel:`Days to Convert`: measures the number of days it took a lead to " "be converted to an opportunity." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:266 msgid "" ":guilabel:`Exceeded Closing Days`: measures the number of days by which a " "lead exceeded its Expected Closing date." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:268 msgid "" ":guilabel:`Expected MRR`: measures the Expected Recurring Revenue of a lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:269 msgid ":guilabel:`Expected Revenue`: measures the Expected Revenue of a lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:270 msgid "" ":guilabel:`Prorated MRR`: measures the Prorated Monthly Recurring Revenue of" " a lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:271 msgid "" ":guilabel:`Prorated Recurring Revenues`: measures the Prorated Recurring " "Revenues of a lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:272 msgid ":guilabel:`Prorated Revenue`: measures the Prorated Revenue of a lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:273 msgid "" ":guilabel:`Recurring Revenues`: measures the Recurring Revenue of a lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:274 msgid "" ":guilabel:`Count`: measures the total amount of leads that match the search " "criteria." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:281 msgid "" "After configuring filters, groupings, and measurements, the " ":guilabel:`Pipeline Analysis` page can display the data in a variety of " "ways. By default, the page uses the graph view, but can be changed to a " "pivot view, cohort view, or list view." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:285 msgid "" "To change the pipeline to a different view, click one of the four view " "icons, located in the top-right of the :guilabel:`Pipeline Analysis` page." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:290 msgid "Graph View" msgstr "Grafični prikaz" #: ../../content/applications/sales/crm/performance/win_loss.rst:292 msgid "" "The graph view is the default selection for the :guilabel:`Pipeline " "Analysis` page. It displays the analysis as either a: bar chart, line chart," " or pie chart." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:295 msgid "" "This view option is useful for quickly visualizing and comparing simple " "relationships, like the :guilabel:`Count` of leads in each stage, or the " "leads assigned to each :guilabel:`Salesperson`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:299 msgid "" "By default, the graph measures the :guilabel:`Count` of leads in each group," " but this can be changed by clicking the :guilabel:`Measures` button, and " ":ref:`selecting another option ` from the resulting drop-" "down menu." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "The Graph View displays the analysis as a Bar Chart, Line Chart, or Pie " "Chart." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:308 msgid "" "When using a bar chart in this view, consider deselecting the " ":guilabel:`Stacked` option, in order to make the breakdown of results more " "legible." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:311 #: ../../content/applications/sales/crm/performance/win_loss.rst:512 msgid "Pivot View" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:313 msgid "" "The pivot view displays the results of the analysis as a table. By default, " "the table groups the results by the stages of the sales pipeline, and " "measures :guilabel:`Expected Revenue`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:316 msgid "" "The pivot view is useful for analyzing more detailed numbers than the graph " "view can handle, or for adding the data to a spreadsheet, where custom " "formulas can be set up, like in an Excel file." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Pivot View displays the analysis as a table." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:324 msgid "" "The three icons at the top-left of the page perform the following functions:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:332 msgid "" "The :guilabel:`Stage` grouping cannot be removed, but the measurement can be" " changed by clicking the :guilabel:`Measures` button, and selecting another " "option." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:335 msgid "Cohort View" msgstr "Kohortni pogled" #: ../../content/applications/sales/crm/performance/win_loss.rst:337 msgid "" "The cohort view displays the analysis as periods of time (cohorts) that can " "be set to days, weeks, months, or years. By default, :guilabel:`Week` is " "selected." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:340 msgid "" "This view option is useful specifically for comparing how long it has taken " "to close leads." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Cohort View displays the analysis as individual weeks of the year." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:346 msgid "" "From left-to-right, top-to-bottom, the columns in the chart represent the " "following:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:348 msgid "" ":guilabel:`Created On`: rows in this column represent the weeks of the year," " in which records matching the search criteria exist." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:351 msgid "" "When set to :guilabel:`Week`, a row with the label :guilabel:`W52 2023` " "means the results occurred in: Week 52 of the Year 2023." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:353 msgid "" ":guilabel:`Measures`: the second column in the chart is the measurement of " "the results. By default, it is set to :guilabel:`Count`, but can be changed " "by clicking the :guilabel:`Measures` button, and selecting an option from " "the drop-down menu." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:356 msgid "" ":guilabel:`Closed Date - By Day/Week/Month/Year`: this column looks at what " "percentage of the measured results were closed in subsequent " "days/weeks/months/years." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:358 msgid "" ":guilabel:`Average`: this row provides the average of all other rows in the " "column." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:360 msgid "" "The cohort view can also be downloaded as an Excel file, by clicking the " ":guilabel:`Download` icon in the top-left of the page." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:363 #: ../../content/applications/sales/crm/performance/win_loss.rst:537 msgid "List View" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:365 msgid "" "The list view displays a single list of all leads matching the search " "criteria. Clicking a lead opens the record for closer review. Additional " "details such as :guilabel:`Country`, :guilabel:`Medium`, and more can be " "added to the list, by clicking the :guilabel:`Filters` icon in the top-right" " of the list." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:370 msgid "This view option is useful for reviewing many records at once." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "The List View displays a single list of all records matching the search " "criteria." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:376 msgid "" "Clicking the :guilabel:`⚙️ (gear)` icon opens the Actions drop-down menu, " "with options for the following:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:379 msgid "" ":guilabel:`Import records`: opens a page for uploading a spreadsheet of " "data, as well as a template spreadsheet to easily format that data." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:381 msgid ":guilabel:`Export All`: downloads the list as an xlsx file for Excel." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:382 msgid "" ":guilabel:`Knowledge`: inserts a view of, or link to, the list in an article" " in the *Knowledge* app." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:384 msgid "" ":guilabel:`Dashboard`: adds the list to *My Dashboard* in the *Dashboards* " "app." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:385 msgid "" ":guilabel:`Spreadsheet`: links to, or inserts, the list in a spreadsheet in " "the *Documents* app." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:389 msgid "" "On the list view, clicking :guilabel:`New` closes the list, and opens the " "*New Quotation* page. Clicking :guilabel:`Generate Leads` opens a pop-up " "window for lead generation. Neither feature is intended to manipulate the " "list view." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:396 #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:77 msgid "Create reports" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:398 msgid "" "After understanding how to :ref:`navigate the pipeline analysis page " "`, the :guilabel:`Pipeline Analysis` page can be used to " "create and share different reports. Between the pre-made options and custom " "filter and groupings, almost any combination is possible." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:402 msgid "" "Once created, reports can be :ref:`saved to favorites, shared with other " "users, and/or added to dashboards and spreadsheets `." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:405 msgid "" "A few common reports that can be created using the :guilabel:`Pipeline " "Analysis` page are detailed below." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:411 msgid "Win/Loss reports" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:413 msgid "" "Win/Loss is a calculation of active or previously active leads in a pipeline" " that were either marked as **Won** or **Lost** over a specific period of " "time. By calculating opportunities won over opportunities lost, teams can " "clarify key performance indicators (KPIs) that are converting leads into " "sales, such as specific teams or team members, certain marketing mediums or " "campaigns, and so on." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:419 msgid "" "\\begin{equation}\n" "Win/Loss Ratio = \\frac{Opportunities Won}{Opportunities Lost}\n" "\\end{equation}\n" "\n" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:424 msgid "" "A win/loss report filters the leads from the past year, whether won or lost," " and groups the results by their stage in the pipeline. Creating this report" " requires a custom filter, and grouping the results by :guilabel:`Stage`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "The search criteria for win/loss reports is Created On, Stage, and Active is" " in true false." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:432 msgid "Follow the steps below to create a win/loss report:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:434 msgid "Navigate to :menuselection:`CRM app --> Reporting --> Pipeline`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:435 msgid "" "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down " "arrow)` icon, next to the search bar, to open a drop-down menu of filters " "and groupings." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Search menu containing the filters for a basic win/loss report." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:442 msgid "" "In drop-down menu that appears, under the :guilabel:`Group By` heading, " "click :guilabel:`Stage`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:443 msgid "" "Under the :guilabel:`Filters` heading, click :guilabel:`Add Custom Filter` " "to open another pop-up menu." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:445 msgid "" "In the :guilabel:`Add Custom Filter` pop-up menu, click on the first field " "in the :guilabel:`Match any of the following rules:` section. By default, " "this field displays :guilabel:`Country`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:448 msgid "" "Clicking that first field reveals a sub-menu with numerous options to choose" " from. From this sub-menu, locate and select the :guilabel:`Active` option. " "Doing so automatically populates the remaining fields." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:452 msgid "" "The first field reads: :guilabel:`Active`. The second field reads: " ":guilabel:`is`. And lastly, the third field reads: :guilabel:`set`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:455 msgid "In total, the rule reads: :guilabel:`Active is set`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:456 msgid "" "Click :guilabel:`New Rule`, change the first field to :guilabel:`Active`, " "and the last field to :guilabel:`not set`. In total, the rule reads " ":guilabel:`Active is not set`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:458 #: ../../content/applications/sales/crm/performance/win_loss.rst:640 msgid "Click :guilabel:`Add`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "The Add Custom Filter menu showing two rules: (1) Active is set, and (2) " "Active is not set." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:464 msgid "" "The report now displays the total :guilabel:`Count` of leads, whether " "\"Won\" or \"Lost,\" grouped by their stage in the CRM pipeline. Hover over " "a section of the report to see the number of leads in that stage." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "A basic win/loss report showing all leads whether won or lost grouped by " "stage." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:473 msgid "Customize win/loss reports" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:475 msgid "" "After :ref:`creating a win/loss report `, consider using " "the options below to customize the report for different needs." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:479 msgid "" "A sales manager might group wins and losses by salesperson, or sales team, " "to see who has the best conversion rate. Or, a marketing team might group by" " sources, or medium, to determine where their advertising has been most " "successful." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:485 msgid "Filters and groups" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:487 msgid "" "To add more filters and groups, click the :guilabel:`⬇️ (down arrow)` icon, " "next to the search bar, and select one or more options from the drop-down " "menu." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:490 msgid "Some useful options include:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:492 msgid "" ":guilabel:`Created on`: adjusting this filter to a different period of time," " such as the last 30 days, or the last quarter, can provide more timely " "results." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:494 msgid "" ":guilabel:`Add Custom Filter`: clicking this option, and scrolling through " "the numerous options in the drop-down menu, opens up additional search " "criteria, like :guilabel:`Last Stage Update` or :guilabel:`Lost Reason`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:497 msgid "" ":guilabel:`Add Custom Group > Active`: Clicking :menuselection:`Add Custom " "Group --> Active` separates the results into **Won** (:guilabel:`true`) or " "**Lost** (:guilabel:`false`). This shows at what stage leads are being " "marked **Won** or **Lost**." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:500 msgid "" ":guilabel:`Multiple Groupings`: add multiple :guilabel:`Group By` selections" " to split results into more relevant and manageable chunks." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:503 msgid "" "Adding :guilabel:`Salesperson` or :guilabel:`Sales Team` breaks up the total" " count of leads in each :guilabel:`Stage`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:505 msgid "" "Adding :guilabel:`Medium` or :guilabel:`Source` can reveal what marketing " "avenues generate more sales." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Search menu open and the Won and Lost filters highlighted." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:514 msgid "" "By default, pivot view groups win/loss reports by :guilabel:`Stage` and " "measures :guilabel:`Expected Revenue`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:517 msgid "To flesh out the table:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:519 msgid "Click the :guilabel:`⬇️ (down arrow)` next to the search bar." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:520 msgid "" "In the pop-up menu, replace the :guilabel:`Stage` grouping with something " "like :guilabel:`Salesperson` or :guilabel:`Medium`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:522 msgid "" "Click the :guilabel:`Measures` button and click :guilabel:`Count` to add the" " number of leads back into the report." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:525 msgid "" "Other useful measures for pivot view include :guilabel:`Days to Assign` and " ":guilabel:`Days to Close`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "A win/loss report in Pivot View displays the data in table form." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:533 msgid "" "In pivot view, the :guilabel:`Insert In Spreadsheet` button may be greyed " "out due to the report containing :guilabel:`duplicate group bys`. To fix " "this, replace the :guilabel:`Stage` grouping in the search bar with another " "option." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:539 msgid "In list view, a win/loss report displays all leads on a single page." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:541 msgid "" "To better organize the list, click the :guilabel:`⬇️ (down arrow)` next to " "the search bar, and add more relevant groupings or re-organize the existing " "ones. To re-order the nesting, remove all :guilabel:`Group By` options and " "re-add them in the desired order." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:545 msgid "To add more columns to the list:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:547 msgid "Click the :guilabel:`Filters` icon in the top-right of the page." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:548 msgid "" "Select options from the resulting drop-down menu. Some useful filters " "include:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:550 msgid "**Campaign**: Shows the marketing campaign that originated each lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:551 msgid "" "**Medium**: Shows the marketing medium (Banner, Direct, Email, Google " "Adwords, Phone, Website, etc.) that originated each lead." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:553 msgid "" "**Source**: Shows the source of each lead (Newsletter, Lead Recall, Search " "Engine, etc.)." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "A win/loss report in List View displays all leads in an easy-to-read list." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:562 msgid "Save and share reports" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:564 msgid "" "After :ref:`creating a report `, the search criteria can " "be saved, so the report does not need to be created again in the future. " "Saved searches automatically update their results every time the report is " "opened." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:568 msgid "" "Additionally, reports can be shared with others, or added to " "spreadsheets/dashboards for greater customization and easier access." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:573 msgid "Save to Favorites" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:575 msgid "To save a report for later:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:577 msgid "" "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down " "arrow)` icon, next to the search bar." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:579 msgid "" "In the drop-down menu that appears, under the :guilabel:`Favorites` heading," " click :guilabel:`Save current search`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:581 msgid "In the next drop-down menu that appears, enter a name for the report." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:583 msgid "" "Checking the :guilabel:`Default filter` box sets this report as the default " "analysis when the :guilabel:`Pipeline Analysis` page is accessed." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:585 msgid "" "Checking the :guilabel:`Shared` box makes this report available to other " "users." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:587 msgid "" "Finally, click :guilabel:`Save`. The report is now saved under the " ":guilabel:`Favorites` heading." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "Under the Favorites heading, click Save current search and save the report " "for later." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:594 msgid "Add to a Spreadsheet" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:596 msgid "" "Inserting a report into a spreadsheet not only saves a copy of the report, " "it allows users to add charts and formulas like in an Excel file." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:599 msgid "To save a report as a spreadsheet:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:601 msgid "**In Graph or Pivot View**:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:603 msgid "Click the :guilabel:`Insert in spreadsheet` button." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:604 msgid "In the pop-up menu that appears, click :guilabel:`Confirm`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:606 msgid "**In Cohort or List View**:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:608 msgid "Click the :guilabel:`⚙️ (gear)` icon." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:609 msgid "" "In the drop-down menu that appears, hover over :guilabel:`Spreadsheet`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:610 msgid "" "In the next drop-down menu, click either :guilabel:`Insert in spreadsheet` " "or :guilabel:`Link in spreadsheet`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:613 msgid "Saved reports are viewable in the *Documents* app." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "Pivot View reports especially benefit from being inserted in spreadsheets." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:620 msgid "" "After modifying a spreadsheet and adding additional formulas, consider then " "adding the entire spreadsheet to a dashboard. Using this method, the " "spreadsheet can be added to a public dashboard instead of only :guilabel:`My" " Dashboard`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:624 msgid "Click :menuselection:`File --> Add to dashboard`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:625 msgid "" "In the pop-up menu that appears, name the spreadsheet and select a " ":guilabel:`Dashboard Section` to house the report." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:627 msgid "Click :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:629 msgid "Add to a Dashboard" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:631 msgid "" "Adding a report to a dashboard saves it for later and makes it easy to view " "alongside the rest of :guilabel:`My Dashboard`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:634 msgid "To add a report to :guilabel:`My dashboard`:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:636 msgid "" "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⚙️ (gear)` " "icon." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:637 msgid "In the drop-down menu that appears, hover over :guilabel:`Dashboard`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:638 msgid "" "In the :guilabel:`Add to my dashboard` drop-down menu, enter a name for the " "report (by default, it is named :guilabel:`Pipeline`)." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:642 msgid "To view a saved report:" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:644 msgid "" "Return to the main apps page, and navigate to :menuselection:`Dashboards app" " --> My Dashboard`." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "To access the saved report, open the Dashboard app and click My Dashboard." msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:652 msgid ":doc:`../acquire_leads/convert`" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:653 msgid ":doc:`../acquire_leads/send_quotes`" msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:654 msgid ":doc:`../pipeline/lost_opportunities`" msgstr "" #: ../../content/applications/sales/crm/pipeline.rst:5 msgid "Organize the pipeline" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:3 msgid "Manage lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 msgid "" "Not every opportunity results in a successful sale. To keep the pipeline up-" "to-date, *lost* opportunities need to be identified. Specifying why an " "opportunity was lost provides additional insight that can prove useful for " "future opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 msgid "Mark an opportunity as lost" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 msgid "" "To mark an opportunity as lost, first open the :menuselection:`CRM app`, and" " select an opportunity from the pipeline, by clicking on its corresponding " "Kanban card. Doing so reveals that opportunity's detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:16 msgid "" "Then, click :guilabel:`Lost`, located at the top of the opportunity's detail" " form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "" "Buttons from the top of an opportunity record with the lost button " "emphasized." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:22 #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:185 msgid "" "This opens the :guilabel:`Mark Lost` pop-up window. From the :guilabel:`Lost" " Reason` drop-down menu, choose an existing lost reason. If no applicable " "reason is available, create a new one by entering it into the " ":guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:26 msgid "" "Additional notes and comments can be added below the lost reason in the " "designated :guilabel:`Closing Note` field." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:30 msgid "" "Neither the :guilabel:`Lost Reason` field, nor the :guilabel:`Closing Note` " "field, on the :guilabel:`Mark Lost` pop-up window are required. However, it " "is recommended to include this information for the sake of traceability, " "accountability, and reporting purposes." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Lost reasons popup with sample reasons." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 msgid "" "After clicking :guilabel:`Mark as Lost`, a red :guilabel:`Lost` banner is " "added to the upper-right corner of the opportunity." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "A lost opportunity with the lost banner added." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:49 msgid "" "To mark an *inactive* (archived) opportunity as lost, set the " ":guilabel:`Probability` field to `0` percent." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:55 msgid "Create/edit lost reasons" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:57 msgid "" "To create a new lost reason, or edit an existing one, navigate to " ":menuselection:`CRM app --> Configuration --> Lost Reasons`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:60 msgid "To edit an existing lost reason:" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:62 msgid "Click on the reason to be edited to highlight it." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:63 msgid "" "Change the selected lost reason by editing the :guilabel:`Description` " "field." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 msgid "When finished, click :guilabel:`Save` in the upper-left corner." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 msgid "To create a new lost reason:" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 msgid "" "Click :guilabel:`New` in the upper-left corner of the :guilabel:`Lost " "Reasons` page." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:69 msgid "" "In the new blank line, click in the :guilabel:`Description` field, then type" " the new lost reason." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:70 msgid "When finished, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:73 msgid "View lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:75 msgid "" "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM " "app`. On the main :guilabel:`Pipeline` dashboard, click into the " ":guilabel:`Search...` bar at the top of the page, and remove all of the " "default filters." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Search bar with lost filter emphasized." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 msgid "" "Open the :guilabel:`Filters` drop-down menu, by clicking the " ":guilabel:`🔻(triangle pointed down)` icon to the right of the " ":guilabel:`Search...` bar to open the drop-down menu containing " ":guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` " "options, designated into respective columns." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:88 msgid "" "Select the :guilabel:`Lost` option from the :guilabel:`Filters` section. " "Upon selecting :guilabel:`Lost`, only the opportunities marked as `Lost` " "appear on the :guilabel:`Pipeline` page." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:92 msgid "Sort opportunities by lost reason" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:94 msgid "" "To filter opportunities by a specific lost reason, click the " ":guilabel:`🔻(triangle pointed down)` icon to the right of the " ":guilabel:`Search...` bar again to open the drop-down menu. In addition to " "the :guilabel:`Lost` filter, under the :guilabel:`Filters` column, click " ":guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` " "pop-up window." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:99 msgid "" "On the :guilabel:`Add Custom Filter` pop-up window, click in the first " "field, and type `Lost Reason` in the :guilabel:`Search...` bar, or scroll to" " search through the list to locate it. Then, click into the next field, and " "select :guilabel:`=` from the drop-down menu. Click into the third field, " "and select a lost reason from the drop-down menu. Finally, click " ":guilabel:`Add`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Search bar with custom filter added for lost reason." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:109 msgid "" "To view results for more than one lost reason, select the operator " ":guilabel:`is in` in the second field of the custom filter in the " ":guilabel:`Add Custom Filter` pop-up window. Choosing this operator makes it" " possible to choose multiple lost reasons in the third field." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:0 msgid "Add Custom Filter pop-up with multiple lost reasons selected." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:118 msgid "Restore lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:120 msgid "" "To restore a lost opportunity, open the :menuselection:`CRM app` to reveal " "the :guilabel:`Pipeline` dashboard. Or, navigate to :menuselection:`CRM app " "--> Sales --> My Pipeline`. From here, click the :guilabel:`🔻(triangle " "pointed down)` icon to the right of the :guilabel:`Search...` bar to open " "the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, " "and :guilabel:`Favorites` columns." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:126 msgid "" "Under the :guilabel:`Filters` column, select :guilabel:`Lost`. Doing so " "reveals all the lost opportunities on the :guilabel:`Pipeline` page." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:130 msgid "" "To see all opportunities in the database, remove the default :guilabel:`My " "Pipeline` filter from the :guilabel:`Search...` bar." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:133 msgid "" "Then, click on the Kanban card of the desired lost opportunity to restore, " "which opens that opportunity's detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:136 msgid "" "From the lost opportunity's detail form, click :guilabel:`Restore` in the " "upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the" " opportunity form, signifying the opportunity has been restored." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Lost opportunity with emphasis on the Restore button." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:145 msgid "Restore multiple opportunities at once" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:147 msgid "" "To restore multiple opportunities at once, navigate to the main " ":guilabel:`Pipeline` dashboard in the *CRM* app, open the " ":guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:150 msgid "" "Next, select the list view option, represented by the :guilabel:`≣ (list)` " "icon in the upper-right corner. Doing so places all the opportunities from " "the :guilabel:`Pipeline` page in a list view. With the list view chosen, " "select the checkbox to the left of each opportunity to be restored." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:154 msgid "" "Once the desired opportunities have been selected, click the :guilabel:`⚙️ " "Actions` drop-down menu at the top of the :guilabel:`Pipeline` page. From " "the :guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:158 msgid "" "Doing so removes those selected opportunities from the :guilabel:`Pipeline` " "page because they no longer fit the :guilabel:`Lost` filter criteria. Delete" " the :guilabel:`Lost` filter from the search bar to reveal these newly-" "restored opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Action button from list view with the Unarchive option emphasized." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:167 msgid "Manage lost leads" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:169 msgid "" "If *Leads* are enabled on a database, they can be marked as *lost* in the " "same manner as opportunities. Leads use the same :ref:`lost reasons " "` as opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:173 msgid "" "To enable leads, navigate to :menuselection:`CRM app --> Configuration --> " "Settings` and check the :guilabel:`Leads` checkbox. Then, click " ":guilabel:`Save`. This adds a new :guilabel:`Leads` menu to the header menu " "bar at the top of the page." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:178 msgid "Mark a lead as lost" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:180 msgid "" "To mark a lead as lost, navigate to :menuselection:`CRM app --> Leads`, and " "select a lead from the list. Doing so reveals that lead's detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:183 msgid "" "Then, click :guilabel:`Lost`, located at the top of the lead's detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:189 msgid "" "Additional notes and comments can be added below the lost reason designated " "in the :guilabel:`Closing Note` field." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:196 msgid "Restore lost leads" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:198 msgid "" "To restore a lost lead, navigate to :menuselection:`CRM app --> Leads`, then" " click the :guilabel:`🔻 (triangle pointed down)` icon to the right of the " ":guilabel:`Search...` bar to open the drop-down menu that contains the " ":guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` " "columns." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:202 msgid "" "Under the :guilabel:`Filters` column, select :guilabel:`Lost`. Doing so " "reveals all the lost leads on the :guilabel:`Leads` page." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:205 msgid "" "Then, click on the desired lost lead to restore, which opens that lead's " "detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:207 msgid "" "From the lost lead's detail form, click :guilabel:`Restore` in the upper-" "left corner. Doing so removes the red :guilabel:`Lost` banner from the lead " "form, signifying the lead has been restored." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:211 msgid "Restore multiple leads at once" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:213 msgid "" "To restore multiple leads at once, navigate to :menuselection:`CRM app --> " "Leads`, open the :guilabel:`Filters` drop-down menu, and select the " ":guilabel:`Lost` option. Select the checkbox to the left of each lead to be " "restored." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:217 msgid "" "Once the desired leads have been selected, click the :guilabel:`⚙️ Actions` " "drop-down menu at the top of the :guilabel:`Leads` page. From the " ":guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:221 msgid "" "Doing so removes those selected leads from the :guilabel:`Leads` page " "because they no longer fit the :guilabel:`Lost` filter criteria. Delete the " ":guilabel:`Lost` filter from the :guilabel:`Search...` bar to reveal these " "newly-restored leads." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:226 msgid ":doc:`../performance/win_loss`" msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:3 msgid "Manage sales teams" msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:5 msgid "" "The *Sales Teams* feature within Odoo's *CRM* app allows for the creation " "and management of multiple sales teams, each with their own assignment " "rules, invoicing targets, and roster of salespeople." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:9 msgid "Create a sales team" msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:11 msgid "" "To create a new sales team, go to :menuselection:`CRM app --> Configuration " "--> Sales Teams`, then click :guilabel:`New`." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:14 msgid "" "On the blank sales team form, enter a name in the :guilabel:`Sales Team` " "field." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:16 msgid "Next, select a :guilabel:`Team Leader` from the drop-down list." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:18 msgid "" "Set an :guilabel:`Email Alias` to automatically generate a lead/opportunity " "for this sales team whenever a message is sent to that unique email address." " Choose whether to accept emails from :guilabel:`Everyone`, " ":guilabel:`Authenticated Partners`, :guilabel:`Followers Only`, or " ":guilabel:`Authenticated Employees`." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:23 msgid "" "Select a :guilabel:`Company` from the drop-down menu to assign this team to." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:26 msgid "" "The :guilabel:`Company` field is only visible in multi-company databases, " "and is not required." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst-1 msgid "The settings page for a new sales team." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:33 msgid "" "If the *Sales* app is installed on the database, an :guilabel:`Invoicing " "Target` field appears on the sales team form. This is the revenue target for" " the current month. The amount entered in this field is used to populate the" " invoicing progress bar on the :ref:`sales team dashboard `." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:39 msgid "Add sales team members" msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:41 msgid "" "To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab" " when editing the sales team's configuration page. This opens a " ":guilabel:`Create Sales Team Members` pop-up window." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:45 msgid "" "If the :guilabel:`Rule-Based Assignment` feature has **not** been enabled on" " the *CRM* app's *Settings* page, clicking :guilabel:`Add` under the " ":guilabel:`Members` tab opens an :guilabel:`Add: Salespersons` pop-up " "window. Tick the checkbox to the far-left of the salesperson to be added to " "the team, then click :guilabel:`Select`." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:0 msgid "The Add: Salespersons pop-up window on a new sales team." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:54 msgid "" "Select a user from the :guilabel:`Salesperson` drop-down list to add them to" " the team. To prevent this salesperson from being automatically assigned " "leads, tick the :guilabel:`Skip auto assignment` checkbox. If this feature " "is activated, the salesperson can still be assigned leads manually." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst-1 msgid "The Create Sales Team Members pop-up window." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:62 msgid "" "The :guilabel:`Leads (30 days)` field tracks how many leads the salesperson " "has been assigned in the past thirty days for this team, and the maximum " "number of leads they should be assigned. To edit the maximum number of leads" " this salesperson can be assigned, enter that amount in the :guilabel:`Leads" " (30 days)` field." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:68 msgid "" ":doc:`Assignment rules <../track_leads/lead_scoring>` can be configured for " "individual salespeople using the :guilabel:`Domain` section." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:71 msgid "" "Click :guilabel:`Save & Close` when finished, or :guilabel:`Save & New` to " "add additional members." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:74 msgid "Enable multi teams" msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:76 msgid "" "To allow salespeople to be assigned to more than one sales team, the *Multi " "Teams* setting needs to be enabled. First, navigate to :menuselection:`CRM " "app --> Configuration --> Settings`. Under the :guilabel:`CRM` section, tick" " the checkbox labeled :guilabel:`Multi Teams`. Then, click :guilabel:`Save` " "at the top-left of the page." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst-1 msgid "The settings page of the CRM app with the Multi Teams setting enabled." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:88 msgid "Sales team dashboard" msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:90 msgid "" "To view the sales team dashboard, go to :menuselection:`CRM app --> Sales " "--> Teams`. Any team the user is a member of appears in the dashboard." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst-1 msgid "The sales team dashboard in the CRM app." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:97 msgid "" "Each Kanban card gives an overview of the sales team's open opportunities, " "quotations, sales orders, and expected revenue, as well as a bar graph of " "new opportunities per week, and an invoicing progress bar." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:101 msgid "" "Click the :guilabel:`Pipeline` button to go directly to that team's *CRM* " "pipeline." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:103 msgid "" "Click on the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in " "the top-right corner of the Kanban card to open a drop-down menu. Then, to " "view or edit the team's settings, click :guilabel:`Configuration`." msgstr "" #: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:108 msgid ":doc:`../optimize/utilize_activities`" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:3 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. Identifying these duplicated records allows them to be merged " "without losing any information in the process. Not only does this help keep " "the *pipeline* organized, but it also prevents customers from being " "contacted by more than one salesperson." msgstr "" #: ../../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 " "reference." 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 "Comparing 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 --> Pipeline` or :menuselection:`CRM app --> Leads`." " Open a lead or opportunity, and click the :guilabel:`Similar Leads` smart " "button. Doing so opens a 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 "Merging similar leads and opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:43 msgid "" "After confirming that the leads/opportunities should be merged, return to " "the Kanban view using the breadcrumb link, or by clicking the " ":guilabel:`Similar Leads` smart button. Click the :icon:`oi-view-list` " ":guilabel:`(list)` icon to change to list view." msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:47 msgid "" "Check the box on the left of the page for the leads/opportunities to be " "merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` 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:52 msgid "" "When :guilabel:`Merge` is selected from the :icon:`fa-cog` " ":guilabel:`Actions` drop-down menu, a :guilabel:`Merge` pop-up modal " "appears. In that pop-up modal, under the :guilabel:`Assign opportunities to`" " heading, select a :guilabel:`Salesperson` and :guilabel:`Sales Team` from " "the appropriate drop-down menus." msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:57 msgid "" "Below those fields, the leads/opportunities to merge are listed, along with " "their related information. To merge those selected leads/opportunities, " "click :guilabel:`Merge`." 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:65 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:69 msgid "When leads/opportunities should not be merged" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:71 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:76 msgid "Lost leads" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:78 msgid "" "If a lead/opportunity has been marked as :doc:`lost `, " "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:83 msgid "Different contact within an organization" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:85 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:90 msgid "Existing duplicates with more than one salesperson" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:92 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:98 msgid "Contact information is similar but not exact" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:100 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 *exact*, they may need to remain " "independent." msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:105 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:108 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:111 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/track_leads.rst:5 msgid "Assign and track leads" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:3 msgid "Lead distribution report" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:5 msgid "" "A *lead distribution report* can be used to see if active leads are being " "assigned equitably across sales members. It can also be used to view the " "distribution of good or :doc:`quality leads `, and see" " how frequently each salesperson is receiving (and keeping) leads." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:9 msgid "" "Lead distribution reports can be run each week to help keep salespeople on " "track, while providing them with ample good leads. These reports can also be" " used to see whether sales members are staying productive, if good leads are" " being lost too often by one salesperson, and what percentage of good leads " "are being retained overall." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:15 msgid "Create lead distribution reports" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:17 msgid "" "To create a lead distribution report, first navigate to :menuselection:`CRM " "app --> Reporting --> Pipeline`, which reveals the :guilabel:`Pipeline " "Analysis` dashboard." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:20 msgid "" "Remove all the default filters in the search bar at the top of the page. " "Doing so displays data related to *all* leads." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:23 msgid "" ":ref:`Custom filters ` can now be added by clicking " "the :icon:`fa-caret-down` :guilabel:`(down caret)` icon, to the right of the" " search bar, to reveal a drop-down menu of search and filter options." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:27 msgid "" "Three columns are displayed: :ref:`Filters `, :ref:`Group By" " `, and :ref:`Favorites `. To begin, " "navigate to the bottom of the :guilabel:`Filters` column, and click " ":guilabel:`Add Custom Filter`. This opens an :guilabel:`Add Custom Filter` " "pop-up window, where the essential filters can be added one at a time." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:35 msgid "Essential filters" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:37 msgid "" "The following filter conditions are used to create a basic lead distribution" " report. Together they gather all leads created within a certain timespan " "that have an associated contact method and have been assigned to a sales " "team." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:42 msgid "Lead creation date" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:44 msgid "" "Click the first field, under :guilabel:`Match any of the following rules:`, " "that has the value :guilabel:`Country` in it. In the popover that appears, " "type `Created on` in the search bar, or scroll to search through the list to" " locate and select it." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:48 msgid "" "Then, in the second field of that row, select :guilabel:`>=` from the drop-" "down menu. This operator **only** includes values greater than (or equal to)" " the value in the third, rightmost field." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:51 msgid "" "The third field on the :guilabel:`Add Custom Filter` pop-up window should " "contain the earliest date leads are selected from." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:54 msgid "" "For example, setting `01/01/2024 00:00:00` only includes leads created from," " and including, the first day of 2024." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst-1 msgid "Add a Created On rule for the start of the year onward." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:64 msgid "Sales team" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:66 msgid "" "Click :guilabel:`New rule` to add another row to the form, and choose " ":guilabel:`Sales Team` for this rule's parameter. Then, click the second " "field of the new rule, and select :guilabel:`contains` from the drop-down " "menu. Selecting this operator filters for any records that contain the words" " in the third, rightmost field." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:72 msgid "" "For certain pre-determined, limited choices like a sales team, the " ":guilabel:`is in` operator helps make for an easier and more accurate " "selection, via a drop-down menu in the third field, instead of risking a " "typo or incorrect value in the text box field that accompanies the " ":guilabel:`contains` operator." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:77 msgid "" "In this third field, enter the name of the desired sales team(s) that are to" " be included in the report. It is important for all :guilabel:`contains` " "argument values to be specific enough and spelled correctly as they exist in" " Odoo, otherwise this risks returning multiple (or zero) values." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst-1 msgid "Use Sales Team to filter the location the lead is associated with." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:86 msgid "" "By adding more than one rule to the form, a new option emerges at the top of" " the pop-up window above all the filters, to specify whether :guilabel:`any`" " :icon:`fa-caret-down` or :guilabel:`all` :icon:`fa-caret-down` of the " "conditions should match. This distinction is important to set correctly, as " "it impacts the driving logic of how the filters return data." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:91 msgid "" "Click the default :guilabel:`any` :icon:`fa-caret-down` menu item and be " "sure the :guilabel:`all` :icon:`fa-caret-down` option is chosen instead. " "This setting will **only** show records that match *all* the rules contained" " inside the form." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:98 msgid "Contact method" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:101 msgid "" "The instruction below is not necessary, however, it's highly recommended to " "add a set contact value to the report's search criteria. A lot of spam, " "duplicate, or low quality leads can easily be screened out of the report " "simply by adding either a set :guilabel:`Phone` or :guilabel:`Email` rule." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:106 msgid "" "Add another :guilabel:`New rule` to the form and set the first field to the " "first field to :guilabel:`Phone`. Then, select :guilabel:`is set` from the " "drop-down menu in the second field. Selecting this operator **only** filters" " for records that have a phone number associated with the lead." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:111 msgid "" "Alternatively (or in addition to the above rule), click :guilabel:`New rule`" " and set the first field to :guilabel:`Email`. Then, select :guilabel:`is " "set` from the drop-down menu in the second field." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:114 msgid "" "These rules add only leads with an associated contact method to the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:119 msgid "Active status" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:121 msgid "" "Click the :icon:`fa-sitemap` :guilabel:`(Add branch)` icon to the right of " "the `Phone is set` line, to add a new rule that branches from the rules " "above." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:124 msgid "" "Two horizontal sets of fields appear below a line showing :guilabel:`any` " ":icon:`fa-caret-down` :guilabel:`of:` option. This setting filters for " "records that match **any** of the rules contained inside. This uses the same" " logic as an OR (`|`) logical operator." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:128 msgid "" "Set the first field to :guilabel:`Active`. Then, select :guilabel:`is set` " "in the next field." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:130 msgid "" "Next, click the :icon:`fa-plus` :guilabel:`(Add New Rule)` button next to " ":guilabel:`Active is set` to create a new line of fields beneath it." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:133 msgid "" "Set the first field to :guilabel:`Active`. Then, select :guilabel:`is not " "set` in the next field." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst-1 msgid "Use Active to include active status in the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:139 msgid "This rule adds the activity status of the lead to the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:142 msgid "" "Active status is an important filter to include when creating a lead " "distribution report because it includes **all** leads regardless of won/lost" " or active/inactive status in the report. This provides a comprehensive view" " of all the leads assigned to each sales member." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:147 msgid "Group by" msgstr "Združi po" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:149 msgid "" "Once all filters are set, click the :guilabel:`Add` button to add these " "filters to the search bar. To have the report grouped appropriately, click " "the :icon:`fa-caret-down` :guilabel:`(down caret)` icon, to the right of the" " search bar, and click :guilabel:`Salesperson` in the :guilabel:`Group By` " "section. All results are now grouped by the salesperson assigned to each " "lead." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:154 msgid "" "Once the rules for the filter are set, click the purple :guilabel:`Confirm` " "button at the bottom of the pop-up menu to save the custom filter and close " "the pop-up menu." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:157 msgid "" "The :guilabel:`Pipeline Analysis` dashboard is now displayed again with each" " filter rule in the search bar." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:160 msgid "" "Click the :icon:`fa-area-chart` :guilabel:`(Graph)` icon, to the right of " "the search bar, to view the report as a bar chart. Alternatively, click the " ":icon:`oi-view-list` :guilabel:`(List)` icon to view leads in a grouped " "list." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:165 msgid "" "To save the filter so it can easily be re-applied, click the :guilabel:`Save" " current search` button in the :guilabel:`Favorites` section of the search " "bar drop-down menu." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:168 msgid "" "Next, type a name for the filter in the text box below. Check the " ":guilabel:`Shared` checkbox to have the filter shared with any user with " "access to the pipeline. Finally, click the purple :guilabel:`Save` button " "below to save the filter." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:172 msgid "" "The filter will now appear with the name it was given under the " ":guilabel:`Favorites` section of the drop-down menu and can be re-applied by" " clicking on it." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:176 msgid "Filter for quality leads" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:178 msgid "" "The following additional conditions are provided as an example of a *good*, " "but *not comprehensive*, set of rules for finding quality leads. These " "filters should be applied on top of the :ref:`crm/track_leads/essential-" "filters` in the order specified to achieve a heavily-detailed filter." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:183 msgid "" "**Referred-by:** Filter for referrals, such as by appointment or sales " "member." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:184 msgid "" "**Source:** Filter for specific source UTMs, such as Facebook or LinkedIn." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:185 msgid "**Notes:** Filter for internal notes." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:186 msgid "**Tags:** Filter for categorical tags." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:187 msgid "" "**Email:** Filter for specific email domains, such as gmail.com or " "yahoo.com." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:188 msgid "" "**Salesperson:** Filter for leads associated with certain sales members." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:190 msgid "" "These conditions can be added, removed, or modified to best fit the desired " "information in the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:194 msgid ":ref:`quality_leads_report/add-quality-rules`" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:195 msgid ":doc:`../../../essentials/search`" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:3 msgid "Assign leads with predictive lead scoring" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5 msgid "" "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 " "the appropriate salespeople." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:10 msgid "" "Odoo automatically calculates the probability of winning each lead using a " "method called *predictive lead scoring*." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:14 msgid "Predictive lead scoring" 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." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19 msgid "" "As a company processes opportunities through the CRM pipeline, Odoo collects" " data on which opportunities are won and lost. Predictive lead scoring uses " "this data to predict the probability of winning each new lead or " "opportunity." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:23 msgid "" "The more opportunities that are sent through the CRM pipeline, the more data" " Odoo collects, resulting in more accurate probabilities." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:26 msgid "" "Specifically, Odoo's predictive lead scoring uses the *naive Bayes* " "probability model:" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:28 msgid "" "\\begin{equation}\n" "P(A | B) = \\frac{P(A) \\times P(B | A)}{P(B)}\n" "\\end{equation}\n" "\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 "" #: ../../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: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: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: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:69 msgid "" "Then, click on the drop-down menu to choose which variables the predictive " "lead scoring feature will take into account." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 msgid "" "The Update Probabilities window in the Predictive Lead Scoring settings." msgstr "" #: ../../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:78 msgid "" ":guilabel:`State`: the geographical state from which the opportunity " "originates" msgstr "" #: ../../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: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: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: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:83 msgid ":guilabel:`Language`: the spoken language specified on the opportunity" msgstr "" #: ../../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: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: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:95 msgid "Lastly, click :guilabel:`Confirm` to save changes." msgstr "" #: ../../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: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: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:108 msgid "" "To reactivate automatic probability, click on the gear icon next to the " "probability percentage." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 msgid "" "The gear icon used to reactivate automatic probability on an opportunity " "form." msgstr "" #: ../../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: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:122 msgid "Configure rule-based assignment" msgstr "" #: ../../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: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: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 "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 msgid "The Rule-Based Assignment setting in CRM settings." msgstr "" #: ../../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:144 msgid "Configure assignment rules" msgstr "" #: ../../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: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: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: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: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: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: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 "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:0 msgid "" "Sales team domain set to probability greater than or equal to twenty " "percent." msgstr "" #: ../../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: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: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 "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:3 msgid "Marketing attribution reports" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:5 msgid "" "Use the Odoo *CRM* app to compile a *marketing attribution report*, which " "analyzes the source of leads, and groups them in such a way as to calculate " "marketing's overall impact on lead generation, attribution, won rate, and " "more." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:10 msgid "Leads Analysis dashboard" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:12 msgid "" "Begin by navigating to the :guilabel:`Leads Analysis` dashboard by going to " ":menuselection:`CRM app --> Reporting --> Leads`." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:16 msgid "" "Reports can also be run on the :menuselection:`CRM app --> Leads` dashboard," " which is **only** accessible if the *Leads* feature has been activated on " "the *Settings* page." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:19 msgid "" "If the *Leads* feature has **not** been activated, the :menuselection:`CRM " "app --> Sales --> My Pipeline` dashboard can also be used to run reports." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:22 msgid "" "Both dashboards contain the necessary *Filters* and *Group By* criteria to " "run an attribution report." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:26 msgid ":doc:`Convert leads into opportunities <../acquire_leads/convert>`" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:27 msgid ":doc:`Create leads <../acquire_leads/email_manual>`" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst-1 msgid "" "Open the CRM app and click on the Reporting tab at the top of the page, then" " click Leads." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:33 msgid "" "The :icon:`fa-area-chart` :guilabel:`(graph)` view is shown, by default, " "with :guilabel:`Active or Inactive` and :guilabel:`Created on: [current " "year]` filters active in the :guilabel:`Search...` bar. The graph " "visualization displays the number of leads generated, by month and by sales " "team, with each sales team attributed to its own color per month shown." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:38 msgid "" "Switch the view to the :icon:`oi-view-list` :guilabel:`(list)` option, by " "clicking the respective icon located at the top-right of the dashboard. This" " allows leads to easily be displayed in the grouping set by the *Group By* " "parameters." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst-1 msgid "" "Click the button with four horizontal lines on the top right of the Leads " "Analysis page." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:47 msgid "Add UTM parameters" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:49 msgid "" "*Urchin Tracking Modules (UTMs)* are snippets of text embedded in URLs that " "are used to track visitor data. This includes parameters relating to how a " "visitor reached the link, such as the type of website visited, and/or " "marketing campaign the visit came from." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:53 msgid "" "Odoo can use these UTMs as parameters in the marketing attribution report to" " track the metrics and performance of marketing campaigns." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:57 msgid "Create UTMs" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:59 msgid "" "The :doc:`link tracker <../../../websites/website/reporting/link_tracker>` " "in Odoo can be used to create and configure UTMs." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:62 msgid "" "UTMs can also be automatically generated by the :doc:`Email Marketing " "<../../../marketing/email_marketing>` and :doc:`Marketing Automation " "<../../../marketing/marketing_automation>` apps." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:66 msgid "" "The UTM parameters used in a marketing attribution report are *Medium*, " "*Source*, and *Campaign*, in descending order of coverage." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:69 msgid "" "*Medium* is the UTM with the widest coverage, and is used to identify the " "medium used to access the link. This can include mediums such as social " "media, email, or cost per click (CPC)." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:71 msgid "" "*Source* is more narrow, and is used to identify the source of traffic. For " "example, the name of a website, search engine used, or a specific social " "media platform." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:73 msgid "" "*Campaign* is the most narrow, and can track specific marketing campaigns by" " name. This can include a contest or product name, type of sale, etc." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:79 msgid "" "To start creating a report, click the :icon:`fa-caret-down` :guilabel:`(down" " arrow)` to the right of the :guilabel:`Search...` bar to see the list of " "filtering and grouping parameters." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:82 msgid "" ":guilabel:`Filters`, located in the left column of the search options, can " "be used to keep only the results that fit the filter. For example, selecting" " the :guilabel:`Won` filter only shows leads that have been won in the " "attribution report." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:86 msgid "" ":guilabel:`Group By`, found in the middle column, is used to organize the " "results into groups, and can be used with or without filters." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst-1 msgid "Select any number of filters and groups in the search options." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:94 msgid "" "Setting multiple :guilabel:`Group By` options creates nested groups, " "according to which option is selected first. For example, selecting " ":guilabel:`Medium`, followed by :guilabel:`Source`, and then " ":guilabel:`Campaign`, in :guilabel:`Group By` column, sorts all results " "*first* by medium, *then* by the specific sources in each medium, followed " "by the campaigns in each source." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:99 msgid "" "This can be verified by looking at the direction, and order, of the " "selections in the group tile that appears in the :guilabel:`Search...` bar." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:0 msgid "" "The text in the tile is `Country > City`, showing that city is a subgroup of" " country." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:107 msgid "For a useful first report:" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:109 msgid "" "#. From the :guilabel:`Filters` column, select the :guilabel:`Active` filter" " to view only leads that are still marked as active. #. From the " ":guilabel:`Group By` column, select (in this specific order) " ":guilabel:`Source`, followed by the :guilabel:`City` or :guilabel:`Country`," " depending on which grouping is more relevant." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst-1 msgid "Each lead is now sorted by source, followed by city or country." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:119 msgid "" "This report contains all active leads, grouped first by the source of the " "lead, then by the city or country each lead is from. This is useful to see " "the density of active opportunities sorted by location." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:123 msgid "" "With this data, marketing campaigns, such as conferences or billboards, can " "be targeted to the locations generating the largest amount of potential " "revenue. Similarly, more attention can be put toward increasing outreach in " "locations where existing marketing campaigns are less effective." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:129 msgid "Export reports" msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:131 msgid "" "To set the measures of the report, begin by navigating to the :icon:`oi-" "view-pivot` :guilabel:`(pivot view)` on the :guilabel:`Leads Analysis` " "dashboard." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:134 msgid "" "Click the :guilabel:`Measures` button to view the available measures of the " "report. Select the desired measures from the drop-down menu (multiple " "measures can be selected), and verify the measures, filters, and groups are " "all displayed correctly in the pivot table. This ensures the data is ready " "for export." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:139 msgid "" "To quickly export the data in a list, as a .xlsx file, navigate to the " ":icon:`oi-view-list` :guilabel:`(list view)`. Click on the " ":guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` icon, located to the " "right of :guilabel:`Lead Analysis` in the top-left of the page, and click " ":icon:`fa-upload` :guilabel:`Export All`. The report downloads automatically" " as a .xlsx file." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:144 msgid "" "For more export options, the report can be exported to the Odoo *Documents* " "app. From the :icon:`oi-view-list` :guilabel:`(list view)` of " ":guilabel:`Leads Analysis` page, begin by clicking the :guilabel:`Actions` " ":icon:`fa-cog` :guilabel:`(gear)` icon again. Now, navigate to :icon:`fa-" "table` :guilabel:`Spreadsheet`, and click :icon:`oi-view-list` " ":guilabel:`Insert list in spreadsheet`. A pop-up window titled, " ":guilabel:`Select a spreadsheet to insert your list.` appears." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:150 msgid "" "The report can be renamed using the `Name of the list` field, if desired. " "The number of items on the report can be set with the field labeled: `Insert" " the first _ records of the list`. Next, select either a new " ":guilabel:`Blank spreadsheet`, or export into an existing spreadsheet. " "Finally, click the :guilabel:`Confirm` button." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst-1 msgid "" "Set the name, number of records, and location of the export in the option " "menu." msgstr "" #: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:159 msgid "" "To export the report as a .xlsx file, for use in an external spreadsheets " "program, click the :guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` " "icon, and select the :icon:`fa-upload` :guilabel:`Export All` option. If " "prompted, choose a file location, name the file, then click " ":guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:3 msgid "Quality leads report" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:5 msgid "" "A *quality lead* is a lead that is likely to result in a sale. It should " "match the characteristics most commonly believed to help salespeople close a" " deal, in addition to more precise criteria that is specific to each " "organization." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:10 msgid "" "The specific criteria that defines a *quality lead* is different for every " "organization. For more information, see :ref:`Define a quality lead " "`." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:13 msgid "" "A quality leads *report* compares how many quality leads each salesperson " "has received over a specific amount of time, such as within the past 30 " "days. Sales managers can use such a report to make more informed decisions " "when assigning new leads to their team" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:18 msgid "" "A sales manager pulls a quality leads report using their company's criteria:" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:20 msgid "Leads must include a phone number and an email address." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:21 msgid "The email address must be from a professional domain." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:22 msgid "" "The source for the lead must be from a live chat conversation or an " "appointment with a salesperson." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:25 msgid "" "After running the report, the manager can see that, although everyone's " "ability to close a deal has varied, some members of the sales team have " "received a higher number of quality leads than others." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:0 msgid "An example of a quality leads report in the Odoo CRM application." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:33 msgid "" "Using this information, the sales manager may decide to assign more quality " "leads to the sales people currently on the lower end, to balance out the " "distribution of quality leads." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:39 msgid "Create a quality leads report" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:41 msgid "" "To create a quality leads report, first navigate to :menuselection:`CRM app " "--> Reporting --> Pipeline` to open the :guilabel:`Pipeline Analysis` " "dashboard. Click into the :guilabel:`Search...` bar at the top of the page " "and remove any active filters." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:45 msgid "" "Click the :guilabel:`🔻(triangle pointed down)` icon to the right of the " ":guilabel:`Search...` bar to open the drop-down mega menu that contains " ":guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` " "columns. Click :guilabel:`Add Custom Filter`. This opens a :guilabel:`Add " "Custom Filter` pop-up window." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:50 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:65 msgid "" "The :guilabel:`Add Custom Filter` pop-up window allows for the creation of " "more specific filters." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:55 msgid "" "In order to generate a quality leads report, filters need to be created for " "the following conditions:" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:58 msgid "" ":ref:`Starting date `: limits results to" " those created within a specific time frame." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:60 msgid "" ":ref:`Specific sales teams `: limits " "results to only include leads for one or more sales teams. This filter is " "optional and should not be included if the is intended for the entire " "company." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:63 msgid "" ":ref:`Exclude unassigned leads `: " "excludes leads without an assigned salesperson." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:65 msgid "" ":ref:`Include archived leads `: ensures" " that both active and inactive leads are included in the results." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:67 msgid "" ":ref:`Add rules for quality leads `:" " includes or excludes results based on criteria that is specific to a " "company or sales team." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:74 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:140 msgid "" "An example of the Custom Filter pop-up window with all of the rules " "configured." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:74 msgid "" "An example of the *Custom Filter* pop-up window with all of the default " "rules configured." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:79 msgid "Add a starting date filter" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:81 msgid "" "Begin by first defining the rule's parameter with a date range, by clicking " "into the first field, on the left of the row, and typing `Created On` in the" " :guilabel:`Search...` bar, or by scrolling through the menu's list to " "locate it." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:85 msgid "" "In the rule's operator drop-down menu, define the parameter further by " "selecting either:" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:87 msgid "" ":guilabel:`>= (greater than or equal to)` to specify a start date and " "include all entries *after* that start date (as well as the initial value " "itself); or" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:89 msgid "" ":guilabel:`is between` to more sharply define a time frame with a clear " "start and end date. All matching entries that fit within the defined start " "and end dates are included in the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:92 msgid "" "With either option, use the pop-up calendar's day and time pickers, in the " "far right field, to define the respective date range. Setting these values " "concludes the creation of the first rule." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:98 msgid "Add a sales team filter" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:101 msgid "" "This filter is optional. To view results for the entire company, do **not** " "add this filter." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:107 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:129 msgid "" "In the rule's second field, select :guilabel:`is in` from the drop-down " "menu. Selecting this operator limits results to the sales teams selected in " "the next field." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:110 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:132 msgid "" "Lastly, in the third field, select the desired sales team from the drop-down" " menu. Multiple teams can be added in this field, where each parameter is " "treated with an \"or\" (e.g. \"any\") operator in the search logic." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:119 msgid "" "Next, add a :guilabel:`New Rule`. Then, click into the first field for the " "new rule, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll" " to search through the list to locate it." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:122 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:113 msgid "" "In the rule's second field, select :guilabel:`is set` from the drop-down " "menu. Selecting this operator excludes any leads not assigned to a specific " "salesperson." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:128 msgid "Include archived leads" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:131 msgid "" "This filter is also optional, as it adds archived (inactive) leads to the " "report, however it is recommended to include this since it pulls *all* " "assigned leads, regardless of status, into the report. This ensures a more " "accurate representation of assigned leads is captured. However, to pull a " "report that only includes active leads, do **not** activate this feature." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:136 msgid "" "Next, in the upper-right corner of the :guilabel:`Add Custom filter` pop-up " "window, move the :guilabel:`Include archived` toggle to active." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst-1 msgid "" "The Add Custom Filter pop-up with emphasis on the Include Archived toggle." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:143 msgid "Enabling this feature adds archived (inactive) leads to the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:148 msgid "Add rules for quality leads" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:150 msgid "" "The filters added in this step vary, based on how an organization defines a " "*quality lead*." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:155 msgid "Define a quality lead" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:157 msgid "" "As defined earlier, a *quality lead* is a lead that is likely to result in a" " won opportunity. Although the exact criteria for a quality lead varies from" " organization to organization, it is often a combination of factors commonly" " attributed to positive sales outcomes, in addition to factors valued by the" " specific organization." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:162 msgid "" "In addition to the basic filters and grouping options outlined in the " "general :ref:`Quality leads report `, consider the following filters when defining a quality lead:" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:166 msgid "" ":guilabel:`Email` or :guilabel:`Phone`: the information in these fields can " "help determine whether or not a lead is a professional contact." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:168 msgid "" ":guilabel:`Source`: this field links to the marketing and lead generation " "efforts from other Odoo applications, including *Live Chat*, *Social " "Marketing*, and *Email Marketing*." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:170 msgid "" ":guilabel:`Stage`: this filter can be used to eliminate or target leads that" " have reached specific stages." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:172 msgid "" ":guilabel:`Medium`: a lead's source can indicate its quality level, as " "various channels have different won rates and expected revenues." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:174 msgid "" ":guilabel:`Campaign`: adding this filter helps track of the success of " "different marketing efforts to capture high quality leads." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:176 msgid "" ":guilabel:`Lost Reason`: exclude leads that may appear to be quality based " "on various criteria, but have been marked as *lost* for specified reasons." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:178 msgid "" ":guilabel:`Tags`: include or exclude results based on one or more customized" " tags." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:181 msgid "" "When adding rules to a custom filter, keep the statements preceding each " "rule in mind. The statement above a rule determines whether the search " "results must match **all** of the rules below the statement, or **any** of " "the rules below the statement." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:0 msgid "" "Close up of the match rule options on a add custom filter pop-up window." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:190 msgid "View the report" msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:0 msgid "" "Close up on the match all rules option on the add a custom filter pop-up " "window." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:202 msgid "" "After the filters are configured, click :guilabel:`Add`. The default display" " for the report is a bar graph, where the leads are grouped by *stage*." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:205 msgid "" "To group the results by salesperson, click the :guilabel:`🔻(triangle pointed" " down)` icon to the right of the :guilabel:`Search...` bar to open the drop-" "down mega menu. Under the :guilabel:`Group By` heading, select " ":guilabel:`Salesperson`. In the same column, under the :guilabel:`Group By` " "heading, click :guilabel:`Add a Custom Group`, then select " ":guilabel:`Active` on the resulting drop-down menu to layer in lead " "*status*, under the parent :guilabel:`Salesperson` grouping." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:211 msgid "" "The report now displays the total count of *quality leads* each salesperson " "has received in the designated time period. Because there are layered " ":guilabel:`Group By` filters, the grouped leads are also color-coded to " "identify whether they are *active* or *marked as lost*." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:216 msgid "" "To save this search for later, click the :guilabel:`🔻(triangle pointed " "down)` icon next to the :guilabel:`Search...` bar to open the drop-down " "menu. Under the :guilabel:`Favorites` heading, click :guilabel:`Save current" " search`." msgstr "" #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:220 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 "Preprodajalci" #: ../../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 "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:5 msgid "" "*Unattended leads* are leads that have scheduled activities that are either " "due or past due. Whenever an activity is scheduled, Odoo tracks the due " "date, and sends email reminders to the users the activity is assigned to." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:9 msgid "" "An *unattended leads report* compiles all active leads in the pipeline with " "due or past due activities, allowing a sales manager to identify which " "opportunities require immediate attention." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:12 msgid "" "By pulling a daily unattended leads report, sales managers can remind their " "teams to address outstanding activities before they become past due, helping" " avoid neglected leads and reinforcing proactive behaviors in their " "salespeople." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:18 msgid "" "A sales manager starts their day by pulling an unattended leads report, and " "upon switching to list view, they see the following:" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 msgid "" "List view of a sample Unattended Leads report with the activities " "emphasized." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:25 msgid "" "Their team member, Mitchell, has two leads in the *Proposition* stage with " "activities that are due." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:28 msgid "" "The yellow :guilabel:`📞 (phone)` icon indicates that the `Modern Open Space`" " lead has a phone call activity scheduled for today. The red :guilabel:`✉️ " "(envelope)` icon indicates that the `5 VP Chairs` lead has an email activity" " scheduled that is past due." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:32 msgid "" "Clicking on the `5 VP Chairs` lead, the sales manager opens the record of " "the lead and reviews the chatter. They see that the email was scheduled to " "be sent two days ago, but Mitchell never marked this activity as done." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst-1 msgid "Example of overdue activities notification in the chatter of a lead." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:41 msgid "" "In order to pull a unattended leads report, sales teams **must** be " "regularly utilizing activity in the *CRM* pipeline, on individual lead and " "opportunity cards." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:44 msgid "" "It is **not** possible to compile a complete report if the sales people are " "not using the *Activities* feature in the *chatter*" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:47 msgid "" "For more information, refer to :doc:`Activities " "<../../../essentials/activities>`" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:50 msgid "Create an unattended leads report" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:52 msgid "" "To create an unattended leads report, first navigate to :menuselection:`CRM " "app --> Reporting --> Pipeline` to open the :guilabel:`Pipeline Analysis` " "dashboard. Click into the :guilabel:`Search...` bar at the top of the page, " "and remove all of the default filters." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:57 msgid "" "The :guilabel:`Created on` filter can remain active, as this variable may be" " useful to include in the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:60 msgid "" "Next, add custom filters by clicking the :guilabel:`🔻(triangle pointed " "down)` icon to the right of the :guilabel:`Search...` bar to open the drop-" "down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and " ":guilabel:`Favorites` columns. Under the :guilabel:`Filters` column, click " ":guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` " "pop-up window." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:70 msgid "" "In order to generate an unattended leads report, filters need to be created " "for the following conditions:" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:73 msgid "" ":ref:`Past due activities `: limits the " "results to only include leads with an assigned activity where the due date " "has past. This can be altered to include activities due to occur on the date" " the report is generated as well." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:76 msgid "" ":ref:`Unassigned leads `: " "excludes leads without an assigned salesperson." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:78 msgid "" ":ref:`Specific sales teams `: limits " "results to only include leads assigned to one or more sales teams. This " "filter is optional and should not be included if the report is intended for " "the entire company." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:85 msgid "Add filter for past due activities" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:87 msgid "" "Click the first field for the new rule, and type `Activities` in the " ":guilabel:`Search...` bar, or scroll to search through the list to locate " "it. Then, next to :guilabel:`Activities`, click the :guilabel:`> (greater " "than sign)` to open a new drop-down menu with secondary conditions." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:91 msgid "" "Type `Due Date` in the :guilabel:`Search...` bar, or scroll to search " "through the list. Click :guilabel:`Due Date` to add it to the rule." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 msgid "" "Custom filter pop-up with emphasis on the options for activities and due " "date." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:98 msgid "" "Then, click into then next field and select :guilabel:`<=` from the drop-" "down menu. Selecting this operator includes all activities with a due date " "up to, and including, the date selected in the next field." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:102 msgid "The third field can be left as today's date, or adjusted as needed." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:109 msgid "" "After filtering for activities, add a :guilabel:`New Rule`. Then, click into" " the first field for the new rule, and type `Salesperson` in the " ":guilabel:`Search...` bar, or scroll to search through the list to locate " "it." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:119 msgid "Add a Sales team" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:122 msgid "" "This filter is optional. To view results for the entire company, do **not** " "add this filter, and continue to :ref:`View results " "`" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:140 msgid "" "An example of the **Add Custom Filter** pop-up window with all of the rules " "configured." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:156 msgid "" "After the filters are configured, click :guilabel:`Add`. The resulting " "report displays all leads assigned to a salesperson where an activity is " "past due, or is due on the current date. The default display is a bar graph," " where the leads are grouped by *stage*." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:160 msgid "" "To group the results by salesperson, click the :guilabel:`🔻(triangle pointed" " down)` icon to the right of the :guilabel:`Search...` bar to open the drop-" "down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and " ":guilabel:`Favorites` columns. Under the :guilabel:`Group By` heading, " "select :guilabel:`Salesperson`." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:166 msgid "" "The option to group by :guilabel:`Sales Team` is also available under the " ":guilabel:`Group By` heading." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:169 msgid "" "To change to a *list* view, click the :guilabel:`≣ (list)` icon in the top-" "right corner of the screen." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:173 msgid "" "Clicking the :guilabel:`(toggle) icon` opens a drop-down menu of additional " "columns that can be added to the report." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:176 msgid "Some options that are beneficial for this report include:" msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:178 msgid "" ":guilabel:`Activities`: the summary of the latest activity for this lead." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:179 msgid "" ":guilabel:`Expected Closing`: the estimated date on which the lead will be " "won." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:180 msgid ":guilabel:`Probability`: estimated success rate based on the stage." msgstr "" #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:187 msgid ":doc:`Activities <../../../essentials/activities>`" msgstr "" #: ../../content/applications/sales/members.rst:5 msgid "Members" msgstr "Člani" #: ../../content/applications/sales/members.rst:7 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:12 msgid "Membership products" msgstr "Opcije članstva" #: ../../content/applications/sales/members.rst:14 msgid "" "To create a new membership product, navigate to :menuselection:`Members app " "--> Configuration --> Membership Products`, and click :guilabel:`New` to " "open a blank product record." msgstr "" #: ../../content/applications/sales/members.rst:17 msgid "" "Complete the blank form with the necessary information, including the " ":guilabel:`Membership Duration`." msgstr "" #: ../../content/applications/sales/members.rst:21 msgid "" "Membership products require a start and end date, as they are used to " "determine :ref:`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:29 msgid "" "Membership products can be added to a sales order, and invoiced as regular " "products or subscriptions." msgstr "" #: ../../content/applications/sales/members.rst:33 msgid "Activate a membership" msgstr "" #: ../../content/applications/sales/members.rst:35 msgid "" "To activate a membership from the *Contacts* application, navigate to " ":menuselection:`Contacts app`, and click on a contact to open that specific " "contact's detail form." msgstr "" #: ../../content/applications/sales/members.rst:38 msgid "" "From the resulting contact form, open the :guilabel:`Membership` tab, and " "click :guilabel:`Buy Membership`." msgstr "" #: ../../content/applications/sales/members.rst:41 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:44 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:47 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:53 msgid "Membership status" msgstr "" #: ../../content/applications/sales/members.rst:55 msgid "" "The :guilabel:`Current Membership Status` is listed on the " ":guilabel:`Membership` tab of each contact record:" msgstr "" #: ../../content/applications/sales/members.rst:58 msgid "" ":guilabel:`Non Member`: a partner who has **not** applied for membership." msgstr "" #: ../../content/applications/sales/members.rst:59 msgid "" ":guilabel:`Cancelled Member`: a member who has cancelled their membership." msgstr "" #: ../../content/applications/sales/members.rst:60 msgid ":guilabel:`Old Member`: a member whose membership end date has passed." msgstr "" #: ../../content/applications/sales/members.rst:61 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:63 msgid "" ":guilabel:`Invoiced Member`: a member whose invoice has been created, but " "has not been paid." msgstr "" #: ../../content/applications/sales/members.rst:64 msgid ":guilabel:`Paid Member`: a member who has paid the membership fee." msgstr "" #: ../../content/applications/sales/members.rst:67 msgid "Publish members directory" msgstr "" #: ../../content/applications/sales/members.rst:69 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/sales/members.rst-1 msgid "The Online Members directory module in Odoo." msgstr "" #: ../../content/applications/sales/members.rst:78 msgid "Publish individual members" msgstr "" #: ../../content/applications/sales/members.rst:80 msgid "" "Return to :menuselection:`CRM app --> Sales --> Customers`, and click the " "Kanban card for a member. From the resulting 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:84 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:88 msgid "Repeat these steps for all desired members." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:3 msgid "Members analysis" msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:9 msgid "" "The *Members Analysis* report provides a detailed overview of all " "memberships sold and managed within the *Members* application." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:12 msgid "" "To access the *Memberships Analysis* report, navigate to " ":menuselection:`Members app --> Reporting`." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:15 msgid "Navigate the report" msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:17 msgid "" "The default *Members Analysis* report displays a bar chart, measuring the " ":guilabel:`Quantity` of memberships against the amount of :guilabel:`Revenue" " Done`. The data is grouped by the assigned salesperson, then by the month " "the membership begins." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst-1 msgid "A sample of the members analysis report." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:25 msgid "" "Additional :ref:`Group By ` options include the following:" msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:27 msgid "" ":guilabel:`Salesperson`: the internal user in charge of the contact. This " "information is managed in the *Salesperson* field on the *Sales & Purchase* " "tab on the contact's record." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:29 msgid "" ":guilabel:`Associated Partner`: the contact listed as the *Associated " "Member* on the *Membership* tab on the contact's record." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:31 msgid "" ":guilabel:`Membership Product`: the type of membership assigned to a " "contact. This includes both purchased memberships and free memberships." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:33 msgid ":guilabel:`Current Membership State`: the status of the membership." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:34 msgid "" ":guilabel:`Company`: the company the membership is purchased through. This " "option only appears in multi-company databases." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:36 msgid ":guilabel:`Month`: the month the membership began." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:41 msgid "" "Click the :icon:`fa-area-chart` :guilabel:`(graph)` 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/members/members_analysis.rst:46 msgid "Click the |pivot| to change to the pivot view." msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:54 msgid ":ref:`search/custom-filters`" msgstr "" #: ../../content/applications/sales/members/members_analysis.rst:55 msgid ":ref:`search/favorites`" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:6 msgid "Point of Sale" msgstr "Prodajna točka" #: ../../content/applications/sales/point_of_sale.rst:8 msgid "" "With **Odoo Point of Sale**, run your shops and restaurants easily. The app " "works on any device with a web browser, even if you are temporarily offline." " Product moves are automatically registered in your stock, you get real-time" " statistics, and your data is consolidated across all shops." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:13 msgid "" "`Odoo Tutorials: Point of Sale Tutorials `_" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:14 msgid ":doc:`IoT Boxes Documentations `" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:19 msgid "Start a session" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:21 msgid "" "From the **POS dashboard**, click :guilabel:`New Session`, and at the " ":guilabel:`Opening Cash Control` screen, click :guilabel:`Open Session` to " "start a POS session, or click :guilabel:`Continue Selling` if the session is" " already opened." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:26 msgid "" ":doc:`Multiple users ` can be logged into the " "same session at the same time. However, the session can only be opened once " "on the same browser." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:32 msgid "Sell products" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:34 msgid "" "Click on products to add them to the cart. To change the **quantity**, click" " :guilabel:`Qty` and enter the number of products using the keypad. To add a" " **discount** or modify the product **price**, click respectively " ":guilabel:`% Disc` or :guilabel:`Price` and enter the amounts." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:38 msgid "" "Once an order is completed, proceed to checkout by clicking " ":guilabel:`Payment`. Select the **payment method**, enter the received " "amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move " "on to the next customer." msgstr "" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "POS session interface." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:46 msgid "You can use both `,` and `.` on your keyboard as decimal separators." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:47 msgid "" "**Cash** is selected by default if you enter the amount without choosing a " "payment method." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:50 msgid "" "The system can only load a limited number of products for effective opening." " Click :guilabel:`Search more` if the desired product is not loaded " "automatically." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:56 msgid "Set customers" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:58 msgid "" "Registering your customer is necessary to :doc:`collect their loyalty points" " and grant them rewards `, automatically " "apply the :doc:`attributed pricelist `, or" " :ref:`generate and print an invoice `." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:63 msgid "" "You can create customers from an :ref:`open POS session `" " by clicking :menuselection:`Customer --> Create`, and filling in the " "contact information. You can also create customers from the backend by going" " to :menuselection:`Point of Sale --> Orders --> Customers` and clicking " ":guilabel:`New`. Then, fill in the information and save." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:68 msgid "" "To set a customer during an order, access the list of customers by clicking " ":guilabel:`Customer` on the POS interface. You can also set a customer at " "the payment screen by clicking :guilabel:`Customer`." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:75 msgid "Customer notes" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:77 msgid "" "You can add **customer notes** about specific products directly from an open" " :ref:`POS session `. For instance, to provide cleaning " "and maintenance tips. They can also be used to track a customer's particular" " request, such as not wanting the product to be assembled for them." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:81 msgid "" "To do so, select a product and click :guilabel:`Customer Note` on the pad. " "Doing so opens a pop-up window in which you can add or modify content for " "the note." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:85 msgid "" "Product notes from an :doc:`imported SO ` " "are displayed identically in the cart." msgstr "" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "" "Customer note button and notes (SO and POS session) on products in the cart" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:91 msgid "" "Customer notes appear on customers' receipts and invoices similarly to how " "they appear in the cart, under the related product." msgstr "" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "" "Customer receipt with notes from an SO and from the customer note feature" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:100 msgid "Return and refund products" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:102 msgid "To return and refund a product," msgstr "" #: ../../content/applications/sales/point_of_sale.rst:104 msgid ":ref:`start a session ` from the **POS dashboard**;" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:105 msgid "click :guilabel:`Refund` and select the corresponding order;" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:106 msgid "select the product and the quantity to refund using the keypad;" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:107 msgid "click :guilabel:`Refund` to go back to the previous screen;" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:108 msgid "" "once the order is completed, click :guilabel:`Payment` to proceed to the " "refund;" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:109 msgid "" "click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next " "customer." msgstr "" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "refund view from a POS" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:115 msgid "" "You can filter the **orders list** by :guilabel:`Receipt Number`, " ":guilabel:`Date` or :guilabel:`Customer` using the search bar." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:117 msgid "" "You can also refund a product by selecting the returned product from an open" " session, and setting a negative quantity that equals the number of returned" " products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by " "the quantity of returned products." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:124 msgid "Manage the cash register" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:126 msgid "" "To add or take out cash from the register, click the **menu icon** in the " "upper right corner of your screen and :guilabel:`Cash In/Out`." msgstr "" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "" "Dropdown menu to close a POS session, reach the backend, add or take cash out or check\n" "orders" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:133 msgid "" "Doing so opens a pop-up window on which you can select :guilabel:`Cash In` " "or :guilabel:`Cash Out`, enter the amount and the reason, and click " ":guilabel:`Confirm`." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:139 msgid "Close the POS session" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:141 msgid "" "To close your session, click the **menu icon** in the upper right corner of " "your screen and :guilabel:`Close Session`." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:144 msgid "" "Doing so opens the :guilabel:`Closing Control` pop-up screen. From this " "screen, you can retrieve various information:" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:147 msgid "" "the number of orders made and the total amount made during the session;" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:148 msgid "the expected amounts grouped by payment method." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:150 msgid "" "Before closing this window, count your cash using the calculator icon. Doing" " so opens a pop-up window that computes the total amount in the cash drawer " "depending on the coins and bills counted and added manually. Then, click " ":guilabel:`Confirm` or :guilabel:`Discard` to close the window. The computed" " amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money " "Details` are specified in the **Notes** section." msgstr "" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "How to close a POS session." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:159 msgid "" "Once you are done controlling the amounts, click :guilabel:`Close Session` " "to close and go back to the **POS dashboard**." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:163 msgid "" "To reach the backend without closing the session, click :guilabel:`Backend` " "on the dropdown menu." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:165 msgid "To abort, click :guilabel:`Discard` on the pop-up window." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:166 msgid "" "Depending on your setup, you might only be allowed to close a session if the" " expected cash revenue equals the counted cash. To close it anyway, click " ":guilabel:`Ok` on the :guilabel:`Payments Difference` screen." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:171 msgid "" "It is strongly advised to close your POS session at the end of each day." msgstr "" #: ../../content/applications/sales/point_of_sale.rst:172 msgid "" "To look at all your previous sessions, go to :menuselection:`Point of Sale " "--> Orders --> Sessions`." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:3 msgid "Product combos" msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:5 msgid "" "The **Product Combos** feature allows users to define and manage combination" " options for a single product." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:8 msgid "" "In the context of a restaurant, the feature enables users to create " "multiple-choice menus. For example, a user can define a main dish and " "specify various options for sides, drinks, or desserts that customers can " "combine with the main dish." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:12 msgid "" "In retail, this feature allows you to create a product set with multiple " "products to choose from and combine." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:18 msgid "First, you need to create combination choices. To do so:" msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:20 msgid "" "Go to :menuselection:`Point of Sale --> Products --> Product Combos` and " "click :guilabel:`New`." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:21 msgid "" "Name your combo and add the products you want customers to choose from by " "clicking :guilabel:`Add a line`. You can also include an extra price for " "each option in the :guilabel:`Extra Price` column." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:26 msgid "" "As a reference, the selected product's original price is displayed in the " ":guilabel:`Original Price` column." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:32 msgid "" "Second, you need to create a specific product to gather combo choices. To do" " this:" msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:34 msgid "" "Go to :menuselection:`Point of Sale --> Products --> Products` and click " ":guilabel:`New`." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:35 msgid "" "Set the :guilabel:`Product Type` to :guilabel:`Combo` and fill in the " ":guilabel:`General Information` tab." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:39 msgid "" "The sales price of the combo product is fixed and does not vary based on the" " individual prices of included items or the quantity of items in the combo. " "The combo product price is only affected by the extra price optionally " "defined at the combo choice creation or if a variant of one of the items has" " a specified extra price." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:43 msgid "" "Go to the :guilabel:`Combo Choices` tab, click :guilabel:`Add a line`, and " "select the combinations to add. You can also create a new combination at " "this step by clicking :guilabel:`New` on the popup window." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:50 msgid "" "Once you have created and added the combo choices into a product, you can " "sell combos in your retail store or restaurant." msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:54 #: ../../content/applications/sales/point_of_sale/employee_login.rst:26 #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:122 #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:32 msgid "Practical application" msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:56 msgid "" ":ref:`Open a POS session ` and select the combo product. " "Choose the options and click :guilabel:`Add to order`. As a reminder, the " "extra price appears under the related choices." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:11 msgid "Access the POS settings" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:13 msgid "" "To access the general POS settings, go to :menuselection:`Point of Sale --> " "Configuration --> Settings`. Then, open the dropdown menu in the " ":guilabel:`Point of Sale` field and select the POS to configure." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "Dropdown menu to select the POS in the app settings" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:21 msgid "" "These settings are available to users with the :doc:`access rights " "` :guilabel:`Administration` set as " ":guilabel:`Settings`." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:24 msgid "" "You can also configure some settings from the dashboard by clicking the " "vertical ellipsis button (:guilabel:`⋮`) on a POS card. Doing so opens a " "popup window, from which you can:" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:27 msgid ":doc:`Enable multiple employees to log in. `" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:28 msgid ":doc:`Connect and set up an IoT box. <../../general/iot/config/pos>`" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:29 msgid ":doc:`Connect and set up an ePOS printer. `" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "popup window to access quick settings in POS" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:35 msgid "" "These settings are available to users with the :doc:`access rights " "` :guilabel:`Point of Sale` set as " ":guilabel:`Administrator`." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:39 msgid "Make products available" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:41 msgid "" "To make products available for sale, go to :menuselection:`Point of Sale -->" " Products --> Products`, and select a product to open the product form. In " "the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "Making a product available in your POS." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:49 msgid "PoS product categories" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:54 msgid "" "POS product categories allow users to categorize products and get a more " "structured and clean POS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:57 msgid "" "To manage PoS categories, go to :menuselection:`Point of Sale --> " "Configuration --> PoS Product Categories`. To add a new category, click " ":guilabel:`Create`. Then, name it in the :guilabel:`Category Name` field." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:61 msgid "" "To associate a category with a parent category, fill in the " ":guilabel:`Parent Category` field. A parent category groups one or more " "child categories." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:0 msgid "The PoS product categories grouped by parent categories" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:69 msgid "Assign PoS product categories" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:71 msgid "" "Go to :menuselection:`Point of Sale --> Products --> Products` and open a " "product form. Then, go to the :guilabel:`Sales` tab and fill in the " ":guilabel:`Category` field under the :guilabel:`Point of Sale` section." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "Sales tab of a product form to add a PoS product category" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:79 msgid "Adapt the POS interface" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:82 msgid "Start category" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:84 msgid "" "You can select one product category to display when :ref:`opening a POS " "session `. To configure it, go to your :ref:`POS settings" " ` and select a PoS category from the dropdown menu " "of the :guilabel:`Start Category` field within the :guilabel:`PoS Interface`" " section." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "Setting to set up the start category feature" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:93 msgid "Restrict categories" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:95 msgid "" "You can also limit the categories displayed on your POS interface. To " "achieve this, go to your :ref:`POS settings ` and " "choose the specific categories to display in the :guilabel:`Restrict " "Categories` field within the :guilabel:`PoS Interface` section." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "Setting to set up the restrict category feature" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:3 msgid "ePOS printers" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:5 msgid "" "ePOS printers are designed to work seamlessly with Point of Sale systems. " "Once connected, these devices automatically share information, allowing for " "direct printing of tickets from the POS system to the ePOS printer." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:10 msgid "" "Epson printers using Wi-Fi/Ethernet connections and following the `EPOS SDK " "Javascript protocol " "`_" " are compatible with Odoo **without** needing an :doc:`IoT Box " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:14 msgid "" "Thermal printers using ESC/POS or StarPRNT protocol are compatible **with** " "an :doc:`IoT Box `." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:16 msgid "" "Epson printers using only USB connections are compatible **with** an " ":doc:`IoT Box `." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:18 msgid "Epson printers that connect via Bluetooth are **not compatible**." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:21 msgid ":doc:`https`" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:22 #: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 msgid ":doc:`epos_ssc`" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:25 msgid "Directly supported ePOS printers" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:27 msgid "" "The following ePOS printers are directly compatible with Odoo without " "needing an :doc:`IoT Box `." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:30 msgid "Epson TM-m30 i/ii/iii (Wi-Fi/Ethernet models only; Recommended)" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:31 msgid "Epson TM-H6000IV-DT (Receipt printer only)" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:32 msgid "Epson TM-T70II-DT" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:33 msgid "Epson TM-T88V-DT" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:34 msgid "Epson TM-L90-i" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:35 msgid "Epson TM-T70-i" msgstr "" #: ../../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:37 msgid "Epson TM-T83II-i" msgstr "" #: ../../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:39 msgid "Epson TM-m10" msgstr "" #: ../../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:41 msgid "Epson TM-P60II (Receipt: Wi-Fi® model)" msgstr "" #: ../../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:43 msgid "Epson TM-P80 (Wi-Fi® model)" msgstr "" #: ../../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: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:51 msgid "Epson TM-T20 family (incompatible ePOS software)" msgstr "" #: ../../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:53 msgid "Epson TM-U220 family (incompatible ePOS software)" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5 msgid "Self-signed certificate for ePOS printers" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7 msgid "" "To work with Odoo, some printer models that can be used without an :doc:`IoT" " box ` may require :doc:`the HTTPS" " protocol ` to establish a secure connection between the browser and " "the printer. However, trying to reach the printer's IP address using HTTPS " "leads to a warning page on most web browsers. In that case, you can " "temporarily :ref:`force the connection `, which " "allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " "long as the browser window stays open." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:15 msgid "" "The connection is lost after closing the browser window. Therefore, this " "method should only be used as a **workaround** or as a pre-requisite for the" " :ref:`following instructions `." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 msgid "Generate, export, and import self-signed certificates" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 msgid "" "For a long-term solution, you must generate a **self-signed certificate**. " "Then, export and import it into your browser." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 msgid "" "**Generating** an SSL certificate should only be done **once**. If you " "create another certificate, devices using the previous one will lose HTTPS " "access." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:33 msgid "Windows 10 & Linux OS" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:37 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:166 msgid "Generate a self-signed certificate" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:39 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 msgid "" "Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force " "the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " "[IP address] (unsafe)`." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "warning page about the connection privacy on Google Chrome" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:176 msgid "Warning page on Google Chrome, Windows 10" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:178 msgid "" "Then, sign in using your printer credentials to access the ePOS printer " "settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " "printer serial number in the :guilabel:`Password` field." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 msgid "" "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` " "section, and click :guilabel:`create` to generate a new **Self-Signed " "Certificate**. The :guilabel:`Common Name` should be automatically filled " "out. If not, fill it in with the printer IP address number. Select the years" " the certificate will be valid in the :guilabel:`Validity Period` field, " "click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the " "printer." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:60 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:189 msgid "" "The self-signed certificate is generated. Reload the page and click " ":guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure " "**Selfsigned Certificate** is correctly selected in the :guilabel:`Server " "Certificate` section." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 msgid "Export a self-signed certificate" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:66 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:195 msgid "" "The export process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser. Start by accessing your ePOS printer settings on your web " "browser by navigating to its IP address (e.g., `https://192.168.1.25`). " "Then, force the connection as explained in the **Generate a self-signed " "certificate tab**." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:71 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:131 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:200 msgid "If you are using **Google Chrome**," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:73 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202 msgid "" "click :guilabel:`Not secure` next to the search bar, and " ":guilabel:`Certificate is not valid`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection to the printer not secure button in Google Chrome browser." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:79 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:208 msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:80 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:209 msgid "" "add `.crt` at the end of the file name to ensure it has the correct " "extension;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:81 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210 msgid "" "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " "of the pop-up window;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:83 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:100 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:229 msgid "save, and the certificate is exported." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:86 msgid "" "Make sure that the certificate ends with the extension `.crt`. Otherwise, " "some browsers might not see the file during the import process." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:143 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 msgid "If you are using **Mozilla Firefox**," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 msgid "click the **lock-shaped** icon on the left of the address bar;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:92 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:221 msgid "" "go to :menuselection:`Connection not secure --> More information --> " "Security tab --> View certificate`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection is not secure button in Mozilla Firefox browser" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227 msgid "scroll down to the :guilabel:`Miscellaneous` section;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:99 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:228 msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:102 msgid "Import a self-signed certificate" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 msgid "" "The import process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:109 msgid "Windows 10" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 msgid "" "Windows 10 manages certificates, which means that self-signed certificates " "must be imported from the certification file rather than the browser. To do " "so," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 msgid "" "open the Windows File Explorer and locate the downloaded certification file;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:115 msgid "" "right-click on the certification file and click :guilabel:`Install " "Certificate`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 msgid "" "select where to install the certificate and for whom - either for the " ":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " "click :guilabel:`Next`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:120 msgid "" "on the `Certificate Store` screen, tick :guilabel:`Place all certificates in" " the following store`, click :guilabel:`Browse...`, and select " ":guilabel:`Trusted Root Certification Authorities`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:126 msgid "click :guilabel:`Finish`, accept the pop-up security window;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 msgid "restart the computer to make sure that the changes are applied." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 msgid "Linux" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:133 msgid "open Chrome;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 msgid "" "go to :menuselection:`Settings --> Privacy and security --> Security --> " "Manage certificates`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 msgid "" "go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " "the exported certification file;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:138 msgid "accept all warnings;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 msgid "click :guilabel:`ok`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:150 msgid "restart your browser." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 msgid "open Firefox;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:146 msgid "" "go to :menuselection:`Settings --> Privacy & Security --> Security --> View " "Certificates... --> Import`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:148 msgid "select the exported certification file;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:149 msgid "tick the checkboxes and validate;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 msgid "Mac OS" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 msgid "" "On Mac OS, you can secure the connection for all browsers by following these" " steps:" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 msgid "" "open Safari and navigate to your printer's IP address. Doing so leads to a " "warning page;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:157 msgid "" "on the warning page, go to :menuselection:`Show Details --> visit this " "website --> Visit Website`, validate;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 msgid "reboot the printer so you can use it with any other browser." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 msgid "" "To generate and export an SSL certificate and send it to IOS devices, open " "**Google Chrome** or **Mozilla Firefox**. Then," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Warning page about the connection privacy on Google Chrome" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection to the printer not secure button in Google Chrome" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:215 msgid "" "Make sure that the certificate ends with the extension `.crt`. Otherwise, " "some browsers might not find the file during the import process." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection is not secure button in Mozilla Firefox" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:231 msgid "Android OS" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233 msgid "" "To import an SSL certificate into an Android device, first create and export" " it from a computer. Next, transfer the `.crt` file to the device using " "email, Bluetooth, or USB. Once the file is on the device," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237 msgid "open the settings and search for `certificate`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:238 msgid "click :guilabel:`Certificate AC` (Install from device storage);" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:239 msgid "select the certificate file to install it on the device." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:242 msgid "" "The specific steps for installing a certificate may vary depending on the " "version of Android and the device manufacturer." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245 msgid "iOS" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:247 msgid "" "To import an SSL certificate into an iOS device, first create and export it " "from a computer. Then, transfer the `.crt` file to the device using email, " "Bluetooth, or any file-sharing service." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:251 msgid "" "Downloading this file triggers a warning pop-up window. Click " ":guilabel:`Allow` to download the configuration profile, and close the " "second pop-up window. Then," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254 msgid "go to the **Settings App** on the iOS device;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:255 msgid "click :guilabel:`Profile Downloaded` under the user's details box;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256 msgid "locate the downloaded `.crt` file and select it;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:257 msgid "click :guilabel:`Install` on the top right of the screen;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258 msgid "if a passcode is set on the device, enter the passcode;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:259 msgid "" "click :guilabel:`Install` on the top right of the certificate warning screen" " and the pop-up window;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:261 msgid "click :guilabel:`Done`." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:265 msgid "" "The certificate is installed, but it still needs to be authenticated. To do " "so," msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267 msgid "" "go to :menuselection:`Settings --> General --> About > Certificate Trust " "Settings`;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:268 msgid "enable the installed certificate using the **slide button**;" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:269 msgid "click :guilabel:`Continue` on the pop-up window." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272 msgid "" "If you need to export SSL certificates from an operating system or web " "browser that has not been mentioned, search for `export SSL certificate` + " "`the name of your browser or operating system` in your preferred search " "engine." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:275 msgid "" "Similarly, to import SSL certificates from an unmentioned OS or browser, " "search for `import SSL certificate root authority` + `the name of your " "browser or operating system` in your preferred search engine." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280 msgid "Check if the certificate was imported correctly" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282 msgid "" "To confirm your printer's connection is secure, connect to its IP address " "using HTTPS. For example, navigate to `https://192.168.1.25` in your " "browser. If the SSL certificate has been applied correctly, you should no " "longer see a warning page, and the address bar should display a padlock " "icon, indicating that the connection is secure." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:3 msgid "Secure connection (HTTPS)" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:5 msgid "" "If **Direct Devices** is enabled in a Point of Sale settings (for example, " "if you use an :doc:`ePos printer `), HTTP becomes the default" " protocol." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:9 msgid "Force your Point of Sale to use a secure connection (HTTPS)" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:11 msgid "" "Add a new **key** in the **System Parameters** to force your Point of Sale " "to use a secure connection with the HTTPS protocol." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:14 msgid "" "To do so, activate the :ref:`developer mode `, go to " ":menuselection:`Settings --> Technical --> Parameters --> System " "Parameters`, then create a new parameter, add the following values and click" " on *Save*." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:18 msgid "**Key**: `point_of_sale.enforce_https`" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:19 msgid "**Value**: `True`" msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:3 msgid "Multi-employee management" msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:5 msgid "" "Odoo Point of Sale allows you to manage access to a specific POS by enabling" " the **Multi Employees per Session** feature. When activated, :ref:`you can " "select which users can log into the POS ` and :ref:`keep" " track of the employees involved in each order `." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:15 msgid "" ":ref:`Access the POS settings ` and select your POS," " or click the vertical ellipsis button (:guilabel:`⋮`) on a POS card and " "click :guilabel:`Edit`. Then, enable :guilabel:`Multi Employees per " "Session`, and add the allowed employees in the :guilabel:`Allowed Employees`" " field." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "setting to enable multiple cashiers in POS" msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:28 msgid "" "Once the feature is activated, cashiers can log in :ref:`by scanning their " "badge ` or selecting their name from the list of " "allowed employees to :ref:`open the session `." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "window to open a session when the multiple cashiers feature is enabled" msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:35 msgid "" "To switch to another user :ref:`from an open session `, " "click the employee name at the top-right of the screen and select the " "employee to swap with from the list." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "button to switch from one cashier to another." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:41 msgid "" "You can also require your employees to enter a pin code every time they log " "into a POS to prevent them from logging in as someone else. To define the " "code, go to the **Employees** app, open the employee form, and click the " ":guilabel:`HR settings` tab. Then, enter a pin code of your choice in the " ":guilabel:`PIN Code` field of the :guilabel:`Attendance/Point of Sale` " "category." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "setting on the employee form to assign a badge ID and a PIN code." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:52 msgid "Log in using badges" msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:54 msgid "" "For your employees to be able to log in by scanning their badge, they must " "have a badge ID assigned. To do so, go to the **Employees** app, open the " "employee form, and click the :guilabel:`HR settings` tab. Then, enter the " "badge ID of your choice in the :guilabel:`Badge ID` field of the " ":guilabel:`Attendance/Point of Sale` category or click :guilabel:`Generate`." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:59 msgid "" "To switch to another user, lock the session by clicking the lock-shaped icon" " (:guilabel:`🔓`) at the top-right of the screen and scan your badge." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:65 msgid "Analytics" msgstr "Analitika" #: ../../content/applications/sales/point_of_sale/employee_login.rst:67 msgid "" "Once you close and post the POS session, access the comprehensive report to " "review all session activities, including who initiated the session and who " "handled specific orders. To access the session's report, click the vertical " "ellipsis button (:guilabel:`⋮`) on the POS card and select " ":guilabel:`Sessions` from the :guilabel:`View` section. Then, select a " "specific session for more detailed information, and click the " ":guilabel:`Orders` button to view a list of all orders placed during that " "session." msgstr "" #: ../../content/applications/sales/point_of_sale/employee_login.rst:74 msgid "" "To get an overview of all orders, regardless of the session, click the " "vertical ellipsis button (:guilabel:`⋮`) on the POS card and select " ":guilabel:`Orders` from the :guilabel:`View` section." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:5 msgid "Payment methods" msgstr "Načini plačila" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:7 msgid "" "To add a payment method, you first need to create it. Go to " ":menuselection:`Point of Sale --> Configuration --> Payment Methods --> " "New`, and set a name. Check :guilabel:`Identify Customer` to allow this " "payment method *exclusively* for registered customers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:11 msgid "" "Then, select the :guilabel:`Journal`. Choose :guilabel:`Cash` to use this " "payment method for cash payments, or :guilabel:`Bank` to use it for card " "payments." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst-1 msgid "Creating a new payment method for a POS." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:18 msgid "" "Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a" " Payment Terminal` field in which you can add your :doc:`payment terminal's " "information `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:23 msgid ":doc:`payment_methods/terminals`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:50 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:63 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81 msgid "" "Once the payment method is created, you can select it in your POS settings. " "To do so, go to the :ref:`POS' settings `, click " ":guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` " "section." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5 msgid "Payment terminals" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7 msgid "" "Connecting and integrating a payment terminal with your POS system allows " "you to accept multiple payment options, including credit and debit cards, " "making the payment process more efficient." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:15 msgid "" "Go to the :ref:`application settings `, scroll down " "to the :guilabel:`Payment Terminals` section, and tick your terminal's " "checkbox." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst-1 msgid "checkbox in the settings to enable a payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 msgid "Then, follow the corresponding documentation to configure your device:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 msgid ":doc:`Adyen configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 msgid ":doc:`Ingenico configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 msgid ":doc:`Mercado Pago configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26 msgid ":doc:`Razorpay configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:27 msgid ":doc:`SIX configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28 msgid ":doc:`Stripe configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:29 msgid ":doc:`Vantiv configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:30 msgid ":doc:`Viva Wallet configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:31 msgid ":doc:`Worldline configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:33 msgid "" "Once the terminal is configured, you can :doc:`create the corresponding " "payment method and add it to the POS <../payment_methods>`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3 msgid "Adyen" msgstr "Adyen" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:5 msgid "" "Connecting an **Adyen payment terminal** allows you to offer a fluid payment" " flow to your customers and ease the work of your cashiers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:9 msgid "" "Adyen payment terminals do not require an :doc:`IoT Box " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:10 msgid "" "Adyen terminals can be used in many countries, but not worldwide. Check the " "`List of countries supported by Adyen `_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:12 msgid "" "Adyen works only with businesses processing more than **$10 million " "annually** or invoicing a minimum of **1,000 transactions per month**." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:16 msgid "" "`List of payment methods supported by Adyen `_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:17 msgid "" "`List of Adyen terminals `_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:22 msgid "" "Start by creating your Adyen account on `Adyen's website " "`_. Then, board your terminal following the steps " "described on your terminal's screen." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:26 msgid "" "`Adyen Docs - Payment terminal quickstart guides " "`_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31 msgid "Generate an Adyen API key" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:33 msgid "" "The **Adyen API key** is used to authenticate requests from your Adyen " "terminal. To generate an API key, go to your :menuselection:`Adyen account " "--> Developers --> API credentials`, and **create** new credentials or " "select **existing** ones. Click :guilabel:`Generate an API key` and save the" " key to paste it into the Odoo :guilabel:`Adyen API key` field at :ref:`the " "payment method creation `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 msgid "" "`Adyen Docs - API credentials `_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46 msgid "Locate the Adyen terminal identifier" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:48 msgid "" "The **Adyen Terminal Identifier** is the terminal's serial number, which is " "used to identify the hardware." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:51 msgid "" "To find this number, go to your :menuselection:`Adyen account --> Point of " "Sale --> Terminals`, select the terminal to link with, and save its serial " "number to paste it into the Odoo :guilabel:`Adyen Terminal Identifier` field" " at :ref:`the payment method creation `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:57 msgid "Set the Event URLs" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:59 msgid "" "For Odoo to know when a payment is made, you must configure the terminal " "**Event URLs**. To do so," msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:61 msgid "Log in to `Adyen's website `_;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:62 msgid "" "Go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and" " select the connected terminal;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:64 msgid "From the terminal settings, click :guilabel:`Integrations`;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65 msgid "" "Set the :guilabel:`Switch to decrypted mode to edit this setting` field as " ":guilabel:`Decrypted`;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:66 msgid "" "Click the **pencil icon** button and enter your server address, followed by " "`/pos_adyen/notification` in the :guilabel:`Event URLs` field;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68 msgid "Click :guilabel:`Save` at the bottom of the screen to save changes." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:73 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:41 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:30 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:81 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:72 msgid "Configure the payment method" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:75 msgid "" "Enable the payment terminal :ref:`in the application settings " "` and :doc:`create the related payment method " "<../../payment_methods>`. Set the journal type as :guilabel:`Bank` and " "select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:79 msgid "" "Finally, fill in the mandatory fields with your :ref:`Adyen API key " "`, :ref:`Adyen Terminal Identifier `, and " ":guilabel:`Adyen Merchant Account`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:89 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:56 #: ../../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/viva_wallet.rst:123 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:96 msgid "Pay with a payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:91 msgid "" "When processing a payment, select :guilabel:`Adyen` as the 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/adyen.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:0 msgid "" "In case of connection issues between Odoo and the payment terminal, force " "the payment by clicking on :guilabel:`Force Done`, which allows you to " "validate the order." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:0 msgid "" "This option is only available after receiving an error message informing you" " that the connection failed." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:100 msgid "To cancel the payment request, click on :guilabel:`cancel`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:3 msgid "Ingenico" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:5 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:5 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:5 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:5 msgid "" "Connecting a payment terminal allows you to offer a fluid payment flow to " "your customers and ease the work of your cashiers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:9 msgid "" "Ingenico payment terminals require an :doc:`IoT Box " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:10 msgid "" "Ingenico is currently only available in Belgium, the Netherlands and " "Luxembourg." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:11 msgid "" "Odoo works with the Ingenico Lane/, Desk/, and Move/ payment terminals as " "they support the TLV communication protocol through TCP/IP." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:18 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:19 msgid "Connect an IoT Box" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:20 msgid "" "Connecting an Ingenico payment terminal to Odoo is a feature that requires " "an IoT Box. For more information on how to connect an IoT Box to your " "database, please refer to the :doc:`IoT documentation " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:25 msgid "Configure the Lane/Desk/Move 5000 terminals for Ingenico BENELUX" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 msgid "" "Press the function button (:guilabel:`F` on Lane/5000, :guilabel:`⦿` on " "Desk/5000 and Move/5000)." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:29 msgid "" "Go to :menuselection:`Kassa menu --> Settings Menu` and enter the settings " "password." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:30 msgid "" "Select :guilabel:`Change Connection` and press :guilabel:`OK` on the next " "screen." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:31 msgid "Select :guilabel:`TCP/IP` and :guilabel:`IP-address`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:32 msgid "On the next screen, enter the IP address of your IoT Box." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:33 msgid "" "Enter `9000` as port number and press :guilabel:`OK` on the next screen." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:35 msgid "" "At this point, the terminal restarts and should be displayed in your IoT Box" " form in Odoo." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:43 msgid "" "Enable the payment terminal :ref:`in the application settings " "` and :doc:`create the related payment method " "<../../payment_methods>`. Set the journal type as :guilabel:`Bank` and " "select :guilabel:`Ingenico` in the :guilabel:`Use a Payment Terminal` field." " Then, select your terminal device in the :guilabel:`Payment Terminal " "Device` field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:57 msgid "" "In your *PoS interface*, when processing a payment, select a *Payment " "Method* using a payment terminal. Check that the amount in the tendered " "column is the one that has to be sent to the payment terminal and click on " "*Send*. When the payment is successful, the status will change to *Payment " "Successful*." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:66 msgid "" "If you want to cancel the payment request, click on cancel. You can still " "retry to send the payment request." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:69 msgid "" "If there is any issue with the payment terminal, you can still force the " "payment using the *Force Done*. This will allow you to validate the order in" " Odoo even if the connection between the terminal and Odoo has issues." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:75 msgid "" "This option will only be available if you received an error message telling " "you the connection failed." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:78 msgid "" "Once your payment is processed, on the payment record, you’ll find the type " "of card that has been used and the transaction ID." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:3 msgid "Mercado Pago" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:9 msgid "" "Only **Point Smart** payment terminals in **Argentina**, **Brazil**, and " "**Mexico** are supported. They can be purchased on `Mercado Pago's website " "`_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:14 msgid "" "`Mercado Pago online payments `_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:22 msgid "Create a `Mercado Pago account `_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:23 msgid "" "Associate your Point Smart terminal with a :guilabel:`store` and a " ":guilabel:`cash drawer` by following `Mercado Pago's documentation " "`_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:27 msgid "" "All purchased terminals are automatically displayed on your Mercado " "dashboard." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:29 msgid "" "Set your Point Smart terminal to the :guilabel:`Point of Sale` operation " "mode." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:32 msgid "Odoo does not support the :guilabel:`Standalone` operation mode." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:34 msgid "" ":ref:`Create a Point Smart application `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:35 msgid ":ref:`Generate your credentials `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:36 msgid "" ":ref:`Create and configure the related payment method `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:41 msgid "Point Smart application" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:43 msgid "" "Create a new application from Mercado Pago's `developer panel " "`_ by following `Mercado Pago's " "applications documentation `_, " "making sure you select :guilabel:`In person Payments`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:51 msgid "Credentials" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:53 msgid "" "Once the Point Smart application is created, three credentials are required:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:55 msgid "An access token that Odoo uses to call Mercado Pago." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:56 msgid "" "A webhook secret key that Odoo uses to authenticate notifications sent by " "Mercado Pago." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:57 msgid "" "The **terminal serial number** at the back of your Point Smart terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:59 msgid "" "Retrieve the access token and webhook secret key by following `Mercado " "Pago's credentials documentation " "`_. Then, copy and paste them into Odoo when " "creating the payment method." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:64 msgid "" "For the webhooks configuration, add the URL of your Odoo database (e.g., " "`https://mycompany.odoo.com`) followed by `/pos_mercado_pago/notification` " "(e.g., `https://mycompany.odoo.com/pos_mercado_pago/notification`)." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:0 msgid "Webhooks configuration on Mercado Pago." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:74 msgid "Payment method" msgstr "Način plačila" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:76 msgid "" ":doc:`Activate the POS Mercado Pago module " "<../../../../general/apps_modules>` to enable the payment terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:78 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:34 msgid "" ":doc:`Create the related payment method <../../payment_methods>` by going to" " :menuselection:`Point of Sale --> Configuration --> Payment Methods`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:80 msgid "Set the journal type as :guilabel:`Bank`" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:81 msgid "" "Select :guilabel:`Mercado Pago` in the :guilabel:`Use a Payment Terminal` " "field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:82 msgid "" "Fill in the mandatory fields with the :ref:`previously generated credentials" " `:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:85 msgid "" "Fill in the :guilabel:`Production user token` field using the access token." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:86 msgid "" "Fill in the :guilabel:`Production secret key` field using the webhook secret" " key." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:87 msgid "" "Fill in the :guilabel:`Terminal S/N` field using the terminal serial number." " You can find it at the back of your terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:89 msgid "" "Click the :guilabel:`Force PDV` button to activate the Point of Sale mode." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst-1 msgid "Form to create a new payment method." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:94 msgid "" "Select the payment method by going to the :ref:`POS' settings " "` and adding it to the payment method under the " ":guilabel:`Payment Methods` field of the :guilabel:`Payment` section." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:101 msgid "Paying with a payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:103 msgid "" "When processing a payment, select your Mercado Pago payment method, check " "the amount, and click :guilabel:`Send`. Once the payment is successful, the " "status changes to :guilabel:`Payment Successful`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:108 msgid "" "In case of connection issues between Odoo and the payment terminal, force " "the payment by clicking :guilabel:`Force Done`, which allows you to validate" " the order. This option is only available after receiving an error message " "informing you that the connection failed." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:111 msgid "To cancel the payment request, click :guilabel:`Cancel`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:114 msgid "" "Any action made on the terminal should trigger a notification on the POS " "interface. Ensure the :ref:`webhook secret key ` is correctly configured if you are not notified." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:3 msgid "Razorpay" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:5 msgid "" "Connecting a Razorpay payment terminal allows you to offer a fluid payment " "flow to your customers and ease the work of your cashiers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:9 msgid "" ":doc:`Use Razorpay as apayment provider. " "<../../../../finance/payment_providers/razorpay>`" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:17 msgid "Locate your Razorpay credentials" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:19 msgid "" "`Create a Razorpay account `_ and set it up on their website." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:22 msgid "" "You need the following credentials to set up the payment method in Odoo:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:24 msgid "" "`API key `_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:25 msgid "Razorpay username" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:26 msgid "" "Razorpay device serial number, which can be found underneath the device or " "on `Razorpay's dashboard `_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:32 msgid "" ":doc:`Activate the POS Razorpay module <../../../../general/apps_modules>` " "to enable the payment terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:37 msgid "Set the :guilabel:`Journal` type as :guilabel:`Bank`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:38 msgid "" "Select :guilabel:`Razorpay` in the :guilabel:`Use a Payment Terminal` field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:39 msgid "" "Enter your username in the :guilabel:`Razorpay Username` field and your " "device's serial number in the :guilabel:`Razorpay Device Serial No` field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:41 msgid "" "Fill in the :guilabel:`Razorpay API Key` field with the :ref:`Razorpay API " "key `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:43 msgid "" "Set the :guilabel:`Razorpay Allowed Payment Modes` according to your needs." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst-1 msgid "Razorpay connection form" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:49 msgid "" "You can enable the :guilabel:`Razorpay Test Mode` field while testing or " "keep it unchecked for production." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:52 msgid "" "Once the payment method is created, you can enable it for your POS. 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/razorpay.rst:58 msgid "" "When processing a payment, select the Razorpay payment method. Check the " "amount and click :guilabel:`Send`. Once the payment is successful, the " "status changes to :guilabel:`Payment Successful`. To cancel the payment " "request, click :guilabel:`Cancel`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:70 msgid "The terminal must have at least a 10% battery level to use it." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:3 msgid "SIX" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5 msgid "" "Connecting a **SIX payment terminal** allows you to offer a fluid payment " "flow to your customers and ease the work of your cashiers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9 msgid "" "Even though Worldline has acquired SIX Payment Services and both companies " "use Yomani payment terminals, the firmware they run is different. Terminals " "received from Worldline are, therefore, not compatible with this " "integration." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:17 msgid "Install the POS IoT Six module" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 msgid "" "To activate the POS IoT Six module, go to :guilabel:`Apps`, remove the " ":guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds " "the necessary driver and interface to your database to detect Six terminals." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:24 msgid "This module replaces the **POS Six** module." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:27 msgid "Connect an IoT box" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29 msgid "" "Connecting a Six payment terminal to Odoo is requires :doc:`using a " "Raspberry Pi or virtual (for Windows OS only) IoT box " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33 msgid "Configure the terminal ID" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35 msgid "" "Navigate to your IoT Box homepage, where you can find the :guilabel:`Six " "payment terminal` field once your database server is connected to the IoT " "box. Click :guilabel:`Configure`, fill in the :guilabel:`Terminal ID` field " "with the ID received from Six, and click :guilabel:`Connect`. Your Six " "terminal ID should appear in the :guilabel:`Current Terminal Id` section." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Setting the Six terminal ID" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:43 msgid "" "Odoo automatically restarts the IoT box when the Six terminal ID is " "configured. If your Six terminal is online, it will be automatically " "detected and connected to the database. Check the IoT box homepage under the" " :guilabel:`Payments` section to confirm the connection." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Confirming the connection to the Six payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55 msgid "" "Enable the payment terminal :ref:`in the application settings " "` and :doc:`create the related payment method " "<../../payment_methods>`. Set the journal type as :guilabel:`Bank` and " "select :guilabel:`SIX IOT` in the :guilabel:`Use a Payment Terminal` field. " "Then, select your terminal device in the :guilabel:`Payment Terminal Device`" " field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Creating a new payment method for the SIX payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:70 msgid "" "When processing a payment, select :ref:`your Six payment method " "` in the :guilabel:`Payment Method` section and click " ":guilabel:`Send`. To cancel the payment request, click :guilabel:`Cancel`. " "Once the payment is successful, the status switches to :guilabel:`Payment " "Successful`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Paying with Six" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:79 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:101 msgid "" "Once your payment is processed, the type of card used and the transaction ID" " appear on the payment record." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:81 msgid "" "The language used for error messages is the same as the Six terminal. " "Configure the terminal to change the language or contact Six." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:83 msgid "By default, the port used by the Six terminal is `7784`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:86 msgid "" "If there are connection issues between the payment terminal and Odoo, you " "can still force the payment validation in Odoo using the :guilabel:`Force " "Done` button." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:3 msgid "Stripe" msgstr "Stripe" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:9 msgid "" "Stripe payment terminals do not require an :doc:`IoT Box " "`" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:10 msgid "" "Stripe terminals can be used in many countries, but not worldwide. Check the" " `global availability for Stripe Terminal " "`_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:12 msgid "" "Stripe's integration works with `Stripe Terminal smart readers " "`_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 msgid "" ":doc:`Stripe as payment provider " "<../../../../finance/payment_providers/stripe>`" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:16 msgid "" "`List of payment methods supported by Stripe " "`_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:24 msgid "" "Activate **Stripe** in the settings by going to :menuselection:`Point of " "Sale --> Configuration --> Settings --> Payment Terminals` and enabling " ":guilabel:`Stripe`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:27 msgid "Then, create the payment method:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:29 msgid "" "Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, " "click :guilabel:`Create`, and complete the :guilabel:`Method` field with " "your payment method's name;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:31 msgid "" "Set the :guilabel:`Journal` field as :guilabel:`Bank` and the :guilabel:`Use" " a Payment Terminal` field as :guilabel:`Stripe`;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:33 msgid "" "Enter your payment terminal serial number in the :guilabel:`Stripe Serial " "Number` field;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:34 msgid "" "Click :guilabel:`Don't forget to complete Stripe connect before using this " "payment method.`" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst-1 msgid "payment method creation form" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:41 msgid "" "Click :guilabel:`Identify Customer` to allow this payment method " "**exclusively** for identified customers. For any unidentified customers to " "be able to pay with Stripe, leave the :guilabel:`Identify Customer` field " "unchecked." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:44 msgid "" "The :guilabel:`Outstanding Account` and the :guilabel:`Intermediary Account`" " can stay empty to use the default accounts." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:46 msgid "" "Find your payment terminal serial number under the device or on `Stripe's " "dashboard `_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:50 msgid "Connect Stripe to Odoo" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:52 msgid "" "Click :guilabel:`Connect Stripe`. Doing so redirects you automatically to a " "configuration page. Fill in all the information to create your Stripe " "account and link it with Odoo. Once the forms are completed, the API keys " "(:guilabel:`Publishable Key` and :guilabel:`Secret Key`) can be retrieved on" " **Stripe's** website. To do so, click :guilabel:`Get your Secret and " "Publishable keys`, click the keys to copy them, and paste them into the " "corresponding fields in Odoo. Your terminal is ready to be configured in a " "POS." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 msgid "stripe connection form" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:64 msgid "" "When you use **Stripe** exclusively in Point of Sale, you only need the " "**Secret Key** to use your terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:66 msgid "" "When you use Stripe as **payment provider**, the :guilabel:`State` can stay " "set as :guilabel:`Disabled`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:68 msgid "" "For databases hosted **On-Premise**, the :guilabel:`Connect Stripe` button " "does not work. To retrieve the API keys manually, log in to your `Stripe " "dashboard `_, type `API` in the search bar, " "and click :guilabel:`Developers > API`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:74 msgid "Configure the payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:76 msgid "" "Swipe right on your payment terminal, click :guilabel:`Settings`, enter the " "admin PIN code, validate and select your network." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:80 msgid "The user's device and the terminal must share the same network." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:81 msgid "In case of a Wi-Fi connection, the network must be secured." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:82 msgid "" "You must enter the admin PIN code to access your payment terminal settings. " "By default, this code is `07139`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:116 msgid "Link the payment method to a POS" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:88 msgid "" "To add a **payment method** to your point of sale, go to " ":menuselection:`Point of Sale --> Configuration --> Settings`. Select the " "POS, scroll down to the :guilabel:`Payments` section, and add your payment " "method for **Stripe** in the :guilabel:`Payment Methods` field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:95 msgid "" "When processing a payment, select :guilabel:`Stripe` as the payment method. " "Check the amount and click :guilabel:`Send`. Once the payment is successful," " the status changes to :guilabel:`Payment Successful`. To cancel the payment" " request, click :guilabel:`cancel`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104 msgid "The terminal must have at least 10% battery level to use it." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:105 msgid "The device does not work for payments under €0.50." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:108 msgid "Troubleshooting" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:111 msgid "Payment terminal unavailable in your Stripe account" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:113 msgid "" "If the payment terminal is unavailable in your Stripe account, you must add " "it manually:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:115 msgid "" "Log into your `Stripe's dashboard `_ and go to" " :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:117 msgid "" "Add a location by clicking the :guilabel:`+ New` button or selecting an " "already created location;" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:118 msgid "" "Click the :guilabel:`+ New` button in the :guilabel:`Readers` box and fill " "in the required information." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:122 msgid "" "You must provide a **registration code**. To retrieve that code, swipe right" " on your device, enter the admin PIN code (by default: `07139`), validate, " "and click :guilabel:`Generate a registration code`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:3 msgid "Vantiv" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:5 msgid "" "Connecting a Vantiv payment terminal allows you to offer a fluid payment " "flow to your customers and ease the work of your cashiers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:9 msgid "" "Please note MercuryPay only operates with US and Canadian banks, making this" " procedure only suitable for North American businesses." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 msgid "" "Vantiv card readers should be purchased exclusively from Vantiv, as certain " "Vantiv terminals bought on Amazon do not include the correct encryption " "needed to be used with an Odoo database." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22 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: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 "" "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:43 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:125 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/viva_wallet.rst:3 msgid "Viva Wallet" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:5 msgid "" "Connecting a **Viva Wallet** :doc:`payment terminal <../terminals>` allows " "you to offer a fluid payment flow to your customers and ease the work of " "your cashiers." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:9 msgid "" "Viva Wallet lets you turn your phone into a mobile card reader: `Tap On " "Phone `_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:15 msgid "" "Start by creating your Viva Wallet account on `Viva Wallet's website " "`_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:18 msgid "Locate your Viva Wallet credentials" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:20 msgid "" "When configuring Viva Wallet in Point of Sale, you need to use specific " "credentials that are available in your Viva Wallet account. These " "credentials include your :ref:`Merchant ID `, :ref:`API " "key `, :ref:`POS API credentials `," " and :ref:`Terminal ID ` number." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:28 msgid "Merchant ID and API key" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:30 msgid "" "Locate your `Merchant ID and API key following the Viva documentation " "`_. Then, save the keys and paste them " "into the Odoo :guilabel:`Merchant ID` and :guilabel:`API Key` fields " ":ref:`when creating the payment method `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst-1 msgid "merchant ID and API key fields" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:39 msgid "These credentials are used for APIs that authenticate with Basic Auth." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:44 msgid "POS API credentials" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:46 msgid "" "Locate and generate your `POS API credentials following the Viva " "documentation `_. Then, save the keys and paste " "them in the Odoo :guilabel:`Client secret` and :guilabel:`Client ID` fields " ":ref:`when creating the payment method `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:52 msgid "" "These credentials are only displayed once. Ensure you keep a copy to secure " "them." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst-1 msgid "Client secret and client ID fields" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:58 msgid "" "These credentials are used for Android and iOS POS Activation requests, as " "well as the Cloud Terminal API." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:64 msgid "Terminal ID" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:66 msgid "Your terminal ID number is used to identify your terminal. To find it:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:68 msgid "Go to your Viva Wallet account and select the relevant account." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:69 msgid "" "Go to :menuselection:`Sales --> Physical payments --> Card terminals` in the" " navigation menu." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:71 msgid "" "The terminal ID number is located under the :guilabel:`Terminal ID (TID)` " "column. Save it to paste it into the :guilabel:`Terminal ID` field " ":ref:`when creating the payment method `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst-1 msgid "Viva terminal ID" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:83 msgid "" ":doc:`Activate the POS Viva Wallet module " "<../../../../general/apps_modules>` to enable the payment terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:85 msgid "" ":doc:`Create the related payment method <../../payment_methods>` by going to" " :menuselection:`Point of Sale --> Configuration --> Payment Methods` and " "clicking :guilabel:`New`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:88 msgid "Set the journal type as :guilabel:`Bank`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:89 msgid "" "Select :guilabel:`Viva Wallet` in the :guilabel:`Use a Payment Terminal` " "field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:90 msgid "Fill in the mandatory fields with your:" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:92 msgid ":ref:`Merchant ID and API key `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:93 msgid ":ref:`Client ID and Client secret `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:94 msgid ":ref:`Terminal ID `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:96 msgid "" "Save the form and copy the generated webhook URL from the :guilabel:`Viva " "Wallet Webhook Endpoint` field. This URL is necessary :ref:`when configuring" " the webhook `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:106 msgid "Configure the webhook" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:108 msgid "" "Webhooks allow you to receive real-time notifications whenever a transaction" " occurs within your Viva Wallet account. Set them up for `payment " "transactions following the Viva documentation " "`_." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:113 msgid "" "`Setting up webhooks `_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:118 msgid "" "You can select the payment method in your POS settings once the payment " "method is created. To do so, go to the :ref:`POS' settings " "` and add the payment method under the " ":guilabel:`Payment methods` field of the :guilabel:`Payment` section." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:134 msgid "To cancel the payment request, click :guilabel:`cancel`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3 msgid "Worldline" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 msgid "" "Worldline payment terminals require an :doc:`IoT Box " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:10 msgid "" "Worldline is currently only available in Belgium, the Netherlands and " "Luxembourg." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:11 msgid "" "Odoo is compatible with Worldline terminals that use the CTEP protocol " "(e.g., the Yomani XR and Yoximo terminals). If you have any doubts, contact " "your payment provider to ensure your terminal's compatibility." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:21 msgid "" "Connecting a Worldline Payment Terminal to Odoo is a feature that requires " "an IoT Box. For more information on how to connect one to your database, " "please refer to the :doc:`IoT documentation " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:26 msgid "Configure the protocol" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:28 msgid "" "From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " "0 --> 9`. Enter the technician password **\"1235789\"** and click on " ":menuselection:`OK --> 4 --> 2`. Then, click on :menuselection:`Change --> " "CTEP (as Protocole ECR) --> OK`. Click on **OK** thrice on the subsequent " "screens (*CTEP ticket ECR*, *ECR ticket width*, and *Character set*). " "Finally, press **Stop** three times; the terminal automatically restarts." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:35 msgid "Set the IP address" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:37 msgid "" "From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " "0 --> 9`. Enter the technician password **\"1235789\"** and click on " ":menuselection:`OK --> 4 --> 9`. Then, click on :menuselection:`Change --> " "TCP/IP` (*TCP physical configuration* screen) :menuselection:`--> OK --> OK`" " (*TCP Configuration client* screen)." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:42 msgid "Finally, set up the hostname and port number." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:45 msgid "Hostname" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:48 msgid "" "To set up the hostname, enter your IoT box's IP address' sequence numbers " "and press **OK** at each \".\" until you reach the colon symbol." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:49 msgid "Then, press **OK** twice." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 msgid "Here's an IP address sequence: `10.30.19.4:8069`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 msgid "" "On the *Hostname screen*, type :menuselection:`10 --> OK --> 30 --> OK --> " "19 --> OK --> 4 --> OK --> OK`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:57 msgid "" "Your IoT box's IP address is available in your IoT Box application's " "database." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:60 msgid "Port number" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:62 msgid "" "On the *Port number* screen, enter **9001** (or **9050** for Windows) and " "click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> " "OK`. Click on **Stop** three times; the terminal automatically restarts." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:67 msgid "" "For **Windows** IoT devices, it is necessary to add a firewall exception. " "Follow the :ref:`additional instructions in the Windows IoT documentation " "` to add the exception to Windows Firewall." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:74 msgid "" "Enable the payment terminal :ref:`in the application settings " "` and :doc:`create the related payment method " "<../../payment_methods>`. Set the journal type as :guilabel:`Bank` and " "select :guilabel:`Worldline` in the :guilabel:`Use a Payment Terminal` " "field. Then, select your terminal device in the :guilabel:`Payment Terminal " "Device` field." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:88 msgid "Technician password: `1235789`" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:89 msgid "" "To reach Wordline's technical assistance, call `02 727 61 11` and choose " "\"merchant\". Your call is automatically transferred to the desired service." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 msgid "" "Configure the cashier terminal if you have both a customer and a cashier " "terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:92 msgid "" "To avoid blocking the terminal, check the initial configuration beforehand." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:93 msgid "" "Set a fixed IP to your IoT Box’s router to prevent losing the connexion." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98 msgid "" "When processing a payment, select *Worldline* as payment method. Check the " "amount and click on *Send*. Once the payment is successful, the status " "changes to *Payment Successful*." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:108 msgid "" "In case of connexion issues between Odoo and the payment terminal, force the" " payment by clicking on *Force Done*, which allows you to validate the " "order. This option is only available after receiving an error message " "informing you that the connection failed." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:111 msgid "To cancel the payment request, click on **cancel**." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing.rst:5 msgid "Pricing features" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:3 msgid "Cash rounding" msgstr "Gotovinsko zaokroževanje" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:5 msgid "" "**Cash rounding** is required when the lowest physical denomination of " "currency, or the smallest coin, is higher than the minimum unit of account." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:9 msgid "" "For example, some countries require their companies to round up or down the " "total amount of an invoice to the nearest five cents, when the payment is " "made in cash." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:13 msgid "" "Each point of sale in Odoo can be configured to apply cash rounding to the " "totals of its bills or receipts." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:19 msgid "" "Go to :menuselection:`Point of Sale --> Configuration --> Settings` and " "enable *Cash Rounding*, then click on *Save*." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:25 msgid "" "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, " "open the point of sale you want to configure, and enable the *Cash Rounding*" " option." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:29 msgid "" "To define the **Rounding Method**, open the drop-down list and click on " "*Create and Edit...*." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:32 msgid "" "Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*," " then save both the Rounding Method and your Point of Sale settings." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:39 msgid "" "All total amounts of this point of sale now add a line to apply the rounding" " according to your settings." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:46 msgid "" "Odoo Point of Sale only supports the :guilabel:`Add a rounding line` " "rounding strategy." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:3 msgid "Discount tags (barcode scanner)" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:5 msgid "" "If you want to sell your products with a discount, for a product getting " "close to its expiration date for example, you can use discount tags. They " "allow you to scan discount barcodes." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:10 msgid "To use discount tags you will need to use a barcode scanner." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:13 msgid "Barcode Nomenclature" msgstr "Nomenklatura črtne kode" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:15 msgid "To use discounts tags, we need to learn about barcode nomenclature." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:17 msgid "" "Let's say you want to have a discount for the product with the following " "barcode:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:23 msgid "" "You can find the *Default Nomenclature* under the settings of your PoS " "interface." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:32 msgid "" "Let's say you want 50% discount on a product you have to start your barcode " "with 22 (for the discount barcode nomenclature) and then 50 (for the %) " "before adding the product barcode. In our example, the barcode would be:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:41 msgid "Scan the products & tags" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:43 msgid "You first have to scan the desired product (in our case, a lemon)." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:48 msgid "" "And then scan the discount tag. The discount will be applied and you can " "finish the transaction." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:333 msgid "Discounts" msgstr "Popusti" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:5 msgid "" "By offering discounts, you can entice your customers and drastically " "increase your revenue. It is vital to offer discounts, whether they are " "time-limited, seasonal or manually given." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:9 msgid "" "To manage discounts, Odoo has powerful features that help set up a pricing " "strategy tailored to every business." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:13 msgid "Apply manual discounts" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:15 msgid "" "If you seldom use discounts, applying manual ones might be the easiest " "solution for your Point of Sale." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:18 msgid "" "You can either apply a discount on the whole order or on specific products " "inside an order." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:22 msgid "Apply a discount on a product" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:24 msgid "From your PoS session interface, use the *Disc* button." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the discount button for manual discount" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:30 msgid "" "Then, you can input a discount over the product that is currently selected." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:34 msgid "Apply a global discount" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:36 msgid "" "To apply a discount on the whole order, go to :menuselection:`Point of Sales" " --> Configuration --> Point of Sale` and select your PoS." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:39 msgid "" "Once on your PoS form, select *Global Discounts*, under the *Pricing* " "category." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the feature to enable for global discount" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:45 msgid "Now, you have a new *Discount* button appearing on your PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the button to use for global discount via the pos interface" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:51 msgid "Click on it and enter the wanted discount." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the discount offered in the payment summary" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:58 msgid "" "On this example, there is a global discount of 50% as well as a specific 50%" " discount on oranges." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:62 msgid "Apply time-limited discounts" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:64 msgid "" "To activate time-limited discounts, you must activate the *Pricelists* " "feature. To do so, go to :menuselection:`Point of Sales --> Configuration " "--> Point of Sale` and open your PoS. Then, enable the pricelist feature." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the pricelist feature" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:73 msgid "" "Once activated, you must choose the pricelists you want to make available in" " the PoS and define a default one." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:77 msgid "Create a pricelist" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:79 msgid "" "By default, Odoo has a *Public Pricelist* configured. To create more, go to " ":menuselection:`Point of Sale --> Products --> Pricelists`. Then click on " "create." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:83 msgid "" "When creating a pricelist, you can set several criteria to use a specific " "price: period, min. quantity, etc. You can also decide to apply that " "pricelist on specific products or on the whole range." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of a time-limited pricelist for two products" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:92 msgid "Using a pricelist with the PoS interface" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:94 msgid "" "On the PoS interface, a new button appears. Use it to select a pricelist." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "" "View of the button to use for time-limited discounts via the pos interface" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:101 msgid "" "Click on it to instantly update the prices with the selected pricelist. " "Then, you can finalize the order." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:3 msgid "Electronic shelf labels" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:5 msgid "" "Electronic shelf labels allow you to display product information like prices" " and barcodes on store shelves and to synchronize them remotely from the " "backend. This removes the need to print new labels when product information " "changes." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst-1 msgid "electronic label from Pricer" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:13 msgid "Odoo uses electronic labels from `Pricer `_." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:19 msgid "Pricer setup" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:21 msgid "" "`Get in touch with Pricer `_ to create and " "configure your Pricer account." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:23 msgid "Create your stores: one pricer store equates to one physical store." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:24 msgid "Link as many transceivers as needed to the Pricer store(s)." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:25 msgid "" "Create the following variables to share product information between your " "Odoo database system and Pricer. These variables act like placeholders on " "the label template." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:28 msgid "" "`itemId`: this holds the unique internal identifier assigned to each product" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:29 msgid "`itemName`: the actual name of the product" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:30 msgid "" "`price`: the selling price of the product, including any applicable taxes" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:31 msgid "" "`presentation`: the template name used in Pricer for displaying the product " "information on the label" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:33 msgid "`currency`: the currency of your company (e.g., USD, EUR)" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:34 msgid "`barcode`: the barcode number associated with each product" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:37 msgid "" "The names for these variables must be **identical** in your Pricer database." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:39 msgid "" "Create a template named `NORMAL`. This template is used to display " "information on your digital tags." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:42 msgid "" "Once your account, stores, variables, and template are configured on Pricer," " you can proceed with the setup of your Odoo database." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:46 msgid "" "The account associated with your Pricer store must have access to send API " "requests to Pricer." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:49 msgid "Odoo setup" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:51 msgid "" "As a pre-requisite, :ref:`activate ` the :guilabel:`POS " "Pricer` module *(technical name: pos_pricer)* to have all the required " "features to use Pricer electronic tags." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst-1 msgid "Installing POS Pricer module from Apps" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:57 msgid "" "Once the module is activated, configure your :ref:`pricer stores " "` and associate :ref:`Pricer tags ` " "with your products." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:63 msgid "Pricer stores" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:65 msgid "" "Similarly to the configuration in Pricer, you need to create one pricer " "store per physical location. To do so, go to :menuselection:`Point of Sale " "--> Configuration --> Pricer Stores`, click :guilabel:`New`, and fill in the" " line with the required information:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:69 msgid ":guilabel:`Store Name`: you can put any name of your liking." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:70 msgid "" ":guilabel:`Pricer Tenant Name`: the name of your company account in Pricer, " "usually followed by `-country_code`. This value is provided by Pricer." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:72 msgid ":guilabel:`Pricer Login`: the login of your Pricer account." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:73 msgid ":guilabel:`Pricer Password`: the password of your Pricer account." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:74 msgid "" ":guilabel:`Pricer Store ID`: the ID of the related Pricer store as defined " "on your Pricer database." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst-1 msgid "Configuring a Pricer Store" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:81 msgid "" "The :guilabel:`Pricer Tags` column is updated automatically when a label is " "linked to a product." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:83 msgid "" "The :guilabel:`Last Update` and :guilabel:`Last Update Status` columns are " "updated automatically when the tags are updated." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:89 msgid "Pricer tags" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:91 msgid "" "For a label to display specific product information, the label needs to be " "associated with the product. To do so:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:94 msgid "" "Open the product form by going to :menuselection:`Point of Sale --> Products" " --> Products` and clicking :guilabel:`New` or selecting an existing " "product." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:98 msgid "" "If you are creating a new product, configure and save it before associating " "any Pricer tags." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:100 msgid "" "Go to the :guilabel:`Sales` tab, scroll to the :guilabel:`Pricer` section, " "and select the corresponding :guilabel:`Pricer Store`." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:0 msgid "Linking Pricer tags to products" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:107 msgid "" "Fill in the :guilabel:`Pricer tags ids` field by copying the label's ID from" " the label itself or scanning its barcode." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:111 msgid "Pricer tag IDs are composed of a letter followed by 16 digits." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:114 msgid "" "We recommended using a barcode scanner to speed up the encoding process." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:115 msgid "" "When setting up Pricer with Odoo for the first time, it is recommended that " "you configure only one product first. Before configuring more products, " "ensure you can display their information on a Pricer tag." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:119 msgid "" "Now that you have a product associated with a Pricer tag, we can send its " "information to Pricer." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:124 msgid "" "Odoo automatically sends requests to Pricer to synchronize the tags every 12" " hours if you make any modifications to:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:127 #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:137 msgid "Product name, price, barcode, or customer taxes" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:128 #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:138 msgid "Currency" msgstr "Valuta" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:129 #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:139 msgid "Associated Pricer store or Pricer tags" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:131 msgid "" "To force the update, activate the :ref:`developer mode `. " "Then:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:133 msgid "" "Go to :menuselection:`Point of Sale --> Configuration --> Pricer Store`." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:134 msgid "Select the desired store(s)." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:135 msgid "" "Click :guilabel:`Update tags` to update all tags affected by changes to:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:141 msgid "" "Alternatively, click :guilabel:`Update all tags` to force the update of " "every tag, regardless of whether changes were made." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst-1 msgid "Update all Pricer tags" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:147 msgid "" "If Pricer has processed and accepted the request, the status field shows " ":guilabel:`Update successfully sent to Pricer`. If there is any issue, the " "system displays an error message." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:151 msgid "" "If a request sent to Pricer fails, Odoo still considers that the product has" " been updated. In that case, we recommend forcing the update of all tags." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:3 msgid "Flexible taxes (fiscal positions)" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:5 msgid "" "When running a business, you may need to apply different taxes and record " "transactions on various accounts based on the location and type of business " "of your customers and providers." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:8 msgid "" "The **fiscal positions** feature enables you to establish rules that " "automatically select the right taxes and accounts used for each transaction." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:12 #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:51 msgid ":doc:`../../../finance/accounting/taxes/fiscal_positions`" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:13 msgid ":doc:`../../../finance/accounting/taxes`" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:18 msgid "" "To enable the feature, go to :menuselection:`Point of Sale --> Configuration" " --> Settings`, scroll down to the :guilabel:`Accounting` section, and " "enable :guilabel:`Flexible Taxes`." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:21 msgid "" "Then, set a default fiscal position that should be applied to all sales in " "the selected POS in the :guilabel:`Default` field. You can also add more " "fiscal positions to choose from in the :guilabel:`Allowed` field." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:28 msgid "" "According to the :doc:`fiscal localization package " "<../../../finance/fiscal_localizations>` activated, several fiscal positions" " are preconfigured and can be set and used in POS. However, you can also " ":ref:`create new fiscal positions `." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:33 msgid "" "If you do not set a fiscal position, the tax remains as defined in the " "**customer taxes** field on the product form." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:37 msgid "Use fiscal positions" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:39 msgid "" "Open a :ref:`POS session ` to use one of the allowed " "fiscal positions. Then, click the :guilabel:`Tax` button next to the **book-" "shaped** icon and select a fiscal position from the list. Doing so applies " "the defined rules automatically to all the products subject to the chosen " "fiscal position's regulations." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:48 msgid "" "If a default fiscal position is set, the tax button displays the name of the" " fiscal position." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:3 msgid "Loyalty programs" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:5 msgid "" "Encourage your customers to continue to shop at your point of sale with a " "*Loyalty Program*." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:11 msgid "" "To activate the *Loyalty Program* feature, go to :menuselection:`Point of " "Sale --> Configuration --> Point of sale` and select your PoS interface. " "Under the Pricing features, select *Loyalty Program*" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:19 msgid "From there you can create and edit your loyalty programs." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:24 msgid "" "You can decide what type of program you wish to use, if the reward is a " "discount or a gift, make it specific to some products or cover your whole " "range. Apply rules so that it is only valid in specific situation and " "everything in between." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:30 msgid "Use the loyalty program in your PoS interface" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:32 msgid "" "When a customer is set, you will now see the points they will get for the " "transaction and they will accumulate until they are spent. They are spent " "using the button *Rewards* when they have enough points according to the " "rules defined in the loyalty program." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:40 msgid "" "You can see the price is instantly updated to reflect the pricelist. You can" " finalize the order in your usual way." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:44 msgid "" "If you select a customer with a default pricelist, it will be applied. You " "can of course change it." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 #: ../../content/applications/sales/subscriptions/products.rst:116 msgid "Pricelists" msgstr "Ceniki" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:5 msgid "" "Pricelists allow you to adjust product prices depending on various criteria " "automatically. For example, you can set POS-specific prices, create " "temporary discount periods, reward specific customers, or offer discounts " "when set quantities are ordered." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:14 msgid "" "Navigate to the :ref:`general POS app settings ` and" " ensure :guilabel:`Flexible Pricelists` are enabled under the " ":guilabel:`Pricing` section." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:17 msgid "" ":ref:`Multiple prices per product ` is the default " "pricelist option for setting simple fixed price rules per product. Select " ":ref:`Advanced price rules (discounts, formulas) ` to " "apply price rules to multiple products at once and to compute prices " "dynamically using percentage discounts or more complex formulas in addition " "to setting fixed prices." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 msgid "Enabling pricelists in the general P0S settings" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:26 msgid "" "The selected pricelist type applies to the entire database, including the " ":doc:`Sales <../../sales/products_prices/prices/pricing>` and " ":ref:`eCommerce ` apps." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:33 msgid "Create pricelists" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:35 msgid "" "Go to :menuselection:`Point of Sale --> Products --> Pricelists` and click " ":guilabel:`New` or select an existing pricelist. The pricelist setup differs" " depending on the :ref:`selected pricelist option " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:98 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:255 msgid "Multiple prices per product" msgstr "Več različnih cen na proizvodu" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:44 msgid "" "When pricelists are configured to use the :guilabel:`Multiple prices per " "product` option, it is possible to use multiple fixed prices for different " "products or their variants depending, if necessary, on one or several " "conditions. To add a new price rule to a pricelist:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:48 msgid "" "Click :guilabel:`Add a line`, and select a **product** and its **variant** " "if needed." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:49 msgid "Add the condition(s):" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:51 msgid "" "a product quantity to be reached by using the :guilabel:`Min. Quantity` " "column;" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:52 msgid "" "a determined period during which the pricelist is applied by using the " ":guilabel:`Start Date` and :guilabel:`End Date` columns." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:55 msgid "" "Add the :guilabel:`Price` to be applied when the conditions are met (if " "any)." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 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:126 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 msgid "Advanced price rules" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:65 msgid "" "When pricelists are configured to use the :guilabel:`Advanced price rules " "(discounts, formulas)` option, it is possible to use percentage " "discounts/mark-ups and formulas in addition to using fixed prices. To add a " "new price rule to a pricelist, click :guilabel:`Add a line`. In the pop-up " "windows:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:69 msgid "Select a :guilabel:`Computation` method:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:71 msgid "" ":guilabel:`Fixed Price` to set a new fixed price (similarly to the " ":guilabel:`Multiple prices per product` option)." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:73 msgid "" ":guilabel:`Discount` to compute a percentage discount (e.g., `10.00` %) or " "mark-up (e.g., `-10.00` %)." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:75 msgid "" ":guilabel:`Formula` to compute the price according to a formula. It is " "required to define what the calculation is **based on** (:guilabel:`Sales " "Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`). You can then:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:79 msgid "Apply a percentage :guilabel:`Discount` or mark-up." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:80 msgid "" "Add an :guilabel:`Extra Fee` (e.g., $ `5.00`) or subtract a fixed amount " "(e.g., $ `-5.00`)." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:81 msgid "" "Define a :doc:`Rounding Method ` by forcing the price after " ":guilabel:`Discount` to be a multiple of the value set. The :guilabel:`Extra" " Fee` is applied afterward." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:86 msgid "" "To have the final price end with `.99`, set the :guilabel:`Rounding Method` " "to `1.00` and the :guilabel:`Extra Fee` to `-0.01`." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:89 msgid "" "Specify the minimum (e.g., $ `20.00` ) and maximum (e.g., $ `50.00` ) profit" " :guilabel:`Margins` for computations based on :guilabel:`Cost`." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:92 msgid "Select on which product(s) the price rule should be **applied**:" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:94 msgid ":guilabel:`All Products`" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:95 msgid "a :guilabel:`Product Category`" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:96 msgid "a :guilabel:`Product`" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:97 msgid "a :guilabel:`Product Variant`" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:99 msgid "" "Add conditions, such as a specific quantity to reach for the price to change" " by using the :guilabel:`Min. Quantity` field or a specific period during " "which the pricelist should be applied by using the :guilabel:`Validity` " "fields." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 msgid "Setup form to configure an advanced pricelist" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:107 msgid "Select pricelists" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:109 msgid "" "Go to the :ref:`specific POS settings ` and add all " "the available pricelists in the :guilabel:`Available` field. Then, set its " "**default pricelist** in the :guilabel:`Default` field." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:113 msgid "" "When you :ref:`open a POS session `, click the " "**pricelists** button, and select the desired pricelist from the list." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 msgid "Button to select a pricelist on the POS frontend" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:120 msgid "" "Multiple pricelists must be selected for the **pricelist button** to be " "displayed." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:121 msgid "" "If a pricelist is selected on a POS order while its conditions are **not** " "met, the price will **not** be adjusted." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:125 msgid "" "You can also set a pricelist to be selected automatically once a specific " ":ref:`customer is set `. To do so, go to the customer form " "and switch to the preferred pricelist in the :guilabel:`Pricelist` field of " "the :guilabel:`Sales & Purchase` tab." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:130 msgid ":doc:`../../sales/products_prices/prices/pricing`" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:131 msgid "" ":ref:`How to use pricelists in an ecommerce environment " "`" msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:3 msgid "Receipts and invoices" msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:6 msgid "Receipts" msgstr "Dokazila" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:8 msgid "" "Set up receipts by going to :menuselection:`Point of Sale --> Configuration " "--> Point of Sale`, selecting a POS, and scrolling down to the " ":guilabel:`Bills & Receipts` section." msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:11 msgid "" "To **customize** the **header** and **footer**, activate :guilabel:`Header &" " Footer` and fill in both fields with the information to be printed on the " "receipts." msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:14 msgid "" "To **print receipts** automatically once the payment is registered, enable " "the :guilabel:`Automatic Receipt Printing` setting." msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "POS receipt" msgstr "" #: ../../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:23 msgid ":doc:`configuration/epos_printers`" msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26 msgid "Reprint a receipt" msgstr "" #: ../../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 "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "Print receipt button from the backend" msgstr "" #: ../../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:42 msgid "Invoices" msgstr "Računi" #: ../../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: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: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 "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "accounting section in the POS settings" msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 msgid "Invoice a customer" msgstr "" #: ../../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: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: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:77 msgid "Retrieve invoices" msgstr "" #: ../../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: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:83 msgid "" "to access an order's invoice, open the **order form** by selecting the " "order, then click :guilabel:`Invoice`." msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "invoice smart button from an order form" msgstr "" #: ../../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: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:96 msgid "QR codes to generate invoices" msgstr "" #: ../../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 "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "order status change" msgstr "" #: ../../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 "" #: ../../content/applications/sales/point_of_sale/reporting.rst:3 msgid "Reporting" msgstr "Poročanje" #: ../../content/applications/sales/point_of_sale/reporting.rst:6 msgid "View statistics" msgstr "" #: ../../content/applications/sales/point_of_sale/reporting.rst:8 msgid "" "To access your statistics, go to :menuselection:`Point of Sale --> Reporting" " --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis " "(:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`." msgstr "" #: ../../content/applications/sales/point_of_sale/reporting.rst:12 msgid "" "These statistics are available in a graph or pivot view that you can filter " "or group depending on your needs." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:5 msgid "Restaurant features" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:7 msgid "" "Managing a restaurant or a bar comes with specific needs. The Point of Sale " "application provides various features that allow performing all the required" " tasks in such businesses." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:10 msgid "Once the POS is set to be used in a restaurant or a bar, you can:" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:12 msgid "" ":doc:`organize your floors and tables to reflect your interior " "`;" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:13 msgid ":ref:`take orders `;" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:14 msgid "" ":doc:`communicate with the kitchen or the bar through the POS " "`;" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:15 msgid "" ":doc:`print bills in advance and split them `;" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:16 msgid ":doc:`collect tips `; and" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:17 msgid "" ":doc:`set different taxes for takeaway food `." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:24 msgid "" "To enable the restaurant and bar-specific features, go to " ":menuselection:`Point of Sale --> Configuration --> Settings`, select the " "POS, and activate :guilabel:`Is a Bar/Restaurant`." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:27 msgid "" "These features are displayed in the :guilabel:`Restaurant & Bar` section." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst-1 msgid "restaurant and bar-specific features" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:36 msgid "Take orders" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:38 msgid "" "Click a table to access the POS interface and start taking your customer's " "order. The system automatically associates the orders and the table, " "allowing you to add more items later and generate a bill specifically for " "that table's orders." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:42 msgid "" "Once you have taken an order, click :guilabel:`Change table` to return to " "the floor plan view." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant.rst:45 msgid "" "As soon as you click a table, the number of guests is automatically set to " "one. If you mistakenly select a table, click :guilabel:`Release table` to " "free it or :ref:`transfer the customer ` to another " "table." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 msgid "Bills" msgstr "Računi" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5 msgid "" "Typical practices in restaurants or bars are to request the bill before " "proceeding to payment or splitting it based on the items ordered. Odoo POS " "provides two features to perform these tasks seamlessly: **Bill Printing** " "and **Bill Splitting**." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 msgid "" "To activate the features, go to :menuselection:`Point of Sale --> " "Configuration --> Settings`, select the POS, and activate :guilabel:`Early " "Receipt Printing` and :guilabel:`Allow Bill Splitting` in the " ":guilabel:`Restaurant & Bar` section." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst-1 msgid "" "activate the bill printing and bill splitting features in the POS settings" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:21 msgid "Bill printing" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:23 msgid "" "From an open session, click :menuselection:`Bill --> Print` at any moment to" " generate and print a bill." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:27 msgid "" "The printed bill is **not** final and will be updated to reflect any changes" " to the order." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:30 msgid "Bill splitting" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:32 msgid "" "From an open session, click :guilabel:`Split` to select the items to " "regroup. Once everything is selected, click :guilabel:`Payment` and proceed " "to checkout for these items. Repeat for each guest." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:36 msgid "" "Once you return to the table, the selected items are no longer on order, as " "they have been paid for." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:38 msgid "The feature is available as soon as at least two items are ordered." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:41 msgid ":doc:`floors_tables`" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:3 msgid "Floors and tables" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:5 msgid "" "The **Floor plan view** enables you to manage restaurant floors and table " "arrangements and monitor table status in real time, including occupancy, " "reservations, and kitchen orders." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:0 msgid "example of a floor plan view with visual keys to understand it." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:13 msgid "Table 1: An order has been placed and sent to the kitchen." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:14 msgid "" "Table 3: An order of four items has been placed and needs to be sent to the " "kitchen." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:15 msgid "Tables 2, 4, and 5: These tables are available." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:16 msgid "" "Tables 2, 4, and 5: These tables' total capacity is, respectively, 2, 4, and" " 8 people." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:17 msgid "Table 1: The table of two is full." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:18 msgid "Table 3: The table of four is taken by one person." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:19 msgid "Table 5: \"Famous Joe\" has a reservation for 8 people at 12:00." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:25 msgid "From the POS backend" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:27 msgid "" "To create floors and tables from the backend, go to :menuselection:`Point of" " Sale --> Configuration --> Floor Plans`, and click :guilabel:`New` to " "create a floor. Name it, select the related point(s) of sales, and click " ":guilabel:`Add a line` to create a table. Name the table and assign a number" " of seats. You can also link it to an appointment resource to make the table" " bookable. Once done, click :guilabel:`Save & Close` or :guilabel:`Save & " "New` to confirm." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "window to create a table in the POS backend" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:38 msgid "" "The POS must be opened and :ref:`edited from the frontend " "` to create a map of your restaurant or bar " "reflecting your actual floor plan." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:42 msgid "" "Create floors on the spot: :ref:`access your POS settings " "`, type your floor name in the :guilabel:`Floor` " "field of the :guilabel:`Floors & Tables Map` category, and press *enter*." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:0 msgid "setting to create floors from the POS settings" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:53 msgid "From the POS frontend" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:55 msgid "" "To create floors and tables from the frontend, :ref:`open a POS session " "`, click the hamburger menu icon :guilabel:`≡` in the " "upper right corner, then :guilabel:`Edit Plan` to enter the **edit mode**." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:59 msgid "" "Click :guilabel:`+ Add Floor` to add a floor, then enter a name in the pop-" "up window." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:61 msgid "" "Once a floor is created, add a table by clicking :guilabel:`+ TABLE`. To " "move it, select it and drag and drop it as desired. You can also modify the " "attributes of the selected table, such as the number of seats by clicking " ":guilabel:`SEATS`, the table shape using :guilabel:`SHAPE`, the table color " "using :guilabel:`FILL`, or the table name by clicking :guilabel:`RENAME`. To" " duplicate an existing table, select it and click :guilabel:`COPY`. You can " "also remove the table by clicking :guilabel:`DELETE`." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:68 msgid "" "After making all the necessary modifications, click :guilabel:`CLOSE` to " "save." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "the floor plan view in edit mode." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:74 msgid "If no table is selected, the modifications are applied to the floor." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:77 msgid "Removing a table or a floor cannot be undone." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:82 msgid "Table transfer" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84 msgid "" "To move customers from one table to another, select a table and click " ":guilabel:`→ Transfer` on the POS interface. This redirects you to the floor" " plan view, where you can choose the new table to which you want to transfer" " the customers." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:88 msgid "" "When you transfer customers, all of the orders they have placed and that are" " linked to the original table are also transferred." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:3 msgid "Orders printing" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:5 msgid "" "Integrating printers in a restaurant or bar's workflow can enhance " "communication and collaboration between the front-of-house and back-of-house" " teams, leading to a more streamlined and efficient service." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:15 msgid "Enable and create printers" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:17 msgid "" "To enable sending orders to a kitchen or bar printer, go to " ":menuselection:`Point of Sale --> Configuration --> Settings`, scroll down " "to the :guilabel:`Restaurant & Bar` section, and enable :guilabel:`Kitchen " "Printers`. Type in a name for the printer in the :guilabel:`Printers` field " "and click :guilabel:`Create and edit...` to open a setup form." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:22 msgid "" "To get a list of all the printers already created or to modify an already " "created printer, click :guilabel:`--> Printers` and select the desired " "printer to open the setup form." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 msgid "settings to enable the kitchen printers" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:32 msgid "Setup form" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:34 msgid "" "From the :ref:`setup form `, select the " ":guilabel:`Printer Type` according to your installation:" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:37 msgid "" "If your printer is connected to an IoT box, select :guilabel:`Use a printer " "connected to the IoT Box` and select the device in the :guilabel:`IoT " "Device` field." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:39 msgid "" "If you use an Epson printer that does not need an IoT box, select " ":guilabel:`Use an Epson printer` and enter the printer's IP address in the " ":guilabel:`Epson Printer IP Address` field." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:43 msgid ":doc:`/applications/general/iot/config/connect`" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44 msgid ":doc:`/applications/general/iot/devices/printer`" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:45 msgid ":doc:`../configuration/epos_ssc`" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:47 msgid "" "Set your printer to print specific products based on their POS category. To " "do so, click :guilabel:`Add a line` in the :guilabel:`Printed Product " "Categories` field. If you leave this field empty, all products are sent to " "the printer regardless of their POS category." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 msgid "setup form to configure a kitchen printer" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:56 msgid "Print orders" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:58 msgid "" "From an open session, start taking an order and click :guilabel:`Order` to " "send it to the bar or the kitchen." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 msgid "order button from the POS UI to send orders to a kitchen or a bar" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:66 msgid "" "When products can be printed, they appear in green in the cart, and the " "order button turns green." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3 msgid "Tips" msgstr "Napitnina" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:5 msgid "" "Tipping is customary in multiple countries. Point of Sale allows tipping in " ":ref:`shops `, :doc:`bars <../restaurant>`, or :doc:`restaurants " "<../restaurant>`." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:13 msgid "" "To allow tipping in your POS, activate the :guilabel:`Tips` feature in " ":menuselection:`Point of Sale --> Configuration --> Settings`. At the top of" " the page, select the POS in which you wish to allow **tipping**, scroll " "down to the :guilabel:`Payment` section and check :guilabel:`Tips`. Once " "enabled, add a :guilabel:`Tip Product` in the corresponding field, and save." " The designated product will be used as a reference on customers' receipts." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "enable tips in a POS" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:25 msgid "Tip products" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:27 msgid "" "**Tip products** can be created on the spot. To do so, enter a product's " "name in the :ref:`Tip Product ` field and click " ":guilabel:`Create` or press **enter**. The product is automatically " "configured to be used as a tip at the payment screen." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:31 msgid "" "However, if you wish to be able to select the tip product in a POS session, " "you must activate the **Available in POS** setting. To do so, click " ":guilabel:`Create and edit...` to open the product configuration form. Then," " go to the :guilabel:`Sales` tab, tick the :guilabel:`Available in POS` " "checkbox, and click :guilabel:`Save & Close`." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:37 msgid "" "When you create a product to use as a tip, leave the **product type** as " ":guilabel:`Consumable` to avoid unnecessary inventory movements." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:39 msgid "" "You can only select one tip product per POS, but you can choose a different " "one for each." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:42 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:72 msgid "Tip using an Adyen terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:44 msgid "" "If you use an :doc:`Adyen <../payment_methods/terminals/adyen>` payment " "terminal and wish to enable **tips** using the terminal, check " ":guilabel:`Add tip through payment terminal (Adyen)` below the :ref:`tip " "settings `." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:49 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:79 msgid "Tip after payment" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:51 msgid "" "If you use a POS system in a bar or a restaurant, you can enable " ":guilabel:`Add tip after payment (North America specific)`. Doing so " "generates a bill to print and complete manually by the customer and the " "waiter. That bill indicates the tip value the customer chooses to give after" " the payment." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:56 msgid "" "To use this feature, the selected payment method must have a bank journal " "attributed." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:59 msgid "Add tips" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:61 msgid "" "To add tips to an order, :ref:`access the payment screen ` and " "click :guilabel:`♥ Tip`. Then, enter the tipping amount, click " ":guilabel:`Confirm` to validate, and process the payment." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "tip popup window" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:67 msgid "" "Alternatively, you can select the :ref:`tip product ` on the " "POS interface to add it to the cart. When selected, the product is " "automatically set as a tip, and its default value equals its **Sales " "Price**." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:74 msgid "" "During checkout, select **Adyen** as the payment terminal, and send the " "payment request to the device by clicking :guilabel:`Send`. The customers " "are asked to enter the desired tipping amount on the terminal's screen " "before proceeding to the payment." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:81 msgid "" "At checkout, select a card payment method and click :guilabel:`Close Tab`. " "Doing so generates a bill to complete by the customer." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "tipping bill after payment to complete by customers" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:87 msgid "" "On the following screen, click the percentage (:guilabel:`15%`, " ":guilabel:`20%`, :guilabel:`25%`), :guilabel:`No Tip`, or enter the tipping " "amount the customer chose to give. Then, click :guilabel:`Settle` to move to" " the following order." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "screen to select a tip amount to collect after payment" msgstr "" #: ../../content/applications/sales/point_of_sale/shop.rst:5 msgid "Shop features" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:3 msgid "Barcodes" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:5 msgid "" "Using a barcode scanner to process point-of-sale orders improves your " "efficiency in providing quicker customer service. Barcode scanners can be " "used both to scan products or to log employees into a POS session." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:12 msgid "" "To use a barcode scanner, you must enable the feature in the Inventory app. " "Go to :menuselection:`Inventory --> Configuration --> Settings`, in the " ":guilabel:`Barcode` section, tick :guilabel:`Barcode Scanner` and save." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst-1 msgid "barcode setting in the Inventory application" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:21 msgid "" ":doc:`Set up a barcode scanner " "`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22 msgid "" ":doc:`Activate barcode scanners " "`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:24 msgid "" "Once enabled in **Inventory**, you can use the barcode feature in **Point of" " Sale** with products that have a barcode number assigned." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:28 msgid "Assign barcodes" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:31 msgid "To your products" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:33 msgid "" "To use this feature in POS, your products must have barcodes assigned. To do" " so, go to :menuselection:`Point of Sale --> Products --> Products` and open" " a **product form**. Add a barcode number in the :guilabel:`Barcode` field " "in the :guilabel:`General Information` tab." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:38 msgid "To your employees" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:40 msgid "" "To add an identification number to an employee, go to the **Employees** app " "and open an **employee form**. Choose an identification number for your " "employee and fill in the :guilabel:`PIN Code` field in the :guilabel:`HR " "Settings` tab." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:45 msgid "Use barcodes" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:48 msgid "Scan products" msgstr "Skeniraj izdelke" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:50 msgid "" "Scan a product's barcode using a barcode scanner. Doing so adds it directly " "to the cart. To change the quantity, scan a product as many times as needed," " or click :guilabel:`Qty` and enter the number of products using the keypad." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:54 msgid "" "You can also enter the barcode number manually in the search bar to look for" " the product. Then, click it to add it to the cart." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:58 msgid "Log employees" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:60 msgid "" "You can also use a barcode scanner to log your employees. To do so, " ":ref:`restrict access ` to the POS and " ":ref:`use barcodes to log your employees in ` your " "POS." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:3 msgid "Customer display" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:5 msgid "" "The **customer display** feature provides customers with real-time checkout " "updates on a secondary display." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst-1 msgid "customer screen" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:14 msgid "" "Depending on your POS setup, the feature can be displayed :ref:`locally on a" " secondary screen ` or on :ref:`another monitor " "connected to an IoT Box `." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:18 msgid "" "To activate the feature, go to the POS settings, scroll down to the " ":guilabel:`Connected Devices` section, and tick the :guilabel:`Customer " "Display` checkbox." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst-1 msgid "customer display setting checkbox" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:27 msgid "Local" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:29 msgid "" "Connect a second screen to your POS and :ref:`open a POS session " "`. Then, click :guilabel:`Customer Screen` to open a new " "window to drag and drop onto the second screen." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:35 msgid "IoT box" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:37 msgid "" "Connect an IoT box to your database and the second screen to the IoT box. " "Then, go to :menuselection:`Point of Sale --> Configuration --> Settings`, " "scroll down to the :guilabel:`Connected Devices` section, tick the " ":guilabel:`IoT Box` checkbox, and select the second monitor in the " ":guilabel:`Customer Display` field." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst-1 msgid "iot setting to connect a customer display" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:46 msgid "Both devices need to be connected to the same local network." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:49 msgid ":doc:`../../../general/iot/config/pos`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3 msgid "Sales orders" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:5 msgid "" "When working in retail, you might need to order products directly from your " "Point of sale. Fortunately, Odoo Point of Sale is fully integrated with Odoo" " Sales, meaning that you can create a sales order and pay for it directly " "from your point of sale." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:10 msgid "Select a sales order" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:12 msgid "" "From the **Point of Sale** application, open a new session. Then, click on " ":guilabel:`Quotations/Orders` to get the complete list of quotations and " "sales orders created on the sales application." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 msgid "Quotations and sales order button on the Point of Sale interface" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:21 msgid "" "To ease finding the right sales order, you can filter that list on the " "**customer** or on the **order reference**. You can also set the customer " "before clicking on :guilabel:`Quotations/Orders` to reduce the list to one " "particular customer." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:26 msgid "Apply a down payment or settle the order" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:28 msgid "From the list of sales order, select one to make a payment." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 msgid "list view of sales orders and quotations" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:34 msgid "You can either:" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:36 msgid "" "Settle the order **partially**: after clicking on :guilabel:`Apply a down " "payment`, enter the percentage of down payment you want the customer to pay." " Then, click on :guilabel:`ok` and proceed with the order." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:39 msgid "" "Settle the order **completely**: click on :guilabel:`Settle the order` to " "pay for the total of the sales order." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:43 msgid "" "Once you settle a sales order, the applied down payment is automatically " "deducted from the total amount." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:47 msgid ":doc:`/applications/sales/sales/invoicing/down_payment`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:3 msgid "Serial numbers and lots" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:5 msgid "" "Working with **serial numbers** and **lots** allows tracking your products' " "movements. When products are tracked, the system identifies their location " "based on their last movement." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:8 msgid "" "To enable traceability, go to :menuselection:`Point of Sale --> Products -->" " Products`. Then, select a product and check the :guilabel:`Tracking By " "Unique Serial Number` or the :guilabel:`Tracking By Lots` box in the " ":guilabel:`Inventory` tab." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 msgid "Enable traceability settings" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:17 msgid "Serial numbers and lots importation" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:19 msgid "" "You can import serial numbers in Point of Sale. To do so, select a **sales " "order** or a **quotation** containing tracked products. Then, agree to load " "the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 msgid "Pop-up window for serial number import" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:28 msgid "" "The imported tracking numbers appear below the tracked products. You can " "modify them by clicking on the list-view button next to the products." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:37 msgid ":doc:`../shop/sales_order`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:40 msgid "Serial numbers and lots creation" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:42 msgid "" "If a tracked product is available in your POS, adding the product to the " "cart opens a pop-up window where you can type or scan the product's serial " "or lot numbers. To add more than one of the same tracked products, click on " "**enter** to validate and start a new line." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 msgid "adding new serial and lots numbers" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:52 msgid "" "Changing a tracked product's quantity using the numpad turns the list-view " "button red. Click on it to add the missing lot and serial numbers." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:54 msgid "" ":guilabel:`Lot & Serial Number(s)` are :guilabel:`required` on tracked " "products but not mandatory. Meaning that not attributing some or any does " "**not** prevent from completing the sale." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:59 msgid "" ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:60 msgid "" ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:3 msgid "Ship later" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:5 msgid "" "The **Ship Later** feature allows you to sell products and schedule delivery" " at a later date. It is useful, for example, when a product is out of stock " "or so voluminous that it requires to be shipped, or if, for any reason, the " "customer needs their order to be shipped later, etc." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:12 msgid "" ":ref:`Go to the POS settings `, scroll down to the " ":guilabel:`Inventory` section, and enable :guilabel:`Allow Ship Later`." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst-1 msgid "settings to enable and configure the ship later feature" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:19 msgid "Once activated, you can:" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:21 msgid "" "Choose the location from where the products are shipped by selecting a " ":guilabel:`Warehouse`." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:22 msgid "" "Define a :guilabel:`Specific route`, or leave this field empty to use the " "default route." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:23 msgid "" "Define the :guilabel:`Shipping Policy`; select :guilabel:`As soon as " "possible` if the products can be delivered separately or :guilabel:`When all" " products are ready` to ship all the products at once." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:28 msgid "" ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:29 msgid "" ":doc:`../../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:34 msgid ":ref:`Open a session ` and make a sale." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:35 msgid "" "On the payment screen, set a customer and select :guilabel:`Ship Later`." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:36 msgid "" "On the popup window, set a shipping date and click :guilabel:`Confirm` to " "proceed to payment." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst-1 msgid "selecting ship later at checkout." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:42 msgid "" "The system instantly creates a delivery order from the warehouse to the " "shipping address." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:45 msgid "" "The selected customer must have referenced an address in the system for " "products to be shipped." msgstr "" #: ../../content/applications/sales/rental.rst:3 msgid "Rental" msgstr "" #: ../../content/applications/sales/rental.rst:5 msgid "" "The Odoo *Rental* application provides comprehensive solutions to configure " "and manage rentals." msgstr "" #: ../../content/applications/sales/rental.rst:7 msgid "" "Send quotations, confirm orders, schedule rentals, register products when " "they are picked up and returned, and invoice customers from this single " "platform." msgstr "" #: ../../content/applications/sales/rental.rst:11 msgid "`Odoo Rental: product page `_" msgstr "" #: ../../content/applications/sales/rental.rst:12 msgid "`Odoo Tutorials: Rental `_" msgstr "" #: ../../content/applications/sales/rental.rst:17 msgid "Dashboard" msgstr "Nadzorna plošča" #: ../../content/applications/sales/rental.rst:19 msgid "" "Upon opening the *Rental* application, the :guilabel:`Rental Orders` " "dashboard is revealed." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "Example of the Rental Orders dashboard available in the Odoo Rental " "application." msgstr "" #: ../../content/applications/sales/rental.rst:25 msgid "" "In the default kanban view, all rentals are visible. Each rental card " "displays the customer name, the price of the rental, the related sales order" " number, along with the status of the rental." msgstr "" #: ../../content/applications/sales/rental.rst:29 msgid "" "Rental kanban cards that do **not** display a rental status means those " "rentals have confirmed quotations, but have not been picked up yet." msgstr "" #: ../../content/applications/sales/rental.rst:32 msgid "" "On the left sidebar, the :guilabel:`Rental Status` for each rental can be " "found. Beneath that, the :guilabel:`Invoice Status` of the rentals is " "accessible. Clicking any option in the left sidebar filters the displayed " "rentals on the dashboard." msgstr "" #: ../../content/applications/sales/rental.rst:37 #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:17 msgid "Settings" msgstr "Nastavitve" #: ../../content/applications/sales/rental.rst:39 msgid "" "To configure additional rental delay costs, availability of rental items, or" " minimum time of rental, navigate to :menuselection:`Rental app --> " "Configuration --> Settings`." msgstr "" #: ../../content/applications/sales/rental.rst-1 #: ../../content/applications/sales/rental.rst-1 msgid "How the Settings page appears in the Odoo Rental application." msgstr "" #: ../../content/applications/sales/rental.rst:46 msgid "" "In the :guilabel:`Rental` section, there are options to configure " ":guilabel:`Default Delay Costs` and :guilabel:`Default Padding Time`. There " "is also the option to activate :guilabel:`Rental Transfers` and " ":guilabel:`Digital Documents`." msgstr "" #: ../../content/applications/sales/rental.rst:50 msgid ":guilabel:`Default Delay Costs` are additional costs for late returns." msgstr "" #: ../../content/applications/sales/rental.rst:51 msgid "" ":guilabel:`Default Padding Time` represents the minimum amount of time " "between two rentals." msgstr "" #: ../../content/applications/sales/rental.rst:52 msgid "" ":guilabel:`Rental Transfers` means stock deliveries and receipts can be used" " for rental orders." msgstr "" #: ../../content/applications/sales/rental.rst:54 msgid "" ":guilabel:`Digital Documents` allows users to upload documents for customers" " to sign prior to" msgstr "" #: ../../content/applications/sales/rental.rst:54 msgid "confirming their rental." msgstr "" #: ../../content/applications/sales/rental.rst:56 msgid "" "In the :guilabel:`Rent Online` section, there are options to configure a " ":guilabel:`Minimal Rental Duration` and designate :guilabel:`Unavailability " "days`, or days during which pickup and return are not possible." msgstr "" #: ../../content/applications/sales/rental.rst:61 msgid "Rental products" msgstr "" #: ../../content/applications/sales/rental.rst:63 msgid "" "To view all products that can rented in the database, navigate to " ":menuselection:`Rentals app --> Products`. By default, the :guilabel:`Can be" " Rented` search filter appears in the search bar." msgstr "" #: ../../content/applications/sales/rental.rst:66 msgid "" "Each product kanban card displays that product's name, rental price, and " "product image (if applicable)." msgstr "" #: ../../content/applications/sales/rental.rst:70 msgid "Rental pricing" msgstr "" #: ../../content/applications/sales/rental.rst:72 msgid "" "To adjust the rental pricing on a product, go to the :guilabel:`Products` " "page in the *Rental* app, then select the desired product or click " ":guilabel:`New` to create a new product from scratch." msgstr "" #: ../../content/applications/sales/rental.rst:75 msgid "" "On the product form, ensure the :guilabel:`Can be Rented` checkbox is " "ticked. Then, open the :guilabel:`Rental prices` tab." msgstr "" #: ../../content/applications/sales/rental.rst:83 msgid "" "If creating a rental product outside of the *Rental* app, just ensure the " ":guilabel:`Can be Rented` checkbox is ticked on the product form. By " "default, this checkbox is ticked whenever a product is created directly in " "the *Rental* application." msgstr "" #: ../../content/applications/sales/rental.rst:90 msgid "" "Under the :guilabel:`Pricing` section of the :guilabel:`Rental prices` tab, " "designate custom rental prices and rental periods for the product." msgstr "" #: ../../content/applications/sales/rental.rst:93 msgid "" "To add pricing for a rental, click :guilabel:`Add a price`. Then, choose a " "*pricing period* (:dfn:`the unit of duration of the rental`) in the " ":guilabel:`Period` column, or create a new pricing period by typing in the " "name and clicking :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/rental.rst:97 msgid "" "Next, decide whether or not to apply this custom rental price to a specific " ":guilabel:`Pricelist`." msgstr "" #: ../../content/applications/sales/rental.rst:99 msgid "" "Lastly, enter the desired :guilabel:`Price` for that specific " ":guilabel:`Period`." msgstr "" #: ../../content/applications/sales/rental.rst:102 msgid "" "There is no limit to how many pricing lines can be added. Multiple pricing " "options for rental products are typically used to give discounts for " "customers who agree to longer rental durations." msgstr "" #: ../../content/applications/sales/rental.rst:105 msgid "" "To delete any rental pricing option, click the :guilabel:`🗑️ (trash)` icon, " "and that row is deleted." msgstr "" #: ../../content/applications/sales/rental.rst:109 msgid "Reservations" msgstr "Rezervacije" #: ../../content/applications/sales/rental.rst:111 msgid "" "Under the :guilabel:`Reservations` section of the :guilabel:`Rental prices` " "tab, there is the option to configure additional fines for any " ":guilabel:`Extra Hour` or :guilabel:`Extra Day` that the customer takes to " "return a rental." msgstr "" #: ../../content/applications/sales/rental.rst:115 msgid "" "There is also the option to set a :guilabel:`Security Time`, expressed in " "hours, to make the rental product temporarily unavailable between two rental" " orders. Such a feature may prove useful if maintenance or cleaning is " "required between rentals." msgstr "" #: ../../content/applications/sales/rental.rst:120 msgid "Price computing" msgstr "" #: ../../content/applications/sales/rental.rst:122 msgid "" "Odoo always uses two rules to compute the price of a product when a rental " "order is created:" msgstr "" #: ../../content/applications/sales/rental.rst:124 msgid "Only one price line is used." msgstr "" #: ../../content/applications/sales/rental.rst:125 msgid "The cheapest line is selected." msgstr "" #: ../../content/applications/sales/rental.rst:128 msgid "Consider the following rental pricing configuration for a product:" msgstr "" #: ../../content/applications/sales/rental.rst:130 msgid "1 day: $100" msgstr "" #: ../../content/applications/sales/rental.rst:131 msgid "3 days: $250" msgstr "" #: ../../content/applications/sales/rental.rst:132 msgid "1 week: $500" msgstr "" #: ../../content/applications/sales/rental.rst:134 msgid "" "A customer wants to rent this product for eight days. What price will they " "pay?" msgstr "" #: ../../content/applications/sales/rental.rst:136 msgid "" "After an order is created, Odoo selects the second line as this is the " "cheapest option. The customer has to pay three times '3 days' to cover the " "rental's eight days, for a total of $750." msgstr "" #: ../../content/applications/sales/rental.rst:142 msgid "Rental orders" msgstr "" #: ../../content/applications/sales/rental.rst:144 msgid "" "To create a rental order in the *Rental* app, navigate to " ":menuselection:`Rental app --> Orders --> Orders`, and click " ":guilabel:`New`. Doing so reveals a blank rental order form to be filled in " "accordingly." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "Sample of a filled out rental order available in the Odoo Rental " "application." msgstr "" #: ../../content/applications/sales/rental.rst:152 msgid "" "Start by adding a :guilabel:`Customer`, then configure the desired duration " "of the rental in the :guilabel:`Rental period` field." msgstr "" #: ../../content/applications/sales/rental.rst:155 msgid "" "To adjust the rental duration, click the first date in the :guilabel:`Rental" " period` field, and select the range of dates to represent the rental " "duration from the pop-up calendar form that appears." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "Sample of a rental period calendar pop-up window in the Odoo Rental " "application." msgstr "" #: ../../content/applications/sales/rental.rst:163 msgid "" "Once complete, click :guilabel:`Apply` in the calendar pop-up form. " "Following that, the pop-up form disappears, and the designated time period " "of the rental is represented in the :guilabel:`Duration` field." msgstr "" #: ../../content/applications/sales/rental.rst:167 msgid "" "Next, add a rental product in the :guilabel:`Order Lines` tab, by clicking " ":guilabel:`Add a product`, and selecting the desired rental product to add " "to the form." msgstr "" #: ../../content/applications/sales/rental.rst:171 msgid "" "If a rental product is added *before* the :guilabel:`Rental period` field " "has been properly configured, the user can *still* adjust the " ":guilabel:`Rental period` field accordingly." msgstr "" #: ../../content/applications/sales/rental.rst:174 msgid "" "Simply select the desired range of dates to represent the duration of the " "rental, then click :guilabel:`Update Rental Prices` in the " ":guilabel:`Duration` field." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "The update rental prices option that appears in the Odoo Rental application." msgstr "" #: ../../content/applications/sales/rental.rst:181 msgid "" "Doing so reveals a :guilabel:`Confirmation` pop-up window. If everything is " "correct, click :guilabel:`Ok`, and Odoo recalculates the rental price " "accordingly." msgstr "" #: ../../content/applications/sales/rental.rst:184 msgid "" "Once all the information has been entered correctly on the rental order " "form, click the :guilabel:`Send by Email` button to send the quotation to " "the customer, or click the :guilabel:`Confirm` button to confirm the order." msgstr "" #: ../../content/applications/sales/rental.rst:189 msgid "Customer signature" msgstr "" #: ../../content/applications/sales/rental.rst:191 msgid "" "Upon confirming a rental order, the :guilabel:`Sign Documents` button " "appears. This gives the ability to request the customer sign a rental " "agreement, outlining the arrangement between the company and customer, " "*before* they pick up the rental product(s)." msgstr "" #: ../../content/applications/sales/rental.rst:195 msgid "" "Such documents can ensure everything is returned on-time and in its original" " condition." msgstr "" #: ../../content/applications/sales/rental.rst:198 msgid "" "The :guilabel:`Sign Documents` button/option **only** appears if the " ":guilabel:`Digital Documents` feature has been activated in the *Rental* " "application settings. To do so, navigate to :menuselection:`Rental app --> " "Configuration --> Settings`, activate :guilabel:`Digital Documents`, and " "click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/rental.rst:204 msgid "" "This feature also requires the :doc:`Sign <../productivity/sign>` app. If " "necessary, Odoo automatically installs it after activating the " ":guilabel:`Digital Documents` setting." msgstr "" #: ../../content/applications/sales/rental.rst:207 msgid "" "To request a customer signature on a rental agreement, select a confirmed " "rental order, and click the :guilabel:`Sign Documents` button to reveal a " ":guilabel:`Sign Documents` pop-up window." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "The Sign Documents pop-up window that appears in the Odoo Rental " "application." msgstr "" #: ../../content/applications/sales/rental.rst:214 msgid "" "From here, select the desired document from the :guilabel:`Document " "Template` field. Then, click :guilabel:`Sign Document`. Doing so reveals a " ":guilabel:`New Signature Request` pop-up window." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "The New Signature Request pop-up window that appears in the Odoo Rental " "application." msgstr "" #: ../../content/applications/sales/rental.rst:221 msgid "" "Upon confirming the information in the :guilabel:`New Signature Request` " "pop-up form, click :guilabel:`Sign Now` to initiate the signing process." msgstr "" #: ../../content/applications/sales/rental.rst:224 msgid "" "A separate page is then revealed, showcasing the document to be signed, " "which is accessible to the customer via the customer portal." msgstr "" #: ../../content/applications/sales/rental.rst:227 msgid "" "Odoo guides the customer through the signing process with clear, clickable " "indicators, and allows them to create electronic signatures to quickly " "complete the form." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "The adopt your signature pop-up window that appears in the Odoo Rental " "application." msgstr "" #: ../../content/applications/sales/rental.rst:234 msgid "" "Once the document has been signed and completed, click the " ":guilabel:`Validate & Send Completed Document` button at the bottom of the " "document." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "The validate and send completed document button in the Odoo Rental " "application." msgstr "" #: ../../content/applications/sales/rental.rst:241 msgid "" "Upon clicking the :guilabel:`Validate & Send Completed Document` button, " "Odoo presents the option to download the signed document for record-keeping " "purposes, if necessary." msgstr "" #: ../../content/applications/sales/rental.rst:245 msgid "`Odoo Tutorials: Sign `_" msgstr "" #: ../../content/applications/sales/rental.rst:250 msgid "Pickup products" msgstr "" #: ../../content/applications/sales/rental.rst:252 msgid "" "When a customer picks up the product(s), navigate to the appropriate rental " "order, click the :guilabel:`Pickup` button, and then click " ":guilabel:`Validate` in the :guilabel:`Validate a pickup` pop-up form that " "appears." msgstr "" #: ../../content/applications/sales/rental.rst:256 msgid "" "Doing so places a :guilabel:`Picked-up` status banner on the rental order." msgstr "" #: ../../content/applications/sales/rental.rst:259 msgid "Return products" msgstr "" #: ../../content/applications/sales/rental.rst:261 msgid "" "When a customer returns the product(s), navigate to the appropriate rental " "order, click the :guilabel:`Return` button, and validate the return by " "clicking :guilabel:`Validate` in the :guilabel:`Validate a return` pop-up " "form that appears." msgstr "" #: ../../content/applications/sales/rental.rst:265 msgid "" "Doing so places a :guilabel:`Returned` status banner on the rental order." msgstr "" #: ../../content/applications/sales/rental.rst:268 msgid "Print pickup and return receipts" msgstr "" #: ../../content/applications/sales/rental.rst:270 msgid "" "Pickup and return receipts can be printed for customers when they pick up " "and/or return rental products." msgstr "" #: ../../content/applications/sales/rental.rst:273 msgid "" "To print pickup and/or return receipts, navigate to the appropriate rental " "order, click the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu." msgstr "" #: ../../content/applications/sales/rental.rst-1 msgid "" "The pickup and return receipt print option in the Odoo Rental application." msgstr "" #: ../../content/applications/sales/rental.rst:280 msgid "" "From this drop-down menu, hover over the :guilabel:`Print` option to reveal " "a sub-menu. Then select :guilabel:`Pickup and Return Receipt`." msgstr "" #: ../../content/applications/sales/rental.rst:283 msgid "" "Odoo generates and downloads a PDF, detailing all information about the " "current status of the rented item(s)." msgstr "" #: ../../content/applications/sales/sales.rst:10 msgid "" "**Odoo Sales** is the application to run your sales process (from quotation " "to sales order) and deliver and invoice what has been sold." msgstr "" #: ../../content/applications/sales/sales.rst:14 msgid "" "`Odoo Tutorials: Sales Tutorials `_" msgstr "" #: ../../content/applications/sales/sales/amazon_connector.rst:5 msgid "Amazon Connector" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:3 msgid "Amazon Connector features" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:5 msgid "" "The *Amazon Connector* synchronizes orders between Amazon and Odoo, which " "considerably reduces the amount of time spent manually entering Amazon " "orders (from the Amazon Seller account) into Odoo. It also allows users to " "accurately keep track of Amazon sales in Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:10 msgid "Supported features" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:12 msgid "The Amazon Connector is able to:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:14 msgid "" "Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM), and " "their order items, which include:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:17 msgid "product name, description, and quantity" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:18 msgid "shipping costs for the product" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:19 msgid "gift wrapping charges" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:21 msgid "" "Create any missing partner related to an order in Odoo (contact types " "supported: contact and delivery address)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:24 msgid "Notify Amazon of confirmed shipment in Odoo (FBM) to get paid." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:26 msgid "" "Synchronize (Odoo to Amazon) all available quantities of your products " "(FBM)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:28 msgid "Support multiple seller accounts." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:30 msgid "Support multiple marketplaces per seller account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:32 msgid "" "The following table lists capabilities provided by Odoo when using the " "Amazon Connector:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:35 msgid "Fulfilled By Amazon (FBA)" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:35 msgid "Fulfilled By Merchant (FBM)" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:37 msgid "**Orders**" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:37 msgid "Synchronize shipped and canceled orders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:37 msgid "Synchronize unshipped and canceled orders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:40 msgid "**Shipping**" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:40 msgid "" "Shipping cost is computed by Amazon, and included in the synchronized order." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:40 msgid "" "Shipping cost is computed by Amazon and included in the synchronized orders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:44 msgid "Shipping done by Amazon." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:44 msgid "" "A delivery order is automatically created in Odoo for each new order. Once " "it has been processed in Odoo, the status is then synchronized in Amazon." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:50 msgid "**Gift Wrapping**" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:50 #: ../../content/applications/sales/sales/amazon_connector/features.rst:61 msgid "Handled by Amazon." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:50 msgid "" "Cost is computed by Amazon, and included in the synchronized order. Gift " "message is added on a line of the order and on the delivery order. Then it " "is up to the user." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:56 msgid "**Stock Management**" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:56 msgid "" "Managed by Amazon, and synchronized with a virtual location to follow it in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:56 msgid "Managed in Odoo Inventory app, and synchronized with Amazon." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:61 msgid "**Delivery Notifications**" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:61 msgid "Send by Amazon, based on delivery status synchronized from Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:66 #: ../../content/applications/sales/sales/amazon_connector/manage.rst:20 msgid "" "The stock synchronization does **not** currently support selling the same " "product as :abbr:`FBM (Fulfilled By Merchant)` *and* :abbr:`FBA (Fulfilled " "By Amazon)`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:69 #: ../../content/applications/sales/sales/amazon_connector/manage.rst:23 msgid "" "At times, when stock is sent for all products, it triggers a stock problem " "with Amazon, where Amazon incorrectly thinks the :abbr:`FBM (Fulfilled By " "Merchant)` product has some quantity in :abbr:`FBM (Fulfilled By Merchant)`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:73 #: ../../content/applications/sales/sales/amazon_connector/manage.rst:27 msgid "" "As a result, Amazon then sells it as :abbr:`FBM (Fulfilled By Merchant)`, " "instead of taking from their own warehouse. Odoo developers are currently " "working on resolving this issue to avoid future discrepancies." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:78 msgid "" "The Amazon Connector is designed to synchronize the data of sales orders. " "Other actions, such as downloading monthly fees reports, handling disputes, " "or issuing refunds, **must** be managed from the *Amazon Seller Central*, as" " usual." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:83 msgid "" "As of February 19, 2024, in North American marketplaces, :abbr:`FBA " "(Fulfilled by Amazon)` orders created with the *Amazon Connector*, do not " "get the customer's name passed onto the sales/delivery order in Odoo. This " "is due to the fact that Amazon now calculates, and remits, sales tax on " "behalf of sellers. In other words, personally identifiable customer " "information is not transmitted to the seller any longer, after a :abbr:`FBA " "(Fulfilled by Amazon)` order." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:92 msgid "Supported marketplaces" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:94 msgid "" "If a marketplace is not listed in your Amazon marketplaces, it's possible to" " :ref:`add a new marketplace `." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:98 msgid "**North America region**" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:100 msgid "Canada" msgstr "Kanada" #: ../../content/applications/sales/sales/amazon_connector/features.rst:100 msgid "Amazon.ca" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:102 msgid "Mexico" msgstr "Mehika" #: ../../content/applications/sales/sales/amazon_connector/features.rst:102 msgid "Amazon.com.mx" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:104 msgid "US" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:104 msgid "Amazon.com" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:108 msgid "**Europe region**" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:110 msgid "Germany" msgstr "Nemčija" #: ../../content/applications/sales/sales/amazon_connector/features.rst:110 msgid "Amazon.de" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:112 msgid "Spain" msgstr "Španija" #: ../../content/applications/sales/sales/amazon_connector/features.rst:112 msgid "Amazon.es" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:114 msgid "France" msgstr "Francija" #: ../../content/applications/sales/sales/amazon_connector/features.rst:114 msgid "Amazon.fr" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:116 msgid "UK" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:116 msgid "Amazon.co.uk" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:118 msgid "Italy" msgstr "Italija" #: ../../content/applications/sales/sales/amazon_connector/features.rst:118 msgid "Amazon.it" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:120 msgid "Netherlands" msgstr "Nizozemska" #: ../../content/applications/sales/sales/amazon_connector/features.rst:120 msgid "Amazon.nl" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:124 #: ../../content/applications/sales/sales/amazon_connector/manage.rst:208 #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:16 #: ../../content/applications/sales/sales/ebay_connector/manage.rst:30 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:8 msgid ":doc:`setup`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:125 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:155 #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:17 #: ../../content/applications/sales/sales/ebay_connector/setup.rst:17 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:9 msgid ":doc:`manage`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:3 msgid "Amazon order management" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:6 msgid "Order synchronization" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:8 msgid "" "Orders are automatically fetched from Amazon, and synchronized in Odoo, at " "regular intervals." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:10 msgid "" "The synchronization is based on the Amazon status: only orders whose status " "has changed since the last synchronization are fetched from Amazon. This " "includes changes on either end (Amazon or Odoo)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:13 msgid "" "For *FBA* (Fulfilled by Amazon), only *Shipped* and *Canceled* orders are " "fetched." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:15 msgid "" "For *FBM* (Fulfilled by Merchant), the same is done for *Unshipped* and " "*Canceled* orders. For each synchronized order, a sales order and customer " "are created in Odoo (if the customer is not already registered in the " "database)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:32 msgid "" "When an order is canceled in Amazon, and was already synchronized in Odoo, " "the corresponding sales order is automatically canceled in Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:36 msgid "Force synchronization" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:38 msgid "" "In order to force the synchronization of an order, whose status has **not** " "changed since the previous synchronization, start by activating the " ":ref:`developer mode `. This includes changes on either end " "(Amazon or Odoo)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:42 msgid "" "Then, navigate to the Amazon account in Odoo (:menuselection:`Sales app --> " "Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon " "Accounts`), and modify the date under :menuselection:`Orders Follow-up --> " "Last Order Sync`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:46 msgid "" "Be sure to pick a date that occurs prior to the last status change of the " "desired order to synchronize and save. This will ensure synchronization " "occurs correctly." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:51 msgid "" "To immediately synchronize the orders of an Amazon account, switch to " ":ref:`developer mode `, head to the Amazon account in Odoo, " "and click :guilabel:`Sync Orders`. The same can be done with pickings by " "clicking :guilabel:`Sync Pickings`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:56 msgid "Manage deliveries in FBM" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:58 msgid "" "Whenever an FBM (Fulfilled by Merchant) order is synchronized in Odoo, a " "picking is instantly created in the *Inventory* app, along with a sales " "order and customer record. Then, decide to either ship all the ordered " "products to the customer at once, or ship products partially using " "backorders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:62 msgid "" "When a picking related to the order is confirmed, a notification is then " "sent to Amazon, who, in turn, notifies the customer that the order (or a " "part of it) is on its way." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:66 msgid "" "Amazon requires users to provide a tracking reference with each delivery. " "This is needed to assign a carrier." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:69 msgid "" "If the carrier doesn't automatically provide a tracking reference, one must " "be set manually. This rule applies to all Amazon marketplaces." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:73 msgid "" "If the chosen carrier isn't supported by Odoo, a carrier with the same name " "can still be created (e.g. create a carrier named `easyship`). The name used" " is **not** case sensitive, but be mindful to avoid typos. If there are " "typos, Amazon will **not** recognize them. Next, create a delivery carrier " "named `Self Delivery` to inform Amazon that the user will make the " "deliveries. Even with this route, a tracking reference still **must** be " "entered. Remember, the customer is notified by email about the delivery, and" " the carrier, along with the tracking reference, are displayed in the email " "to the customer." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:82 msgid "" ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:87 msgid "Manage errors when synchronizing deliveries" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:89 msgid "" "Sometimes, Amazon can fail to correctly process all the information sent by " "Odoo. In this case, Odoo sends an email listing all the shipments that " "failed and the errors Amazon sent with them. In addition, these shipments " "are flagged with a :guilabel:`Synchronization with Amazon failed` tag." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:93 msgid "" "Usually, the error can be corrected directly in the Amazon backend or in " "Odoo. If the problem is corrected in Odoo, synchronize the shipment again " "using the :guilabel:`Retry Amazon Sync` button." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:97 msgid "" "It might happen that Odoo receives a notification from Amazon saying that " "some delivery information was not processed, but without specifying which " "shipments were affected. In that case, all the shipments in an unknown state" " will be treated as if they failed to synchronize. Once Odoo receives a " "notification from Amazon saying that a shipment was processed, its tag will " "change to :guilabel:`Synchronized with Amazon`. To speed up this process, on" " your Amazon account, click on :guilabel:`Sync Orders` to manually " "synchronize these orders, or click on :guilabel:`Recover Order` and enter " "the relevant Amazon Order Reference." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:106 msgid "Follow deliveries in FBA" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:108 msgid "" "When an FBA (Fulfilled by Amazon) order is synchronized in Odoo, a stock " "move is recorded in the *Inventory* app for each sales order item. That way," " it's saved in the system." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:111 msgid "" "Inventory managers can access these stock moves by navigating to " ":menuselection:`Inventory app --> Reporting --> Moves History`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:114 msgid "" "For FBA orders, the stock move is automatically created in Odoo by the " "Amazon connector, thanks to the shipping status of Amazon. When sending new " "products to Amazon, the user should manually create a picking (delivery " "order) to transfer these products from their warehouse to the Amazon " "location." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:119 msgid "" "To follow *Amazon (FBA)* stock in Odoo, make an inventory adjustment after " "replenishing stock. An automated replenishment from reordering rules can " "also be triggered on the Amazon location." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:122 msgid "" "The Amazon location is configurable by accessing the Amazon account managed " "in Odoo. To access Amazon accounts in Odoo navigate to :menuselection:`Sales" " app --> Configuration --> Settings --> Connectors --> Amazon Sync --> " "Amazon Accounts`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:126 msgid "" "All accounts of the same company use the same Amazon location, by default. " "However, it is possible to follow the stock filtered by marketplace." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:129 msgid "" "To do that, first remove the marketplace, where the desired stock to follow " "separately can be found, from the list of synchronized marketplaces, which " "can be found by navigating to :menuselection:`Sales app --> Configuration " "--> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:134 msgid "" "Next, create another registration for this account, and remove all " "marketplaces--- **except** the marketplace this is desired to be isolated " "from the others." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:137 msgid "" "Lastly, assign another stock location to the second registration of the " "account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:140 msgid "Invoice and register payments" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:143 msgid "Issue invoices" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:145 msgid "" "Due to Amazon's policy of not sharing customer email addresses, it is " "**not** possible to send invoices directly to Amazon customers from Odoo. " "However, it **is** possible to manually upload the generated invoices from " "Odoo to the Amazon back-end." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:149 msgid "" "Additionally, for B2B clients, it is currently required to manually retrieve" " VAT numbers from the Amazon back-end **before** creating an invoice in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:153 msgid "" "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: " "invoices created from Amazon sales orders are **not** synchronized with " "TaxCloud, since Amazon already includes them in its own tax report to " "TaxCloud." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:158 msgid "TaxCloud integration will be decommissioned in Odoo 17+." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:161 msgid "Register payments" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:163 msgid "" "Since customers pay Amazon as an intermediary, creating a dedicated *Bank* " "journal (e.g. named `Amazon Payments`), with a dedicated *Bank and Cash* " "intermediary account is recommended." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:166 msgid "" "Additionally, as Amazon makes a single monthly payment, selecting all the " "invoices linked to a single payment is necessary when registering payments." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:169 msgid "" "To do that, use the appropriate :guilabel:`Journal` dedicated to Amazon " "payments, and select :guilabel:`Batch Deposit` as the :guilabel:`Payment " "Method`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:172 msgid "" "Then, select all the generated payments, and click :menuselection:`Actions " "--> Create batch payment --> Validate`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:176 msgid "" "This same action can be performed with vendor bills from Amazon dedicated to" " commissions." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:178 msgid "" "When the balance is received in the bank account at the end of the month, " "and the bank statements are recorded, credit the Amazon intermediary account" " by the amount received." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:182 msgid "Follow Amazon sales in sales reporting" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:184 msgid "" "On the Amazon account profile in Odoo, a sales team is set under the " ":guilabel:`Order Follow-up` tab." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:187 msgid "" "This gives quick access to important metrics related to sales reporting. By " "default, the Amazon account's sales team is shared between all of the " "company's accounts." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:190 msgid "" "If desired, the sales team on the account can be changed for another, in " "order to perform a separate reporting for the sales of this account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:194 msgid "It is also possible to perform reporting on a per-marketplace basis." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:196 msgid "" "First, remove the desired marketplace from the list of synchronized " "marketplaces." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:198 msgid "" "To access the list of synchronized marketplaces in Odoo, navigate to " ":menuselection:`Sales app --> Configuration --> Settings --> Connectors --> " "Amazon Sync --> Amazon Accounts`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:201 msgid "" "Then, create another registration for this account, and remove all other " "marketplaces **except** the one to isolate." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:204 msgid "" "Lastly, assign another sales team to one of the two registrations of the " "account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:207 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:154 msgid ":doc:`features`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:3 msgid "Amazon Connector configuration" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:5 msgid "" "Odoo allows users to register an Amazon seller account in the database, but " "the user **must** have a paid Amazon Seller account prior to completing the " "configuration." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:8 msgid "" "Set up a paid Seller account on Amazon by first logging into the Amazon " "platform, and navigating to :menuselection:`Account \\& Lists --> Start a " "Selling Account` from the drop-down menu located in the header section." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:12 msgid "" "Then on the :guilabel:`Sell with Amazon` page, follow the sign-up process " "and finally proceed to follow the instructions below to register and link " "that Amazon Seller account in Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:16 msgid "`Sell with Amazon `_" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:19 msgid "Connect Amazon Seller account to Odoo" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:23 msgid "" "To connect an Amazon Seller account in Odoo, navigate to " ":menuselection:`Sales app --> Configuration --> Settings --> Connectors " "section`, activate the :guilabel:`Amazon Sync` feature, and click " ":guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:27 msgid "" "Then, return to :menuselection:`Sales app --> Configuration --> Settings -->" " Connectors section`, and click on the :guilabel:`Amazon Accounts` link " "under the :guilabel:`Amazon Sync` setting." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 msgid "" "The Amazon Accounts link beneath the Amazon Sync settings in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:34 msgid "" "Doing so reveals a separate :guilabel:`Amazon Accounts` page. From here, " "click :guilabel:`New` to create and link a new Amazon account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:37 msgid "" "On the blank :guilabel:`Amazon Account` form page, start by choosing a name " "for the account (e.g. `American Marketplace`). Then, in the " ":guilabel:`Credentials` tab, select the marketplace on which the seller " "account was initially created from the :guilabel:`Home Marketplace` drop-" "down menu." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 msgid "A typical Amazon Account form page in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:45 msgid "" "After saving, the field in the :guilabel:`Credentials` tab is replaced by a " ":guilabel:`Link with Amazon` button." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 msgid "" "A typical Amazon Account form page and Link with Amazon button in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:52 msgid "" "Clicking that button redirects to either the Amazon login page, or directly " "to the required consent page, if the user is already logged in to Amazon." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:55 msgid "On the login page, log in to the desired Amazon seller account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:57 msgid "" "On the consent page, confirm that Amazon is allowed to give Odoo access to " "the account and related data." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:60 msgid "" "Upon confirmation, Amazon returns the user to Odoo, and the account has been" " registered." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:62 msgid "" "With the Amazon account successfully registered, the marketplaces available " "to this specific account are synchronized with Odoo and listed under the " ":guilabel:`Marketplaces` tab." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:65 msgid "" "If desired, remove items from the list of synchronized marketplaces to " "disable synchronization." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:68 msgid "Amazon orders in Odoo" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:70 msgid "" "When an Amazon order is synchronized, up to three line items are created on " "the sales order in Odoo. Each one represents a product sold on Amazon: one " "for the product that was sold on Amazon Marketplace, one for the shipping " "charges (if any), and one for the gift wrapping charges (if any)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:76 msgid "" "The selection of a database product for a sales order item is done by " "matching its :guilabel:`Internal Reference` (a customizable product " "reference idenifier in Odoo, like `FURN001`) with the Amazon *SKU* for " "marketplace items, the Amazon *Shipping Code* for delivery charges, and the " "Amazon *Gift Wrapping* code for gift wrapping charges." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:81 msgid "" "For marketplace products, pairings are saved as *Amazon Offers*, which are " "listed under the :guilabel:`Offers` smart button on the account form." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 msgid "The Amazon Offers smart button on the account form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:88 msgid "" "Offers are automatically created when the pairing is established, and " "they're used for subsequent orders to lookup SKUs. If no offer with a " "matching SKU is found, :ref:`the internal reference is used instead " "`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:93 msgid "" "It's possible to force the pairing of a marketplace item with a specific " "product, by changing either the product or the SKU of an offer to ensure " "they match. The offer can be manually created if it was not automatically " "done yet." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:97 msgid "" "This is useful if the internal reference is not used as the SKU, or if the " "product sells under different conditions." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:100 msgid "" "If no database product with a matching internal reference is found for a " "given Amazon SKU or gift wrapping code, then a default database product, " "*Amazon Sale*, is used. The same is done with the default product *Amazon " "Shipping* if no database product is found for a given Amazon shipping code." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:105 msgid "" "To modify default products, activate the :ref:`developer mode `, and navigate to :menuselection:`Sales app --> Configuration --> " "Settings --> Connectors --> Amazon Sync --> Default Products`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:110 msgid "Product tax configuration" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:112 msgid "" "To allow for tax reporting of Amazon sales with Odoo, the taxes applied to " "the sales order items are those set on the product, or determined by the " "fiscal position." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:115 msgid "" "Make sure to have the correct taxes set on your products in Odoo, or have it" " done by a fiscal position, to avoid discrepancies in the subtotals between " "*Amazon Seller Central* and Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:119 msgid "" "As Amazon does not necessarily apply the same taxes as those configured in " "Odoo, it may happen that order totals differ by a few cents between Odoo and" " *Amazon Seller Central*. Those differences can be resolved with a write-off" " when reconciling the payments in Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:126 msgid "Add a new marketplace" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:128 msgid "" "All marketplaces are supported by the Amazon Connector. To add a new " "marketplace, proceed as follows:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:131 msgid "Activate the :ref:`developer mode `." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:132 msgid "" "Go to :menuselection:`Sales app --> Configuration --> Settings --> " "Connectors --> Amazon Sync --> Amazon Marketplaces`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:134 msgid "Click :guilabel:`New` to create a new marketplace record." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:135 msgid "" "Enter the Marketplace ID in the :guilabel:`API Idenifier` field, and select " "the :guilabel:`Amazon Region` for your marketplace as described in the " "`Amazon Documentation for marketplace IDs and regions `_, and the :guilabel:`Seller " "Central URL` as described in the `Amazon Documentation for seller central " "URLs `_." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:140 msgid "" "Set the :guilabel:`Name` of the record to `Amazon.` to easily " "retrieve it (e.g. `Amazon.se`). The :guilabel:`API Identifier`, the " ":guilabel:`Region` and the :guilabel:`Seller Central URL` fields should " "respectively hold the *Marketplace ID*, the selected Amazon region, and the " "*Seller Central URL* values from the Amazon Documentation." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:144 msgid "" "Once the marketplace is saved, update the Amazon Account configuration by " "going to :menuselection:`Sales app --> Configuration --> Settings --> " "Connectors --> Amazon Sync --> Amazon Accounts`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:147 msgid "" "Select the account on which to use the new marketplace, go to the " ":guilabel:`Marketplaces` tab, and click on :guilabel:`Update available " "marketplaces`. An animation should confirm the success of the operation. " "Newly added marketplaces are automatically added to the list of synchronized" " marketplaces. If the new marketplace is not added to the list, it means " "that it is either incompatible or unavailable for the seller account." msgstr "" #: ../../content/applications/sales/sales/ebay_connector.rst:5 msgid "eBay Connector" msgstr "eBay povezovalnik" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:3 msgid "Linking existing listings" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:5 msgid "" "Once the eBay account is linked existing listings from within the eBay " "seller account need to be added manually to the Odoo product listings." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:8 msgid "" "The process will be as follows: - Turn off eBay scheduled actions - Add " "products and link listings - Turn on eBay scheduled actions" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:14 #: ../../content/applications/sales/sales/ebay_connector/manage.rst:28 #: ../../content/applications/sales/sales/ebay_connector/setup.rst:15 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:6 msgid "To learn more about the eBay connector visit these pages as well:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:18 #: ../../content/applications/sales/sales/ebay_connector/manage.rst:32 #: ../../content/applications/sales/sales/ebay_connector/setup.rst:19 msgid ":doc:`troubleshooting`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:21 msgid "Turn off eBay scheduled actions" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:23 msgid "" "To start linking existing listings in eBay, first turn off the eBay " "notifications in the scheduled actions in Odoo. The reason for this is so " "that no orders or eBay data syncs during this process. The " ":guilabel:`Scheduled Actions` can be accessed by first activating " ":ref:`developer mode `. After doing so, go to " ":menuselection:`Settings --> Technical --> Automation --> Scheduled " "Actions`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:30 msgid "" ":doc:`../../../general/developer_mode` must be activated to ensure the " "technical menu appears for the user." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:33 msgid "" "Disabling scheduled actions enables users to sync and validate eBay data " "before receiving orders. The following are descriptions of scheduled actions" " that need to be temporarily deactivated:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:36 msgid "" ":guilabel:`eBay: get new orders`: eBay pushes new orders not already in Odoo" " (based on :guilabel:`client_order_reference`, or :guilabel:`sales order " "reference` field). This command also updates existing orders, where changes " "we made in eBay. New and updated orders are then placed in draft mode. " "Customers will be created if they are not already in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:40 msgid "" ":guilabel:`eBay: synchronize stock`: eBay displays Odoo's stock on hand." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:41 msgid "" ":guilabel:`eBay: update categories`: eBay will push updated monthly " "categories (only up to fourth layer; a manual update required for the rest)." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:44 msgid "" "To toggle off the eBay notification, select the entry from the " ":guilabel:`Scheduled Actions` list. Then, on the page, click the " ":guilabel:`Active` toggle button to turn it off." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:48 msgid "Sync eBay categories" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:50 msgid "" "To ensure that Odoo's eBay products have all the categories available on " "eBay, the eBay categories should be synced to Odoo next." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:53 msgid "" "Navigate to :menuselection:`Settings --> Technical --> Automation --> " "Scheduled Actions`. Click into the scheduled action labeled: " ":guilabel:`Ebay: update categories` and then click :guilabel:`Run Manually`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:58 msgid "" "Odoo only recognizes eBay category paths up to four layers deep. If a " "product has a listing of more than four, the category field will only " "populate up to the fourth layer." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:61 msgid "" "If product categories beyond four paths are required, users need to manually" " add those paths. This has historically been done by getting a list of all " "product categories beyond 4 paths, manually importing them into the Product " "Category model in Odoo, then linking them individually to the product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:66 msgid "" "Users can import the remaining product categories into the eBay product " "categories manually using using the :guilabel:`Action` menu and " ":guilabel:`Import` feature." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:70 msgid "Link eBay listings" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:72 msgid "" "To add eBay listings in Odoo, either manually add products, using a listing " "ID, or establish an automatic listing link between Odoo and eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:76 msgid "" "For more information on listing a product from scratch visit: :ref:`How to " "list a product? `" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:80 msgid "Manual listing link" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:82 msgid "" "To add an eBay listing to products in Odoo, begin by going to " ":menuselection:`Sales app --> Products --> Products` and selecting the " "desired product. Click on :guilabel:`Sell on eBay` (either in the " ":guilabel:`eBay` tab or under the :guilabel:`Product name`). Select " ":guilabel:`Save` if necessary." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:86 msgid "" "Still the product form, click :guilabel:`link to listing` in the top menu " "and enter in listing ID from eBay in the pop up (the listing ID is in the " "eBay product URL)." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:90 msgid "" "An example URL would be as such: " "`www.ebay.com/itm/272222656444?hash=item3f61bc17bb:g:vJ0AAOSwslJizv8u`. The " "listing ID is `272222656444` in this case. Once the listing ID has been " "entered the eBay listing information will sync into Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:96 msgid "Turn on eBay scheduled Actions" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:98 msgid "" "The next step is to turn on the eBay notifications in the scheduled actions " "in Odoo so that orders and data are exchanged. The :guilabel:`Scheduled " "Actions` can be accessed by first activating :ref:`developer mode " "` and go to :menuselection:`Settings --> Technical --> " "Automation --> Scheduled Actions`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:103 msgid "" "Turning on the following scheduled actions allows users to sync and validate" " eBay data automatically." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:106 msgid "" ":guilabel:`eBay: get new orders`: eBay will push all new orders not already " "in Odoo (based on client_order_reference, or sales order reference field), " "and will update orders if there has been a change from eBay. Orders will be " "put in draft mode. Customers will be created if they are not already in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:110 msgid "" ":guilabel:`eBay: synchronize stock`: eBay will display the stock on hand in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:111 msgid "" ":guilabel:`eBay: update categories`: eBay will push updated monthly " "categories (only up to fourth layer, will need to manually update the rest)." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:115 msgid "" "If an order comes in and the listing from the order is not linked to a " "product, eBay will create a consumable product.product in its place. These " "consumables should be altered on the *Sales Order* while in draft state to " "represent a storable product, and then the user can link to the listing as " "they come in." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:121 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:127 msgid ":doc:`/applications/sales/sales/ebay_connector/manage`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:122 #: ../../content/applications/sales/sales/ebay_connector/manage.rst:160 msgid ":doc:`/applications/sales/sales/ebay_connector/troubleshooting`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:123 #: ../../content/applications/sales/sales/ebay_connector/manage.rst:162 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:129 msgid ":doc:`/applications/sales/sales/ebay_connector/setup`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:3 msgid "How to list a product?" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:7 msgid "" "In order to list a product on eBay and Odoo there are two methods in Odoo to" " do so:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:9 msgid "(*Preferred method*) Make a product in Odoo and list the item eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:11 msgid "" "Click :guilabel:`List Item on eBay` in the top menu of the product template." " The product template can be accessed by navigating to :menuselection:`Sales" " app --> Products --> Product` and selecting the individual product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:14 msgid "" "(*Less preferred method*) List the item on eBay, then create the product in " "Odoo, and finally link product to the item on eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:17 msgid "" "Click :guilabel:`Link With Existing eBay Listing` in the top menu on the " "product template.The product template can be accessed by navigating to " ":menuselection:`Sales app --> Product --> Product` and selecting the " "individual product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:22 msgid "" "If an order comes in and the listing from the order is not linked to a " "product, eBay will create a consumable product.product in its place. These " "consumables should be altered on the *sales order* while in draft state to " "represent a storable product, and then the user can link to the listing as " "they come in." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:31 #: ../../content/applications/sales/sales/ebay_connector/setup.rst:18 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:10 msgid ":doc:`linking_listings`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:35 msgid "Listing without variation" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:37 msgid "" "Access the product template by navigating to :menuselection:`Sales app --> " "Products --> Product` and selecting the individual product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:40 msgid "" "In order to list a product, select the :guilabel:`Sell on eBay` field on a " "product template. :guilabel:`Sell on eBay` is either in an :guilabel:`eBay` " "tab or under the :guilabel:`Product name`. Click :guilabel:`Save` if " "necessary." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst-1 msgid "The eBay template form listed in the product template in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:48 msgid "" "When the :guilabel:`Use Stock Quantity` field is checked, the quantity set " "on eBay is the Odoo *Forecast Quantity* (Odoo *Inventory* app)." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:51 msgid "" "The policies need to be set in order to be able to list on eBay. A value " "must be selected for the following fields :guilabel:`Payment Policy`, " ":guilabel:`Return Policy`, and :guilabel:`Shipping Policy`. The options are " "imported from the eBay database. If no option appears, they can be imported " "by navigating to :menuselection:`Sales app --> Configuration --> Settings " "--> eBay`, and clicking on the :guilabel:`Policies` button in the " ":guilabel:`Synchronization` field. This button **only** appears once the " "production and sandbox credentials have been set." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:58 msgid "" "The :guilabel:`Description Template` allows the administrator to use " "templates in listings. The default template only uses the :guilabel:`eBay " "Description` field of the product. HTML can be used inside the " ":guilabel:`Description Template`, and in the :guilabel:`eBay Description` in" " Odoo 14. Starting in Odoo 15, the powerbox feature is available to use in " "the template and description. Simply type a forward slash `/` to reveal a " "menu with formatting, layout, and text options. To add an image, type " "`/image`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:65 msgid "" "To use images in the listing, an image needs to be added as one of the " "*Attachments* on the product template." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:69 msgid "" "For more information on template configuration in Odoo visit: " ":doc:`../../../general/companies/email_template`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:73 msgid "Listing with variations" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:75 msgid "" "When the :guilabel:`Sell on eBay` is checked on a product containing " "variations with :guilabel:`Fixed Price` as :guilabel:`Listing Type`, the " "eBay form is slightly different. Go to the :guilabel:`Variants` tab to or " "click :guilabel:`Configure Variants` in the top menu to configure the " "variant settings. Pricing can be configured for each variation." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:80 msgid "" "When the :guilabel:`Listing Type` is changed to :guilabel:`Fixed Price`, " "Odoo presents a variant table at the bottom of the :guilabel:`eBay` tab, in " "which the :guilabel:`Fixed Price` can be entered, and the decision to " ":guilabel:`Publish on eBay` can be made for specific variants, along with " "other options." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst-1 msgid "" "The fixed price listing type in the eBay tab on a product form in Odoo " "sales." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:90 msgid "Product identifiers" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:92 msgid "" "Products identifiers such as EAN, UPC, Brand or MPN are required in most of " "the eBay categories." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:95 msgid "EAN and UPC identifiers" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:97 msgid "" "The module manages the EAN and UPC identifiers with the :guilabel:`Barcode` " "field of the product variant. If the :guilabel:`Barcode` field is empty or " "is value is not valid, the EAN and UPC values will be set as 'Does not " "apply' as recommended by eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:101 msgid "" "Barcodes can be found on the product template, under the the " ":guilabel:`General Information` tab. Access the product template, first, by " "navigating to :menuselection:`Sales app --> Products --> Product` and " "selecting the individual product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:106 msgid "Listing with item specifics" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:108 msgid "" "In order to add item specifics, one should create a product attribute with a" " single value in the :guilabel:`Attributes & Variants` tab on the product " "form. Examples of item specifics include: `MPN` or `Brand`. The Brand and " "MPN values are working as item specifics and should be defined in the " ":guilabel:`Attributes & Variants` tab on the product form. If these values " "are not set, 'Does not apply' will be used for the eBay listing." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:115 msgid "Process invoices and payments" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:118 msgid "Posting payment" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:120 msgid "" "When eBay orders are placed they are always paid for up front, via the eBay " "site. At no point will users pay for items on eBay through Odoo. Therefore, " "once orders are synced into Odoo from eBay they are already paid for. Odoo's" " invoicing and payment functionalities are not utilized. However, invoices " "need to be created and marked as Paid to “close” the *Sales Order*." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:125 msgid "" "Users can opt to mass create and post invoices in batches. To do so, " "navigate to Quotations in the list view by going to :menuselection:`Sales " "app --> Orders --> Quotations`. In the upper right corner, select the list " "view icon. Hover over the icons to reveal the name of each. Then check the " "boxes on the left that invoices should be made for and go to the " ":guilabel:`Action` menu or ⚙️ [Gear icon] . Click on :guilabel:`Create " "Invoices`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:131 msgid "" "A pop-up will appear and click on the :guilabel:`Create and view invoice` " "button. A new screen will populate with the newly created invoices. Next, " "select all of them by clicking on the box icon next to :guilabel:`Number` in" " the header row of the list, this will select all the records. Then navigate" " to the :guilabel:`Action` menu and click :guilabel:`Post entries`. " "Following this step, a pop-up will appear and click on :guilabel:`Post " "journal entries`. This will take the invoices out of *draft* and set them to" " *posted*." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:139 msgid "Reconciling payments" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:141 msgid "" "Users typically utilize PayPal to receive payment from eBay, and then send " "lump sums from PayPal into their bank account. To reconcile this income, " "users can reconcile the one PayPal transfer with all related invoices." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:145 msgid "" "First navigate to the :guilabel:`Accounting Dashboard` by going to the " ":menuselection:`Accounting app --> Dashboard --> Bank`. :guilabel:`Create` a" " new transaction and enter the :guilabel:`Label` as `eBay Sales`. Fill out " "the :guilabel:`Amount` and enter a :guilabel:`Statement` date in. Click on " ":guilabel:`Create and edit`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:150 msgid "" "For the :guilabel:`Ending Balance` field, enter the same account that was " "entered for the :guilabel:`Amount` above. Click on :guilabel:`Save`. Next, " "open the new balance that needs to be reconciled. Under the tab marked: " ":guilabel:`Match Existing Entries` select the entries that are included in " "this balance." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:155 msgid "" "After adding all the necessary entries, click :guilabel:`Validate` to " "complete the reconciliation. To verify the payment, navigate to " ":menuselection:`Customers --> Invoices` and select the desired customer " "invoice. The *Paid* label should appear under the :guilabel:`Payment Status`" " column." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:161 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:128 msgid ":doc:`/applications/sales/sales/ebay_connector/linking_listings`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:3 msgid "eBay connector setup" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:6 msgid "Overview" msgstr "Pregled" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:8 msgid "" "Odoo's eBay connector allows eBay listings to connect with Odoo products. " "Once connected, :doc:`updates to the listings ` can be " "made in Odoo or in eBay. When an item sells on eBay, draft *sales orders* " "are created in Odoo for the user to review and confirm. Once the sales order" " is confirmed, Odoo *Inventory* and *Sales* apps function standard to pull " "products out of inventory, and allow the user to create invoices." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:22 msgid "eBay - Odoo linked fields" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:24 msgid "" "The following are eBay product details. Each of these eBay fields update " "corresponding fields in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:27 msgid "eBay URL" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:28 msgid "eBay status" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:29 msgid "Quantity sold" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:30 msgid "Start date" msgstr "Datum začetka" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:31 msgid "Title" msgstr "Naslov" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:32 msgid "Subtitle" msgstr "Podnaslov" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:33 msgid "Item condition" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:34 msgid "Category" msgstr "Kategorija" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:35 msgid "Category 2" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:36 msgid "Store category" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:37 msgid "Store category 2" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:38 msgid "Payment policy" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:39 msgid "Seller profiles" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:40 msgid "Postal code" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:41 msgid "Shipping policy" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:42 msgid "Listing type (fixed price or auction)" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:44 msgid "Starting price for Auction" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:45 msgid "Buy it now price" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:46 msgid "Fixed Price amount" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:48 msgid "Use stock quantity" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:49 msgid "Quantity on eBay" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:50 msgid "Duration" msgstr "Trajanje" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:51 msgid "Allow best offer" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:52 msgid "Private listing" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:53 msgid "eBay description" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:54 msgid "eBay product image" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:55 msgid "Country" msgstr "Država" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:58 msgid "eBay terms" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:60 msgid "" "*Variations* group multiple products into one, with variation (or variant) " "options. Variations can sync to Odoo's attributes and values. Variations " "will appear in drop down menus near the top of the page when viewing an eBay" " listing. These are comparable to product variants in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 msgid "An example on eBay of the variations that can be added to a product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:68 msgid "" "*Item specifics*, located at the bottom of the listing, detail product-" "specific information. These specifics don't sync with Odoo fields by " "default; a development is required to link these fields." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 msgid "Item specifics listed on an eBay product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:75 msgid "" "*Sandbox* and *Production* are terms that are used to categorize the eBay " "environments as either still in development/testing (*Sandbox*) or for use " "in the real instance of the database with real customer information/dataset " "(*Production*). It is recommended to start first in the *Sandbox* to test, " "and then following the processes below, create a *Production* instance." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:81 msgid "" "eBay's sandbox environment can be accessed by navigating to `eBay's sandbox " "portal `_ at `https://sandbox.ebay.com/`. eBay's " "production environment can be accessed by navigating to `eBay.com portal " "`_ or `https://www.ebay.com/`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:87 msgid "" "The environment selection **must** remain the same for all environment " "settings on eBay and on Odoo throughout this setup." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:91 msgid "eBay actions available on Odoo" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:93 msgid "" "The following are built-in actions in Odoo that add or update eBay listings:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:95 msgid "" "**List**/ **Link**: generate a new eBay listing with an Odoo product by " "clicking :guilabel:`List Item on eBay` or :guilabel:`Link With Existing eBay" " Listing`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:97 msgid "" ":guilabel:`Revise item` button: after making changes to an eBay listing in " "Odoo, save the record, and then click the :guilabel:`Revise Item` in Odoo to" " update the eBay listing." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:99 msgid "" "**Relist**: if an item's listing was ended early or :guilabel:`auto-relist` " "was not selected, a user can relist the item from Odoo. The start date will " "reset." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:101 msgid "" ":guilabel:`End item's listing` button: end a listing on eBay directly from " "Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:102 msgid "" "**Unlink product listings**: users can unlink a product from the eBay " "listing; the listing will stay intact on eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:106 msgid "Setup required on Odoo prior to eBay setup" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:108 msgid "" "To link eBay with Odoo, install the eBay module by navigating to the Odoo " "dashboard and clicking into the :guilabel:`Apps` application. Search the " "term `eBay` and install the `eBay Connector` module." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:112 msgid "The following items must be configured before eBay is set up:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:114 msgid "" "In Odoo, create and configure products that are intended to be listed in " "eBay. eBay does not import new products into Odoo. All products must first " "be created in Odoo, and then linked to listings." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 msgid "" "Odoo does not allow multiple eBay listings to be linked per product in Odoo." " If the company sells the same product for multiple listings, follow these " "instructions:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:121 msgid "" "Set up one *base* product (noted in the :guilabel:`Component` field of the " ":abbr:`BoM (Bill of Materials)`) from which all eBay listings will pull " "from. This will be a storable product so stock can be kept. Highlighted in " "green below, this product will be included in the kit on each subsequent " "“linked” product below." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:126 msgid "" "Set up 2+ *linked* products (noted in the :guilabel:`Product` field of the " ":abbr:`BoM (Bill of Materials)`, one for each eBay listing. The product type" " will be determined by the company's accounting settings, as explained in " "the Documentation. Highlighted in yellow below, each product should " "have a :guilabel:`BoM type` equal to :guilabel:`Kit` and have the base " "product as a :guilabel:`Component` of the kit. When this linked eBay product" " is sold, the delivery order created will have the base product listed in " "lieu of the linked product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:0 msgid "Setting up bill of materials with base product and linked products." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:138 msgid "" ":doc:`../../../inventory_and_mrp/manufacturing/basic_setup/bill_configuration/`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:140 msgid "" "eBay does not automatically create invoices for eBay orders that get pushed " "into Odoo. Set invoicing policy on eBay products: invoicing policy will " "dictate when the product can be invoiced. Since most eBay users collect " "payment before the product is shipped, “invoice on ordered” will allow users" " to mass create invoices for eBay orders every day." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:144 msgid "" "Set the :guilabel:`Outgoing Shipments` route for the warehouse to " ":guilabel:`Deliver goods directly (1 step)`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:148 msgid "" "When the :guilabel:`Outgoing Shipments` route is set to two or three steps, " "a known bug occurs: eBay wrongly marks orders as delivered when the pick " "operation in Odoo is confirmed. The expected behavior is to mark orders as " "delivered **after** the *delivery order* is confirmed. This mislabeling " "prevents tracking numbers in eBay from being imported onto the delivery " "order." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:152 msgid "" "If the Accounting/Invoicing apps are installed, practice registering payment" " and reconciling invoices created from eBay orders with incoming eBay money." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:156 msgid ":doc:`../../..//finance/accounting/bank/reconciliation`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:158 msgid "" "Generate a marketplace account deletion/closure notification token. To " "begin, navigate to :menuselection:`Sales app --> Configuration --> " "Settings`. Under the :guilabel:`eBay` heading, change the mode to " ":guilabel:`Production`, and input random text values for the " ":guilabel:`Production Cert Key`. Then click the :guilabel:`Generate Token` " "button under the :guilabel:`eBay Marketplace Account Deletion/Closure " "Notifications` section. This token will be used during the setup on eBay for" " the deletion/closure notifications configuration." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 msgid "Generate a verification token in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:170 msgid "Set up on eBay" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:173 msgid "Set up eBay developer account" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:175 msgid "" "To start, create an eBay developer account via `eBay's developer portal " "`_. This site requires a different login and" " password than the eBay account, though the same email address can be used " "to register. The verification to create a developer account is around 24 " "hours." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:181 msgid "Set up eBay keyset" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:183 msgid "" "Once the eBay developer account is created, set up an application on `eBay's" " developer portal `_. Next, navigate to the " ":guilabel:`Hi [username]` heading at top right of screen, then from the " "drop-down menu options, click :guilabel:`Application Keysets`. Doing so " "opens a pop-up that prompts the user to :guilabel:`Enter Application Title` " "(up to fifty characters), and choose a development environment " "(:guilabel:`Sandbox` or :guilabel:`Production`). These two fields generate " "first keyset. This application title is not saved until the keyset is " "generated. Click on :guilabel:`Create a keyset` to generate the keyset." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:192 msgid "" "The newly created *production keyset* is disabled by default. Activate it by" " subscribing to the eBay Marketplace 'account deletion or closure " "notifications' or by applying to eBay for an exemption. Once enabled, the " "database can make 5000 calls per day using this keyset." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 msgid "Disabled keyset present after creating a keyset." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:201 msgid "Configure account deletion / notification settings (Production)" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:203 msgid "" "To configure notifications or delete the database on a production " "environment, navigate to the `eBay developer portal " "`_. Configure the account " "deletion/notification settings in eBay by navigating to the `Hi [username]` " "at top right of screen, then :guilabel:`Application Keysets`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:208 msgid "" "Next, click the :guilabel:`marketplace deletion/account closure " "notification` option under the :guilabel:`Production` keyset column. Enter " "an email under :guilabel:`Email to notify if marketplace account deletion " "notification endpoint is down`. Click :guilabel:`Save` to enable the email." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:212 msgid "" "Following this action, enter the :guilabel:`Marketplace account deletion " "notification endpoint` URL provided by Odoo. This HTTPs endpoint is found in" " Odoo by navigating to :menuselection:`Sales app --> Configuration --> " "Settings`, in the :guilabel:`eBay Marketplace Account Deletion/Closure " "Notifications` field." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:217 msgid "" "Clicking the :guilabel:`Generate Token` button in Odoo below this field " "creates a verification token for the eBay production environment. In Odoo, " ":guilabel:`Copy` the newly created token and navigate to eBay to fill in the" " :guilabel:`Verification token` field. Click :guilabel:`Save` to enable the " ":guilabel:`Event Notification Delivery Method`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 msgid "Configuring account deletion / notification settings in eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:226 msgid "" "After completing the above fields, click :guilabel:`Send Test Notification` " "to test the new notifications. Proceed to the next step when the green check" " mark appears. Revisit the above settings if the test post is not as " "expected." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:230 msgid "" "After configuring notification settings, go back to the " ":menuselection:`Application Keys` page to generate production keysets." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:234 msgid "Creating the keyset" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:236 msgid "" "A successful setup of the notifications enables the ability to create " "Production Keysets which are needed in the remainder of the Odoo " "configuration. Navigate back to the :menuselection:`Application Keys` page " "generate a production keyset." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:240 msgid "" "The administrator is prompted to :menuselection:`Confirm the Primary " "Contact`. Enter or confirm the account owner (the person legally responsible" " for the eBay API License Agreement). Fill out :guilabel:`First Name`, " ":guilabel:`Last Name`, :guilabel:`Email`, :guilabel:`Phone`. Then, select " "either the :guilabel:`Individual` or :guilabel:`Business` options." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:246 msgid "" "The provided email address or phone number does **not** have to match the " "account's. eBay uses this information to contacting the business or " "individual in case of issues with user tokens. Additional contacts can be " "added from the :guilabel:`Profile & Contacts` page on eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:250 msgid "" "Click on :guilabel:`Continue to Create Keys` to confirm the primary contact." " The :guilabel:`Application Keys` populates in a new screen and an email is " "also sent to the developer account. An :guilabel:`App ID (Client ID)`, " ":guilabel:`Dev ID`, and :guilabel:`Cert ID (Client Secret)` all populate." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 msgid "Application keys are populated after creating the app in eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:259 msgid "" "Copy these values down as they will be input into Odoo later in the process." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:262 msgid "Create eBay user token" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:264 msgid "" "Now, create a *user token* in eBay by navigating to the `Hi [username]` at " "top right of screen, then :guilabel:`User Access Tokens`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 msgid "Generate user token s on the eBay developer console." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:271 msgid "" "Select the correct :guilabel:`Environment`: :guilabel:`Sandbox` for testing " "or :guilabel:`Production` for the live database. Maintain the same selection" " for all environment settings on both eBay and Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:275 msgid "Next, select the radio button labeled :guilabel:`Auth'n'Auth`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:277 msgid "" "Choose :guilabel:`Sign in to Production` or :guilabel:`Sign in to Sandbox` " "to get a user token in the chosen environment. This button varies based on " "the selection made above for either :guilabel:`Sandbox` or " ":guilabel:`Production`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:281 msgid "" "Doing so triggers a a pop-up window to :guilabel:`Confirm your Legal " "Address`. Complete the required fields, which are :guilabel:`First Name`, " ":guilabel:`Last Name`, :guilabel:`Primary Email`, :guilabel:`Legal Address`," " and :guilabel:`Account Type`. For :guilabel:`Account Type`, select either " ":guilabel:`Individual` or :guilabel:`Business`. To complete the " "confirmation, click :guilabel:`Sign into eBay to get a Token`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:288 msgid "" "eBay will contact this individual or business should there be any issues " "with the application keys. Other contacts can be added on the " ":menuselection:`Profile & Contacts` eBay page." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:291 msgid "" "The administrator will be redirected to either a sandbox or production sign-" "in page for eBay. This login is different than the eBay developer's console," " it is the eBay account where the items will be sold on. This email and/or " "login can differ from the eBay developer account." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:295 msgid "" "Enter the :guilabel:`Email` or :guilabel:`Username` for the eBay account and" " sign into the eBay account." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:299 msgid "" "Should an additional user be needed for the sandbox simulation, a test user " "needs to be created. Visit `eBay's Register for Sandbox form " "`_. Detailed instructions can " "be found on eBay's help pages: `Create a test Sandbox user " "`_." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:305 msgid "Grant application access" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:307 msgid "" "After signing into the production or sandbox environment, eBay presents the " "administrator with an *agreement* to grant access to the user's eBay data." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:310 msgid "" "Clicking :guilabel:`Agree` allows eBay to link the eBay account with the " "*application programming interface* (API). This agreement can be changed at " "any time by visiting eBay's account preferences." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:314 msgid "" "eBay has a timed sequence between signing in and agreeing to the terms for " "the :abbr:`API (Application Programming Interface)` linkage to the account. " "Once complete a :guilabel:`User Token` will populate on the " ":menuselection:`User Tokens` page." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:318 msgid "" "A :guilabel:`User Token` will populate on the screen. Make sure to copy this" " token down as it will be used in the next steps along with the " ":guilabel:`Application Keyset`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 msgid "" "Generated user token and API explorer link on the eBay developer console." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:326 msgid "" "Signing in to the eBay account is necessary to create to the token. The eBay" " developer can also revoke the token by clicking on the :guilabel:`Revoke a " "Token` link." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:330 msgid "API explorer" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:332 msgid "" "Now that the :guilabel:`Application Keyset` and :guilabel:`User Token` have " "been created, a test can be executed via the `API Explorer " "`_ to " "ensure that the :abbr:`API (Application Programming Interface)` is " "configured correctly. This test will execute a simple search using the " ":abbr:`API (Application Programming Interface)`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:338 msgid "" "To begin the :abbr:`API (Application Programming Interface)` test, click on " ":guilabel:`Get OAuth Application Token`. This will populate the key into the" " :guilabel:`Token` field." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:341 msgid "" "A basic search function is set to execute. Click on :guilabel:`Execute` to " "complete the test. A successful test will respond with a :guilabel:`Call " "Response` of `200 OK` with a corresponding :guilabel:`Time`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:346 msgid "Entering credentials into Odoo" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:348 msgid "" "The previously copied :guilabel:`User Token` and :guilabel:`Application " "Keyset` are now ready to be entered into the Odoo database." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:351 msgid "" "Navigate back the eBay settings in Odoo (:menuselection:`Sales app --> " "Configuration --> Settings --> eBay`) and paste the following credentials " "from eBay into the corresponding fields in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:358 msgid "Platform" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:359 msgid "Dev Key/ID" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:360 msgid "Token" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:361 msgid "App Key/ID" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:362 msgid "Cert Key/ID" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:363 msgid "eBay" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:364 msgid "Dev ID" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:365 msgid "User Token" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:366 msgid "App ID (Client ID)" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:367 msgid "Cert ID (Client Secret)" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:368 #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:102 msgid "Odoo" msgstr "Odoo" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:369 msgid "Developer Key" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:370 msgid "Production/Sandbox Token" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:371 msgid "Production/Sandbox App Key" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:372 msgid "Production/Sandbox Cert Key" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:375 msgid "" "The :guilabel:`Application Keyset` can be accessed by going to `eBay's " "developer portal `_ and navigate to the `Hi " "[username]` at top right of screen, then click on :guilabel:`Application " "Keysets`. Get to the *User Token* in eBay by navigating to the `Hi " "[username]` at top right of screen, then :guilabel:`User Access Tokens` and " "click on :guilabel:`Sign in to Sandbox`. The :guilabel:`User Token` can also" " be accessed by clicking on :guilabel:`User Tokens` from the " ":menuselection:`Application Keys` page." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:382 msgid "" "Confirm that the setup is correct by saving the credentials in Odoo. Once " "the initial setup is complete, a new menu tab in products will appear called" " `eBay` with the option to :guilabel:`Sell on eBay`. See the :doc:`manage` " "documentation on how to list products." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:387 msgid "" "Sync product categories by clicking :guilabel:`Product Categories`. After " "syncing, a new menu item, `eBay Category`, appears available for products to" " be configured with. These eBay categories are imported from the Odoo " "database and are available when listing an item on eBay through Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:393 msgid "" "If Product Categories beyond four paths are required, users will need to " "manually add those paths. This has historically been done by getting a list " "of all product categories beyond four paths, manually importing them into " "the Product Category model in Odoo, and then linking them individually to " "the product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:399 msgid "Now that the setup is complete, proceed to either:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:401 msgid ":doc:`Create listings `" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:402 msgid ":doc:`Link existing listings `" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:3 msgid "Troubleshooting eBay connector" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:13 msgid "Accept account deletion notifications" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:15 msgid "" "Since September 2021, **eBay requires supporting customer account " "deletion/closure notifications**. As such, when eBay receives an account " "request for deletion, all eBay partners must confirm the reception of the " "request and take further action if necessary." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:19 msgid "" "Odoo has a notification endpoint to receive those notifications, confirm the" " reception of the request, and handle the first set of actions to anonymize " "the account details in *Contacts* and remove the customer's access to the " "portal." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:24 msgid "" "Make sure to correctly :ref:`set up the subscription to the marketplace " "account deletion notifications ` as eBay may temporarily disable the related eBay account " "until the subscription is completed." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:29 msgid "Verify the installation of Odoo is up to date" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:31 msgid "" "In order to activate the endpoint, the module *eBay Connector - Account " "Deletion* must be installed. If the Odoo database was first created after " "September 2021, the module is installed automatically and the administrator " "can proceed to the :ref:`next step `." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:36 msgid "Update Odoo to the latest release" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:38 msgid "" "The notification endpoint is made available through a new Odoo module; to be" " able to install it, the administrator must make sure that the Odoo source " "code is up-to-date." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:41 msgid "" "If the company uses Odoo on Odoo.com or Odoo.sh platform, the code is " "already up-to-date, so proceed to the next step." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:43 msgid "" "If the company uses Odoo with an on-premise setup or through a partner, then" " the administrator must update the installation as detailed in :doc:`this " "documentation page ` or by contacting an " "integrating partner." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:48 msgid "Update the list of available modules" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:50 msgid "" "New modules must be *discovered* by the Odoo instance to be available in the" " :menuselection:`Apps` menu." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:53 msgid "" "To do so, activate the :ref:`developer mode `, and go to " ":menuselection:`Apps -> Update Apps List`. A wizard will ask for " "confirmation." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:57 msgid "Install the eBay Connector - Account Deletion update" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:60 msgid "" "**Never** install new modules in the production database without testing " "them in a duplicate or staging environment. For Odoo.com customers, a " "duplicate database can be created from the database management page. For " "Odoo.sh users, the administrator should use a staging or duplicate database." " For on-premise users, the administrator should use a staging environment - " "contact the integrating partner for more information regarding how to test a" " new module in a particular setup." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:67 msgid "" "To install the module, go to the :menuselection:`Apps` menu, remove the " "`Apps` search facet and search for `eBay`. If the module *eBay Connector - " "Account Deletion* is present and marked as installed, the Odoo database is " "already up-to-date and the administrator can proceed with the next step. If " "it is not yet installed, install it now." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:75 msgid "Retrieve endpoint details from Odoo" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:77 msgid "" "The endpoint details can be found in :menuselection:`Sales --> Configuration" " --> Settings --> eBay`. First, input random text values for the " ":guilabel:`Production App Key` and for the :guilabel:`Production Cert Key`. " "Click on :guilabel:`Generate Token` to retrieve the :guilabel:`Verification " "Token`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:89 msgid "Subscribe to account deletion notifications" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:91 msgid "" "Navigate to the `eBay developer portal `_. " "Configure the account deletion/notification settings in eBay by navigating " "to the `Hi [username]` at the top right of screen, then go to " ":guilabel:`Alerts & Notifications`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 msgid "Overview of the Alerts & Notifications dashboard of eBay" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:99 msgid "" "To subscribe to deletion/closure notifications, eBay needs a few details:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:101 msgid "" "An *email address* to send notifications to if the endpoint is unreachable." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:102 msgid "The *endpoint details*:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:104 msgid "The URL to Odoo's account deletion notification endpoint" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:105 msgid "A verification token" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 msgid "Dedicated fields to enter the endpoint details" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:112 msgid "" "The administrator can edit the last two fields once the email address field " "is filled out." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:115 msgid "Verify the connectivity with the endpoint" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:117 msgid "" "After setting the retrieved endpoint details in eBay's dashboard, consider " "testing the connectivity with the :guilabel:`Send Test Notification` button." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:120 msgid "" "The following confirmation message should be received: \"A test notification" " was sent successfully!\"" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 msgid "Button to send test notification" msgstr "" #: ../../content/applications/sales/sales/invoicing.rst:5 msgid "Invoicing Method" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 msgid "Down payments" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:5 msgid "" "A down payment is a partial payment made by the buyer when a sales contract " "is concluded. This implies both parties' (seller and buyer) full commitment " "to honor the contract." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:8 msgid "" "With a down payment, the buyer pays a portion of the total amount owed while" " agreeing to pay the remaining amount at a later date. In turn, the seller " "provides goods or services to the buyer after accepting the down payment, " "trusting that the remaining amount will be paid later on." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 msgid "Create invoices" msgstr "Ustvari račune" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 msgid "" "When a sales order is confirmed, the option to create an invoice becomes " "available, via the :guilabel:`Create Invoice` button, located in the upper-" "left corner of the sales order form. When clicked, a :guilabel:`Create " "invoices` pop-up appears." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "Create invoices pop-up form that appears in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:24 msgid "" "Invoices are automatically created as drafts, so they can be reviewed before" " validation." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:26 msgid "" "On the :guilabel:`Create invoices` pop-up, there are 3 options to choose " "from in the :guilabel:`Create Invoice` field:" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 msgid ":guilabel:`Regular invoice`" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:42 msgid ":guilabel:`Down payment (percentage)`" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:31 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:43 msgid ":guilabel:`Down payment (fixed amount)`" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 msgid "" "If :guilabel:`Regular Invoice` is selected, the other fields disappear, as " "they only pertain to down payment configurations." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 msgid "Initial down payment request" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:40 msgid "" "On the :guilabel:`Create invoices` pop-up form, the down payment options " "are:" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:45 msgid "" "Once the desired down payment option is selected in the :guilabel:`Create " "Invoice` field on the pop-up form, designate the desired amount, either as a" " percentage or a fixed amount, in the :guilabel:`Down Payment Amount` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:49 msgid "" "Then, select the appropriate income account for the invoice in the " ":guilabel:`Income Account` field. Next, select a tax amount, if necessary, " "in the :guilabel:`Customer Taxes` drop-down field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "A create invoices pop-up form with down payment fields filled in with " "information." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 msgid "" "Once all fields are filled in with the desired information, click the " ":guilabel:`Create Draft Invoice` button. Upon clicking this button, Odoo " "reveals the :guilabel:`Customer Invoice Draft`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:59 msgid "" "In the :guilabel:`Invoice Lines` tab of the :guilabel:`Customer Invoice " "Draft`, the down payment that was just configured in the :guilabel:`Create " "invoices` pop-up form appears as a :guilabel:`Product`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "Down payment as a product in the invoice lines tab of a customer invoice " "draft in Odoo." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:68 msgid "" "When the :guilabel:`Down payment` product in the :guilabel:`Invoice Lines` " "tab is clicked, Odoo reveals the product form for the down payment." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:71 msgid "" "By default, the :guilabel:`Product Type` of down payment products generated " "for invoices are set as :guilabel:`Service`, with the :guilabel:`Invoicing " "Policy` set to :guilabel:`Prepaid/Fixed Price`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "Down payment product form with service product type and invoicing policy " "field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:79 msgid "This product can be edited/modified at any time." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:82 msgid "" "If :guilabel:`Based on Delivered Quantity (Manual)` is chosen as the " ":guilabel:`Invoicing Policy`, an invoice will **not** be able to be created." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:88 msgid "Example: request 50% down payment" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:91 msgid "" "The following example involves a 50% amount down payment on a product " "(:guilabel:`Cabinet with Doors`) with :guilabel:`Ordered quantities` as the " ":guilabel:`Invoicing Policy`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:0 msgid "Cabinet with doors product form showcasing various details and fields." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:335 #: ../../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 msgid ":doc:`invoicing_policy`" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:101 msgid "" "First, navigate to :menuselection:`Sales app --> New`, and add a " ":guilabel:`Customer` to the quotation." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:104 msgid "" "Then, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab, " "and select the :guilabel:`Cabinet with Doors` product." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:107 msgid "" "When the order is confirmed (via the :guilabel:`Confirm` button), the " "quotation turns into a sales order. Once this occurs, create and view the " "invoice by clicking :guilabel:`Create Invoice`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "Cabinet with doors sales order that's been confirmed in the Odoo Sales " "application." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:114 msgid "" "Next, on the :guilabel:`Create invoices` pop-up window that appears, select " ":guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down " "Payment Amount` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:118 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:264 msgid "" "The :guilabel:`Income Account` and :guilabel:`Customer Taxes` fields are " "*not* required fields, and they will *not* appear if they've already been " "preconfigured in previous down payment requests." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:122 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:268 msgid "" "For more information, check out the documentation on :ref:`customer taxes " "modification on down payments ` and :ref:`income account modification on down payments " "`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 msgid "" "Lastly, click :guilabel:`Create Draft Invoice` to create and view the " "invoice draft." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:128 msgid "" "Clicking :guilabel:`Create Draft Invoice` reveals the draft invoice, which " "includes the down payment as a :guilabel:`Product` in the :guilabel:`Invoice" " Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:131 msgid "" "From there, the invoice can be confirmed and posted by clicking " ":guilabel:`Confirm`. Confirming the invoice changes the status from " ":guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of " "buttons at the top of the page." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "A sample draft invoice with down payment mentioned in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:139 msgid "" "From those buttons, the payment can be registered by clicking " ":guilabel:`Register Payment`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "Showcase of the Register Payment button on a confirmed customer invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:145 msgid "" "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-" "populated with the necessary information. Confirm the information provided " "is correct, and make any necessary adjustments. When ready, click the " ":guilabel:`Create Payment` button." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "Showcase of the Register Payment pop-up window with create payment button." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:153 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:291 msgid "" "After clicking :guilabel:`Create Payment`, Odoo reveals the customer " "invoice, now with a green :guilabel:`In Payment` banner in the upper-right " "corner." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "Customer Invoice with a green In Payment banner located in the upper-right " "corner." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:160 msgid "" "Now, when the customer wants to pay the remaining amount of the order, " "another invoice must be created. To do that, return to the sales order, via " "the breadcrumb links." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:163 msgid "" "Back on the sales order, a new :guilabel:`Down Payments` section is present " "in the :guilabel:`Order Lines` tab, along with the down payment that was " "just invoiced and posted." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "The down payments section in the order lines tab of a sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 msgid "Next, click the :guilabel:`Create Invoice` button." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:172 msgid "" "On the :guilabel:`Create invoices` pop-up window that appears, there are two" " new fields: :guilabel:`Already invoiced` and :guilabel:`Amount to invoice`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "The deduct down payment option on the create invoices pop up in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:179 msgid "" "If the remaining amount is ready to be paid, select the :guilabel:`Regular " "Invoice` option. Odoo will create an invoice for the exact amount needed to " "complete the total payment, as indicated in the :guilabel:`Amount to " "invoice` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:183 msgid "Once ready, click :guilabel:`Create Draft Invoice`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:185 msgid "" "Doing so reveals another :guilabel:`Customer Invoice Draft` page, listing " "*all* the invoices for that specific sales order in the :guilabel:`Invoice " "Lines` tab. Each invoice line item displays all the necessary information " "related to each invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:189 msgid "" "To complete the flow, click :guilabel:`Confirm`, which changes the status of" " the invoice from :guilabel:`Draft` to :guilabel:`Posted`. Then, click " ":guilabel:`Register Payment`." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:192 msgid "" "Once again, the :guilabel:`Register Payment` appears, with all fields auto-" "populated with the necessary information, including the remaining amount " "left to be paid on the order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "The second register payment pop-up form in Odoo sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:199 msgid "" "After confirming that information, click :guilabel:`Create Payment`. Doing " "so reveals the final :guilabel:`Customer Invoice` with a green :guilabel:`In" " Payment` banner in the upper-right corner. Also, both down payments are " "present in the :guilabel:`Invoice Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "The second down payment invoice with in payment banner in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:207 msgid "At this point, the flow is now complete." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:210 msgid "" "This flow is also possible with the :guilabel:`Fixed amount` down payment " "option." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:213 msgid "" "If a down payment is used with a product that has a :guilabel:`Delivered " "quantities` invoicing policy, and the cost of the product *exceeds* the 50% " "down payment (as in most cases), a regular invoice is created." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:217 msgid "" "However, for products that cost *less* than the 50% down payment, the down " "payments will **not** be able to be deducted when it comes time to invoice " "the customer." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:220 msgid "" "This is because the product(s) would have to be delivered *before* creating " "the final invoice due to Odoo not allowing negative totals for invoices." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:223 msgid "" "If nothing has been delivered, a :guilabel:`Credit Note` is created, which " "cancels the draft invoice that was created after the down payment." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:226 msgid "" "To utilize the :guilabel:`Credit Note` option, the *Inventory* application " "must be installed, in order to confirm the delivery. Otherwise, the " "delivered quantity can be entered manually directly on the sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:233 msgid "Example: request 100% down payment" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:235 msgid "" "The process of requesting a 100% down payment is similar to the process of " "setting up a :ref:`50% down payment `, but with fewer steps." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:239 msgid "" "A 100% down payment is **not** the same as a full payment of the sales " "order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:241 msgid "" "A sales order paid through the regular invoice process will not allow any " "additional invoices to be generated, and **will not** display the *Create " "Invoice* button on the Sales Order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:244 msgid "" "Following this example **will** cause the *Create Invoice* button to be " "displayed on the Sales Order. This is because Odoo expects another invoice " "to be created after the down payment to complete payment of the sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:248 msgid "The *Solar Panel Installation* product is being used in this example." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:250 msgid "" "To configure a 100% down payment, begin by navigating to " ":menuselection:`Sales app --> New`, and add a :guilabel:`Customer` to the " "quote." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:253 msgid "" "Next, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab, " "and select the `Solar Panel Installation` product." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:256 msgid "" "Upon clicking the :guilabel:`Confirm` button, the quotation turns into a " "sales order. At that point, an invoice can now be created by clicking " ":guilabel:`Create Invoice` in the top-left corner." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:259 msgid "" "On the :guilabel:`Create invoices` pop-up window that appears, select " ":guilabel:`Down payment (percentage)`, and type `100` in the :guilabel:`Down" " Payment Amount` field. Then, if desired, select an :guilabel:`Income " "Account` and :guilabel:`Customer Taxes` in their respective fields." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" "The Down payment (percentage) option selected with 100% set as the Down " "Payment." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:276 msgid "" "Next, click :guilabel:`Create Draft Invoice` to create an invoice draft. " "This will also bring the draft invoice into view, which includes the " ":guilabel:`Down payment` as a :guilabel:`Product` in the :guilabel:`Invoice " "Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:280 msgid "" "The invoice can now be confirmed and posted by clicking :guilabel:`Confirm`." " Confirming the invoice changes the status from :guilabel:`Draft` to " ":guilabel:`Posted`. It also reveals a new series of buttons at the top of " "the page." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:284 msgid "" "The payment can be registered by clicking the :guilabel:`Register Payment` " "button." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:286 msgid "" "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-" "populated with the necessary information. Confirm the information provided " "is correct and make any necessary adjustments. When ready, click the " ":guilabel:`Create Payment` button." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:298 msgid "" "The process is now complete, and the 100% down payment has been successfully" " applied." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:303 msgid "Customer taxes modification on down payments" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:305 msgid "" "To adjust the income account and customer taxes attached to a down payment, " "navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> " "Products --> Products`), search for the `Down Payment` product in the search" " bar, and select it to reveal the product detail page." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:309 msgid "" "On the :guilabel:`Down Payment` product page, in the :guilabel:`General " "Information` tab, the customer taxes can be modified in the " ":guilabel:`Customer Taxes` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "How to modify the income account link to down payments." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:319 msgid "Income account modification on down payments" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:321 msgid "" "To change or adjust the income account attached to the :guilabel:`Down " "Payment` product page, the *Accounting* app **must** be installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:324 msgid "" "With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes " "available on the product page. That tab will **not** be accessible without " "the *Accounting* app installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:327 msgid "" "In the :guilabel:`Accounting` tab, the income account can be changed in the " ":guilabel:`Income Account` field, located in the :guilabel:`Receivables` " "section." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:3 msgid "Reinvoice expenses to customers" msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:5 msgid "" "While working on a project for a client, employees often have to spend their" " own money on various expenses related to the project." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:8 msgid "" "For example, an employee may need to use their own money to pay for a hotel," " while they provide an on-site service for a client. As a company, this " "expense should be reinvoiced to the customer. With Odoo, these kinds of " "expenses can quickly be reinvoiced to the customer related to the project." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:13 msgid "Expenses application" msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:15 msgid "" "To be able to reinvoice a customer for an expense, the *Expenses* " "application **must** be installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:17 msgid "" "To install the *Expenses* application, navigate to :menuselection:`main Odoo" " dashboard --> Apps`, and click :guilabel:`Install` on the *Expenses* " "application block. When clicked, Odoo installs the application, refreshes " "the page, and returns to the main Odoo dashboard." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:22 msgid "Add expenses to sales orders" msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:24 msgid "" "To begin, have a sales order confirmed in the *Sales* app to which a " "reinvoiced expense can be added. Or, create a new sales order from scratch. " "To do that, navigate to the :menuselection:`Sales app --> New`. Doing so " "reveals a blank quotation form." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:28 msgid "" "Then, add a :guilabel:`Customer`, and add a product to the :guilabel:`Order " "Lines` tab, by clicking :guilabel:`Add a product`. Next, select a product " "from the drop-down menu." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:31 msgid "Lastly, click :guilabel:`Confirm` to confirm the sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "" "This is how a confirmed sales order looks in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:37 msgid "With the sales order confirmed, it's time to create an expense." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:39 msgid "" "To do that, navigate to the *Expenses* application, by going to " ":menuselection:`main Odoo dashboard --> Expenses`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:42 msgid "" "Then, from the *Expenses* dashboard, click :guilabel:`New` to reveal a blank" " expenses form." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "A blank expenses form in the Odoo Expenses application." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:48 msgid "" "On the expenses form, add a :guilabel:`Description` to easily reference the " "expense." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:50 msgid "" "Then, in the :guilabel:`Category` field, select one of the following options" " from the drop-down menu:" msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:53 msgid "" ":guilabel:`Communication`: any form of communication related to a " "project/order." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:54 msgid "" ":guilabel:`Others`: expense that doesn't fit into any other categories." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:55 msgid ":guilabel:`Meals`: any form of meal costs related to a project/order." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:56 msgid ":guilabel:`Gifts`: any form of gift costs related to a project/order." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:57 msgid "" ":guilabel:`Mileage`: any form of mileage (gas) costs related to " "project/order." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:58 msgid "" ":guilabel:`Travel \\& Accommodation`: any travel or accommodation costs " "related to a project/order." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:61 msgid "" "New expense categories can be created from an expense form, by clicking the " ":guilabel:`Category` field drop-down menu, selecting :guilabel:`View All`, " "and clicking :guilabel:`New` from the :guilabel:`Search:Category` pop-up " "window." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:0 msgid "" "The Search:Category expenses pop-up window from a blank expenses form in " "Odoo Expenses." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:69 msgid "" "For this sample workflow, which will reinvoice a customer for a brief hotel " "stay, the :guilabel:`Category` for this example is :guilabel:`[TRANS \\& " "ACC] Travel \\& Accommodation`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:73 msgid "" "The following example requires the *Sales*, *Accounting*, and *Expense* apps" " to view/modify all the fields mentioned during the workflow." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:76 msgid "" "Beneath the :guilabel:`Category` field, enter in the amount to be expensed " "in the :guilabel:`Total` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:79 msgid "" "Next, designate if there are any :guilabel:`Included taxes` in the " ":guilabel:`Total`. If a preconfigured tax amount is selected from the " ":guilabel:`Included taxes` field, Odoo auto-calculates the taxed amount, " "based on the amount entered in the :guilabel:`Total` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:83 msgid "" "Then, choose which :guilabel:`Employee` was responsible for the expense, and" " choose an option in the :guilabel:`Paid By` field: :guilabel:`Employee (to " "reimburse)` or :guilabel:`Company`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:86 msgid "" "In this case, our employee paid for the hotel with their own money, so the " ":guilabel:`Employee (to reimburse)` option is chosen." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:89 msgid "" "On the right-hand side of the expenses form, the option to add a " ":guilabel:`Bill Reference` is available. Beneath that, the auto-populated " ":guilabel:`Expense Date` and :guilabel:`Account` fields are available." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:94 msgid "" "The :guilabel:`Expense Date` and :guilabel:`Account` field can be modified, " "if needed." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:96 msgid "" "Next, in the :guilabel:`Customer to Reinvoice` field, click the blank field " "to reveal a drop-down menu. From this drop-down menu, select the appropriate" " sales order to which this expense should be attached. This field **must** " "be filled, in order to reinvoice a customer for an expense." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:100 msgid "" "Lastly, the option to modify the :guilabel:`Analytic Distribution` and " ":guilabel:`Company` fields are available. These fields are *not* required to" " complete a reinvoiced expense to a customer, but are available to modify, " "if needed." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:104 msgid "" "Also, at the bottom of the expense form, there is a :guilabel:`Notes...` " "section, wherein any notes related to this expense can be added, if needed." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "A filled out expenses form in the Odoo Expenses application." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:111 msgid "" "At the top of the expense form, there are buttons to :guilabel:`Attach " "Receipt`, :guilabel:`Create Report`, and :guilabel:`Split Expense`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:114 msgid "" "If there is a physical or digital receipt that should be attached to the " "expense, click :guilabel:`Attach Receipt`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:117 msgid "" "If the cost of this expense needs to be split, click :guilabel:`Split " "Expense`. This feature can be used for a number of reasons (spitting expense" " with another employee, to accommodate different tax rates, etc.)." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:121 msgid "" "If neither of these options are necessary, click :guilabel:`Create Report` " "to lock in the expense report that was just configured." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:124 msgid "" "Doing so reveals an :guilabel:`Expense Report Summary` for the new expense." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "An expense report summary in the Odoo Expenses application." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:130 msgid "" "Here, once the details related to the expense have been confirmed, click " ":guilabel:`Submit to Manager`. This sends the expense report to the " "approving manager, who will review the expense." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:133 msgid "" "The manager in charge of reviewing and approving the expense will inspect " "the details related to the expense, and if there are no issues, they will " "click the :guilabel:`Approve` button — which *only* appears on the manager's" " view of the :guilabel:`Expense Report Summary` that's been submitted to the" " manager by the employee." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "" "An expense report summary that a manager will approve with an Approve " "button." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:142 msgid "" "Once approved, the buttons at the top of the :guilabel:`Expense Report " "Summary` change once again. At this point, the buttons at the top of the " ":guilabel:`Expense Report Summary` are: :guilabel:`Post Journal Entries`, " ":guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, and :guilabel:`Reset" " to Draft`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "" "An expense report summary with post journal entries button at the top of the" " form." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:151 msgid "" "When the manager is satisfied with the :guilabel:`Expense Report Summary`, " "they'll click :guilabel:`Post Journal Entries`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:154 msgid "" "Upon clicking :guilabel:`Post Journal Entries`, that button disappears, and " "the :guilabel:`Analytic Distribution` column in the :guilabel:`Expense` tab " "is filled with the sales order that was initially configured to the expense " "in the :guilabel:`Customer to Reinvoice` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:159 msgid "" "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: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 "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "" "A sales order with the configured expense ready to be invoiced in the Order " "Lines tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst: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 "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "" "A create invoices pop-up window that appears when the Create Invoice is " "clicked." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst: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:213 msgid "" "Doing so reveals a :guilabel:`Customer Invoice Draft` showing *only* the " "expense in the :guilabel:`Invoice Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "" "A customer invoice draft with the expense in the Invoice Lines tab of the " "form." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst: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: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: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:231 msgid "" "Back on the :guilabel:`Customer Invoice`, click the :guilabel:`Register " "Payment` button when the customer pays for the invoiced expense." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "" "A customer invoice with the register payment button ready to be clicked." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst: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 "" #: ../../content/applications/sales/sales/invoicing/expense.rst-1 #: ../../content/applications/sales/sales/invoicing/expense.rst-1 msgid "A register payment pop-up window on a customer invoice in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst: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:256 #: ../../content/applications/sales/sales/invoicing/milestone.rst:236 msgid ":doc:`time_materials`" msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:257 msgid ":doc:`milestone`" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:3 msgid "Invoice based on delivered or ordered quantities" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:5 msgid "" "Different business policies might require different options for invoicing:" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:7 msgid "" "The *Invoice what is ordered* rule is used as the default mode in Odoo " "*Sales*, which means customers are invoiced once the sales order is " "confirmed." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:9 msgid "" "The *Invoice what is delivered* rule invoices customers once the delivery is" " done. This rule is often used for businesses that sell materials, liquids, " "or food in large quantities. In these cases, the ordered quantity may differ" " slightly from the delivered quantity, making it preferable to invoice the " "quantity actually delivered." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:14 msgid "" "Being able to have different invoicing options provides more flexibility." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:17 msgid "Invoicing policy features" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:19 msgid "" "To activate the necessary invoicing policy features, go to " ":menuselection:`Sales app --> Configuration --> Settings`, and under the " ":guilabel:`Invoicing` heading, select an :guilabel:`Invoicing Policy` rule: " ":guilabel:`Invoice what is ordered` or :guilabel:`Invoice what is " "delivered`." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 msgid "Choosing an invoicing policy on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:29 msgid "" "If the :guilabel:`Invoice what is delivered` rule is chosen, it is **not** " "possible to activate the :guilabel:`Automatic Invoice` feature, which " "automatically generates invoices when an online payment is confirmed." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:34 msgid "Invoicing policy on product form" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:36 msgid "" "On any product page, via the :menuselection:`Sales app --> Products --> " "Products dashboard`, locate the :guilabel:`Invoicing Policy` option located " "under the :guilabel:`General Information` tab. It can be changed manually " "using the drop-down menu." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 msgid "How to change your invoicing policy on a product form on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:45 msgid "Impact on sales flow" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:47 msgid "" "In Odoo *Sales*, the basic sales flow starts with the creation of a " "quotation. Then, that quotation is sent to a customer. Next, it needs to be " "confirmed, which turns the quotation into a sales order. This, in turn, " "creates an invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:51 msgid "" "The following is a breakdown of how invoicing policy rules impact the " "aforementioned sales flow:" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:53 msgid "" ":guilabel:`Invoice what is ordered`: No impact on the basic sales flow. An " "invoice is created as soon as a sale is confirmed." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:55 msgid "" ":guilabel:`Invoice what is delivered`: Minor impact on sales flow, because " "the delivered quantity needs to be manually entered on the sales order. Or, " "the *Inventory* app can be installed and used to confirm the delivered " "quantity before creating an invoice with the *Sales* app." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:60 msgid "" "If a user attempts to create an invoice without validating the delivered " "quantity, the following error message appears: :guilabel:`There is no " "invoiceable line. If a product has a Delivered quantities invoicing policy, " "please make sure that a quantity has been delivered.`" msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:0 msgid "" "If Delivered Quantities invoicing policy is chosen, ensure a quantity has " "been delivered." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:69 msgid "" "Once a quotation is confirmed, and the status changes from " ":guilabel:`Quotation sent` to :guilabel:`Sales order`, the delivered and " "invoiced quantities are available to view, directly from the sales order. " "This is true for both invoicing policy rule options." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 msgid "How to see your delivered and invoiced quantities on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:77 msgid "" "Odoo automatically adds the quantities to the invoice, both " ":guilabel:`Delivered` and :guilabel:`Invoiced`, even if it's a partial " "delivery, when the quotation is confirmed." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:80 msgid "" "Finally, there are a few different options to create an invoice: " ":guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)` or " ":guilabel:`Down payment (fixed amount)`." msgstr "" #: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:84 msgid "" "Be sure to check out the documentation explaining down payment options to " "learn more: :doc:`/applications/sales/sales/invoicing/down_payment`" msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:3 msgid "Invoice project milestones" msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:5 msgid "" "Invoicing based on project milestones can be used for expensive or large-" "scale projects. The series of milestones in a project represent a clear " "sequence of work that will inevitably result in the completion of a project " "and/or contract." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:9 msgid "" "This method of invoicing ensures the company gets a consistent flow of money" " throughout the lifetime of the project. Customers can closely monitor every" " phase of the project's development as it happens, in addition to paying a " "large bill in several installments, instead of all at once." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:14 msgid "Create milestone products" msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:16 msgid "" "In Odoo, each milestone of a project is considered as an individual product." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:18 msgid "" "To create and/or configure products to work like this, first navigate to " ":menuselection:`Sales app --> Products --> Products`. Then, click on a " "product, or create a new one by clicking :guilabel:`New`." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:22 msgid "" "The option to invoice based on milestones is only available for certain " "product types." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:24 msgid "" "On the product form, under the :guilabel:`General Information` tab, the " ":guilabel:`Product Type` field *must* be set on any of the following " "options: :guilabel:`Service`, :guilabel:`Event Ticket`, :guilabel:`Event " "Booth`, or :guilabel:`Course`." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The invoicing policy field drop-down menu with options on product form." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:32 msgid "" "With any of those :guilabel:`Product Type` options selected, choose " ":guilabel:`Based on Milestones` from the :guilabel:`Invoicing Policy` drop-" "down menu." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:39 msgid "Beneath that is the :guilabel:`Create on Order` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:41 msgid "" "To ensure workflows are as seamless as possible, it is recommended that an " "option in the :guilabel:`Create on Order` field is selected." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:45 msgid "" "Leaving it on the default :guilabel:`Nothing` option won't negatively affect" " the desired workflow. However, a project *must* then be created directly " "from a sales order form with that specific product. Once a project is " "created *then* milestones and tasks can be created and configured." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:50 msgid "" "When the :guilabel:`Create on Order` default option of :guilabel:`Nothing` " "is clicked, a drop-down menu is revealed with the following options:" msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:53 msgid "" ":guilabel:`Task`: Odoo creates a task related to this milestone product in " "the *Projects* app when this specific product is ordered." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:55 msgid "" ":guilabel:`Project \\& Task`: Odoo creates a project and task related to " "this milestone product in the *Projects* app when this specific product is " "ordered." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:57 msgid "" ":guilabel:`Project`: Odoo creates a project related to this milestone " "product in the *Projects* app when this specific product is ordered." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:60 msgid "" "When :guilabel:`Task` is selected, a :guilabel:`Project` field appears. In " "this field, select to which existing project in the *Projects* app this " "created task should be connected." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The Project field appears when the Task option is selected in Create on " "Order field." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:67 msgid "" "When :guilabel:`Project \\& Task` or :guilabel:`Project` is selected, two " "new fields appear: :guilabel:`Project Template` and :guilabel:`Workspace " "Template`." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The Project template and workspace template fields that appear on milestone " "product." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:74 msgid "" "The :guilabel:`Project Template` field provides template options to use for " "the project that will be created when this specific product is ordered." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:77 msgid "" "The :guilabel:`Workspace Template` field provides template options to use " "for the workspace (for the *Documents* app, not the *Projects* app) that " "will be automatically generated for the project when this specific product " "is ordered." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:82 msgid "" "For organizational purposes, click the :guilabel:`Sales` tab on the product " "form, and enter a custom 'Milestone' related descriptor in the " ":guilabel:`Sales Description` field. This information appears in the " ":guilabel:`Description` column on the :guilabel:`Order Lines` tab of the " "sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:87 msgid "" "Or, directly edit/modify the :guilabel:`Description` field on the " ":guilabel:`Order Lines` tab of the sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:90 msgid "This is *not* a requirement." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:93 msgid "Invoice milestones" msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:96 msgid "" "The following flow features a trio of milestone products that have " ":guilabel:`Service` set as their :guilabel:`Product Type`, and " ":guilabel:`Task` set on their :guilabel:`Create on Order` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:0 msgid "" "Product with Service \"Product Type\" and \"Task\" in the Create on Order " "field on form." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:104 msgid "" "Those tasks are then attached to a pre-existing :guilabel:`Project`, which, " "in this case, is titled, :guilabel:`Rebranding Projects`." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:107 msgid "" "To invoice milestones, create a sales order with the milestone product(s). " "To do that, go to :menuselection:`Sales app --> New`. Doing so reveals a " "blank quotation form." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:110 msgid "" "From this quotation form, add a :guilabel:`Customer`. Then, click " ":guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Next, add the " "milestone product(s) to the :guilabel:`Order Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:113 msgid "" "Once the corresponding milestone product(s) have been added, click " ":guilabel:`Confirm` to confirm the order, which turns the quotation into a " "sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:116 msgid "" "When the order is confirmed, new smart buttons appear at the top of the " "sales order based on what was selected in the :guilabel:`Create on Order` " "field on the product form." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:119 msgid "" "From the sales order, click the :guilabel:`Milestones` smart button. Doing " "so reveals a blank :guilabel:`Milestones` page. Click :guilabel:`New` to add" " milestones." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "Adding milestones to a sales order with milestone products." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:126 msgid "" "Enter a :guilabel:`Name` for the milestone. Next, apply it to the " "corresponding :guilabel:`Sales Order Item`. Lastly, assign a " ":guilabel:`Deadline` to the milestone, if desired." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:129 msgid "Repeat that process for all milestone sales order items." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:131 msgid "" "Then, return to the sales order, via the breadcrumbs. From the sales order, " "click the :guilabel:`Tasks` smart button. Doing so reveals a " ":guilabel:`Tasks` page with a task for each sales order item with that " "option designated in the :guilabel:`Create on Order` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "Sample tasks page accessed via the smart button from a sales order with " "milestone products." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:139 msgid "" "To manually assign a configured milestone to a task, click the desired task," " which reveals the task form. On the task form, select the appropriate " "milestone to which this task should be connected, in the " ":guilabel:`Milestone` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The milestone field on the task form when dealing with milestone products in" " Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:147 msgid "Repeat this process for all milestone tasks." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:149 msgid "" "With those tasks properly configured, employees log in their progress as " "they work on the task, in addition to adding any notes related to the task." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:152 msgid "" "Then, when that task is complete, that means that milestone has been " "reached. At that point, it is time to invoice that milestone." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:155 msgid "" "To invoice a milestone, first return to the sales order — either via the " "breadcrumb links, or by navigating to :menuselection:`Sales app --> Orders " "--> Orders` and picking the appropriate sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:159 msgid "" "Back on the sales order form, click the :guilabel:`Milestones` smart button," " and check the box in the :guilabel:`Reached` column for that particular " "task." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "What it looks like to mark a milestone as reached via the milestone smart " "button." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:166 msgid "" "Next, return to the sales order — either by clicking :guilabel:`View Sales " "Order` on the :guilabel:`Milestones` page, or via the breadcrumb links." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:169 msgid "" "Back on the sales order, the line item for the milestone that's been reached" " has its :guilabel:`Delivered` column filled. That's because the milestone " "has been reached, and therefore delivered." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "A milestone product that's been reached marked as delivered on the sales " "order in Odoo." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:177 msgid "" "Click :guilabel:`Create Invoice` in the upper-left corner. Doing so reveals " "a :guilabel:`Create invoices` pop-up window." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The create invoices pop-up window that appears when create invoice button is" " clicked." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:184 msgid "" "On the :guilabel:`Create invoices` pop-up window, leave the " ":guilabel:`Create Invoice` option on the default :guilabel:`Regular Invoice`" " selection, and click the :guilabel:`Create Draft Invoice` button." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:188 msgid "" "Upon clicking :guilabel:`Create Draft Invoice`, Odoo reveals the " ":guilabel:`Customer Invoice Draft`, *only* showing that reached milestone in" " the :guilabel:`Invoice Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "A customer invoice draft showing only the milestone product that's been " "reached." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:195 msgid "" "From this invoice page, click the :guilabel:`Confirm` button to confirm the " "invoice. Then, when the customer has paid for this milestone, click " ":guilabel:`Register Payment`." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:198 msgid "" "When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment`" " pop-up window appears." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The Register Payment pop-up window that appears when Register Payment is " "clicked." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:204 msgid "" "On this pop-up window, confirm the accuracy of the auto-populated fields, " "then click :guilabel:`Create Payment`." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:207 msgid "" "When clicked, the pop-up window disappears, and Odoo returns to the invoice " "for that milestone, which now has a green :guilabel:`In Payment` banner in " "the upper-right corner. This banner signifies the invoice has been paid." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "An invoice with a milestone product that has been paid with an In Payment " "banner." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:215 msgid "" "Then, return to the sales order, via the breadcrumb links. Back on the sales" " order, in the :guilabel:`Order Lines` tab, the reached milestone that's " "been invoiced and paid for, now has its :guilabel:`Invoiced` column filled." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The Invoiced column of a milestone product that's been paid for is filled." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:223 msgid "" "There is also a new :guilabel:`Invoices` smart button at the top of the " "sales order. Clicking that reveals all the invoices that are connected to " "this sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst-1 msgid "" "The invoices smart button that appears at the top of a sales order with " "milestones." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:230 msgid "" "Simply repeat the above process for each milestone as it is worked on, and " "subsequently, completed." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:232 msgid "" "Continue that process until the entire project has been completed, each " "milestone has been invoiced, and the entire order has been paid for in full." msgstr "" #: ../../content/applications/sales/sales/invoicing/milestone.rst:237 msgid ":doc:`proforma`" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:3 msgid "Pro-forma invoices" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:5 msgid "" "A *pro-forma invoice* is an abridged or estimated invoice sent in advance of" " a delivery of goods. It notes the kind and quantity of goods, their value, " "and other important information, such as weight and transportation charges." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:9 msgid "" "Pro-forma invoices are commonly used as preliminary invoices with a " "quotation. They are also used during importation for customs purposes. They " "differ from a normal invoice, in that they are *not* a demand (or request) " "for payment." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:16 msgid "" "In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature " "**must** be activated." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:18 msgid "" "To enable this feature, navigate to :menuselection:`Sales app --> " "Configuration --> Settings`, and in the :guilabel:`Quotations \\& Orders` " "section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, " "click :guilabel:`Save` to save all changes." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst-1 msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:27 msgid "Send pro-forma invoice" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:29 msgid "" "With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send" " a pro-forma invoice is now available on any quotation or sales order, via " "the :guilabel:`Send Pro-Forma Invoice` button." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst-1 msgid "" "The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:37 msgid "" "Pro-forma invoices can **not** be sent for a sales order or quotation if an " "invoice for a down payment has already been sent, or for a recurring " "subscription." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:40 msgid "" "In either case, the :guilabel:`Send Pro-Froma Invoice` button does **not** " "appear." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:42 msgid "" "However, pro-forma invoices **can** be sent for services, event " "registrations, courses, and/or new subscriptions. Pro-forma invoices are not" " limited to physical, consumable, or storable goods." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:45 msgid "" "When the :guilabel:`Send Pro-Forma Invoice` button is clicked, a pop-up " "window appears, from which an email can be sent." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:48 msgid "" "In the pop-up window, the :guilabel:`Recipients` field is auto-populated " "with the customer from the sales order or quotation. The :guilabel:`Subject`" " field and the body of the email can be modified, if necessary." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:52 msgid "" "The pro-forma invoice is automatically added as an attachment to the email." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:54 msgid "" "When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with" " the attached pro-forma invoice, to the customer." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst-1 msgid "" "The email pop-up window that appears with pro-forma invoice attached in Odoo" " Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:62 msgid "" "To preview what the pro-forma invoice looks like, click on the PDF at the " "bottom of the email pop-up window *before* clicking :guilabel:`Send`. When " "clicked, the pro-forma invoice is downloaded instantly. Open that PDF to " "view (and review) the pro-forma invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:0 msgid "Sample pro-forma invoice PDF from Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:3 msgid "Invoicing based on time and materials" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:5 msgid "" "Invoicing based on time and/or materials is typically used when accurately " "estimating the size of a project isn't possible, or when the requirements of" " a project may change." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:8 msgid "" "This is different from a fixed-price contract, when a customer agrees to pay" " a specified total for the fulfillment of the contract---no matter what " "needs to be paid to the employees, sub-contractors, vendors, suppliers, and " "so on." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:12 msgid "" "The Odoo *Sales* app can invoice for time and various other expenses (e.g. " "transport, lodging), as well as purchases needed to fulfill an order." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:16 msgid "App and settings configuration" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:18 msgid "" "First, in order to accurately keep track of the progress of a project, the " "Odoo *Project* and *Accounting* apps **must** be installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:21 msgid "" "To install the *Project* app, navigate to :menuselection:`Odoo main " "dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " ":guilabel:`Project` app block, and click :guilabel:`Activate`. The page " "automatically refreshes and returns to the main Odoo dashboard, where the " "*Project* app is now available to access." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:26 msgid "Repeat the same process to install the *Accounting* application." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:28 msgid "" "After installation, click the :guilabel:`Accounting` app icon from the main " "Odoo dashboard, and navigate to :menuselection:`Configuration --> Settings`." " On the :guilabel:`Settings` page, scroll down to the :guilabel:`Analytics` " "section, and ensure the box next to :guilabel:`Analytic Accounting` is " "checked." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "How it looks to activate the Analytic Accounting setting in Odoo Accounting " "Setting page." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:37 #: ../../content/applications/sales/sales/invoicing/time_materials.rst:43 msgid "Then, click :guilabel:`Save` to save all changes." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:39 msgid "" "Then, navigate to :menuselection:`Odoo main dashboard --> Project app --> " "Configuration --> Settings`. On the :guilabel:`Settings` page, in the " ":guilabel:`Time Management` section, ensure the box beside the " ":guilabel:`Timesheets` feature is checked." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "What the Timesheets feature looks like on the Odoo Project settings page." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:52 msgid "Service product configuration" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:54 msgid "" "With the *Timesheets* feature activated in the *Project* app, it is now " "possible to invoice for time spent on a project, but **only** when the " "following product configurations have been made." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:58 msgid "" "Invoicing for time spent on a project is **only** possible with products " "that have *Service* set as the *Product Type* on their product form." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:61 msgid "" "To configure a service product, first navigate to :menuselection:`Sales app " "--> Products --> Products`. On the :guilabel:`Products` page, select the " "desired service product to be configured, or click :guilabel:`New` to create" " a new product." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:65 msgid "" "From the product form, in the :guilabel:`General Information` tab, set the " ":guilabel:`Product Type` to :guilabel:`Service`. Then, open the drop-down " "menu in the :guilabel:`Invoicing Policy` field, and select :guilabel:`Based " "on Timesheets`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:69 msgid "" "Next, from the :guilabel:`Create on Order` drop-down menu, select " ":guilabel:`Project \\& Task`. That setting indicates that, when a sales " "order is created with this specific service product, a new project and task " "is created in the *Project* app." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "The correct settings for Invoicing Policy and Create on Order fields for " "service product." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:78 msgid "" "The option :guilabel:`Task` can be chosen instead from the :guilabel:`Create" " on Order` drop-down menu. If :guilabel:`Task` is chosen, select an existing" " project that the task will appear in from :guilabel:`Project` field, which " "only appears if :guilabel:`Task` is chosen in the :guilabel:`Create on " "Order` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:84 msgid "Add time spent to sales order" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:86 msgid "" "After properly configuring a service product with the correct *Invoicing " "Policy* and *Create on Order* options, it is possible to add time spent to a" " sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:89 msgid "" "To see that in action, navigate to :menuselection:`Sales app --> New` to " "open a blank quotation form. Then, proceed to add a :guilabel:`Customer`, " "and in the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and" " select the properly :ref:`configured service product " "` from the drop-down menu." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:94 msgid "Next, click :guilabel:`Confirm` to confirm the order." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:96 msgid "" "After confirming the sales order, two smart buttons appear at the top of the" " order form: :guilabel:`Projects` and :guilabel:`Tasks`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "How the Projects and Tasks smart buttons look on a Sales Order in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:103 msgid "" "If the :guilabel:`Projects` smart button is clicked, it reveals the specific" " project related to this sales order. If the :guilabel:`Tasks` smart button " "is clicked, it reveals the specific project task related to this sales " "order. Both are also accessible in the *Project* app." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:107 msgid "" "In order to add time spent on a sales order, click the :guilabel:`Tasks` " "smart button." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:109 msgid "" "On the task form, select the :guilabel:`Timesheets` tab. From the " ":guilabel:`Timesheets` tab, employees can be assigned to work on the " "project, and the time they spend working on the task can be added by the " "employees or by the person who created the sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:113 msgid "" "To add an employee, and the time spent working on the task, click " ":guilabel:`Add a line` in the :guilabel:`Timesheets` tab. Then, select the " "appropriate :guilabel:`Date` and :guilabel:`Employee`. There is also the " "option to add a brief description of the work done during this time in the " ":guilabel:`Description` column, but it's not required." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:118 msgid "" "Lastly, enter the amount of time worked on the task in the :guilabel:`Hours " "Spent` column, and click away to complete that line in the " ":guilabel:`Timesheets` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:122 msgid "" "The time entered in the :guilabel:`Hours Spent` column is immediately " "reflected in the :guilabel:`Allocated Time` field (located near the top of " "the task form) as a percentage, which reflects how much of the total " "allocated work hours have been done so far." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:126 msgid "" "That same information is found as numerical hours in the :guilabel:`Hours " "Spent` and :guilabel:`Remaining Hours` fields, located at the bottom of the " ":guilabel:`Timesheets` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 msgid "" "How the Timesheets tab appears on a task form in Odoo Sales and Odoo " "Project." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:133 msgid "" "Repeat this process for however many employees and hours have been worked on" " the project." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:136 msgid "Invoice time spent" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:138 msgid "" "Once all the necessary employees and time spent have been added to the " "project task, return to the sales order to invoice the customer for those " "hours. To do that, either click the :guilabel:`Sales Order` smart button at " "the top of the task form, or return to the sales order via the breadcrumb " "links, located in the upper-left of the screen." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:143 msgid "" "Back on the sales order form, the time that was added to the task is " "reflected in the :guilabel:`Order Lines` tab (in the :guilabel:`Delivered` " "column) and in the new :guilabel:`Recorded Hours` smart button at the top of" " the sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:147 msgid "" "To invoice the customer for time spent on the project, click " ":guilabel:`Create Invoice`, and select :guilabel:`Regular invoice` from the " ":guilabel:`Create invoices` pop-up window. Then, click :guilabel:`Create " "Draft Invoice`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:151 msgid "" "Doing so reveals a :guilabel:`Customer Invoice Draft`, clearly showing all " "the work that's been done in the :guilabel:`Invoice Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:155 msgid "" "Pay attention to the :guilabel:`Analytic Distribution` column in the " ":guilabel:`Customer Invoice`, as that information is necessary to ensure " "other time/material invoicing tasks are completed properly and accurately." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 msgid "Invoice draft showing time spent on sales order in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:163 msgid "" "Click :guilabel:`Confirm` to confirm the invoice and continue with the " "invoicing process." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:169 msgid "Expenses configuration" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:171 msgid "" "In order to track and invoice expenses related to a sales order, the Odoo " "*Expenses* app **must** be installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:174 msgid "" "To install the *Expenses* app, navigate to :menuselection:`Odoo main " "dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " ":guilabel:`Expenses` app block, and click :guilabel:`Activate`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:178 msgid "" "The page automatically refreshes and returns to the main Odoo dashboard, " "where the :guilabel:`Expenses` app is now available to access." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:184 msgid "Add expenses to sales order" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:186 msgid "" "To add an expense to a sales order, first navigate to the " ":menuselection:`Expenses` app. Then, from the main *Expenses* dashboard, " "click :guilabel:`New`, which reveals a blank expense form." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:189 msgid "" "On the expense form, add a :guilabel:`Description` of the expense (e.g. " "`Hotel Stay`, `Plane Ticket`). Next, in the :guilabel:`Category` field, " "select the appropriate option from the drop-down menu (e.g. " ":guilabel:`Meals`, :guilabel:`Miles`, :guilabel:`Travel \\& Accommodation`)." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:194 msgid "" "Expense categories can be added and modified by navigating to " ":menuselection:`Expenses app --> Configuration --> Expense Categories`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:197 msgid "" "Then, enter the total amount of the expense in the :guilabel:`Total` field, " "as well as any :guilabel:`Included Taxes` that may apply. Next, ensure that " "the correct :guilabel:`Employee` is selected, and designate who paid for the" " expense in the :guilabel:`Paid By` field: the :guilabel:`Employee (to " "reimburse)` or the :guilabel:`Company`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:202 msgid "" "Next, in the :guilabel:`Customer to Reinvoice` field, select the appropriate" " sales order from the drop-down menu. Then, select that same sales order " "information from the :guilabel:`Analytic Distribution` field, as well." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:207 msgid "" "The :guilabel:`Analytic Distribution` field will **only** have the " "corresponding sales order as an option if the sales order contains a service" " product that is billed based on *Timesheets*, *Milestones*, or *Delivered " "Quantities*." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "How to properly fill out an expense form that's attached to a sales order in" " Odoo." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:215 msgid "" "If there are any receipts that should be uploaded and attached to the " "expense, click the :guilabel:`Attach Receipt` button, and upload the " "necessary documents to the expense. This is **not** required, but it may " "affect whether or not an expense is approved." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:219 msgid "" "When all the information has been entered, click :guilabel:`Create Report` " "to create an expense report detailing all the expense information that was " "just entered." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "How an Expense Report Summary looks in Odoo Expenses." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:226 msgid "" "Then, there's the option to :guilabel:`Submit to Manager` for approval. Once" " approved, the :guilabel:`Report in Next Payslip` appears." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:229 msgid "" "To showcase a complete flow in this example, select :guilabel:`Submit to " "Manager`. Then, the manager would click :guilabel:`Approve` to approve this " "expense, and click :guilabel:`Post Journal Entries` to post this expense to " "the accounting journal." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:234 msgid "Invoice expenses" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:236 msgid "" "To invoice a customer for an :ref:`expense on a sales order " "`, navigate to the related sales " "order, either from the :menuselection:`Sales` app or from the expense report" " in the :menuselection:`Expenses` app. From the expense report, click the " ":guilabel:`Sales Orders` smart button at the top of the page." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:241 msgid "" "If the expense report was linked to the sales order, the newly-configured " "expense now has its own line in the :guilabel:`Order Lines` tab, and can be " "invoiced to the customer." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "An expense appearing on Order Lines tab of a Sales Order in Odoo Sales " "application." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:248 msgid "" "To invoice the customer for the expense on the sales order, click " ":guilabel:`Create Invoice`, select :guilabel:`Regular Invoice` from the " ":guilabel:`Create invoices` pop-up window, then click :guilabel:`Create " "Draft Invoice`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:252 msgid "" "Doing so reveals a :guilabel:`Customer Invoice Draft` for the expense. Then," " the invoicing process can be completed as usual." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "Sample customer invoice for an expense generated from a sales order in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:260 msgid "Purchase configuration" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:262 msgid "" "In order to invoice a customer for purchases made on a sales order, the " "*Purchase* application **must** be installed." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:265 msgid "" "To install the *Purchase* application, navigate to :menuselection:`Odoo main" " dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " ":guilabel:`Purchase` app block, and click :guilabel:`Activate`. The page " "automatically refreshes and returns to the main Odoo dashboard, where the " ":guilabel:`Purchase` app is now available to access." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:273 msgid "Add purchase to sales order" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:275 msgid "" "To add a purchase to a sales order, a purchase order must first be created. " "To create a purchase order, navigate to :menuselection:`Purchase app --> " "New` to reveal a blank purchase order form." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:278 msgid "" "First, add a :guilabel:`Vendor` to the purchase order. Then, under the " ":guilabel:`Products` tab, click the :guilabel:`extra column options` drop-" "down menu, represented by two horizontal lines with dots on them, located to" " the far-right of the column headers. From that drop-down menu, select " ":guilabel:`Analytic Distribution`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "How to add analytic distribution column on purchase order form in Odoo " "Purchase." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:287 msgid "" "After adding the :guilabel:`Analytic Distribution` column to the headers on " "the :guilabel:`Products` tab of the purchase order form, proceed to add the " "product(s) to the purchase order. To do that, click :guilabel:`Add a " "product`, and select the desired product from the drop-down menu. Repeat for" " all the products to add." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:293 msgid "" "In order for a purchase to be properly invoiced on a sales order, the " "product on the purchase order **must** be marked as :guilabel:`Can be " "Expensed`, have an :guilabel:`Invoicing Policy` set to :guilabel:`Delivered " "quantities`, and have the :guilabel:`At cost` option selected in the " ":guilabel:`Re-Invoice Expenses` field on its product form." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 msgid "" "Product settings for a purchase order to be invoiced on a sales order in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:302 msgid "" "Then, select the appropriate :guilabel:`Analytic Distribution` associated " "with the sales order to which this purchase order is related. To do that, " "click the empty :guilabel:`Analytic Distribution` field to reveal an " ":guilabel:`Analytic` pop-up window." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:306 msgid "" "Then, from the :guilabel:`Departments` drop-down menu, select the analytic " "distribution associated with the desired sales order to be invoiced for the " "purchase." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "How to select the Analytic Distribution department from a purchase order in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:313 msgid "" "Once all the information is entered in the :guilabel:`Products` tab of the " "purchase order, confirm the order by clicking :guilabel:`Confirm Order`. " "Then, click :guilabel:`Receive Products` when the products have been " "received. This creates a receipt form." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:318 msgid "" "If any serial/lot numbers must be entered before validating the receipt of " "products, then on the receipt form, click the :guilabel:`details` icon " "represented by four horizontal lines located to the far-right of the product" " line." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:322 msgid "" "This reveals a :guilabel:`Detailed Operations` tab, in which the necessary " ":guilabel:`Lot/Serial Number(s)` and :guilabel:`Done` quantity can be added." " When ready, click :guilabel:`Confirm` to confirm the data." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:326 msgid "Then, click :guilabel:`Validate` to validate the purchase order." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:328 msgid "" "Next, return to the purchase order, via the breadcrumb links at the top of " "the page, and click :guilabel:`Create Bill` to create a vendor bill that can" " be invoiced to the customer on the attached sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "Vendor bill draft for a purchase order to be invoiced to a customer in Odoo." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:337 msgid "" "Make sure to enter a :guilabel:`Bill Date` on the :guilabel:`Vendor Bill " "Draft` before confirming. If a :guilabel:`Bill Date` is *not* entered, an " "error window appears, requesting that information to be entered before " "confirmation can occur." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:341 msgid "" "Then, click :guilabel:`Confirm` to confirm the vendor bill, which is then " "automatically added to the sales order, where it can be invoiced directly to" " the customer attached to it." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:345 msgid "Invoice purchase" msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:347 msgid "" "To invoice a customer for a purchase on a sales order, first :ref:`add the " "purchase to the sales order `, " "then navigate to the desired sales order in the :menuselection:`Sales` app." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:351 msgid "" "On the sales order that was attached to the purchase order, the purchased " "product now has its own product line under the :guilabel:`Order Lines` tab, " "and it is ready to be invoiced." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "Purchase order product on sales order to be invoiced to customer via Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:358 msgid "" "To invoice the customer for the purchase, simply click :guilabel:`Create " "Invoice`, select :guilabel:`Regular Invoice` from the :guilabel:`Create " "invoices` pop-up window, then click :guilabel:`Create Draft Invoice`." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:362 msgid "" "Doing so reveals a :guilabel:`Customer Invoice Draft` with the newly-added " "purchase order product in the :guilabel:`Invoice Lines` tab." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 msgid "" "Customer invoice draft with purchase product attached to sales order in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:369 msgid "" "To complete the invoicing process, click :guilabel:`Confirm` to confirm the " "invoice, and then click :guilabel:`Register Payment` in the " ":guilabel:`Register Payment` pop-up form." msgstr "" #: ../../content/applications/sales/sales/products_prices.rst:5 msgid "Products & Prices" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:3 msgid "Use eWallets and gift cards" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:5 msgid "" "With Odoo, customers can use **eWallets** and **gift cards** for online and " "in-store shopping." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:7 msgid "" "To enable eWallets and gift cards for eCommerce and Point of Sale (PoS), " "first enable :guilabel:`Discounts, Loyalty & Gift Card` under " ":menuselection:`Sales app --> Configuration --> Settings --> Pricing " "section`. Once enabled, go to :menuselection:`Sales app --> Products --> " "Gift cards & eWallet` and :guilabel:`Create` a new eWallet or gift card " "program." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:13 msgid "eWallets" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:15 msgid "" "eWallets allow customers to save credits on their online account and use " "these credits as a payment method when buying items in an online store or a " "brick-and-mortar store. eWallets can also be used to centralize multiple " ":ref:`gift cards `." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:19 msgid "" "Before creating an eWallet program, it is necessary to create an eWallet " "**top-up** product. Top-ups are pre-defined digital credit values added to " "an eWallet in exchange for its equivalent in real currency. These credits " "can then be used as a payment method in the eCommerce shop or :abbr:`PoS " "(Point of Sale)`. Top-up values can be of different amounts." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:25 msgid "" "A $50 top-up can be bought for $50, and adds that same amount of credits to " "the eWallet." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:27 msgid "" "To create a top-up product, go to :menuselection:`Sales app --> Products -->" " Products` and :guilabel:`Create` a new product. On the product template, " "configure the options as follows:" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:30 msgid "" ":guilabel:`Product Name`: enter a name for the top-up product (for example, " "`$50 Top-Up`)" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:31 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:92 msgid ":guilabel:`Can be Sold`: enabled" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:32 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:93 msgid ":guilabel:`Product Type`: select :guilabel:`Service`" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:33 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:94 msgid ":guilabel:`Invoicing Policy`: select :guilabel:`Prepaid/Fixed Price`" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:34 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:95 msgid ":guilabel:`Create on Order`: select :guilabel:`Nothing`" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:35 msgid ":guilabel:`Sales Price`: enter the amount of the top-up" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:38 msgid "" "In order to have eWallet top-ups of different amounts, create multiple top-" "up products and modify the :guilabel:`Sales Price` accordingly." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:41 msgid "" "Once the top-up is created, go to :menuselection:`Sales app --> Products -->" " Gift cards & eWallet` to :guilabel:`Create` an eWallet program. The " "following configuration options are available:" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:44 msgid ":guilabel:`Program Name`: enter a name for the eWallet program" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:45 msgid ":guilabel:`Program Type`: select :guilabel:`eWallet`" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:46 msgid "" ":guilabel:`eWallet Products`: select the eWallet top-up created earlier. " "Repeat the process if you created top-ups of different amounts." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:48 msgid "" ":guilabel:`Email template`: select the email template used for the email " "sent to the customer. To create a new template, click on the field, select " ":guilabel:`Search More`, and then click :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:51 msgid "" ":guilabel:`Currency`: select the currency to use for the eWallet program" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:52 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:115 msgid "" ":guilabel:`Company`: select the company for which the program is valid and " "available" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:53 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:116 msgid "" ":guilabel:`Available On`: select the applications on which the program is " "valid and available" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:54 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:117 msgid "" ":guilabel:`Website`: select the website on which the program is valid and " "available. Leave this field empty to include all websites." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:56 #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:119 msgid "" ":guilabel:`Point of Sale`: select the :abbr:`PoS (Point of Sale)` in which " "the program is valid and available. Leave this field empty to include all " ":abbr:`PoS (Point of Sale)`." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 msgid "eWallet program configuration page" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:63 msgid "" "Once the program is configured, click the :guilabel:`Generate eWallet` " "button in the upper-left corner to generate eWallets. eWallets can be " "generated based on :guilabel:`Customers` and/or :guilabel:`Customer Tags`. " "The quantity is automatically adapted according to the :guilabel:`Customers`" " and :guilabel:`Customer Tags` selected. Then, set the :guilabel:`eWallet " "value`. Finally, set the :guilabel:`Valid Until` period if applicable." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:69 msgid "" "Generated eWallets can be accessed through the :guilabel:`eWallets` smart " "button in the upper-right corner. From there, :guilabel:`Send` or " ":guilabel:`Share` the eWallets via email or a URL link." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 msgid "eWallets send and share buttons" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:76 msgid "" "Click on an eWallet to change the :guilabel:`Expiration Date`, " ":guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of an " "eWallet *cannot* be changed, deleted, or duplicated." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:82 msgid "Gift cards" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:84 msgid "" "Gift cards can be purchased by customers, and in turn used as a payment " "method upon checkout at an eCommerce shop or :abbr:`PoS (Point of Sale)`." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:87 msgid "" "Before creating a new gift card program, it is necessary to first create " "gift cards as products. To do so, go to :menuselection:`Sales app --> " "Products --> Products` and :guilabel:`Create` a product. On the product " "template, configure the options as follows:" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:91 msgid ":guilabel:`Product Name`: enter a name for the gift card product" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:96 msgid ":guilabel:`Sales Price`: enter the amount of the gift card" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:99 msgid "" "In order to have gift cards of different amounts, create multiple gift card " "products and modify the :guilabel:`Sales Price` accordingly." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:102 msgid "" "Once the gift card product is created, go to :menuselection:`Sales app --> " "Products --> Gift cards & eWallet` to :guilabel:`Create` a gift card " "program. The following configuration options are available:" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:106 msgid ":guilabel:`Program Name`: enter a name for the gift card program" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:107 msgid ":guilabel:`Program Type`: select :guilabel:`Gift Card`" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:108 msgid "" ":guilabel:`Gift Card Products`: select the gift card product created " "earlier. Repeat the process if you created gift card products of different " "amounts." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:110 msgid "" ":guilabel:`Email template`: select the default :guilabel:`Gift Card: Gift " "Card Information` template, or create a new template by clicking on the " "field, selecting :guilabel:`Search More`, and then clicking " ":guilabel:`Create`." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:113 msgid ":guilabel:`Print Report`: select :guilabel:`Gift Card`" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:114 msgid "" ":guilabel:`Currency`: select the currency to use for the gift card program" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 msgid "Gift card program configuration page" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:126 msgid "" "Once the program is configured, click the :guilabel:`Generate Gift Cards` " "button in the upper-left corner to generate gift cards. Gift cards can be " "generated either for :guilabel:`Anonymous Customers` or :guilabel:`Selected " "Customers`. Set the :guilabel:`Quantity to generate` for " ":guilabel:`Anonymous Customers`, or select the :guilabel:`Customers` and/or " ":guilabel:`Customer Tags` for :guilabel:`Selected Customers`. Then, set the " ":guilabel:`Gift Card value`. Finally, set the :guilabel:`Valid Until` period" " if applicable." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:133 msgid "" "Generated gift cards can be accessed through the :guilabel:`Gift Cards` " "smart button in the upper-right corner. From there, :guilabel:`Send` or " ":guilabel:`Share` the gift cards via email or a URL link." msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 msgid "Gift cards send and share buttons" msgstr "" #: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:141 msgid "" "Click on a gift card to change the :guilabel:`Expiration Date`, " ":guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of a gift " "card *cannot* be changed, deleted, or duplicated." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:3 msgid "Discount and loyalty programs" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:5 msgid "" "The Odoo *Sales*, *eCommerce*, and *Point of Sale* applications allow users " "to create discount and loyalty programs that customers can use for online " "and in-store shopping. These programs offer more varied, public, and time-" "sensitive pricing options than :doc:`pricelists " "`." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:11 msgid "Configure the settings" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:13 msgid "" "To begin using discount and loyalty programs, navigate to " ":menuselection:`Sales --> Configuration --> Settings`. Under the " ":guilabel:`Pricing` heading, activate the :guilabel:`Discounts, Loyalty & " "Gift Card` setting by checking the box next to the feature. Finally, click " ":guilabel:`Save` to save the changes." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:19 msgid "Configure discount and loyalty programs" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:21 msgid "" "To create discount and loyalty programs, go to :menuselection:`Sales --> " "Products --> Discount & Loyalty`." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:24 msgid "" "If no discount or loyalty programs have been created yet, Odoo provides a " "choice of templates to help create the first program. Choose one of the " "template cards, or click :guilabel:`New` to create a new program from " "scratch." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:28 msgid "" "Or, if there are already existing programs, select an existing program to " "edit it." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 msgid "Discount and loyalty program template cards." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:35 msgid "" "Templates **only** appear when no programs have been created, and they " "disappear once the first program is created." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:38 msgid "Creating or editing a program opens the program form." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 msgid "Program options on the loyalty program form." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:44 msgid "The program form contains the following fields:" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:46 msgid "" ":guilabel:`Program Name`: Enter the name of the program in this field. The " "program name is **not** visible to the customer." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:48 msgid "" ":guilabel:`Program Type`: Select the desired :ref:`program type " "` from the drop-down menu." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:50 msgid ":guilabel:`Currency`: Select the currency used for the program." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:51 msgid "" ":guilabel:`Pricelist`: If desired, select a pricelist from the drop-down " "menu to have this loyalty program applied to a specific pricelist (and " "customers attached to the pricelist). More than one pricelist can be " "selected in this field. When a single loyalty program is linked to several " "pricelists, it makes it viable for different customer segments to have " "different pricelists, but the *same* loyalty programs. If this field is left" " blank, the program applies to everyone, regardless of pricelist." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:57 msgid "" ":guilabel:`Points Unit`: Enter the name of the points used for the " ":guilabel:`Loyalty Cards` program (e.g. `Loyalty Points`). The points unit " "name *is* visible to the customer. This field is **only** available when the" " :guilabel:`Program Type` is set to :guilabel:`Loyalty Cards`." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:60 msgid "" ":guilabel:`Start Date`: Select the date on which the program becomes valid. " "Leave this field blank if the program should always be valid and not expire." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:62 msgid "" ":guilabel:`End Date`: Select the date on which the program stops being " "valid. Leave this field blank if the program should always be valid and not " "expire." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:64 msgid "" ":guilabel:`Limit Usage`: If desired, tick this checkbox, and enter a number " "of :guilabel:`usages` to limit the number of times the program can be used " "during the validity period." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:66 msgid "" ":guilabel:`Company`: If working in a multi-company database, choose the one " "company for which the program is available. If left blank, the program is " "available to all companies in the database." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:68 msgid "" ":guilabel:`Available On`: Select the apps on which the program is available." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:69 msgid "" ":guilabel:`Website`: Select a website on which the program is available. " "Leave this field blank to make it available on all websites." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:71 msgid "" ":guilabel:`Point of Sale`: Select the point(s) of sale at which the program " "is available. Leave this field blank to make it available at all :abbr:`PoS " "(Point of Sale)`." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:75 msgid "" "The options available on the program form vary depending on the " ":ref:`Program Type ` selected." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:78 msgid "" "All of the existing cards, codes, coupons, etc. that have been generated for" " the program are accessible through the smart button located at the top of " "the form." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 msgid "Program items smart button on the loyalty program form." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:86 msgid "" "In Odoo 17 (and later), when a loyalty card or coupon is associated with a " "contact in the database, a :guilabel:`Loyalty Cards` smart button " "conditionally appears on the contact form." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 msgid "" "The Loyalty Card smart button as it appears on a contact form in Odoo 17." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:93 msgid "" "This smart button **only** appears if a loyalty card or coupon is associated" " with the contact." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:98 msgid "Program types" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:100 msgid "" "The different :guilabel:`Program Types` available on the program form are:" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:102 msgid "" ":guilabel:`Coupons`: Generate and share single-use coupon codes that grant " "immediate access to rewards." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:104 msgid "" ":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates " "points to exchange for rewards on current and/or future orders." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:106 msgid "" ":guilabel:`Promotions`: Set conditional rules for ordering products, which, " "when fulfilled, grant access to rewards for the customer." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:108 msgid "" ":guilabel:`Discount Code`: Set codes which, when entered upon checkout, " "grant discounts to the customer." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:110 msgid "" ":guilabel:`Buy X Get Y`: for every (X) item bought, the customer is granted " "1 credit. After accumulating a specified amount of credits, the customer can" " trade them in to receive (Y) item." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:112 msgid "" ":guilabel:`Next Order Coupons`: Generate and share single-use coupon codes " "that grant access to rewards on the customer's next order." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:116 msgid "Conditional rules" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:118 msgid "" "Next, configure the :guilabel:`Conditional rules` that determine when the " "program applies to a customer's order." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:121 msgid "" "In the :guilabel:`Rules & Rewards` tab, click :guilabel:`Add` next to " ":guilabel:`Conditional rules` to add *conditions* to the program. This " "reveals a :guilabel:`Create Conditional rules` pop-up window." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 msgid "Rules & Rewards tab of the loyalty program form." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:130 msgid "" "The options for :guilabel:`Conditional rules` vary depending on the selected" " :ref:`Program Type `." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:133 msgid "The following options are available for configuring conditional rules:" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:135 msgid "" ":guilabel:`Discount Code`: Enter a custom code to be used for the " ":guilabel:`Discount Code` program, or use the default one generated by Odoo." " This field is only available when the :guilabel:`Program Type` is set to " ":guilabel:`Discount Code`." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:138 msgid "" ":guilabel:`Minimum Quantity`: Enter the minimum number of products that must" " be purchased in order to access the reward. Set the minimum quantity to at " "least `1` to ensure that the customer must make a purchase in order to " "access the reward." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:141 msgid "" ":guilabel:`Minimum Purchase`: Enter the minimum amount (in currency), with " ":guilabel:`tax Included` or :guilabel:`tax Excluded`, that must be spent in " "order to access the reward. If both a minimum quantity *and* minimum " "purchase amount are entered, then the customer's order must meet both " "conditions." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:145 msgid "" ":guilabel:`Products`: Select the specific product(s) for which the program " "applies. Leave this field blank to apply it to all products." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:147 msgid "" ":guilabel:`Categories`: Select the category of products for which the " "program applies. Choose :guilabel:`All` to apply it to all product " "categories." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:149 msgid "" ":guilabel:`Product Tag:` Select a tag to apply the program to products with " "that specific tag." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:150 msgid "" ":guilabel:`Grant`: Enter the number of points the customer earns " ":guilabel:`per order`, :guilabel:`per currency spent`, or :guilabel:`per " "unit paid` (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get Y` " "programs)." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 msgid "" "Conditional rules configuration window for a discount or loyalty program." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:158 msgid "" "Click :guilabel:`Save & Close` to save the rule and close the pop-up window," " or click :guilabel:`Save & New` to save the rule and immediately create a " "new one." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:162 msgid "Rewards" msgstr "Nagrade" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:164 msgid "" "In the :guilabel:`Rules & Rewards` tab of the program form, click " ":guilabel:`Add` next to :guilabel:`Rewards` to add *rewards* to the program." " This reveals a :guilabel:`Create Rewards` pop-up window." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:169 msgid "" "The options for :guilabel:`Rewards` vary depending on the selected " ":ref:`Program Type `." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:172 msgid "The following options are available for configuring rewards:" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:174 msgid "" ":guilabel:`Reward Type`: Select the reward type among :guilabel:`Free " "Product`, :guilabel:`Discount`, and :guilabel:`Free Shipping`. The other " "options for reward configuration depend on the :guilabel:`Reward Type` " "selected." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:178 msgid ":guilabel:`Free Product`:" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:180 msgid "" ":guilabel:`Quantity Rewarded`: Select the number of free products rewarded " "to the customer." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:181 msgid "" ":guilabel:`Product`: Select the product given for free as a reward. Only one" " product can be selected." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:183 msgid "" ":guilabel:`Product Tag`: Select a tag to further specify the free product " "eligible for the reward." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:186 msgid ":guilabel:`Discount`:" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:188 msgid "" ":guilabel:`Discount`: Enter the discounted amount in either " ":guilabel:`percentage`, :guilabel:`currency per point`, or " ":guilabel:`currency per order`. Then, select whether the discount applies to" " the entire :guilabel:`Order`, only the :guilabel:`Cheapest Product` on the " "order, or only :guilabel:`Specific Products`." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:192 #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:197 msgid "" ":guilabel:`Max Discount`: Enter the maximum amount (in currency) that this " "reward may grant as a discount. Leave this field at `0` for no limit." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:195 msgid ":guilabel:`Free Shipping`:" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:200 msgid "" ":guilabel:`In exchange of`: Enter the number of points required to exchange " "for the reward (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get " "Y` programs)." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:202 msgid "" ":guilabel:`Description on order`: Enter the description of the reward, which" " is displayed to the customer upon checkout." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 msgid "Rewards configuration window for a discount or loyalty program." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices.rst:5 msgid "Manage your pricing" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:3 msgid "Foreign currencies" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:5 msgid "" "With Odoo, pricelists can be used to manage prices in a number of foreign " "currencies. Specifically, Odoo has the ability to work with 167 total " "currencies." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:9 msgid "" "In order to use multiple currencies in Odoo *Sales*, the *Accounting* " "application **must** be installed." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:15 msgid "" "Once the *Accounting* app has been installed, foreign currencies can be " "added to the database. Navigate to :menuselection:`Accounting app --> " "Configuration --> Settings`, scroll to the :guilabel:`Currencies` section, " "and locate the :guilabel:`Main Currency` setting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 msgid "" "How the main currency feature appears on settings page in Odoo Accounting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:23 msgid "" "Odoo automatically sets the main currency as the currency of the country the" " company is based in." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:25 msgid "" "To change the main currency of the company, select the drop-down menu in the" " :guilabel:`Currency` field, select the desired currency, and be sure to " ":guilabel:`Save` the changes." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:29 msgid "" "To ensure currency rates are updated automatically, enable the *automatic " "currency rates* feature on the *Accounting* settings page " "(:menuselection:`Accounting app --> Configuration --> Settings --> " "Currencies section`)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:37 msgid "" "Click the checkbox beside the :guilabel:`Automatic Currency Rates` feature, " "choose a designated bank to get the currency rates from in the " ":guilabel:`Service` field drop-down menu, and select an :guilabel:`Interval`" " of time for the updates to take place. Then determine when the date of the " ":guilabel:`Next Run` should be." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:42 msgid "" "To instantly update the currency rates, click the :guilabel:`🔁 (circular " "arrows)` icon, located to the right of the :guilabel:`Next Run` field." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:45 msgid "" "When all configurations are complete, be sure to :guilabel:`Save` all " "changes." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:48 msgid "" "All payment methods **must** be in the same currency as the sales journal, " "or the company currency, if the company currency is not set. If it is not " "the same, a :guilabel:`Validation Error` message appears." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:53 msgid "View, edit, and add currencies" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:55 msgid "" "To view, edit, and add currencies to the database, making them available on " "pricelists and on the :guilabel:`Main Currency` drop-down menu, click the " ":guilabel:`Currencies` link, located beneath the :guilabel:`Currency` field " "on the :menuselection:`Accounting app --> Settings` page." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:59 msgid "" "When the :guilabel:`Currencies` link is clicked, a separate " ":guilabel:`Currencies` page is revealed." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 msgid "How the main currencies page appears in Odoo Accounting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:65 msgid "" "On this page, Odoo provides a master list of 167 global currencies. Each row" " shows the corresponding :guilabel:`Currency`, :guilabel:`Symbol`, " ":guilabel:`Name`, date of the :guilabel:`Last Update`, and " ":guilabel:`Current Rate` (compared to the default currency of the country in" " which the company is based)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:70 msgid "" "To the far right, there are two columns, which can be toggled on or off:" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:72 msgid "" ":guilabel:`Use on eBay`: this currency can be used with the connected eBay " "account (if applicable)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:74 msgid "" ":guilabel:`Active`: this currency is activated, which means it can be added " "to a pricelist, or used as the main currency of the company, if desired (via" " :menuselection:`Accounting app --> Configuration --> Settings --> " "Currencies section`)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:79 msgid "" "By default, all the :guilabel:`Active` currency options are at the top of " "the list." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:82 msgid "" "It is recommended that *at least* one pricelist is created per " ":guilabel:`Active` currency. See :doc:`./pricing` to learn more about " "pricelist configuration." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:85 msgid "" "To toggle options on/off, click the toggle switch in the row for the " "corresponding column. When *on* the color of the switch is green. When " "*off*, the color of the switch is grey." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:89 msgid "Currency detail form" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:91 msgid "" "To edit any currency on the :guilabel:`Currencies` page, click the desired " "currency to reveal the detail form for that specific currency, and proceed " "to make any necessary changes." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 msgid "How a currency detail form looks in Odoo Accounting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:98 msgid "" "On the currency detail form, the relevant currency code appears in the " ":guilabel:`Currency` field. Beneath that, the name for the currency is in " "the :guilabel:`Name` field." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:101 msgid "" "Then, toggle the currency's availability with the :guilabel:`Active` toggle:" " *on* is indicated with a green switch, and *off* is indicated with a grey " "switch." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:104 msgid "" "On the right of the currency detail form, the appropriate " ":guilabel:`Currency Unit` (e.g. `Dollars`) and :guilabel:`Currency Subunit` " "(e.g. `Cents`) can be found." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:107 msgid "" "If the currency is meant to be used for eBay purposes, toggle the " ":guilabel:`Use on eBay` option to the desired activation." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:110 msgid "" "Next, under the :guilabel:`Rates` tab, the various conversion rates can be " "viewed, added, or deleted. Each row shows the :guilabel:`Date` of that " "specific rate, the :guilabel:`Company` to which it is connected, followed by" " the :guilabel:`Unit per...` and :guilabel:`...per Unit`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:115 #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:166 msgid "" "The *...* in each of the last two columns represents the main currency set " "for the company. For example, if the main currency is set to `USD`, the " "columns are titled :guilabel:`Unit per USD` and :guilabel:`USD per Unit`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:119 msgid "" "To add a new rate, click :guilabel:`Add a line` in the :guilabel:`Rates` " "tab, and proceed to fill in the necessary information in the aforementioned " "columns." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:123 msgid "Main currency detail form" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:125 msgid "" "If the selected currency is the main currency of the company, a blue banner " "appears at the top of the currency detail form with the message: " ":guilabel:`This is your company's currency.`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 msgid "How a main currency detail form looks in Odoo Accounting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:132 msgid "" "All the fields are the same as a typical currency detail form, but there " "will **not** be a :guilabel:`Rates` tab because all other currency rates are" " based off the main currency of the company." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:137 msgid "Create new currency" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:139 msgid "" "If a desired currency isn't on the :guilabel:`Currencies` page, click the " ":guilabel:`New` button to open a blank currency template form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:143 msgid "" "The same :guilabel:`New` button is located in the upper-right corner of any " "currency detail form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 msgid "How a blank currency detail form looks in Odoo Accounting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:149 msgid "" "On the blank currency detail form, proceed to enter the desired currency " "code in the :guilabel:`Currency` field. Beneath that, enter the name for the" " currency in the :guilabel:`Name` field." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:153 msgid "" "Then, toggle the currency's availability with the :guilabel:`Active` toggle " "switch." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:155 msgid "" "On the right of the currency detail form, enter the appropriate " ":guilabel:`Currency Unit` (e.g. `Dollars`) and appropriate " ":guilabel:`Currency Subunit` (e.g. `Cents`)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:158 msgid "" "If the currency is meant to be used for eBay purposes, toggle the " ":guilabel:`Use on eBay` to the desired activation." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:161 msgid "" "Next, under the :guilabel:`Rates` tab, add a new rate by clicking " ":guilabel:`Add a line`. Then, proceed to confirm and adjust the " ":guilabel:`Date`, :guilabel:`Company`, :guilabel:`Unit per...`, and " ":guilabel:`...per Unit` fields to ensure all the auto-populated information " "is accurate." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:171 msgid "Currency-specific pricelists" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:173 msgid "" "It is recommended that *at least* one pricelist is created per active " "currency in the database. To create (or assign) a pricelist to a specific " "currency, start by navigating to :menuselection:`Sales app --> Products --> " "Pricelists`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:177 msgid "" "From the :guilabel:`Pricelists` page, either select an existing pricelist to" " edit, or click :guilabel:`New` to create a new pricelist." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:180 msgid "" "On the pricelist detail form, for either a new or existing pricelist, adjust" " the :guilabel:`Currency` field as desired." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:184 msgid ":doc:`./pricing` to learn more about pricelist configuration." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:187 msgid "Auto-conversion from public price" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:189 msgid "" "It should be noted that the public price seen on products is directly " "related to the main currency the company has set, which is configured by " "navigating to :menuselection:`Accounting app --> Configuration --> Settings " "--> Currencies section --> Main Currency --> Currency drop-down menu`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:193 msgid "" "The sales price automatically updates if the pricelist is changed to a " "different pricelist that has a different currency than the company's main " "currency. The change in price is directly related to the updated conversion " "rate for that currency." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:198 msgid "Set product prices" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:200 msgid "" "In order to have product prices set in place to avoid any changes in " "currency rates, start by navigating to :menuselection:`Sales app --> " "Products --> Products`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:203 msgid "" "From the :guilabel:`Products` page, select the desired product to modify. " "Or, create a new product by clicking the :guilabel:`New` button." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:206 msgid "" "Then, on the product detail form, click the :guilabel:`Extra Prices` smart " "button, located in the upper-left corner. Doing so reveals a separate " ":guilabel:`Price Rules` page, specific to that particular product." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 msgid "" "How to set product prices based on foreign currency pricelists in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:214 msgid "" "Click :guilabel:`New`, and select the desired pricelist from the drop-down " "menu in the :guilabel:`Pricelist` column." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:217 msgid "" "The :guilabel:`Applied On` field is auto-populated with the product, so " "proceed to enter in the desired figures in the :guilabel:`Min. Quantity` and" " :guilabel:`Price` fields." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:221 msgid "" "The figure in the :guilabel:`Min. Quantity` field means the " ":guilabel:`Price` being set will **only** trigger if at least that amount of" " product is purchased." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:224 msgid "" "If necessary, configure a :guilabel:`Start Date` and :guilabel:`End Date` " "for the set prices. Leaving those columns blank ensures the set price will " "remain valid, regardless of the date of sale." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:227 msgid "" "If working in a multi-company environment, designate to which company this " "price rule should be applied in the :guilabel:`Company` field. Leaving that " "field blank ensures the price rule applies to all companies in the database." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:231 msgid "" "With those configurations complete, regardless of any changes/updates in " "conversion, whenever those designated pricelists are applied to a customer " "trying to purchase this specific product, these pre-determined set prices " "appear." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:236 msgid ":doc:`./pricing`" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:3 msgid "Pricelists, discounts, and formulas" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:5 msgid "" "Odoo *Sales* has a useful pricelist feature that can be tailored to fit any " "unique pricing strategy." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:7 msgid "" "A *pricelist* is a list of prices (or price rules) that Odoo uses to " "determine the appropriate price for a customer. These pricelists can be set " "with specific criteria (such as time periods, minimum quantity sold, and " "more) in order to apply certain prices or discounts." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:11 msgid "" "Pricelists suggest certain prices, but they can always be overridden on the " "sales order." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:14 msgid "Pricing strategy options" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:16 msgid "" "To choose a pricing strategy, first navigate to :menuselection:`Sales app " "--> Configuration --> Settings`. In the :guilabel:`Pricing` section, click " "the checkbox next to the :guilabel:`Pricelists` feature." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20 msgid "" "Doing so reveals two additional options beneath it: :guilabel:`Multiple " "prices per product` and :guilabel:`Advanced price rules (discounts, " "formulas)`. A link labeled :guilabel:`Pricelists` also appears, which leads " "to a separate pricelists page, wherein pricelists can be created and/or " "modified." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:25 msgid "" ":guilabel:`Multiple prices per product`: provides the option to set several " "different prices per product." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:27 msgid "" ":guilabel:`Advanced price rules (discounts, formulas)`: provides the option " "to create detailed price rules and apply discounts, margins, and roundings." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "How the pricelist feature setting looks in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:34 msgid "" "After clicking the checkbox beside the :guilabel:`Pricelists` feature, " "select one of those two options, then click :guilabel:`Save` to save all " "changes." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:40 msgid "" "After activating and saving the :guilabel:`Pricelists` feature, the " ":guilabel:`Settings` page reloads and, from here, either select the " ":guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on " "the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app -->" " Products --> Pricelists`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:430 msgid "" "Either option reveals the :guilabel:`Pricelists` page, in which pricelists " "can be created and/or modified at any time." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "How the pricelists page looks in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:53 msgid "" "The order of the pricelists on the :guilabel:`Pricelists` page has an impact" " on how they are applied. If several pricelists share the same criteria, " "**only** the first listed pricelist is applied." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:57 msgid "" "For example, for two pricelists with different rules, but same criteria " "(e.g., same website, same country), only the *first* pricelist in the list " "is applied." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:61 msgid "" "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo " "*Sales* and *eCommerce*. This pricelist is applied by default, if there are " "no matching criteria." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:65 msgid "" "In Odoo 17 (and above), it is no longer required to have a pricelist entered" " in the :guilabel:`Pricelist` field on a quotation form in order to confirm " "it (i.e. turn it into a sales order)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:69 msgid "" "It should also be noted that, in Odoo 17 (and above), a chatter section can " "be found on pricelist forms, which enhances the ability to communicate about" " them." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:72 msgid "" "From the :guilabel:`Pricelists` page, either select the desired pricelist to" " edit, or click :guilabel:`New` to create a new pricelist, which reveals a " "blank pricelist form that can be configured in a number of different ways." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "How the pricelist detail form looks in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:80 msgid "" "When creating a new pricelist, start by adding a name for the pricelist at " "the top of the form, in the blank field. Next, select which " ":guilabel:`Currency` should be used." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:83 msgid "" "Then, if working in a multi-company environment, select which company this " "pricelist should apply to in the :guilabel:`Company` field. If this field is" " left blank, the pricelist is automatically applied to all companies in the " "database." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:88 msgid "Price Rules tab" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:90 msgid "" "The :guilabel:`Price Rules` tab functionality on a pricelist form varies " "depending on the :guilabel:`Pricelists` setting chosen: either " ":guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules " "(discounts, formulas)`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:94 msgid "" "However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` " "tab are always the same, regardless of the chosen :guilabel:`Pricelists` " "setting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:100 msgid "" "With the :guilabel:`Multiple prices per product` setting activated, the " ":guilabel:`Price Rules` tab on pricelist forms provides the option to add " "specific products, with a specific price, to a pricelist." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:104 msgid "" "To add a specific product and price to a pricelist form, click the " ":guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the " ":guilabel:`Products` column. Then, select the desired product for which a " "specific price should be applied." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:108 msgid "" "Next, if necessary, select a product variant under the :guilabel:`Variants` " "column (e.g. a specific product size, color, etc.). If no variants are " "selected, then this price will apply to all variants of the product." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:112 msgid "" "If a minimum amount of the product must be purchased in order to apply the " "specific price, enter the amount under the :guilabel:`Min. Quantity` column." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:115 msgid "" "To configure the price of the product for this specific pricelist, enter the" " desired amount under the :guilabel:`Price` column. Then, there is the " "option to add a :guilabel:`Start Date` and :guilabel:`End Date` to the " "configured product price, if desired." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119 msgid "" "To add another product line, click :guilabel:`Add a line` again, and repeat " "the process. There is no limit to how many products can be added in the " ":guilabel:`Price Rules` tab of a pricelist form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:122 msgid "" "For more information, check out the following section: :ref:`Multiple prices" " per product `." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128 msgid "" "With the :guilabel:`Advanced price rules (discounts, formulas)` setting " "activated, the :guilabel:`Price Rules` tab on pricelist forms provides the " "option to configure detailed price rules based on formulas." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:132 msgid "" "Check out the :ref:`Advanced price rules (discounts, formulas) " "` section for detailed steps on how to add " "advanced price rules to a pricelist." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:136 msgid "Recurring Prices tab" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:138 msgid "" "Recurring prices are specifically used with :doc:`subscription products " "<../../../subscriptions/products>`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:141 msgid "" "Under the :guilabel:`Recurring Prices` tab, the same functionality of the " ":guilabel:`Price Rules` tab is present. The only difference being that a " "recurring time period can be applied in the :guilabel:`Recurring Plan` " "column." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145 msgid "" "Once :guilabel:`Products` and/or :guilabel:`Product Variants` are selected, " "click :guilabel:`Add a price rule`, and select the blank field in the " ":guilabel:`Recurring Plan` column to reveal a drop-down menu of pre-" "designated recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:149 msgid "" "New recurrence periods can also be created from this column. To do so, type " "in the name for the new :guilabel:`Recurring Plan`, then select " ":guilabel:`Create` from the resulting drop-down menu to create the time " "period, which can be edited later." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:153 msgid "" "Or, select :guilabel:`Create and edit...` to reveal a :guilabel:`Create " "Recurring Plan` pop-up form. From this pop-up form, the new recurrence " "period can be configured, with specific :guilabel:`Details`, " ":guilabel:`Self-Service`, and :guilabel:`Pricing` options. When the " "configurations are complete, click the :guilabel:`Save & Close` button." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "Custom time period pop-up form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:162 msgid "" "Lastly, add the desired price for this recurring price rule in the " ":guilabel:`Recurring Price` column." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:166 msgid ":doc:`../../../subscriptions`" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:169 msgid "Rental rules tab" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:171 msgid "" "Under the :guilabel:`Rental rules` tab, specific price rules can be " "configured for various rental products, using the same methodology as the " ":guilabel:`Price Rules` and :guilabel:`Recurring Prices` tabs." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:175 msgid "" "To add a rental rule, click :guilabel:`Add a line`, and select a desired " "product in the :guilabel:`Products` column. Then, select any specific " ":guilabel:`Variants`, if necessary." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:178 msgid "" "Next, designate a :guilabel:`Period` of time for the rental rule (e.g. " "`Daily`, `Hourly`, etc.)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:180 msgid "" "Lastly, configure a :guilabel:`Price` for the rental rule in the respective " "column." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:183 msgid "Configuration tab" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:185 msgid "" "Under the :guilabel:`Configuration` tab, there are a few options that can " "further customize the pricelist." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "Configuration tab on pricelist detail form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:192 msgid "" "From here, under the :guilabel:`Availability` section, in the " ":guilabel:`Country Groups` field, certain country groups can be added to the" " pricelist. There is no limit to how many country groups can be added in " "this field." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:197 msgid "" "If no country is set for a customer, Odoo takes the first pricelist without " "any country group." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:199 msgid "" "Under the :guilabel:`Website` section, there are a few options that can be " "configured. In the :guilabel:`Website` field, this pricelist can be applied " "to a specific website, if working in a multi-website environment. If left " "blank, the pricelist is applied to all websites in the database." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:203 msgid "" "Tick the :guilabel:`Selectable` checkbox to have this pricelist as a " "selectable option for customers to choose as they shop. If the " ":guilabel:`Selectable` box is left unticked, customers **cannot** select " "this pricelist for themselves." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:207 msgid "" "Lastly, there is the option to add an :guilabel:`E-commerce Promotional " "Code`. To add a code, type in the desired promo code that, when entered " "during the checkout process, applies the pricelist to the customer, even if " "the customer does not fall into the previously-specified criteria." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:211 msgid "" "Then, in the :guilabel:`Discounts` section, there is a :guilabel:`Discount " "Policy` field with two options to choose from: :guilabel:`Discount included " "in the price` or :guilabel:`Show public price & discount to the customer`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:215 msgid "" "If :guilabel:`Discount included in the price` is selected, the price shown " "to the customer already accounts for the discount being applied. However, if" " :guilabel:`Show public price & discount to the customer` is selected, the " "customer sees the actual public price *and* how much they are saving with " "this pricelist discount." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:221 msgid "Customer pricelist application" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:223 msgid "" "While the default pricelist applied to any customer is the :guilabel:`Public" " Pricelist`, Odoo provides the opportunity to directly apply a different " "pricelist to customers on their contact form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:226 msgid "" "To do that, open the desired customer's contact form, either by navigating " "to :menuselection:`Sales app --> Orders --> Customers` and selecting the " "customer from the main :guilabel:`Customers` page, or by clicking on the " "customer's name on a sales order." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "Sample customer detail form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234 msgid "" "On the desired customer's contact form, under the :guilabel:`Sales & " "Purchase` tab, in the :guilabel:`Sales` section, designate what pricelist " "should be applied to this specific customer from the drop-down menu in the " ":guilabel:`Pricelist` field." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "The pricelist field in a customer detail form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:243 msgid "" "When a customer is added to the database, the default pricelist is " "automatically applied to them. There is **no way** to have a blank " "*Pricelist* field on a contact form. Even if that field is left blank, the " "default pricelist appears when that contact form is opened again." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:247 msgid "" "However, when that contact is added to a quotation, and the *Pricelist* " "field is auto-populated (based on the information from their contact form), " "that predetermined pricelist can be removed from the *Pricelist* field, and " "the quotation can still be confirmed, and subsequently, turned into a sales " "order." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:257 msgid "" "To apply several prices per individual product, select the " ":guilabel:`Multiple prices per product` option, after enabling the " ":guilabel:`Pricelists` feature on the *Sales* app setting page " "(:menuselection:`Sales app --> Configuration --> Settings`), and click " ":guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:261 msgid "" "Next, apply pricelists to specific products using the product form. Navigate" " to the :menuselection:`Sales app --> Products --> Products` and select the " "product for which multiple prices should be applied. Selecting a product " "from the :guilabel:`Products` page reveals that specific product's product " "form on a separate page." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:266 msgid "" "On the product form, click the :guilabel:`Extra Prices` smart button, " "located at the top of the form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "How the extra prices smart button appears in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:273 msgid "" "Doing so reveals a separate page displaying the :guilabel:`Price Rules` that" " are specific to that particular product. Here, price rules can be edited or" " created at any time." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "How the extra price rules per product page appears in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 msgid "" "To create a new price rule for a product from this specific :guilabel:`Price" " Rules` page, click :guilabel:`New` to add a new, customizable row that has " "the desired product already populated in the :guilabel:`Applied On` column." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:284 msgid "" "Next, select which :guilabel:`Pricelist` this specific product price rule " "should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 msgid "" "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo " "*Sales* and *eCommerce*." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:291 msgid "" "To create a new pricelist from this page, type in the desired name of the " "new pricelist in the :guilabel:`Pricelist` column, then select " ":guilabel:`Create` from the drop-down menu. All pricelists can be modified " "at any time, by navigating to :menuselection:`Sales app --> Products --> " "Pricelists`. Pricelists can also be created on that specific " ":guilabel:`Pricelists` page, as well." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:297 msgid "" "After the desired pricelist is added to the row, designate a :guilabel:`Min." " Quantity` for the price rule." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:301 msgid "" "If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the " ":guilabel:`Price` column will be applied to orders of 2 or more products. " "So, in theory, if a single product costs $100, customers can be encouraged " "to buy more, if the :guilabel:`Price` is set at $85 per product for a " ":guilabel:`Min. Quantity` of `2` products." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:306 msgid "" "Next, enter the desired amount in the :guilabel:`Price` column. Then, if " "needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the " "product's price rule." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:309 msgid "" "And lastly, if working in a multi-company environment, select which company " "this price rule should be applied to in the :guilabel:`Company` field. " "Leaving this field blank means the price rule applies for all companies in " "the database." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:313 msgid "" "Click away from the row to activate Odoo's auto-save capability, meaning " "that newly-created price rule is now ready to be used." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:316 msgid "" "Proceed to add as many unique price rules per product as desired. There is " "no limit to how many price rules can be added per product." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:319 msgid "" "With the price rule(s) in place for a specific product, customers who fall " "into those corresponding pricelists automatically see those new prices " "applied. The number of price rules applied to a particular product are also " "displayed in the :guilabel:`Extra Prices` smart button, located on every " "product form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:325 msgid "" "When a price rule/pricelist is added to a product via the :guilabel:`Extra " "Prices` smart button, it is also reflected on the pricelist itself. " "Similarly, when a price rule for a specific product is added to a pricelist," " it is also reflected on the product form via the :guilabel:`Extra Prices` " "smart button." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:335 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:338 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:346 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:350 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:356 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:365 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:369 msgid "Discount button" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:371 msgid "" "In Odoo 17, with the :ref:`Discounts setting ` enabled, a " ":guilabel:`Discount` button appears at the bottom of sales orders." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "" "The discount button located at the bottom of a sales order form in the Odoo " "Sales app." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:378 msgid "" "When the :guilabel:`Discount` button on a sales order is clicked, a " ":guilabel:`Discount` pop-up window appears." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:381 msgid "" "On this pop-up window, configure the :guilabel:`Discount` percentage, and " "select one of the following discount options: :guilabel:`On All Order " "Lines`, :guilabel:`Global Discount`, or :guilabel:`Fixed Amount`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 msgid "" ":guilabel:`On All Order Lines`: When selected, Odoo provides the ability to " "add the specified discount percentage (configured in the " ":guilabel:`Discount` field of the pop-up window) on all existing order lines" " of the sales order." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 msgid "" ":guilabel:`Global Discount`: When selected, Odoo adds a discount product to " "the order, which has the cumulative value equivalent to the specified " "discount percentage (configured in the :guilabel:`Discount` field of the " "pop-up window). Any product added (or removed) *after* the discount is added" " does **not** affect the discount value on the order line." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:394 msgid "" "In this example, since the total of the order is $600, and there is a 30% " "global discount, that specific line is added to the sales order with a -180 " "value (which is 30% of $600)." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 msgid "" "The sales order with the applied global discount option in the Odoo Sales " "application." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:401 msgid "" ":guilabel:`Fixed Amount`: When selected, the percentage designation in the " ":guilabel:`Discount` field turns to a monetary value (e.g. dollars), wherein" " a specific amount must be entered. This configured value is added as a " "discount line on the sales order." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 msgid "" "It is more beneficial to add a :guilabel:`Fixed Amount` discount after " "**all** desired products have been added to a sales order. If there are " "changes made to the sales order *after* the discount is added, make sure to " "change the value on the :guilabel:`Discount` line, or remove the line and " "add the discount again." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 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:420 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:425 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:433 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:436 msgid "" "On the pricelist form, under the :guilabel:`Price Rules` tab, click " ":guilabel:`Add a line` to add an advanced price rule. Doing so reveals a " ":guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule " "is configured." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:445 msgid "Price computation" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:447 msgid "" "On this form, first choose one of the three :guilabel:`Computation` options:" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:449 msgid "" ":guilabel:`Fixed Price`: the price computation is based on a fixed price." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:450 msgid ":guilabel:`Discount`: the price computation is based on a discount." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:451 msgid ":guilabel:`Formula`: the price computation is based on a formula." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:454 msgid "" "Each :guilabel:`Computation` option reveals its own computation-specific " "fields on the form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:456 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:460 msgid "" "If :guilabel:`Formula` is selected, a number of configurable options appear." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 msgid "The various formula computation options present in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:466 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:470 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:474 msgid "" "To formulate a 100% markup (or 2 times the cost of the product), with a $5 " "minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the " ":guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is " "often seen in retail situations." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 msgid "" "How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo" " Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:482 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:487 msgid "Rounding is applied *after* the discount and *before* the surcharge." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:490 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:493 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:495 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:499 msgid "" "To apply 20% discounts, with prices rounded up to 9.99, set the " ":guilabel:`Based on` field to :guilabel:`Sales Price`, the " ":guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to " "`-0.01`, and the :guilabel:`Rounding Method` field to `10`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:508 msgid "Conditions" msgstr "Pogoji" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:510 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:513 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:515 msgid "" ":guilabel:`All Products`: the advanced pricelist rule will be applied to all" " products." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:516 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:518 msgid "" ":guilabel:`Product`: the advanced pricelist rule will be applied to a " "specific product." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:519 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:522 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:526 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:530 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:535 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:539 msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:540 msgid ":doc:`/applications/websites/ecommerce/products/price_management`" msgstr "" #: ../../content/applications/sales/sales/products_prices/products.rst:5 msgid "Manage your products" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:3 msgid "Import products" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:5 msgid "" "Odoo *Sales* provides a template for importing products with categories and " "variants, which can be opened and edited with any spreadsheet software " "(Microsoft Excel, OpenOffice, Google Sheets, etc.)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:8 msgid "" "When this spreadsheet is filled out properly, it can be quickly uploaded to " "the Odoo database. When uploaded, those products are instantly added, " "accessible, and editable in the product catalog." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:12 msgid "Import template" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:14 msgid "" "In order to import products with categories and variants, the *Import " "Template for Products* **must** be downloaded. Once downloaded, the template" " can be adjusted and customized, and then uploaded back into the Odoo " "database." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:18 msgid "" "To download the necessary import template, navigate to :menuselection:`Sales" " app --> Products --> Products`. On the :guilabel:`Products` page, click the" " :guilabel:`⚙️ (gear)` icon in the upper-left corner. Doing so reveals a " "drop-down menu." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:22 msgid "" "From this drop-down menu, select the :guilabel:`Import records` option." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "" "The Import records option selectable from the gear icon on the Products page" " in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:28 msgid "" "Selecting :guilabel:`Import records` reveals a separate page with a link to " "download the :guilabel:`Import Template for Products`. Click that link to " "download the template." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:35 msgid "" "Once the template download is complete, open the spreadsheet file to " "customize it." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:38 msgid "Customize product import template" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:40 msgid "" "When the import template has been downloaded and opened, it's time to modify" " its contents. However, before any changes are made, there are a few " "elements to keep in mind during the process:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:43 msgid "" "Feel free to remove any columns that aren't deemed necessary. But, it is " "*strongly* advised that the :guilabel:`Internal Reference` column remains." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:46 msgid "" "While it's not mandatory, having a unique identifier (e.g. `FURN_001`) in " "the :guilabel:`Internal Reference` column for each product can be helpful in" " many cases. This can even be from previous software spreadsheets to ease " "the transition into Odoo." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:50 msgid "" "For example, when updating imported products, the same file can be imported " "several times without creating duplicates, thus enhancing the efficiency and" " simplicity of imported product management." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:52 msgid "" "Do **not** change the labels of columns that are meant to be imported. " "Otherwise, Odoo won't recognize them, forcing the user to map them on the " "import screen manually." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:54 msgid "" "Feel free to add new columns to the template spreadsheet, if desired. " "However, to be added, those fields **must** exist in Odoo. If Odoo can't " "match the column name with a field, it can be matched manually during the " "import process." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:58 msgid "" "During the import process of the completed template, Odoo reveals a page " "showcasing all the elements of the newly-configured product template " "spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, " "and :guilabel:`Comments`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:62 msgid "" "To manually match a column name with a field in Odoo, click the " ":guilabel:`Odoo Field` drop-down menu next to the :guilabel:`File Column` " "that needs a manual adjustment, and select the appropriate field from that " "drop-down menu." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:0 msgid "" "The Odoo Field drop-down menu next to a Field Column that needs to be " "manually adjusted." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:71 msgid "Import product template spreadsheet" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:73 msgid "" "After customizing the product template spreadsheet, return to the Odoo " "product import page, where the template download link is found, and click " "the :guilabel:`Upload File` button in the upper-left corner." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "" "The upload file button on the import products template download page in Odoo" " Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:81 msgid "" "Then, a pop-up window appears, in which the completed product template " "spreadsheet file should be selected and uploaded to Odoo." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:84 msgid "" "After that, Odoo reveals a page showcasing all the elements of the newly-" "configured product template spreadsheet, separated by :guilabel:`File " "Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "" "The import a file page in Odoo Sales after a product template has been " "uploaded." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:91 msgid "" "From here, the :guilabel:`File Column` can be manually assigned to an " ":guilabel:`Odoo Field`, if necessary." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:94 msgid "" "To make sure everything is appropriate, and all the columns and fields are " "lined up accurately, click the :guilabel:`Test` button in the upper-left " "corner." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:97 msgid "" "If everything is lined up and applied correctly, Odoo reveals a blue banner " "at the top of the page, informing the user that :guilabel:`Everything seems " "valid`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "" "The everything seems valid message that appears if file columns are entered " "correctly." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:104 msgid "" "If there are any errors, Odoo reveals a red banner at the top of the page, " "with instructions of where to locate the specific issues, and how to fix " "them." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "" "The import error message that appears if file columns don't match an Odoo " "Field." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:111 msgid "" "Once those errors are fixed, click :guilabel:`Test` again to ensure all " "necessary issues have been remedied appropriately." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:114 msgid "" "If additional product template spreadsheets need to be uploaded, click the " ":guilabel:`Load File` button, select the desired product template " "spreadsheet, and repeat the process." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:117 msgid "When everything is ready, click the :guilabel:`Import` button." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:119 msgid "" "When clicked, Odoo instantly imports those products, and reveals the main " ":guilabel:`Products` page, with a pop-up message in the upper-right corner. " "This pop-up message informs the user how many products were successfully " "imported." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "" "The pop-up window that appears after a successful product import process in " "Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:127 msgid "" "At this point, all the newly-imported products are accessible and editable " "via the :guilabel:`Products` page." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:131 msgid "Import relation fields, attributes, and variants" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:133 msgid "" "It's important to note that an Odoo object is always related to many other " "objects. For example, a product is linked to product categories, attributes," " vendors, and things of this nature. These links/connections are known as " "relations." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:138 msgid "" "In order to import product relations, the records of the related object " "**must** be imported *first* from their own list menu." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:142 msgid "Relation fields" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:144 msgid "" "On product forms in Odoo, there are a number of fields that can be modified " "and customized at any time. These fields are found under every tab on a " "product form. While these fields are easily editable directly on the product" " form, they can also be modified via a product import." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:148 msgid "" "As mentioned, relation fields of this nature can **only** be imported for " "products if they already exist in the database. For example, if a user " "attempts to import a product with a *Product Type*, it can only be one of " "the preconfigured product types existing in the database (e.g. *Storable " "Product*, *Consumable*, etc.)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:153 msgid "" "To import information for a relation field on a product import template " "spreadsheet, add the name of the field as a column name/title on the " "spreadsheet. Then, on the appropriate product line, add the desired relation" " field option." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:157 msgid "" "When all desired relation field information has been entered, save the " "spreadsheet, and import it to the database, per the process mentioned above " "(:menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> " "Import records --> Upload File`)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:161 msgid "" "Once the spreadsheet with the newly-configured relation field information " "has been uploaded, click :guilabel:`Import`, and Odoo returns to the " ":guilabel:`Products` page." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:164 msgid "" "When the newly-changed/modified products, complete with the new relation " "field information, has been imported and uploaded, that new information can " "be found on the :guilabel:`Products` page." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:168 msgid "Attributes and values" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:170 msgid "" "Odoo also allows users to import product attributes and values that can be " "used for products that already exist in the database, and/or with imported " "products." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:173 msgid "" "To import attributes and values, a separate spreadsheet or CSV file " "dedicated to attributes and values **must** be imported and uploaded before " "they can be used for other products." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:176 msgid "" "The column names/titles of the attributes and values spreadsheet should be " "as follows: :guilabel:`Attribute`, :guilabel:`Display Type`, " ":guilabel:`Variant Creation Mode`, and :guilabel:`Values / Value`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "An attributes and values spreadsheet template for imports." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:184 msgid ":guilabel:`Attribute`: name of the attribute (e.g. `Size`)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:185 msgid "" ":guilabel:`Display Type`: display type used in the product configurator. " "There are three display type options:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:188 msgid ":guilabel:`Radio`: values displayed as radio buttons" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:189 msgid ":guilabel:`Selection`: values displayed in a selection list" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:190 msgid ":guilabel:`Color`: values denoted as a color selection" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:192 msgid "" ":guilabel:`Variant Creation Mode`: how the variants are created when applied" " to a product. There are three variant creation mode options:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:195 msgid "" ":guilabel:`Instantly`: all possible variants are created as soon as the " "attribute, and its values, are added to a product" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:197 msgid "" ":guilabel:`Dynamically`: each variant is created **only** when its " "corresponding attributes and values are added to a sales order" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:199 msgid ":guilabel:`Never`: variants are **never** created for the attribute" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:202 msgid "" "The :guilabel:`Variants Creation Mode` **cannot** be changed once the " "attribute is used on at least one product." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:205 msgid "" ":guilabel:`Values/Value`: values pertaining to the corresponding attribute. " "If there are multiple values for the same attribute, the values need to be " "in individual lines on the spreadsheet." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:208 msgid "" "Once the desired attributes and values have been entered and saved in the " "spreadsheet, it's time to import and upload it into Odoo. To do that, " "navigate to :menuselection:`Sales app --> Configuration --> Attributes --> " "⚙️ (gear) icon --> Import records --> Upload File`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:212 msgid "" "Once the spreadsheet with the newly-configured attributes and values has " "been uploaded, click :guilabel:`Import`, and Odoo returns to the " ":guilabel:`Attributes` page. That's where those newly-added attributes and " "values can be found and edited, if necessary." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:216 msgid "" "As mentioned previously, when attributes and values have been added to the " "Odoo database, they can be used for existing or imported products." 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:181 msgid "Product variants" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:222 msgid "" "When product attributes and values are configured in the database, they can " "be used on product import spreadsheets to add more information and detail to" " products being imported." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:225 msgid "" "To import products with product attributes and values, the product import " "template spreadsheet must be configured with specific :guilabel:`Product " "Attributes / Attribute`, :guilabel:`Product Attributes / Values`, and " ":guilabel:`Name` columns." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:229 msgid "" "There can be other columns, as well, but these columns are **required** in " "order to properly import products with specific variants." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst-1 msgid "" "Product variants spreadsheet with product attributes and variants for import" " purposes." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:236 msgid ":guilabel:`Name`: product name" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:237 msgid ":guilabel:`Product Attributes / Attribute`: name of attribute" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:238 msgid "" ":guilabel:`Product Attributes / Values`: values pertaining to the " "corresponding attribute" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:241 msgid "" "To import multiple values, separate them by *just* a comma, **not** a comma " "followed by a space, in the product import template spreadsheet (e.g. " "`furniture,couch,home`)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:244 msgid "" "When the desired products and product variants have been entered and saved " "in the spreadsheet, it's time to import and upload them into Odoo. To do " "that, navigate to :menuselection:`Sales app --> Products --> Products --> ⚙️" " (gear) icon --> Import records --> Upload File`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:248 msgid "" "Once the spreadsheet with the newly-configured products and product variants" " has been uploaded, click :guilabel:`Import`, and Odoo returns to the " ":guilabel:`Products` page. That's where the newly-added products can be " "found." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:252 msgid "" "To view and modify the attributes and variants on any products, select the " "desired product from the :guilabel:`Products` page, and click the " ":guilabel:`Attributes \\& Variants` tab." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:256 msgid ":doc:`variants`" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3 msgid "Product images with Google Images" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5 msgid "" "Having appropriate product images in Odoo is useful for a number of reasons." " However, if a lot of products need images, assigning them can become " "incredibly time-consuming." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:8 msgid "" "Fortunately, by configuring the *Google Custom Search* API within an Odoo " "database, finding product images for products (based on their barcode) is " "extremely efficient." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:16 msgid "" "In order to utilize *Google Custom Search* within an Odoo database, both the" " database and the Google API must be properly configured." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:20 msgid "" "Free Google accounts allow users to select up to 100 free images per day. If" " a higher amount is needed, a billing upgrade is required." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:26 msgid "Google API dashboard" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28 msgid "" "Go to the `Google Cloud Platform API & Services " "`_ page to generate Google Custom " "Search API credentials. Then, log in with a Google account. Next, agree to " "their :guilabel:`Terms of Service` by checking the box, and clicking " ":guilabel:`Agree and Continue`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:32 msgid "" "From here, select (or create) an API project to store the credentials. Start" " by giving it a memorable :guilabel:`Project Name`, select a " ":guilabel:`Location` (if any), then click :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:35 msgid "" "With the :guilabel:`Credentials` option selected in the left sidebar, click " ":guilabel:`Create Credentials`, and select :guilabel:`API key` from the " "drop-down menu." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "API & Services page on Google Cloud Platform." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:42 msgid "" "Doing so reveals an :guilabel:`API key created` pop-up window, containing a " "custom :guilabel:`API key`. Copy and save :guilabel:`Your API key` in the " "pop-up window -- it will be used later. Once the key is copied (and saved " "for later use), click :guilabel:`Close` to remove the pop-up window." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "The API key created pop-up window that appears." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:50 msgid "On this page, search for `Custom Search API`, and select it." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 msgid "" "From the :guilabel:`Custom Search API` page, enable the API by clicking " ":guilabel:`Enable`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "" "\"Custom Search API\" page with Enable button highlighted on Google Cloud " "Platform." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:65 msgid "Google Programmable Search dashboard" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:67 msgid "" "Next, go to `Google Programmable Search Engine " "`_, and click either of the " ":guilabel:`Get started` buttons. Log in with a Google account, if not " "already logged in." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "Google Programmable Search Engine page with the Get Started buttons." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:75 msgid "" "On the :guilabel:`Create a new search engine` form, fill out the name of the" " search engine, along with what the engine should search, and be sure to " "enable :guilabel:`Image Search` and :guilabel:`SafeSearch`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "" "Create new search engine form that appears with search engine " "configurations." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 msgid "Validate the form by clicking :guilabel:`Create`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:84 msgid "" "Doing so reveals a new page with the heading: :guilabel:`Your new search " "engine has been created`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "" "The Your New Search Engine Has Been Created page that appears with copy " "code." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:91 msgid "" "From this page, click :guilabel:`Customize` to open the " ":menuselection:`Overview --> Basic` page. Then, copy the ID in the " ":guilabel:`Search engine ID` field. This ID is needed for the Odoo " "configuration." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "Basic overview page with search engine ID field." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 msgid "" "In the Odoo database, go to the :menuselection:`Settings app` and scroll to " "the :guilabel:`Integrations` section. From here, check the box beside " ":guilabel:`Google Images`. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "The Google Images setting in the Odoo Settings app page." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:112 msgid "" "Next, return to the :menuselection:`Settings app`, and scroll to the " ":guilabel:`Integrations` section. Then, enter the :guilabel:`API Key` and " ":guilabel:`Search Engine ID` in the fields beneath the :guilabel:`Google " "Images` feature." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:115 msgid "Click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 msgid "Product images in Odoo with Google Custom Search API" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:122 msgid "" "Adding images to products in Odoo can be done on any product or product " "variant. This process can be completed in any Odoo application that provides" " access to product pages (e.g. *Sales* app, *Inventory* app, etc.)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:126 msgid "" "Below is a step-by-step guide detailing how to utilize the *Google Custom " "Search API* to assign images to products in Odoo using the Odoo *Sales* " "application:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:129 msgid "" "Navigate to the :guilabel:`Products` page in the *Sales* app " "(:menuselection:`Sales app --> Products --> Products`). Or, navigate to the " ":guilabel:`Product Variants` page in the *Sales* app (:menuselection:`Sales " "app --> Products --> Product Variants`)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:132 msgid "Select the desired product that needs an image." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:135 msgid "" "Only products (or product variants) that have a barcode, but **not** an " "image, are processed." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:137 msgid "" "If a product with one or more variants is selected, each variant that " "matches the aforementioned criteria is processed." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:140 msgid "" "Click the :guilabel:`Action ⚙️ (gear)` icon on the product page, and select " ":guilabel:`Get Pictures from Google Images` from the menu that pops up." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "" "The Get Pictures from Google Images option from the Action drop-down menu in" " Odoo." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:147 msgid "On the pop-up window that appears, click :guilabel:`Get Pictures`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 msgid "" "The pop-up that appears in which the user should click Get Picture in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:153 msgid "Once clicked, the image(s) will appear incrementally." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:156 msgid "" "Only the first 10 images are fetched immediately. If you selected more than " "10, the rest are fetched as a background job." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:159 msgid "" "The background job processes about 100 images in a minute. If the quota " "authorized by Google (either with a free or a paid plan) is reached, the " "background job puts itself on hold for 24 hours. Then, it will continue " "where it stopped the day before." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:164 msgid "" "`Create, modify, or close your Google Cloud Billing account " "`_" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 msgid "" "Product variants are used to give single products a variety of different " "characteristics and options for customers to choose from, such as size, " "style, or color, just to name a few." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:8 msgid "" "Products variants can be managed via their individual product template, or " "by navigating to either the :guilabel:`Product Variants` or " ":guilabel:`Attributes` page. All of these options are located within the " "Odoo *Sales* application." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:13 msgid "" "An apparel company has the following variant breakdown for one their best-" "selling t-shirts:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:15 msgid "Unisex Classic Tee" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:17 msgid "Color: Blue, Red, White, Black" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:18 msgid "Size: S, M, L, XL, XXL" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:20 msgid "" "Here, the **T-shirt** is the product template, and **T-shirt: Blue, S** is a" " specific product variant." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 msgid "" "**Color** and **Size** are *attributes*, and the corresponding options (like" " **Blue** and **S**) are *values*." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:26 msgid "" "In this instance, there is a total of twenty different product variants: " "four **Color** options multiplied by five **Size** options. Each variant has" " its own inventory count, sales totals, and other similar records in Odoo." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:31 msgid ":doc:`/applications/websites/ecommerce/products/variants`" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:36 msgid "" "To use product variants, the *Variants* setting **must** be activated in the" " Odoo *Sales* application." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:39 msgid "" "To do that, go to :menuselection:`Sales app --> Configuration --> Settings`," " and locate the :guilabel:`Product Catalog` section at the top of the page." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:42 msgid "" "In that section, check the box to enable the :guilabel:`Variants` feature." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 msgid "" "Activating product variants on the Settings page of the Odoo Sales " "application." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:48 msgid "" "Then, click :guilabel:`Save` at the top of the :guilabel:`Settings` page." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:51 msgid "Attributes" msgstr "Lastnosti" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:53 msgid "" "Before product variants can be set up, attributes **must** be created. To " "create, manage, and modify attributes, navigate to :menuselection:`Sales app" " --> Configuration --> Attributes`." 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 *Product Configurator*, *Point of Sale* dashboard, and " "*eCommerce* pages." msgstr "" #: ../../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 "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 msgid "A blank attribute creation form in the Odoo Sales application." msgstr "" #: ../../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: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:73 msgid "The :guilabel:`Display Type` options are:" msgstr "" #: ../../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: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: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: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: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: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:99 msgid ":guilabel:`Never (option)`: never automatically creates variants." msgstr "" #: ../../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: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: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: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: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 "" "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 "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 "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 msgid "" "Attribute values tab when add a line is clicked, showing the custom columns." msgstr "" #: ../../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 "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 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: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: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: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: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: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:188 msgid "" "On the product form, click the :guilabel:`Attributes \\& Variants` tab to " "view, manage, and modify attributes and values for the product." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 msgid "The attributes and values tab on a typical product form in Odoo Sales." msgstr "" #: ../../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: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: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: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:214 msgid "There is no limit to how many values can be added." msgstr "" #: ../../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:221 msgid "Configure variants" msgstr "" #: ../../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 "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 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: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: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: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 "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 msgid "" "A Product Variant Values page accessible via the Product Variants Values " "general page." msgstr "" #: ../../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: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:252 msgid "Variants smart button" msgstr "" #: ../../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 "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 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: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 "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 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:270 msgid "Impact of variants" msgstr "" #: ../../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: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: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: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: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:288 msgid "" ":guilabel:`Picture`: each product variant can have its own specific picture." msgstr "" #: ../../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:294 msgid ":doc:`import`" msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:3 msgid "Returns and refunds" msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:5 msgid "" "The Odoo *Sales* app provides two different ways to process returns. The " "method used depends on whether or not an invoice has been sent." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:9 msgid "Before invoicing" msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:11 msgid "" "Returns are completed using *Reverse Transfers* when a customer decides to " "return a product **before** an invoice has been sent or validated." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:15 msgid "" "In order to use *Reverse Transfers*, the *Inventory* app **must** be " "installed." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:17 msgid "" "To start a return before invoicing, navigate to the :menuselection:`Sales` " "app, select the desired sales order, and click on the :guilabel:`Delivery` " "smart button to open the associated delivery order." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "" "A typical sales order with a highlighted delivery smart button in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:25 msgid "On the validated delivery order, click :guilabel:`Return`." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "" "A validated delivery order with a highlighted Return button in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:31 msgid "This opens a :guilabel:`Reverse Transfer` pop-up window." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:33 msgid "" "By default, the :guilabel:`Quantity` matches the validated quantities from " "the delivery order. Update the quantities, if necessary. Click on the " ":guilabel:`🗑️ (trash)` icon next to a line item to remove it from the " "return." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "" "The \"Reverse Transfer\" pop-up window, to make a return before invoicing " "the customer." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:41 msgid "" "Next, click :guilabel:`Return` to confirm the return. This generates a new " "warehouse operation for the incoming returned product(s)." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "Warehouse operation after a return has been confirmed in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:48 msgid "" "Upon receiving the return, the warehouse team validates the warehouse " "operation by clicking :guilabel:`Validate`. Then, on the original sales " "order, the :guilabel:`Delivered` quantity updates to reflect the difference " "between the initial validated quantities and the returned quantities." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "" "The updated \"Delivered\" quantity on the sales order after the reverse " "transfer." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:56 msgid "" "When an invoice is created, the customer receives an invoice **only** for " "the products they are keeping, if any." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:60 msgid "After invoicing" msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:62 msgid "" "Sometimes, customers return an item after they receive and/or pay for their " "invoice. In these cases, a return using only *Reverse Transfers* is " "insufficient since validated, or sent, invoices cannot be changed." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:66 msgid "" "However, *Reverse Transfers* can be used in conjunction with *Credit Notes* " "to complete the customer's return." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:69 msgid "" "To start a return after invoicing, navigate to the relevant sales order in " "the :menuselection:`Sales` app." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:72 msgid "" "If there is a payment registered on the sales order, the payment details " "appear in the chatter, and the invoice (accessible through the " ":guilabel:`Invoices` smart button) has a green :guilabel:`In Payment` " "banner." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "Sample of a green in payment banner in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:80 msgid "" "From the sales order, click on the :guilabel:`Delivery` smart button to view" " the validated delivery order. Then, click :guilabel:`Return` to open the " ":guilabel:`Reverse Transfer` pop-up window." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:83 msgid "" "Next, edit the :guilabel:`Product` and/or :guilabel:`Quantity`, as needed " "for the return. Then, click :guilabel:`Return`. This generates a new " "warehouse operation for the incoming returned product(s), which is validated" " by the warehouse team once the return is received by clicking " ":guilabel:`Validate`." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:88 msgid "" "Then, on the sales order, the :guilabel:`Delivered` quantity updates to " "reflect the difference between the initial validated quantities and the " "returned quantities." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:91 msgid "" "To process a refund, navigate to the relevant invoice (from the sales order," " click on the :guilabel:`Invoices` smart button). Then, click the " ":guilabel:`Credit Note` button at the top of the validated invoice." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "" "A typical customer invoice with a Credit Note button highlighted in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:99 msgid "Doing so reveals a :guilabel:`Credit Note` pop-up form." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst-1 msgid "Typical credit note pop-up form that appears in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:105 msgid "" "Start by entering a :guilabel:`Reason displayed on Credit Note` and a " "specific :guilabel:`Journal` to process the credit. Then, select a specific " ":guilabel:`Reversal Date`." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:108 msgid "" "After the information is filled in, click :guilabel:`Reverse` or " ":guilabel:`Reverse and Create Invoice`. Then, edit the draft, if needed." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:111 msgid "Lastly, click :guilabel:`Confirm` to confirm the credit note." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:113 msgid "" "When complete, a blue banner reading: :guilabel:`You have outstanding " "credits for this customer. You can allocate them to mark this invoice as " "paid.` appears at the top of the page." msgstr "" #: ../../content/applications/sales/sales/products_prices/returns.rst:117 msgid ":doc:`../../../finance/accounting/customer_invoices/credit_notes`" msgstr "" #: ../../content/applications/sales/sales/send_quotations.rst:5 msgid "Send Quotations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:3 msgid "Create quotations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:5 msgid "" "In Odoo **Sales**, quotations can be created and sent to customers. Once a " "quotation has been confirmed, it officially turns into a *sales order*, " "which can then be invoiced and paid for." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:11 msgid "Quotation settings" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:13 msgid "" "To access these setting options, navigate to :menuselection:`Sales app --> " "Configuration --> Settings`, and scroll to the :guilabel:`Quotations & " "Orders` section." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "The Quotations and Orders section on the Odoo Sales app Settings page." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:20 msgid "" ":guilabel:`Quotation Templates`: Enable this option to create quotation " "templates featuring standard product offers, which are then selectable on " "quotation forms. When this checkbox is ticked, an additional field, " ":guilabel:`Default Template`, appears, along with a link to the " ":guilabel:`Quotation Templates` page." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:24 msgid "" ":guilabel:`Online Signature`: Request an online signature to confirm orders." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:25 msgid "" ":guilabel:`Online Payment`: Request an online prepayment from customers to " "confirm orders. Request a full or partial payment (via down payment). When " "this checkbox is ticked, an additional field, :guilabel:`Prepayment amount " "(%)`, appears. There is also a link to the :guilabel:`Payment Providers` " "page." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:29 msgid "" ":guilabel:`Default Quotation Validity`: Determine a set amount (in " ":guilabel:`days`) that quotations can remain valid for." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:31 msgid "" ":guilabel:`Default Recurrence`: Select a default period from the drop-down " "menu to use as a recurrence period for a new quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:33 msgid "" ":guilabel:`Sale Warnings`: Get warning messages about orders that include " "specific products or customers." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:35 msgid "" ":guilabel:`PDF Quote builder`: Customize the look of quotations with header " "pages, product descriptions, footer pages, and more." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:37 msgid "" ":guilabel:`Lock Confirmed Sales`: Ensure no further edits can be made to " "confirmed orders." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:38 msgid ":guilabel:`Pro-Forma Invoice`: Send pro-forma invoices to customers." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:40 msgid "" "To activate any of these settings, tick the checkbox beside the desired " "option(s). Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:44 msgid "Quotations dashboard" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:46 msgid "" "The *Quotations* dashboard is the page that appears when the " ":menuselection:`Sales app` is opened." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:48 msgid "" "By default, the :guilabel:`Quotations` dashboard displays all quotations in " "the database related to the current user, as indicated by the default " ":guilabel:`My Quotations` filter present in the search bar." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "The Quotations dashboard present in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:57 msgid "" "To view *all* quotations in the database, remove the :guilabel:`My " "Quotations` filter from the search bar." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:60 msgid "" "Quotations on this page appear in a default list view, but can also be " "viewed in a :icon:`oi-view-kanban` :guilabel:`Kanban` view, :icon:`fa-" "calendar` :guilabel:`Calendar`, :icon:`oi-view-pivot` :guilabel:`Pivot` " "table, :icon:`fa-area-chart` :guilabel:`Graph`, or :icon:`fa-clock-o` " ":guilabel:`Activity` view." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:65 msgid "" "To view and/or modify any listed quotation from the :guilabel:`Quotations` " "dashboard, click on the desired quotation line from the list, and Odoo " "reveals the specific form for that selected quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:70 msgid "Create quotation" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:72 msgid "" "To create a quotation, open the :menuselection:`Sales app`, and click the " ":guilabel:`New` button, located in the upper-left corner of the main " ":guilabel:`Quotations` dashboard." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:76 msgid "" "The :guilabel:`New` button is **only** present if the :guilabel:`Quotations`" " dashboard is in list or Kanban view." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:79 msgid "" "Clicking the :guilabel:`New` button reveals a blank quotation form, with " "various fields and tabs to configure." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "A typical quotation form in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:86 msgid "" "Begin by entering the customer's name in the :guilabel:`Customer` field at " "the top of the form. This is a **required** field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:89 msgid "" "If the customer's information is already in the database, the " ":guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields auto-" "populate with the saved information for those respective fields, based on " "the data from that customer's contact record (found in the **Contacts** " "application)." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:94 msgid "" "If the customer was referred by another customer or contact, enter their " "name in the :guilabel:`Referrer` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:97 msgid "" "If a :guilabel:`Referrer` is selected, a new field, :guilabel:`Commission " "Plan` appears, in which a commission can be selected from the drop-down " "menu. This commission is rewarded to the contact selected in the " ":guilabel:`Referrer` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:101 msgid "" "Next, if they have not already been auto-populated with the customer's " "information, enter the appropriate addresses in the :guilabel:`Invoice " "Address` and :guilabel:`Delivery Address` fields. Both of these fields are " "**required**." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:105 msgid "" "Then, if desired, choose a :guilabel:`Quotation Template` from the drop-down" " field to apply to this quotation. It should be noted that some additional " "fields may appear, depending on the template selected." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:109 msgid "" "The default date that appears in the :guilabel:`Expiration` field is based " "on the number configured in the :ref:`Default Quotation Validity setting " "` (in :menuselection:`Sales app --> Configuration " "--> Settings`)." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:114 msgid "" "When using a quotation template, the date in the :guilabel:`Expiration` " "field is based off the :guilabel:`Quotation Validity` figure on the template" " form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:117 msgid "" "If the quotation is for a recurring product or subscription, select the " "desired :guilabel:`Recurring Plan` from that specific drop-down menu." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:120 msgid "" "If desired, select a specific :guilabel:`Pricelist` to be applied to this " "quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:122 msgid "" "Lastly, select any specific :guilabel:`Payment Terms` to be used for this " "quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:125 msgid "Order Lines tab" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:127 msgid "" "The first tab on the quotation form is the :guilabel:`Order Lines` tab." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:129 msgid "" "In this tab, select products, and quantities of those products, to add them " "to the quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:131 msgid "There are two ways to add products to the quotation from this tab." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:133 msgid "" "Click :guilabel:`Add a product`, select the desired item from the " ":guilabel:`Product` drop-down field, and proceed to adjust the quantity of " "that selected product, if necessary." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:136 msgid "" "Or, click :guilabel:`Catalog` to reveal a separate page, showcasing every " "item (and every potential product variant) in an organized catalog display, " "with items organizable by :guilabel:`Product Category` and " ":guilabel:`Attributes`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "" "A product catalog accessible via a quotation in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:144 msgid "" "From here, simply locate the desired items, click the :icon:`fa-shopping-" "cart` :guilabel:`Add` button on the product card, and adjust the quantity, " "if needed. When complete, click the :guilabel:`Back to Quotation` button in " "the upper-left corner to return to the quotation, where the newly-selected " "catalog items can be found in the :guilabel:`Order Lines` tab." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:149 msgid "" "If multiple items should be presented in a more organized way on the " "quotation, click :guilabel:`Add a section`, enter a name for the section, " "and drag-and-drop that section heading in the desired location amongst the " "items in the :guilabel:`Order Lines` tab. The section heading appears in " "bold." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:153 msgid "" "If needed, click :guilabel:`Add a note` beneath a certain product line to " "add a custom note about that specific product. The note appears in italics. " "Then, if needed, proceed to drag-and-drop the note beneath the desired " "product line." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:157 msgid "" "Beneath the product lines, there are buttons that can be clicked to apply " "any of the following: :guilabel:`Coupon Code`, :guilabel:`Promotions`, " ":guilabel:`Discount`, and/or :guilabel:`Add shipping`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:162 msgid ":doc:`../products_prices/ewallets_giftcards`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:163 msgid ":doc:`../products_prices/loyalty_discount`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:164 msgid ":doc:`../products_prices/prices/pricing`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:167 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:160 msgid "Optional Products tab" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:169 msgid "" "Open the :guilabel:`Optional Products` tab to select related products that " "can be presented to the customer, which may result in an increased sale." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:172 msgid "" "For example, if the customer wants to buy a car, an optional product that " "could be offered is a *Trailer Hitch*." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:176 msgid ":doc:`optional_products`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:179 msgid "Other Info tab" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:181 msgid "" "In the :guilabel:`Other Info` tab, there are various quotation-related " "configurations separated into four different sections: :guilabel:`Sales`, " ":guilabel:`Delivery`, :guilabel:`Invoicing`, and :guilabel:`Tracking`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:186 msgid "" "Some fields **only** appear if specific settings and options have been " "configured." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:189 msgid "Sales section" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:191 msgid "" "In the :guilabel:`Sales` section of the :guilabel:`Other Info` tab, there " "are sales specific fields that can be configured." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "" "The Sales section of the Other Info tab of a quotation form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:198 msgid "" ":guilabel:`Salesperson`: Assign a salesperson from the drop-down menu to be " "associated with this quotation. The user who originally created the " "quotation is selected in this field, by default." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:200 msgid "" ":guilabel:`Sales Team`: Assign a specific sales team to this quotation. If " "the selected :guilabel:`Salesperson` is a member of a sales team, that team " "is auto-populated in the field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:202 msgid "" ":guilabel:`Company`: Select a company from the drop-down menu this quotation" " should be associated with. This field only appears when working in a multi-" "company environment." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:204 msgid "" ":guilabel:`Online signature`: Tick this checkbox to request an online " "signature from the customer to confirm the order. This field only appears if" " the *Online Signature* setting has been enabled." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:206 msgid "" ":guilabel:`Online payment`: Tick this checkbox, and enter a desired " "percentage in the adjacent field, to request an online payment from the " "customer (for that designated percentage of the total amount) to confirm the" " order. This field only appears if the *Online Payment* setting has been " "enabled." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:210 msgid "" ":guilabel:`Customer Reference`: Enter a custom reference ID for this " "customer. The entered reference ID can contain letters, numbers, or a mix of" " both." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:212 msgid "" ":guilabel:`Tags`: Add specific tags to the quotation for added organization " "and enhanced searchability in the Odoo **Sales** application. Multiple tags " "can be added, if necessary." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:216 msgid "Delivery section" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:218 msgid "" "In the :guilabel:`Delivery` section of the :guilabel:`Other Info` tab, there" " are delivery-specific fields that can be configured." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "" "The Delivery section of the Other Info tab of a quotation form in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:225 msgid "" ":guilabel:`Shipping Weight`: Displays the weight of the items being shipped." " This field is not modifiable. Product weight is configured on individual " "product forms." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:227 msgid "" ":guilabel:`Incoterm`: Select an Incoterm (International Commerical Term) to " "use as predefined commerical terms for international transactions." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:229 msgid "" ":guilabel:`Incoterm Location`: If an Incoterm is being used, enter the " "international location in this field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:231 msgid "" ":guilabel:`Shipping Policy`: Select a desired shipping policy from the drop-" "down menu. If all products are delivered at once, the delivery order is " "scheduled, based on the greatest product lead time. Otherwise, it is based " "on the shortest lead time. The available options are: :guilabel:`As soon as " "possible` or :guilabel:`When all products are ready`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:235 msgid "" ":guilabel:`Delivery Date`: Click into the empty field to reveal a calendar " "popover, from which a customer delivery date can be selected. If no custom " "date is required, refer to the :guilabel:`Expected` date listed to the right" " of that field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:240 msgid "Invoicing section" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:242 msgid "" "In the :guilabel:`Invoicing` section of the :guilabel:`Other Info` tab, " "there are invoicing specific fields that can be configured." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "" "The Invoicing section of the Other Info tab of a quotation form in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:249 msgid "" ":guilabel:`Fiscal Position`: Select a fiscal position to be used to adapt " "taxes and accounts for particular customers or sales orders/invoices. The " "default value comes from the customer. If a selection is made in this field," " an :icon:`fa-refresh` :guilabel:`Update Taxes` clickable link and icon " "appear. When clicked, the taxes for this partiuclar customer and quotation " "are updated. A confirmation window appears, as well." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:254 msgid "" ":guilabel:`Analytic Account`: Select an analytic account to apply to this " "customer/quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:257 msgid "Tracking section" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:259 msgid "" "In the :guilabel:`Tracking` section of the :guilabel:`Other Info` tab, there" " are tracking specific fields that can be configured." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst-1 msgid "" "The Tracking section of the Other Info tab of a quotation form in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:266 msgid "" ":guilabel:`Source Document`: Enter the reference of the document that " "generated the quotation/sales order, if applicable." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:268 msgid "" ":guilabel:`Opportunity`: Select the specific opportunity (from the **CRM** " "app) related to this quotation, if applicable." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:270 msgid "" ":guilabel:`Campaign`: Select the marketing campaign related to this " "quotation, if applicable." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:271 msgid "" ":guilabel:`Medium`: Select the method by which this quotation originated " "(e.g. *Email*), if applicable." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:273 msgid "" ":guilabel:`Source`: Select the source of the link used to generate this " "quotation (e.g. *Facebook*), if applicable." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:277 msgid ":doc:`../../../websites/website/reporting/link_tracker`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:280 msgid "Notes tab" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:282 msgid "" "In the :guilabel:`Notes` tab of the quotation form, enter any specific " "internal notes about the quotation and/or customer, if desired." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:286 msgid "Sending and confirming quotations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:288 msgid "" "Once all the necessary fields and tabs have been configured, it is time to " "send the quotation to the customer for confirmation. Upon confirmation, the " "quotation turns into an official sales order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:291 msgid "At the top of the form, there is a series of buttons:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:293 msgid "" ":guilabel:`Send by Email`: When clicked, a pop-up window appears with the " "customer's name and email address in the :guilabel:`Recipients` field, the " "quotation (and reference ID) in the :guilabel:`Subject` field, and a brief " "default message in the body of the email, which can be modified, if needed." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:298 #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:306 msgid "" "Below that, a PDF copy of the quotation is attached. When ready, click " ":guilabel:`Send` to send the quotation, via email, to the customer, so they " "can review and confirm it." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:300 msgid "" ":guilabel:`Send PRO-FORMA Invoice`: This button **only** appears if the " "*Pro-Forma Invoice* setting has been enabled. When clicked, a pop-up window " "appears with the customer's name and email address in the " ":guilabel:`Recipients` field, the *Proforma* invoice (and reference ID) in " "the :guilabel:`Subject` field, and a brief default message in the body of " "the email, which can be modified, if needed." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:308 msgid "" ":guilabel:`Confirm`: When clicked, the quotation is confirmed, and the " "status changes to :guilabel:`Sales Order`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:310 msgid "" ":guilabel:`Preview`: When clicked, Odoo reveals a preview of the quotation " "the customer sees when they log into their customer portal. Click the " ":icon:`fa-arrow-right` :guilabel:`Back to edit mode` link at the top of the " "preview page, in the blue banner, to return to the quotation form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:313 msgid ":guilabel:`Cancel`: When clicked, the quotation is canceled." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:316 msgid "" "If the *Lock Confirmed Sales* setting is enabled, the sales order becomes " ":guilabel:`Locked`, and is indicated as such on the sales order form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:319 msgid "" "At this point, the quotation has been confirmed, turned into a sales order, " "and is now ready to be invoiced and paid for." msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:322 msgid "" "For more information about invoicing, refer to the :doc:`Invoice based on " "delivered or ordered quantities <../invoicing/invoicing_policy>`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:326 #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:89 #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:77 #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:99 msgid ":doc:`quote_template`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:327 msgid ":doc:`deadline`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:328 #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:282 msgid ":doc:`get_signature_to_validate`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:329 #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:283 msgid ":doc:`get_paid_to_validate`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:330 msgid ":doc:`pdf_quote_builder`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:331 msgid ":doc:`../invoicing/proforma`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:3 msgid "Quotation deadlines" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:5 msgid "" "In the Odoo *Sales* application, it is possible to set deadlines on sales " "quotations. Doing so encourages customers to act quickly during sales " "negotiations, for they might fear for missing out on a good deal. As well, " "deadlines also can also act as protection for a company in case an order has" " to be fulfilled at a price that is no longer profitable for the business." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:11 msgid "Quotation expiration" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:13 msgid "" "In Odoo *Sales*, there's the option to add an expiration date to a " "quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:15 msgid "" "To add an expiration date to a quotation, navigate to :menuselection:`Sales " "app`, and select a desired quotation, or create a new one by clicking " ":guilabel:`New`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:18 msgid "" "On the quotation form, click the :guilabel:`Expiration` field to reveal a " "pop-up calendar. From this pop-up calendar, select the desired month and " "date as the expiration date for the quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 msgid "The expiration field on a standard quotation form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:26 msgid "" "By clicking the :guilabel:`Preview` button on a quotation, Odoo clearly " "displays when that specific offer expires." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:0 msgid "How customers will see deadlines on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:34 msgid "Quotation template expiration" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:36 msgid "" "The Odoo *Sales* application also makes it possible to add a deadline " "expiration date to quotation templates." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:39 msgid "" "To add a deadline expiration date to a quotation template, navigate to " ":menuselection:`Sales app --> Configuration --> Quotation Templates`, and " "either select the desired quotation template to which a deadline should be " "added, or click :guilabel:`New` to build a new quotation template from " "scratch." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:43 msgid "" "On the quotation template form, add a specific number of days to the " ":guilabel:`Quotation expires after` field, located beneath the quotation " "template name. The number of days represents how long the quotation will be " "valid for, before it expires." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 msgid "" "The quotation expires after field on a quotation template form in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:51 msgid "" "Then, whenever that specific quotation template is used in a quote, an " "expiration date is automatically calculated, based on the number of days " "designated above. However, this date can be overwritten before sending the " "quotation to the customer." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:56 #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:227 msgid ":doc:`/applications/sales/sales/send_quotations/quote_template`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:3 msgid "Deliveries and invoices to different addresses" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:5 msgid "" "People and businesses often use separate addresses for billing (invoicing) " "and shipping (delivery) purposes. With the Odoo *Sales* app, contacts can " "have different specified addresses for delivery and invoicing." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12 msgid "" "To properly utilize multiple addresses in Odoo, go to :menuselection:`Sales " "app --> Configuration --> Settings` and scroll down to the " ":guilabel:`Quotations & Orders` heading. Then, check the box next to " ":guilabel:`Customer Addresses`, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 msgid "Activate the Customer Addresses setting." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23 msgid "Contact form configuration" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:25 msgid "" "To add multiple addresses to a contact, go to :menuselection:`Sales app --> " "Orders --> Customers`, and clear any default filters from the search bar. " "Then, click on the desired customer to open their contact form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:30 msgid "Contact forms can be accessed in the *Contacts* application, as well." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:32 msgid "" "From the contact form, click :guilabel:`Edit`, and then select " ":guilabel:`Add`, which is located under 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/sales/sales/send_quotations/different_addresses.rst-1 msgid "Add a contact/address to the contact form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:40 msgid "" "On the :guilabel:`Create Contact` pop-up form, start by clicking the default" " :guilabel:`Other Address` field to reveal a drop-down menu of address-" "related options." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:43 msgid "Select any of the following options:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:45 msgid "" ":guilabel:`Contact`: adds another contact to the existing contact form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:46 msgid "" ":guilabel:`Invoice Address`: adds a specific invoice address to the existing" " contact form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:47 msgid "" ":guilabel:`Delivery Address`: adds a specific delivery address to the " "existing contact form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:48 msgid "" ":guilabel:`Other Address`: adds an alternate address to the existing contact" " form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49 msgid "" ":guilabel:`Private Address`: adds a private address to the existing contact " "form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:51 msgid "" "Once an option is selected, proceed to enter the corresponding contact " "information that should be used for the specified address type." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 msgid "Create a new contact/address on a contact form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:58 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/sales/sales/send_quotations/different_addresses.rst:62 msgid "Address added to quotations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:64 msgid "" "When a customer is added to a quotation, the :guilabel:`Invoice Address` and" " :guilabel:`Delivery Address` fields autopopulate with the corresponding " "addresses specified on the customer's contact form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 msgid "Invoice and Delivery Addresses autopopulate on a quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:72 msgid "" "The :guilabel:`Invoice Address` and :guilabel:`Delivery Address` can also be" " edited directly from the quotation by clicking the :guilabel:`Edit` button," " and then clicking the :guilabel:`➡️ (right arrow)` internal link buttons " "next to each address line." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:76 msgid "" "These addresses can be updated at any time to ensure accurate invoicing and " "delivery." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:79 msgid "" "If any changes are made on a form in Odoo, include *Contacts* forms, " "remember to click :guilabel:`Save` to save the changes to the database." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 msgid "Online payment order confirmation" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:5 msgid "" "The Odoo *Sales* application provides customers with the ability to confirm " "orders, via an online payment, directly on a sales order. Once the sales " "order is electronically paid for by the customer, the salesperson attached " "to the sales order is instantly notified that the order is confirmed." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:10 msgid "Activate online payments" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:12 msgid "" "In order to have customers confirm orders with an online payment, the " "*Online Payment* setting **must** be activated." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:15 msgid "" "To activate the *Online Payment* feature, go to :menuselection:`Sales app " "--> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& " "Orders` heading, check the box next to the :guilabel:`Online Payment` " "feature, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 msgid "The online payment setting in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:23 msgid "" "Beneath the :guilabel:`Online Payment` option on the *Sales* " ":guilabel:`Settings` page, there's a :guilabel:`Default Quotation Validity` " "field. In this field, there's the option to add a specific number of days " "for quotations to remain valid by default." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:27 msgid "" "To enable this feature on a standard quotation, click the checkbox for the " ":guilabel:`Payment` feature option, located in the :guilabel:`Online " "confirmation` field, on the :guilabel:`Other Info` tab." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 msgid "The online payment setting on a standard quotation in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35 msgid "" "To enable this feature on a quotation template, click the checkbox for the " ":guilabel:`Payment` feature option, located in the :guilabel:`Online " "confirmation` field of the quotation template form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 msgid "The online payment setting on quotation template forms in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:43 #: ../../content/applications/sales/subscriptions/payment_providers.rst:5 msgid "Payment providers" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:45 msgid "" "After activating the :guilabel:`Online Payment` feature, a link to configure" " :guilabel:`Payment Providers` appears beneath it." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:48 msgid "" "Clicking that link reveals a separate :guilabel:`Payment Providers` page, in" " which a large variety of payment providers can be enabled, customized, and " "published." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 msgid "Payment providers page in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:56 #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:91 msgid ":doc:`../../../finance/payment_providers`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:59 msgid "Register a payment" msgstr "Zabeleži plačilo" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:61 msgid "" "After opening quotations in their customer portal, customers can click " ":guilabel:`Accept \\& Pay` to confirm their order with an online payment." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 msgid "The accept and pay button on an online quotation in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:68 msgid "" "After clicking :guilabel:`Accept \\& Pay`, customers are presented with " ":guilabel:`Validate Order` pop-up window containing different options for " "them to make online payments, in the :guilabel:`Pay with` section." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 msgid "" "How to register a payment on a validate order pop-up window in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:77 msgid "" "Odoo will **only** offer payment options on the :guilabel:`Validate Order` " "pop-up window that have been published and configured on the " ":guilabel:`Payment Providers` page." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:80 msgid "" "Once the customer selects their desired method of payment, they will click " "the :guilabel:`Pay` button on the pop-up window to confirm the order. Odoo " "instantly notifies the assigned salesperson upon order confirmation with an " "online payment." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 msgid "" "Sample of notification that appears in the chatter when an online payment is" " made." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 msgid "Online signatures for order confirmations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:5 msgid "" "The Odoo *Sales* application provides customers with the ability to confirm " "orders, via an online signature, directly on the sales order. Once the sales" " order is electronically signed by the customer, the salesperson attached to" " the sales order is instantly notified that the order is confirmed." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:11 msgid "Activate online signatures" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:13 msgid "" "In order to have customers confirm orders with an online signature, the " "*Online Signature* feature **must** be activated." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:16 msgid "" "To activate the *Online Signature* feature, go to :menuselection:`Sales app " "--> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& " "Orders` heading, and activate the :guilabel:`Online Signature` feature by " "checking the box beside it." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 msgid "" "The Online Signature feature option in the Settings of the Odoo Sales " "application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:24 msgid "Then, click the :guilabel:`Save` button in the top-left corner." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:27 msgid "" "When making a quotation template, the online signature feature is the " ":guilabel:`Signature` option, located in the :guilabel:`Online confirmation`" " field of the quotation template form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 msgid "" "The Online confirmation signature option found on every quotation template " "in Odoo." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:34 msgid "" "On standard quotations, the online signature feature is the " ":guilabel:`Signature` option, located under the :guilabel:`Other Info` tab " "of the quotation form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 msgid "" "The online signature feature option in the Other Info tab of a quotation " "form in Odoo." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:42 msgid "Order confirmations with online signatures" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:44 msgid "" "When clients access quotations online through their customer portal, there's" " a :guilabel:`Sign \\& Pay` button directly on the quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 msgid "The Sign and Pay button present on online quotations in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 msgid "" "When clicked, a :guilabel:`Validate Order` pop-up window appears. In this " "pop-up window, the :guilabel:`Full Name` field is auto-populated, based on " "the contact information in the database." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 msgid "The Validate Order pop-up window for online signatures in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:58 msgid "" "Then, customers have the option to enter an online signature with any of the" " following options: :guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:61 msgid "" ":guilabel:`Auto` lets Odoo automatically generate an online signature based " "on the information in the :guilabel:`Full Name` field. :guilabel:`Draw` lets" " the customer use the cursor to create a custom signature directly on the " "pop-up window. And :guilabel:`Load` lets the customer upload a previously-" "created signature file from their computer." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:66 msgid "" "After the customer has chosen any of the three previously mentioned " "signature options (:guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`)," " they will click the :guilabel:`Accept \\& Sign` button." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:70 msgid "" "When :guilabel:`Accept \\& Sign` is clicked, the various payment method " "options become available for them to choose from (if the *online payment* " "option applies to this quotation)." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:73 msgid "" "Then, when the quotation is paid and confirmed, a delivery order is " "automatically created (if the Odoo *Inventory* app is installed)." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3 msgid "Optional products" msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:5 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/optional_products.rst:9 #: ../../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 "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:14 msgid "Optional products on quotations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:16 msgid "" "With the Odoo *Sales* application, it is possible to add or modify optional " "products directly on quotations by navigating to the :guilabel:`Optional " "Products` tab on a quotation form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 msgid "How to add optional products to your quotations on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:23 msgid "" "To add an optional product(s) to a quotation, click :guilabel:`Add a " "product` in the :guilabel:`Optional Products` tab of a quotation. Doing so " "reveals a blank field in the :guilabel:`Product` column." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:27 #: ../../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 "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:31 msgid "" "If the desired product isn't readily visible, type the name of the desired " "product in the field, and the option appears in the drop-down menu. Then, " "select that desired product to add it to the quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:36 msgid "" "When a product is added, the default :guilabel:`Quantity` is `1`, but that " "can be edited at any time." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:39 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:186 msgid "" "To delete any line item from the :guilabel:`Optional Products` tab, click " "the :guilabel:`🗑️ (trash can)` icon." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:42 msgid "" "Click the :guilabel:`Preview` button, located in the upper-left corner of " "the quotation, to reveal a preview of the quotation customers would receive," " via email, along with the optional products they can potentially add to " "their order, located in the :guilabel:`Options` section." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 #: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 msgid "Preview your quotations on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:50 msgid "" "Customers are able to add different optional products to an order by " "clicking the :guilabel:`🛒 (shopping cart)` icon, located to the right of the" " optional product line." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:53 msgid "" "If a customer selects optional products, these are automatically added to " "the quotation managed by the salesperson." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:56 msgid "" "When the customer adds an optional product(s) to an order, the salesperson " "is instantly notified about the change, along with any other change the " "customer makes to an order. This allows salespeople to stay up-to-date with " "everything related to an order in the backend of the *Sales* application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:62 msgid "Optional products on quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 msgid "" "Be sure to review the :doc:`quote_template` documentation to better " "understand how quotation templates work before reading the following " "information." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:68 msgid "" "For quotation templates, just like a typical quotation form, there is also " "an :guilabel:`Optional Products` tab, wherein related products or services " "can be added to a quotation template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:71 msgid "" "To add optional products to a quotation template, navigate to " ":menuselection:`Sales app --> Configuration --> Quotation Templates`. Then, " "either select an existing quotation template to edit, or create a new one by" " clicking :guilabel:`New`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:75 msgid "" "On the quotation template form, click the :guilabel:`Optional Products` tab." " Under the :guilabel:`Optional Products` tab, click :guilabel:`Add a line`, " "and select the desired product to add as an optional product to the " "quotation template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:83 msgid "" "The products added in the :guilabel:`Optional Products` tab are present in " "the quotation, by default, whenever that particular quotation template is " "used. These products can be removed, and additional products can be added, " "before the quotation is sent to a customer." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:88 msgid "" "It's best to offer optional products that would encourage a customer to add " "additional items to their order, or entice them to purchase a more expensive" " version of their initially selected product." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:92 msgid "" "For example, if a customer purchases a wooden chair, some optional products " "could be: a warranty on that chair and/or a wooden chair with leather seats." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:96 msgid "" "There is no limit to how many optional products can be added to a quotation " "template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:3 msgid "Product variants on quotations and sales orders" msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:5 msgid "" "Before getting into detail about how to use product variants on quotations " "and sales orders, it's recommended to learn about " ":doc:`../products_prices/products/variants` in Odoo." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:8 msgid "" "Once familiarized with the basics surrounding product variants, the " "following covers how product variants can be added to quotations and sales " "orders using the *product configurator* or *order grid entry*." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:13 msgid "" "It should be noted that the setting is titled, *Variant Grid Entry* on the " "*Sales* app settings page, and titled, *Order Grid Entry* on product forms. " "So, be sure to keep that in mind." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:19 msgid "" "When working with product variants, Odoo uses the product configurator, by " "default. To add the variant grid entry option, that feature **must** be " "enabled in the Odoo *Sales* application. The variant grid entry option " "provides a pop-up window on the quotation/sales order to simplify the " "variant selection process." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:24 msgid "" "To enable that setting, go to :menuselection:`Sales app --> Configuration " "--> Settings`, and scroll to the :guilabel:`Product Catalog` section. Then, " "check the box next to the :guilabel:`Variant Grid Entry` option, and click " ":guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 msgid "The variant grid entry setting in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:33 msgid "" "Of course, the :guilabel:`Variants` feature **must** also be activated, in " "order to use product variants on quotations and sales orders." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 msgid "Product configuration" msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:39 msgid "" "Once the :guilabel:`Variant Grid Entry` setting is enabled, both options " "(*Product Configurator* and *Order Grid Entry*) become available on every " "product form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:42 msgid "" "To configure a product form to use either a product configurator or variant " "grid entry, start by navigating to :menuselection:`Sales app --> Products " "--> Products` to view all the products in the database." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:46 msgid "" "Then, select the desired product to configure, or click :guilabel:`New`, to " "create a new product from scratch. Once on the product form, click into the " ":guilabel:`Attributes \\& Variants` tab, where product variants can be " "viewed, modified, and added." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:50 msgid "" "At the bottom of the :guilabel:`Attributes \\& Variants` tab, there is a " ":guilabel:`Sales Variant Selection` section with two options: " ":guilabel:`Product Configurator` and :guilabel:`Order Grid Entry`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:55 msgid "" "It should be noted that these options **only** appear if at least two values" " of an attribute have been added to the record." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 msgid "" "Sales variant selection options on the attributes and variants tab on " "product form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:62 msgid "" "These options determine which method is used when adding product variants to" " quotations or sales orders." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:65 msgid "" "The :guilabel:`Product Configurator` provides a pop-up window that neatly " "displays all the available product variants for that particular product when" " it's added to a quotation. However, only one variant can be selected/added " "at a time." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:69 msgid "" "The :guilabel:`Order Grid Entry` provides the same information as the " ":guilabel:`Product Configurator` in a table layout, allowing the user to " "select larger numbers of unique product variants, and add them to a " "quotation/sales order, in a single view." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74 msgid "Product configurator" msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:76 msgid "" "The product configurator feature appears as a :guilabel:`Configure` pop-up " "window, as soon as a product with (at least two) variants is added to a " "quotation or sales order, but **only** if the :guilabel:`Product " "Configurator` option is selected on its product form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 msgid "" "The product configurator pop-up window that appears on a quotation or sales " "order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:85 msgid "" "This :guilabel:`Configure` pop-up window also appears if the " ":guilabel:`Order Grid Entry` setting is **not** activated, as it is the " "default option Odoo uses when dealing with product variants on quotations " "and/or sales orders." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:89 msgid "" "The :guilabel:`Product Configurator` option lets salespeople choose exactly " "which product variant to add to the quotation or sales order using a format " "similar to online shopping." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:93 msgid "Order grid entry" msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:95 msgid "" "The order grid entry feature appears as a :guilabel:`Choose Product " "Variants` pop-up window, as soon as a product with (at least two) variants " "is added to a quotation or sales order, but **only** if the :guilabel:`Order" " Grid Entry` option is selected on its product form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 msgid "" "The choose product variants pop-up window that appears on a quotation in " "Odoo." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:103 msgid "" "The :guilabel:`Choose Product Variants` pop-up window features all the " "variant options for that particular product. From this pop-up window, the " "salesperson can designate how many of each variant they'd like to add to the" " quotation/sales order at once." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:107 msgid "" "When all the desired quantities and variants have been selected, the " "salesperson simply clicks :guilabel:`Confirm`, and those orders are " "instantly added to the quotation/sales order in the :guilabel:`Order Lines` " "tab." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 msgid "" "Populated order lines tab after order grid entry has been chosen to select " "products." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:116 msgid ":doc:`../products_prices/products/variants`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:3 msgid "PDF quote builder" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:5 msgid "" "The *PDF Quote Builder* in Odoo *Sales* provides the opportunity to send " "customers a fully customized PDF file for quotes, showcasing the company and" " products, with various information and design elements, instead of just " "showing the price and total." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:9 msgid "" "The PDF Quote Builder groups header pages, product descriptions, the " "price(s), and footer pages to create a detailed quote. It can also inject " "dynamic texts in the PDF to personalize the offer for the customer." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:13 msgid "" "Having a customized PDF in quotes provides a heightened conclusion to the " "shopping experience for customers, and adds an elegant level of " "professionalism to a company." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:17 msgid "" "`Odoo Quick Tips - Create a PDF quote [video] " "`_" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:20 msgid "" "It is recommended to edit PDF forms with Adobe software. The form fields on " "the header and footer PDF templates are necessary to get dynamic values with" " Odoo." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:26 msgid "" "In order to add custom PDF files for quotes, the :guilabel:`PDF Quote " "builder` feature *must* be configured." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:29 msgid "" "To do that, navigate to :menuselection:`Sales app --> Configuration --> " "Settings`. Then, on the :guilabel:`Settings` page, scroll to the " ":guilabel:`Quotations & Orders` section, and locate the :guilabel:`PDF Quote" " builder` feature." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 msgid "" "The PDF Quote Builder feature located on the Settings page of the Sales " "application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:37 msgid "" "Here, custom :guilabel:`Header pages` and :guilabel:`Footer pages` can be " "uploaded. To upload either, click the :guilabel:`Upload your file` button, " "or the :guilabel:`✏️ (pencil)` icon to the right of the desired field, and " "proceed to locate, select, and upload the desired PDF file." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:42 msgid "" "Headers and footers can also be added directly in a quotation template, so " "it's possible to have different variations per template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:45 msgid "" "Clicking the :guilabel:`🗑️ (trash)` icon deletes the current PDF file and " "replaces the blank field with an :guilabel:`Upload your file` button." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:48 msgid "" "Once the desired PDF file(s) are uploaded in the appropriate fields in the " ":guilabel:`PDF Quote builder` section of the *Sales* :guilabel:`Settings` " "page, be sure to click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:51 msgid "The files uploaded here will be the default PDF used for all quotes." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:54 msgid "Values set in the PDF Quote Builder settings are company-specific." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:57 msgid "Dynamic text in PDFs" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:59 msgid "" "While creating custom PDFs for quotes, use *dynamic text* for Odoo to auto-" "fill the PDF content with information related to the quote from the Odoo " "database, like names, prices, etc." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:62 msgid "" "Dynamic text values are form components (text inputs) that can be added in a" " PDF file, and Odoo automatically fills those values in with information " "related to the quote." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:66 msgid "Dynamic text values" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:68 msgid "" "Below are common dynamic text values used in custom PDFs, and what they " "represent:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:70 msgid ":guilabel:`name`: Sales Order Reference" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:71 msgid ":guilabel:`partner_id__name`: Customer Name" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:72 msgid ":guilabel:`user_id__name`: Salesperson Name" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:73 msgid ":guilabel:`amount_untaxed`: Untaxed Amount" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:74 msgid ":guilabel:`amount_total`: Total Amount" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:75 msgid ":guilabel:`delivery_date`: Delivery Date" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:76 msgid ":guilabel:`validity_date`: Expiration Date" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:77 msgid ":guilabel:`client_order_ref`: Customer Reference" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:80 msgid "" "Double underscore notation for :guilabel:`partner_id__name` and " ":guilabel:`user_id__name` values are used in place of the typically used `.`" " symbol because the library currently does not support the `.` symbol." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:84 msgid "Product-specific dynamic text values are as follows:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:86 msgid ":guilabel:`description`: Product Description" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:87 msgid ":guilabel:`quantity`: Quantity" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:88 msgid ":guilabel:`uom`: Unit of Measure (UoM)" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:89 msgid ":guilabel:`price_unit`: Price Unit" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:90 msgid ":guilabel:`discount`: Discount" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:91 msgid ":guilabel:`product_sale_price`: Product List Price" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:92 msgid ":guilabel:`taxes`: Taxes name joined by a comma (`,`)" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:93 msgid ":guilabel:`tax_excl_price`: Tax Excluded Price" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:94 msgid ":guilabel:`tax_incl_price`: Tax Included Price" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:97 msgid "" "When a PDF is built, it's best practice to use common dynamic text values " "(:guilabel:`name` and :guilabel:`partner_id_name`). When uploaded into the " "database, Odoo auto-populates those fields with the information from their " "respective fields." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:101 msgid "" "In this case, Odoo would auto-populate the Sales Order Reference in the " ":guilabel:`name` dynamic text field, and the Customer Name in the " ":guilabel:`partner_id_name` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 msgid "PDF quote being built using common dynamic placeholders." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:108 msgid "" "Once the PDF file(s) are complete, save them to the computer's hard drive, " "and proceed to upload them to Odoo via :menuselection:`Sales app --> " "Configuration --> Settings --> PDF Quote builder`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:111 msgid "" "Upload the created PDF in the :guilabel:`Header pages` or :guilabel:`Footer " "pages` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:113 msgid "Once the upload(s) are complete, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:116 msgid "Add PDF to product" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:118 msgid "" "In Odoo *Sales*, it's also possible to add a custom PDF to a product form. " "When a PDF is added to a product, and that product is used in a quotation, " "that PDF is also inserted in the final PDF." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:121 msgid "" "To add a custom PDF to a product, start by navigating to " ":menuselection:`Sales app --> Products --> Products`, and select the desired" " product to which a custom PDF should be added." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:125 msgid "" "A document could also be added to a product variant, instead of a product. " "If there are documents on a product *and* on its variant, **only** the " "documents in the variant are shown." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:128 msgid "" "To add a custom document to a product variant, navigate to " ":menuselection:`Sales app --> Products --> Product Variants`. Select the " "desired variant, click the :guilabel:`Documents` smart button, and proceed " "to upload the custom document(s) to the specific product variant." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:132 msgid "" "On the product page, click the :guilabel:`Documents` smart button at the top" " of the page." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 msgid "The Documents smart button on a product form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:138 msgid "" "Doing so reveals a separate :guilabel:`Documents` page for that product, " "wherein files related to that product can be uploaded. From this page, " "either click :guilabel:`New` or :guilabel:`Upload`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:141 msgid "" "Clicking :guilabel:`Upload` instantly provides the opportunity to upload the" " desired document. Then, the document can be further configured on the " "document card, or by clicking the three dots icon in the top right corner of" " the document card, and then clicking :guilabel:`Edit`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:145 msgid "" "Clicking :guilabel:`New` reveals a blank documents form, in which the " "desired PDF can be uploaded via the :guilabel:`Upload your file` button on " "the form, located in the :guilabel:`File Content` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 msgid "" "A standard document form with various fields for a specific product in Odoo " "Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:153 msgid "" "Various information and configurations related to the uploaded document can " "be modified here." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:155 msgid "" "The first field on the documents form is for the :guilabel:`Name` of the " "document, and it is grayed-out (not clickable) until a document is uploaded." " Once a PDF has been uploaded, the :guilabel:`Name` field is auto-populated " "with the name of the PDF, and it can then be edited." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:159 msgid "" "Prior to uploading a document, there's the option to designate whether the " "document is a :guilabel:`File` or :guilabel:`URL` from the :guilabel:`Type` " "drop-down field menu." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 msgid "A standard document form with an uploaded pdf in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:167 msgid "" "If a PDF is uploaded, the :guilabel:`Type` field is auto-populated to " ":guilabel:`File`, and it cannot be modified." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:170 msgid "" "Then, in the :guilabel:`Sales` section, in the :guilabel:`Visible at` field," " click the drop-down menu, and select either: :guilabel:`Quotation`, " ":guilabel:`Confirmed order`, or :guilabel:`Inside quote`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:174 msgid "" ":guilabel:`Quotation`: the document is sent to (and accessible by) customers" " at any time." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:176 msgid "" ":guilabel:`Confirmed order`: the document is sent to customers upon the " "confirmation of an order. This is best for user manuals and other " "supplemental documents." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:179 msgid "" ":guilabel:`Inside quote`: the document is included in the PDF of the " "quotation, between the header pages and the :guilabel:`Pricing` section of " "the quote." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:183 msgid "" "When the :guilabel:`Inside quote` option for the :guilabel:`Visible at` " "field is chosen, and the custom PDF file, `Sample Builder.pdf` is uploaded, " "the PDF is visible on the quotation the in the *customer portal* under the " ":guilabel:`Documents` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 msgid "" "Sample of an uploaded pdf with the inside quote option chosen in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:191 msgid "" "Lastly, in the :guilabel:`E-Commerce` section, decide whether or not to " ":guilabel:`Show on product page` on the front-end (in the online store)." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:195 msgid "" "When the :guilabel:`Show on product page` option is enabled, a link to the " "uploaded document, `Sample Builder.pdf`, appears on the product's page, " "located on the frontend in the online store." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:198 msgid "" "It appears beneath a :guilabel:`Documents` heading, with a link showcasing " "the name of the uploaded document." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 msgid "" "Showing a link to an uploaded document on a product page using Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:206 msgid "PDF quote" msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:208 msgid "" "Once a quote with a pre-configured PDF has been confirmed, Odoo provides the" " option to print the confirmed quote to check for errors, or to keep for " "records." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:211 msgid "" "To print the PDF quote, navigate to the confirmed quote, and click the " ":guilabel:`⚙️ (gear)` icon to reveal a drop-down menu. From this drop-down " "menu, select :guilabel:`Print`, then select :guilabel:`PDF Quote`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 msgid "" "Print pdf quote option on drop-down menu located on confirmed sales order in" " Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:219 msgid "" "Doing so instantly downloads the PDF quote. When opened, the PDF quote, " "along with the configured product PDF that was set to be visible inside the " "quote, can be viewed and printed." msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:223 msgid "" "Download these :download:`PDF quote builder examples " "` for added reference." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 msgid "Quotation templates" msgstr "Predlog ponudb" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5 msgid "" "In Odoo *Sales*, salespeople have the ability to create reusable quotation " "templates for common products or services that the business offers." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:8 msgid "" "By using these templates, quotations can be tailored and sent to customers " "at a much faster pace, without having to create new quotations from scratch " "every time a sales negotiation occurs." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:16 msgid "" "Begin by activating the setting in :menuselection:`Sales app --> " "Configuration --> Settings`, and scroll to the :guilabel:`Quotations \\& " "Orders` heading." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 msgid "" "In that section, check the box beside the :guilabel:`Quotation Templates` " "option. Doing so reveals a new :guilabel:`Default Template` field, in which " "a default quotation template can be chosen from a drop-down menu." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "How to enable quotation templates on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:27 msgid "" "Also, upon activating the :guilabel:`Quotation Template` feature, an " "internal :guilabel:`➡️ Quotation Templates` link appears beneath the " ":guilabel:`Default Template` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:30 msgid "" "Clicking that link reveals the :guilabel:`Quotation Templates` page, from " "which templates can be created, viewed, and edited." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33 msgid "" "Before leaving the :guilabel:`Settings` page, don't forget to click the " ":guilabel:`Save` button to save all changes made during the session." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:37 msgid "Create quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:39 msgid "" "Click the :guilabel:`Quotation Templates` link on the :guilabel:`Settings` " "page, or navigate to :menuselection:`Sales app --> Configuration --> " "Quotation Templates`. Both options reveal the :guilabel:`Quotation " "Templates` page, where quotation templates can be created, viewed, and " "edited." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "Quotation templates page in the Odoo Sales application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:47 msgid "" "To create a new quotation template, click the :guilabel:`New` button, " "located in the upper-left corner. Doing so reveals a blank quotation " "template form that can be customized in a number of ways." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "Create a new quotation template on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 msgid "" "Start by entering a name for the template in the :guilabel:`Quotation " "Template` field." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:56 msgid "" "Then, in the :guilabel:`Quotation Validity` field, designate how many days " "the quotation template will remain valid for, or leave the field on the " "default `0` to keep the template valid indefinitely." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:60 msgid "" "Next, in the :guilabel:`Confirmation Mail` field, click the blank field to " "reveal a drop-down menu. From the drop-down menu, select a pre-configured " "email template to be sent to customers upon confirmation of an order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65 msgid "" "To create a new email template directly from the :guilabel:`Confirmation " "Mail` field, start typing the name of the new email template in the field, " "and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from" " the drop-down menu that appears." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 msgid "" "Selecting :guilabel:`Create` creates the email template, which can be edited" " later." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:71 msgid "" "Selecting :guilabel:`Create and edit...` creates the email template, and a " ":guilabel:`Create Confirmation Mail` pop-up window appears, in which the " "email template can be customized and configured right away." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "" "Create confirmation mail pop-up window from the quotation template form in " "Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79 msgid "" "When all modifications are complete, click :guilabel:`Save \\& Close` to " "save the email template and return to the quotation form." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:82 msgid "" "If working in a multi-company environment, use the :guilabel:`Company` field" " to designate to which company this quotation template applies." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:85 msgid "" "If a journal is set in the :guilabel:`Invoicing Journal` field, all sales " "orders with this template will invoice in that specified journal. If no " "journal is set in this field, the sales journal with the lowest sequence is " "used." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:89 msgid "" "If the :guilabel:`Online Signature` and/or :guilabel:`Online Payment` " "features are activated in the :guilabel:`Settings` (:menuselection:`Sales " "app --> Configuration --> Settings`), those options are available on " "quotation template forms." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93 msgid "" "Check the box beside :guilabel:`Online Signature` to request an online " "signature from the customer to confirm an order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:96 msgid "" "Check the box beside :guilabel:`Online Payment` to request an online payment" " from the customer to confirm an order. When :guilabel:`Online Payment` is " "checked, a new percentage field appears, in which a specific percentage of " "payment can be entered." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:100 msgid "" "Both options, :guilabel:`Online Signature` and :guilabel:`Online Payment` " "can be enabled simultaneously, in which case the customer must provide " "**both** a signature **and** a payment to confirm an order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:104 msgid "" "In the :guilabel:`Recurring Plan` field, choose from a variety of pre-" "configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`," " etc.) to designate how often this quotation template should occur." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:109 msgid "" "The :guilabel:`Recurring Plan` field **only** applies to subscription plans." " For more information, check out the documentation on " ":doc:`../../subscriptions/plans`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:113 msgid "Lines tab" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:115 msgid "" "In the :guilabel:`Lines` tab, products can be added to the quotation " "template by clicking :guilabel:`Add a product`, organized by clicking " ":guilabel:`Add a section` (and dragging/dropping section headers), and " "further explained with discretionary information (such as warranty details, " "terms, etc.) by clicking :guilabel:`Add a note`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:120 msgid "" "To add a product to a quotation template, click :guilabel:`Add a product` in" " the :guilabel:`Lines` tab of a quotation template form. Doing so reveals a " "blank field in the :guilabel:`Product` column." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:123 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: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: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: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: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: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: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: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: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: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: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 "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "Optional products appearing on a typical sales order with Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst: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: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:190 msgid "Optional products are **not** required to create a quotation template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:193 msgid "Terms \\& Conditions tab" msgstr "" #: ../../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:200 msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`" msgstr "" #: ../../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:206 msgid "PDF Quote Builder tab" msgstr "" #: ../../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: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:216 msgid ":doc:`/applications/sales/sales/send_quotations/pdf_quote_builder`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:219 msgid "Use quotation templates" msgstr "" #: ../../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 "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "Quotation templates field on a standard quotation form in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst: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 "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "Customer preview of a quotation template in Odoo Sales." msgstr "" #: ../../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: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: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 "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:249 msgid "Mass cancel quotations/sales orders" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:251 msgid "" "Cancel multiple quotations (or sales orders) by navigating to the " ":menuselection:`Sales app --> Orders --> Quotations` dashboard, landing, by " "default, in the list view. Then, on the left side of the table, tick the " "preferred checkboxes for removal." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:256 msgid "" "Select all records in the table by selecting the checkbox column header at " "the top-left of the table; the total number of selected items are displayed " "at the top of the page." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:259 msgid "" "Then, with the desired quotations (or sales orders) selected from the list " "view on the :guilabel:`Quotations` page, click the :icon:`fa-cog` " ":guilabel:`Actions` button to reveal a drop-down menu." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:263 msgid "From this drop-down menu, select :guilabel:`Cancel quotations`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "" "The Cancel quotations option on the Actions drop-down menu in the Odoo Sales" " application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:270 msgid "" "This action can be performed for quotations in *any* stage, even if it is " "confirmed as a sales order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:273 msgid "" "Upon selecting the :guilabel:`Cancel quotations` option, a :guilabel:`Cancel" " quotations` confirmation pop-up window appears. To complete the " "cancellation, click the :guilabel:`Cancel quotations` button." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:278 msgid "" "An error pop-up message appears when attempting to cancel an order for an " "ongoing subscription that has an invoice." msgstr "" #: ../../content/applications/sales/subscriptions.rst:5 msgid "Subscriptions" msgstr "Naročnine" #: ../../content/applications/sales/subscriptions.rst:7 msgid "" "Odoo *Subscriptions* is used to run recurring businesses: :ref:`sell new " "contracts `, :doc:`upsell customers " "`, keep the churn under " "control, and :doc:`generate reports " "` on the main :abbr:`KPIs (Key " "Performance Indicators)`: :abbr:`MRR (Monthly Recurring Revenue)`, " ":abbr:`ARR (Annual Recurring Revenue)`, retention, churn, etc." msgstr "" #: ../../content/applications/sales/subscriptions.rst:15 msgid "" "`Odoo Tutorials: Subscriptions " "`_" msgstr "" #: ../../content/applications/sales/subscriptions.rst:16 msgid ":doc:`/applications/sales/subscriptions/products`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:17 msgid ":doc:`/applications/sales/subscriptions/ecommerce`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:18 msgid ":doc:`/applications/sales/subscriptions/plans`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:19 msgid ":doc:`/applications/sales/subscriptions/upselling`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:20 msgid ":doc:`/applications/sales/subscriptions/renewals`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:21 msgid ":doc:`/applications/sales/subscriptions/closing`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:22 msgid ":doc:`/applications/sales/subscriptions/automatic_alerts`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:23 msgid ":doc:`/applications/sales/subscriptions/scheduled_actions`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:24 msgid ":doc:`/applications/sales/subscriptions/reports`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:29 msgid "Subscription quotations" msgstr "" #: ../../content/applications/sales/subscriptions.rst:32 msgid "Sales orders with a defined recurrence become subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions.rst:34 msgid "" "To create a new subscription, click on :guilabel:`New` from the " "*Subscription* or the :doc:`Sales ` app. You can " "either:" msgstr "" #: ../../content/applications/sales/subscriptions.rst:37 msgid "" "Select a :doc:`subscription plan ` " "to prefill the quotation instantly, or" msgstr "" #: ../../content/applications/sales/subscriptions.rst:39 msgid "" "Fill out the quotation normally, making sure to select a recurrence and an " "end date if necessary and adding :doc:`recurrent products " "`." msgstr "" #: ../../content/applications/sales/subscriptions.rst:43 msgid "" "You can define different invoice and delivery addresses by enabling the " ":doc:`Customer Addresses " "` " "feature." msgstr "" #: ../../content/applications/sales/subscriptions.rst:49 msgid "Confirmation" msgstr "Potrditev" #: ../../content/applications/sales/subscriptions.rst:51 msgid "" "Send the quotation to the customer for confirmation by clicking on " ":guilabel:`Send by email`, or confirm it immediately by clicking on " ":guilabel:`Confirm`." msgstr "" #: ../../content/applications/sales/subscriptions.rst:55 msgid "" "Click on :guilabel:`Customer Preview` to preview the customer portal where " "the customer can view their quotation, sign and pay it, and communicate with" " you." msgstr "" #: ../../content/applications/sales/subscriptions.rst:61 msgid "Automatic payments" msgstr "" #: ../../content/applications/sales/subscriptions.rst:63 msgid "" "You can require the customer to set an automatic payment method and pre-pay " "the subscription's first occurrence before they can confirm their quotation." " To do so, go to the :guilabel:`Other Info` tab of the quotation and check " "the :guilabel:`Payment` option in the :guilabel:`Online confirmation` field." msgstr "" #: ../../content/applications/sales/subscriptions.rst:68 msgid "" "If you leave :guilabel:`Payment` unchecked, the customer doesn't have to " "pre-pay to start the subscription. This means that the payment is not " "automatic and that the customer must pay each invoice manually." msgstr "" #: ../../content/applications/sales/subscriptions.rst:73 msgid "" "If the online confirmation requires a pre-payment, your customer can select " "only the :ref:`payment providers ` " "that have the :ref:`tokenization feature `. " "This ensures that the customer is automatically charged at each new period." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:3 msgid "Automation rules" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:5 msgid "" "With subscriptions up-and-running, it is important to stay up-to-date with " "customers. It is efficient to use automation to avoid having to manually go " "through the list of subscribers to see how things are going. That is where " "Odoo's *automation rules* feature comes into play." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:9 msgid "" "The Odoo *Subscriptions* application allows users to set up automatic " "emails, create tasks for salespeople, and even send satisfaction surveys for" " subscribers to evaluate their experience." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:13 msgid "Create automation rules" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:15 msgid "" "To create an automated rule, start by navigating to " ":menuselection:`Subscriptions app --> Configuration --> Automation Rules`. " "This is where all the automation rules for subscriptions can be found." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:19 msgid "" "The :guilabel:`Automation Rules` page shows each rule's :guilabel:`Name`, " ":guilabel:`Action To Do`, what the automated rule will :guilabel:`Trigger " "On`, and the :guilabel:`Company` to which the rule applies." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:23 msgid "" "To view or modify any existing automation rule, simply click the desired " "rule from this page." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:26 msgid "" "When modifying an existing automation rule, Odoo \"grays-out\" the " ":guilabel:`Action` section of the form, and provides the following warning: " "*Action data can not be updated to avoid unexpected behaviors. Create a new " "action instead.*" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:30 msgid "To create a new automation rule, click :guilabel:`New`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 msgid "The Automation Rules page in the Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:36 msgid "" "Clicking :guilabel:`New` reveals a blank :guilabel:`Automation Rules` form " "with numerous fields to configure." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 msgid "A sample Automation Rules form in the Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:44 msgid "Automation rule form fields" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:46 msgid ":guilabel:`Action Name`: title of the automated action rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:49 msgid "Apply On section" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:51 msgid "" "The :guilabel:`Apply On` section dictates which subscription " "orders/customers this automated action applies to." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:54 msgid "" ":guilabel:`MRR Between`: designate a range of monthly recurring revenue to " "target." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:55 msgid "" ":guilabel:`MRR Change More`: designate a change of monthly recurring revenue" " to target, in either percentage or unit of currency." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:57 msgid "" ":guilabel:`Over`: choose a period of time over which the designated KPIs " "(Key Performance Indicators) are calculated." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:59 msgid "" ":guilabel:`Rating Satisfaction`: designate satisfaction as " ":guilabel:`greater than` or :guilabel:`less than` a percentage." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:61 msgid "" ":guilabel:`Status`: select the status of the subscriptions to be included in" " this automation rule. The options are: :guilabel:`Quotation`, " ":guilabel:`Quotation Sent`, :guilabel:`Sales Order`, and " ":guilabel:`Cancelled`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:64 msgid "" ":guilabel:`Stage goes from`: designate when the automation rule should be " "activated using two fields that represent two different stages of the " "subscription." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:66 msgid "" ":guilabel:`Subscription Plans`: choose specific subscription plans to target" " with the automation rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:68 msgid "" ":guilabel:`Products`: select specific product(s) to target with the " "automation rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:69 msgid "" ":guilabel:`Customers`: select specific customer(s) to target with the " "automation rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:70 msgid "" ":guilabel:`Company`: in a multi-company environment, select a specific " "company's subscription data to target with the automation rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:72 msgid "" ":guilabel:`Sales Team`: select the data of specific sales team(s) to target " "with the automation rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:76 msgid "" "If any field is left blank, the rule applies to every subscription without " "that specific designation." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:80 msgid "" "The number of subscriptions that match the configured criteria of the " "customized automation rule are displayed at the bottom of the " ":guilabel:`Apply On` field." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:83 msgid "" "If that green subscriptions link is clicked, Odoo reveals a separate page " "showcasing all the subscriptions that meet that automation rule's criteria." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:87 msgid "Action section" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:89 msgid "" "The :guilabel:`Action` section dictates what action occurs when an automated" " rule is triggered." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:91 msgid "" "In the :guilabel:`Action To Do` field, choose the action that will occur " "once the automated rule is triggered. When clicked, the following options " "become available on a drop-down menu:" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:94 msgid "" ":guilabel:`Create next activity`: creates the next activity to occur, which " "is configured in the :guilabel:`Activity` section that appears at the bottom" " of the automation rule form." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:96 msgid "" ":guilabel:`Send an email to the customer`: sends an email to the customer(s)" " who fit the specified criteria of the automation rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:98 msgid "" ":guilabel:`Send an SMS Text Message to the customer`: sends an SMS message " "to the customer(s) who fit the specified criteria of the automation rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:100 msgid "" ":guilabel:`Set Contract Health value`: set the health value of the " "subscription contract." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:102 msgid "" "If :guilabel:`Send an email to the customer` is selected in the " ":guilabel:`Action To Do` field, the following field appears:" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:105 msgid "" ":guilabel:`Email Template`: create (and edit) a new email template *or* " "select from a list of pre-configured email templates to send to the " "customer(s)." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:108 msgid "" "If :guilabel:`Send an SMS Text Message to the customer` is selected in the " ":guilabel:`Action To Do` field, the following field appears:" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:111 msgid "" ":guilabel:`SMS Template`: create (and edit) a new SMS template *or* select " "from a list of pre-configured SMS templates to send to the customer(s)." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:114 msgid "" "If :guilabel:`Set Contract Health value` is selected in the " ":guilabel:`Action To Do` field, the following field appears:" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:117 msgid "" ":guilabel:`Health`: designate the health of the subscription by choosing one" " of the following options: :guilabel:`Neutral`, :guilabel:`Good`, or " ":guilabel:`Bad`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:120 msgid "" "In the :guilabel:`Trigger On` field, decide whether the automated rule " "should be triggered on a :guilabel:`Modification` or :guilabel:`Timed " "Condition`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:124 msgid "" "A :guilabel:`Trigger Now` button appears at the top of the automation rule " "form *only* when a trigger has been configured for the rule." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:128 msgid "" "When the :guilabel:`Trigger Now` button is clicked, Odoo will trigger the " "action on *all* linked subscriptions, regardless of possible timed " "conditions." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:132 msgid "" "Sending a SMS text message in Odoo requires In-App Purchase (IAP) credit or " "tokens. For more information on :abbr:`IAP (In-App Purchase)`, visit " ":doc:`../../essentials/in_app_purchase`. For more information on sending SMS" " messages, visit :doc:`../../marketing/sms_marketing`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:137 msgid "" "If :guilabel:`Timed Condition` is selected in the :guilabel:`Trigger On` " "field, the following fields appear:" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:140 msgid "" ":guilabel:`Trigger Date`: represents when the condition should be triggered." " If left blank, the action is created upon subscription creation *and* " "updates." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:142 msgid "" ":guilabel:`Delay After Trigger`: select a delayed amount of time " "(:guilabel:`Minutes`, :guilabel:`Hours`, :guilabel:`Days`, or " ":guilabel:`Months`) for Odoo to wait before triggering the configured " "action. If a negative number is entered, the \"delay\" will occur *before* " "the :guilabel:`Trigger Date`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:148 msgid "Activity section" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:150 msgid "" "If :guilabel:`Create next activity` is selected in the :guilabel:`Action To " "Do` field, an :guilabel:`Activity` section appears at the bottom of the " ":guilabel:`Automation Rules` form." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:153 msgid "" ":guilabel:`Activity Type`: select an pre-configured activity type from the " "drop-down menu." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:154 msgid ":guilabel:`Title`: enter a custom title for the chosen activity." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:155 msgid "" ":guilabel:`Note`: leave a note for the employee to whom the activity is " "assigned." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:156 msgid "" ":guilabel:`Due Date In`: enter an amount of days within which the activity " "should be completed." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:157 msgid "" ":guilabel:`Assign To`: choose to assign the specified activity to either: " ":guilabel:`Subscription Salesperson`, :guilabel:`Sales Team Leader`, or " ":guilabel:`Specific Users`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:161 msgid "" "If :guilabel:`Specific Users` is selected as the :guilabel:`Assign To` " "option, a new :guilabel:`Specific Users` field appears beneath it, where a " "specific employee(s) can be chosen as the assignee(s) for the configured " "activity." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:166 #: ../../content/applications/sales/subscriptions/closing.rst:105 #: ../../content/applications/sales/subscriptions/renewals.rst:128 #: ../../content/applications/sales/subscriptions/reports.rst:403 #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:186 #: ../../content/applications/sales/subscriptions/upselling.rst:107 msgid ":doc:`../subscriptions`" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:167 #: ../../content/applications/sales/subscriptions/closing.rst:106 #: ../../content/applications/sales/subscriptions/renewals.rst:129 #: ../../content/applications/sales/subscriptions/reports.rst:404 #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:187 #: ../../content/applications/sales/subscriptions/upselling.rst:108 msgid ":doc:`plans`" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:168 #: ../../content/applications/sales/subscriptions/closing.rst:107 #: ../../content/applications/sales/subscriptions/renewals.rst:130 #: ../../content/applications/sales/subscriptions/reports.rst:405 #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:188 #: ../../content/applications/sales/subscriptions/upselling.rst:109 msgid ":doc:`products`" msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:169 msgid ":doc:`../../essentials/in_app_purchase`" msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:3 msgid "Close subscriptions" msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:5 msgid "" "Odoo *Subscriptions* provides flexibility for businesses to decide whether " "customers can self-manage their subscriptions, or restrict that ability " "entirely." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:11 msgid "" "Start by navigating to :menuselection:`Subscriptions app --> Configuration " "--> Recurring Plans`. From there, either create a new plan by clicking " ":guilabel:`New` or select an existing one to modify it." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:15 msgid "" "Once on the :guilabel:`Recurring Plans` form, enable the " ":guilabel:`Closable` option, in the :guilabel:`Self-Service` section, to " "allow customers to close their own subscriptions using the customer portal." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "The Closable option on a recurring plan form in Odoo Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:24 msgid ":doc:`Configure recurring plans `" msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:27 msgid "Close a subscription" msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:30 msgid "Administrator view" msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:32 msgid "" "After a quotation for a subscription product has been confirmed, it becomes " "a sales order, and the subscription status changes to :guilabel:`In " "Progress`." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:35 msgid "" "At that point, the ability to close the subscription becomes available, via " "the :guilabel:`Close` button at the top of the subscription order, near the " "row that contains :guilabel:`In Progress` and other stages. This option is " "also available after the order has been invoiced and the payment has been " "registered." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "" "Close subscription from an administration point of view with Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:44 msgid "" "Clicking the :guilabel:`Close` button prompts a :guilabel:`Close Reason` " "pop-up window to appear, allowing administrators to input the reason for " "closing the subscription, or choose from the drop-down menu of options in " "the :guilabel:`Reason` field." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "" "The Close Reason pop-up when the Close button is clicked in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:52 msgid "" "When the desired :guilabel:`Reason` is entered, click the :guilabel:`Submit`" " button." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:54 msgid "" "Clicking :guilabel:`Submit` on the :guilabel:`Close Reason` pop-up window " "updates the subscription sales order to show :guilabel:`Churned` status tag," " along with the specified :guilabel:`Close Reason`." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "A churned sales order for a closed subscription in Odoo Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:62 msgid "" "That same close reason can be found in the *Chatter* of the sales order, as " "well." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "" "The chatter of a churned sales order for a closed subscription in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:69 msgid "Customer view" msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:72 msgid "" "As an administrator, the ability to visualize what customers see when " "managing their subscriptions is accessible via the :guilabel:`Preview` " "button, located at the top of the subscription sales order." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:76 msgid "" "From the customer's point of view, in the customer portal, the " ":guilabel:`Close Subscription` button is located on the left side of the " "sales order." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "" "Close subscription button on a customer's view of a sales order in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:83 msgid "" "When the customer clicks the :guilabel:`Close Subscription` button, a " ":guilabel:`Close Subscription` pop-up window appears, in which the customer " "has to choose from a select list of reasons why they are choosing to close " "the subscription." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "" "The close subscription pop-up window customers see when closing a " "subscription." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:92 msgid "" "Customers can *only* chose a pre-configured reason why the subscription is " "being closed. They can *not* enter a custom reason from the customer portal." " These selections can be adjusted by navigating to " ":menuselection:`Subscriptions --> Configuration --> Close Reasons`." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:96 msgid "" "Once the customer has chosen a close reason, they would click the " ":guilabel:`Submit` button on the pop-up window." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:99 msgid "" "Upon closure, the subscription order in the customer portal is tagged as " ":guilabel:`Closed`." msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:101 msgid "" "In addition, the specified :guilabel:`Close Reason` appears on the " "subscription order in the *Subscriptions* app in the backend " "(Administrator's view)." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:3 msgid "Subscriptions in the eCommerce shop" msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:5 msgid "" "Subscription products can be sold in the Odoo *eCommerce* shop just like " "regular sales products." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:7 msgid "" "However, by default, the eCommerce product page **only** displays the " "shortest recurrence period listed in the :guilabel:`Recurring Prices` tab of" " the product form." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:10 msgid "" "For example, if a subscription product has *monthly* and *annaul* recurrence" " periods configured, then *only* the monthly price appears on the eCommerce " "page for that product, by default." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:13 msgid "" "To add more recurrence periods to the eCommerce product page, create a " "*product variant* for each recurrence period." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:17 msgid "" ":doc:`Configure subscription products " "`" msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:18 msgid "" ":doc:`Product variants " "`" msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:21 msgid "Create recurrence periods as product variants" msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:23 msgid "" "To set up each recurrence period as a product variant, go to " ":menuselection:`Subscriptions app --> Products --> Products`, and select a " "product. In the :guilabel:`Attributes & Variants` tab, click :guilabel:`Add " "a line`." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:27 msgid "" "Then proceed to create an :guilabel:`Attribute` called `Billing Period` (or " "something similar), by typing in the name, and clicking :guilabel:`Create` " "from the mini drop-down menu that appears. This attribute name appears as " "option heading on the product page of the eCommerce shop." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:31 msgid "" "Next, create :guilabel:`Values` that correspond to the recurrence periods " "that are configured in the :guilabel:`Recurring Prices` tab of the product " "form." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:34 msgid "" "To do that, type in the name of the recurrence period in the " ":guilabel:`Values` column, on the same :guilabel:`Attribute` line, in the " ":guilabel:`Attributes & Variants` tab. Then, click :guilabel:`Create` from " "the mini drop-down menu that appears." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:38 msgid "" "These value names appear as selectable options on the product page of the " "eCommerce shop." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst-1 msgid "" "Recurrence periods configured as product variants in the \"Attributes & Variants\" tab of\n" "the product form." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:45 msgid "" "With those configurations in place and saved, a :guilabel:`Product Variants`" " column appears in the :guilabel:`Recurring Prices` tab. Proceed to assign " "the different :guilabel:`Product Variants` to their corresponding recurrence" " :guilabel:`Period` and :guilabel:`Price`." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst-1 msgid "Product variants on the \"Time-based pricing\" tab of the product form." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:53 msgid "" "After following those aforementioned steps, the product variants are " "available for selection on the eCommerce product page." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst-1 msgid "" "Recurrence periods configured as product variants on the eCommerce product " "page." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:3 msgid "SEPA Direct Debit" msgstr "SEPA direktna bremenitev" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:7 msgid "" "*SEPA*, or Single Euro Payments Area, is a payment-integration initiative of" " the European Union for simplifying bank transfers denominated in euros." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:10 msgid "" "*SEPA Direct Debit (|sdd|)* is a payment provider that allows future " "payments to be collected from customers' bank accounts by signing a mandate." " This allows recurring payments to be automatically gathered and processed " "using |sdd|." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:15 msgid "" "To create :ref:`direct debit mandates `, the" " **Accounting** app **must** be installed." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:24 msgid "" "Before using |sdd|, the database must be configured to allow the use of " "Euros on sales orders. To do so, a :doc:`pricelist " "<../../point_of_sale/pricing/pricelists>` must be created for Euros." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:27 msgid "" "This can be done using the **Sales** or **Point of Sales** apps. From either" " app, navigate to :menuselection:`Configuration --> Settings`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:30 msgid "" "In the :guilabel:`Pricing` section, underneath the :guilabel:`Pricelists` " "feature, click :icon:`fa-arrow-right` :guilabel:`Pricelists`. Then, click " "the :guilabel:`New` button to open a new pricelist form. Add a name for the " "pricelist in the top field, then set the drop-down menu next to " ":guilabel:`Currency` to :guilabel:`EUR`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:35 msgid "" "To use the wire transfer payment method, first ensure the |sdd| payment " "method is enabled. To do so, navigate to :menuselection:`Accounting app --> " "Configuration --> Settings`, scroll to the :guilabel:`Customer Payments` " "section, and tick the :guilabel:`SEPA Direct Deposit (SDD)` checkbox. Then, " "set a creditor identifier number in the field labeled, :guilabel:`Creditor " "Identifier`. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:42 msgid "" "The company using |sdd| must have a creditor identifier to issue a SEPA " "Direct Debit payment request. If using :ref:`test mode `, use the test creditor identifier number: " "`DE98ZZZ09999999999`, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:46 msgid "" "Next, enable SEPA Direct Debit from the *Payment Providers* page in either " "the **Accounting**, **Website**, or **Sales** apps." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:49 msgid "" "For example, navigate to :menuselection:`Accounting app --> Configuration " "--> Payment Providers`, then click the :guilabel:`SEPA Direct Debit` card." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:53 msgid "" "The *SEPA Direct Debit* form can also be reached by navigating to " ":menuselection:`Website app --> Configuration --> Payment Providers`, or " ":menuselection:`Sales app --> Configuration --> Payment Providers`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:57 msgid "" "Next, set the :guilabel:`State` to :guilabel:`Enabled` to enable |sdd|. Use " "the drop-down menus next to the :guilabel:`Company` and :guilabel:`Website` " "fields to set where |sdd| can be used." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:60 msgid "" "The options in the :guilabel:`Configuration` tab can be configured to " "customize how |sdd| is used. Optionally, tick the checkbox next to " ":guilabel:`Enable QR Codes` to enable the use of QR codes when paying by " "|sdd|, if desired." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:64 msgid "" "Use the drop-down menu next to the :guilabel:`Communication` field to select" " the communication type used on sales orders. Choose :guilabel:`Based on " "Document Reference` to use the sales order (or invoice number), or " ":guilabel:`Based on Customer ID` to use the customer identifier. With either" " method selected, communication is given to the customer, once they choose " "the |sdd| payment method." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:69 msgid "" "The configuration options listed under the :guilabel:`Availability` section " "are used to set payment restrictions, and are optional. Use the " ":guilabel:`Maximum Amount` field to set a maximum payment value, and the " ":guilabel:`Countries` field to restrict payment from any particular " "countries, if desired." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:75 msgid "" "The :guilabel:`Currencies` field should be left with the default " ":guilabel:`EUR` tag to ensure |sdd| is only accessible when customers pay " "with Euros." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:78 msgid "" "The :guilabel:`Payment Journal` field in the :guilabel:`Payment followup` " "section can be used to select the journal in which the successful " "transactions are posted." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:81 msgid "" "In the :guilabel:`Messages` tab, the :guilabel:`Pending Message` field can " "be used to add a message that is displayed, if the order remains pending " "after the payment is processed. By default, this field contains the message:" " :guilabel:`Please make an unique payment transfer to confirm the SEPA " "mandate.`" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst-1 msgid "The SEPA Direct Debit Payment Provider form." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:90 msgid "" "Once all necessary configuration settings are complete, the :icon:`fa-eye-" "slash` :guilabel:`Unpublished` smart button, located at the top of the page " "automatically changes to :icon:`fa-globe` :guilabel:`Published` to show the " "|sdd| payment option is now visible to customers. Only keep the payment " "method published if payments are ready to be received." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:96 msgid "" "It is possible to keep the payment method enabled, but **not** visible to " "customers, until payments are ready to be received. To do this, set the " "smart button to :icon:`fa-eye-slash` :guilabel:`Unpublished` after setting " "the :guilabel:`State` to :guilabel:`Enabled`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:101 msgid "" "The |sdd| configuration menu can also be accessed by navigating to " ":menuselection:`Settings app --> Website`, and in the :guilabel:`Shop - " "Payment` section, click the :icon:`fa-arrow-right` :guilabel:`View other " "providers` button. Then, click the |sdd| card. Alternatively, navigate to " ":menuselection:`Website app --> Configuration --> Settings` to access the " "same button." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:109 #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:75 msgid "Test mode" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:111 msgid "" "The |sdd| payment method can be tested before it is accessed by customers. " "First, ensure the test creditor identifier is :ref:`configured " "` before continuing." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:115 #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:91 msgid "" "It is recommended to use the :guilabel:`Test Mode` setting on a duplicate " "(or test) database to avoid potential issues with invoice numbering." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:118 msgid "" "Next, select the :guilabel:`Test Mode` option in the :guilabel:`State` field" " on the form. Upon selecting :guilabel:`Test Mode`, an orange " ":guilabel:`Test mode` banner appears in the upper-right corner of the form." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:123 #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:87 msgid "" "By default, the payment provider remains :guilabel:`Unpublished` in " ":guilabel:`Test Mode`, so it is not visible to visitors." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:126 msgid "" "Navigate to :menuselection:`Sales app --> Orders --> Quotations`, and click " "the :guilabel:`New` button to create a new sales order." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:129 msgid "" "Select a :guilabel:`Customer`. Select any pay period in the drop-down menu " "next to :guilabel:`Recurring Plan` and select the pricelist using EUR in the" " drop-down menu next to :guilabel:`Pricelist`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:133 msgid "" "Finally, select a subscription product in the :guilabel:`Order Lines` tab of" " the sales order." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:135 msgid "" "Next, confirm the sales order by clicking the :guilabel:`Confirm` button, " "then click the :guilabel:`Preview` button to open a preview of the customer " "invoice. Scroll down to the :guilabel:`Anticipate payment` section to find " "the SEPA Direct Debit payment method." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:140 msgid "" "It can be confirmed that test mode is still enabled if the :icon:`fa-eye-" "slash` (unpublished) and :icon:`fa-exclamation-triangle` (test mode) icons " "are present next to SEPA Direct Debit." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:0 msgid "" "The view of the SEPA Direct Debit payment method presented to customers at " "checkout." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:147 msgid "" "Next, enter a test IBAN number, such as `GB33BUKB20201555555555`, and click " ":guilabel:`Pay`. Return to the sales order in the **Sales** app, and confirm" " the :guilabel:`In Progress` tag is present on the sales order form. At this" " point, the flow is complete." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:151 msgid "" "To re-enable normal function after testing, navigate back to the *SEPA " "Direct Debit* form, and change the *State* setting to :guilabel:`Enabled`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:157 msgid "Pay by SEPA Direct Debit" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:159 msgid "" "Once |sdd| has been :ref:`configured `" " and enabled, |sdd| appears as a payment method during checkout in " "**eCommerce**, and as a payment method on invoices in the **Sales** app. The" " option is presented to customers, and prompts them to enter their IBAN " "number." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:164 msgid "" "Once a customer clicks *Pay*, the sales order is marked with a *In Progress*" " tag until the mandate has been closed." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:167 msgid "" "Mandates automatically close after the end date is reached. If the *End " "date* field is not set, the mandate remains in an *Active* state until it is" " *Closed* or *Revoked*." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:170 msgid "" "|sdd| payments can also be registered manually by navigating to the desired " "invoice and clicking the :guilabel:`Register Payment` button. Next, select " ":guilabel:`SEPA Direct Debit` as the :guilabel:`Payment Method` and click " "the :guilabel:`Create Payment` button. The invoice now displays a green " ":guilabel:`In Payment` banner." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:176 msgid "" "To validate a successful |sdd| payment, navigate to " ":menuselection:`Accounting app --> Customers --> Payments`, and look for the" " entry in the list, along with a :guilabel:`Posted` tag in the " ":guilabel:`Status` column." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:181 msgid "Submit payments" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:183 msgid "" "All |sdd| payments can be processed at once by uploading an `.xml` file " "containing a batch of all posted |sdd| payments to an online banking " "interface. To generate this file, navigate to :menuselection:`Accounting app" " --> Customers --> Batch Payments`. A list of all posted |sdd| payments " "appears. Tick the checkbox next to every payment to be included in the " "batch, or tick the checkbox at the top of the list to select all entries at " "once." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:189 msgid "" "Next, click :guilabel:`Create Batch`. A new batch payment form appears with " "the selected payments added to the list in the :guilabel:`Batch Content` " "tab." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst-1 msgid "The batch payment form containing the selected payments." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:196 msgid "" "This form also contains optional fields to customize the batch payment:" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:198 msgid ":guilabel:`Bank`: Select the bank the payment is sent to." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:199 msgid ":guilabel:`Date`: Set the current date." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:200 msgid ":guilabel:`Reference`: Set a custom reference number for the payment." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:201 msgid "" ":guilabel:`Required collection date`: Set a date when the company expects to" " receive the payment of this batch." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:203 msgid "" ":guilabel:`Batch Booking`: Request batch booking from the bank for the " "related bank statements." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:204 msgid "" ":guilabel:`SDD Scheme`: The B2B scheme is an optional scheme, offered " "exclusively to business payers. Some banks/businesses might not accept B2B " "|sdd|." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:207 msgid "" "Once the payment is configured, click :guilabel:`Validate` to generate the " "`.xml` file, which appears in the chatter. Finally, click the :icon:`fa-" "download` :guilabel:`(download)` icon next to the file in the chatter to " "download the file." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:211 msgid "" "This file can now be uploaded to the desired online banking interface to " "process the payments." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:214 msgid "" "The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02**" " specifications, as required by the SEPA customer-to-bank `implementation " "guidelines `_, which ensures compatibility with the banks." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:220 msgid ":doc:`../../../finance/accounting/payments/batch_sdd`" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/sdd.rst:221 msgid ":doc:`../../../finance/accounting/payments/online`" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:3 msgid "Wire transfer" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:5 msgid "" "The *wire transfer* payment method allows for payment instructions to be " "shared with a customer after purchasing a product. With a subscription, " "these payment instructions are shared every time the payment is renewed." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:10 msgid "" "The wire transfer payment method requires minimal setup, but in most cases, " "it is inefficient compared to other online payment providers. It is " "recommended to use another payment provider with subscriptions, due to wire " "transfers requiring manual confirmation for each payment." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:19 msgid "" "To use the wire transfer payment method, first ensure the *Wire Transfer* " "payment method is enabled." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:21 msgid "" "To do so, begin by navigating to the *Payment Providers* page in either the " "**Accounting**, **Website**, or **Sales** apps." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:24 msgid "" "For example, navigate to :menuselection:`Accounting app --> Configuration " "--> Online Payments: Payment Providers`, then click the :guilabel:`Wire " "Transfer` card." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:28 msgid "" "If the **Accounting** app is not installed, the *Payment Providers* page can" " also be reached by navigating to :menuselection:`Website app --> " "Configuration --> eCommerce: Payment Providers`, or :menuselection:`Sales " "app --> Configuration --> Online Payments: Payment Providers`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:32 msgid "" "Next, set the :guilabel:`State` to :guilabel:`Enabled` to enable wire " "transfers. Use the drop-down menus next to the :guilabel:`Company` and " ":guilabel:`Website` fields to set where wire transfers can be used." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:36 msgid "" "The options in the :guilabel:`Configuration` tab can be used to customize " "the wire transfer. Optionally tick the checkbox next to :guilabel:`Enable QR" " Codes` to enable the use of QR codes when paying by wire transfer, if " "desired." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:40 msgid "" "Use the drop-down menu next to the :guilabel:`Communication` field to select" " the communication type used on sales orders. Choose :guilabel:`Based on " "Document Reference` to use the sales order (or invoice number), or " ":guilabel:`Based on Customer ID` to use the customer identifier. With either" " method selected, communication is given to the customer, once they choose " "the wire transfer payment method." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:46 msgid "" "The configuration options listed under the :guilabel:`Availability` section " "are used to set payment restrictions, and are optional. Use the " ":guilabel:`Maximum Amount` field to set a maximum payment value, the " ":guilabel:`Currencies` field to restrict any currencies from being used for " "payment, and the :guilabel:`Countries` field to restrict payment from any " "particular countries, if desired." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:51 msgid "" "In the :guilabel:`Messages` tab, use the :guilabel:`Pending Message` field " "to add a message containing wire transfer information. This message is " "displayed to the customer after confirming their order, as well as if the " "order is marked as pending after the payment is processed." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:55 msgid "" "If :doc:`a bank account <../../../finance/accounting/bank>` has already been" " defined, the account number is automatically added to the default message " "generated by Odoo. A bank account can also be added afterwards, and the " "message updates with the appropriate bank information by clicking :icon:`fa-" "refresh` :guilabel:`Reload pending message`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:60 msgid "" "Once all necessary configuration settings are complete, the :icon:`fa-eye-" "slash` :guilabel:`Unpublished` smart button located at the top of the page " "automatically changes to :icon:`fa-globe` :guilabel:`Published` to show the " "wire transfer payment option is now visible to customers. Only keep the " "payment method published if payments are ready to be received." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:66 msgid "" "It is possible to keep the payment method enabled, but **not** visible to " "customers, until payments are ready to be received. To do that, set the " "smart button to :icon:`fa-eye-slash` :guilabel:`Unpublished` after setting " "the :guilabel:`State` to :guilabel:`Enabled`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst-1 msgid "The wire transfer card enabled and published." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:77 msgid "" "The wire transfer payment method can be tested before it is accessed by " "customers by selecting the :guilabel:`Test Mode` option in the " ":guilabel:`State` field on the form. Upon selecting :guilabel:`Test Mode`, " "an orange :guilabel:`Test mode` banner appears in the upper-right corner of " "the form." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:82 msgid "" "Next, enter the credentials for a bank account with accessible transactions " "in the :guilabel:`Messages` tab. To re-enable normal function after testing," " change the :guilabel:`State` setting to :guilabel:`Enabled`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:97 msgid "Pay by wire transfer" msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:99 msgid "" "With wire transfers :ref:`enabled and published `, customers see wire transfers as an available " "payment method at checkout when purchasing a product." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:102 msgid "" "When this method is selected by a customer, they are shown the *Pending " "Message* set in the :ref:`wire transfer configuration page " "`, after confirming their " "purchase. Once the purchase is confirmed, a sales order is created." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst-1 msgid "The wire transfer pending message shown to customers." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:111 msgid "" "Online orders remain in the *Quotation sent* (i.e. unpaid order) stage until" " both the payment is received, *and* the order is confirmed manually, using " "the :guilabel:`Confirm` button on the sales order." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:115 msgid "" "To begin processing the payment, navigate to :menuselection:`Sales app --> " "Orders --> Orders`, and click the corresponding sales order. Ensure the " "sales order is correct, then click :guilabel:`Confirm` to confirm the sales " "order." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:119 msgid "" "Next, click the new :guilabel:`Create Invoice` button, then choose " ":guilabel:`Regular invoice`, and click :guilabel:`Create Draft Invoice`. A " "draft of the invoice appears. Click :guilabel:`Confirm` to validate the " "invoice." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:123 msgid "" "To send this invoice to the customer, click the :guilabel:`Send & Print` " "button. A :guilabel:`Send` pop-up window appears, with an email template " "configured, and a PDF invoice attached." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:126 msgid "" "Ensure the information is correct, then click :guilabel:`Send & Print`. The " "pop-up window disappears, and the :guilabel:`Send & Print` button turns gray" " to show the invoice has been sent." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:130 msgid "" "The default template for sending an invoice can be modified by navigating to" " :menuselection:`Settings app --> Companies --> Email Templates --> Review " "All Templates --> Invoice: Sending`." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:134 msgid "" "Next, click the :guilabel:`Register payment` button on the invoice page. A " "pop-up window titled, :guilabel:`Register Payment`, appears with options for" " selecting the type of payment. In the :guilabel:`Journal` field, select " ":guilabel:`Bank` from the drop-down menu. Next, set the :guilabel:`Payment " "Method` to :guilabel:`Manual`. Ensure the :guilabel:`Amount` and " ":guilabel:`Payment Date` are correct, then click the :guilabel:`Create " "Payment` button." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst-1 msgid "The register payment pop-up window." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:144 msgid "" "The customer invoice is revealed with a green :guilabel:`In Payment` banner " "in the upper-right corner. At this point, the flow is now complete." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst-1 msgid "The green in payment banner displayed on the invoice." msgstr "" #: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:152 msgid "" "If payment has been received before sending the invoice, such as in cash, " "the payment can still be registered in Odoo by clicking the " ":guilabel:`Register Payment` button, and creating the payment *before* " "clicking :guilabel:`Send & Print`. Now, when an invoice is sent using the " ":guilabel:`Send & Print` button, a new line is automatically added to the " "invoice message, stating the invoice is already paid." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:3 msgid "Subscription plans" msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:5 msgid "" "*Subscription plans* are :doc:`quotation templates " "` used to " "preconfigure quotations with subscription products. Use subscription plans " "to quickly create subscription orders." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:10 msgid "Configure subscription plans" msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:12 msgid "" "To configure subscription plans, go to :menuselection:`Subscriptions --> " "Configuration --> Plans`. Then, click :guilabel:`New` to create a new plan, " "or select an existing plan to edit it." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:15 msgid "" "Since the Odoo *Subscriptions* app is integrated closely with the *Sales* " "app, subscription plans use the same form as quotation templates." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst-1 msgid "Subscription plan (quotation template) configuration form." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:22 msgid "The subscription plan form contains the following options:" msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:24 msgid "" ":guilabel:`Name`: Enter a name for the subscription plan at the top of the " "page." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:25 msgid "" ":guilabel:`Quotation expires after`: Enter the number of days after which " "the quotation expires, starting from the day the quotation is sent to the " "customer. Leave this field at zero for the quotation to never expire." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:28 msgid "" ":guilabel:`Online Confirmation`: Check the boxes next to " ":guilabel:`Signature` or :guilabel:`Payment` to enable the customer to " "confirm their subscription order by signing or paying for the quotation. " "Enable both to leave the choice to the customer. Enable neither to only " "confirm the quotation in the backend." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:32 msgid "" ":guilabel:`Confirmation Mail`: Select an :doc:`email template " "` for the confirmation email" " that is automatically sent to the customer after the quotation is " "confirmed. Leave this field blank to send nothing." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:37 msgid "" "To create a new email template, enter a name for the template, then click " ":guilabel:`Create and edit`." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:39 msgid "" "To edit an existing email template, select one from the drop-down menu, then" " click on the :guilabel:`Internal link` arrow at the end of the line." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:42 msgid "" ":guilabel:`Recurrence`: Select the recurrence period used for the plan. The " "recurrence periods available here are the same ones that are configured in " ":menuselection:`Subscriptions --> Configuration --> Recurrence Periods`." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:46 msgid "" "Selecting a :guilabel:`Recurrence` turns the quotation template into a " "subscription plan and enables the following additional options:" msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:49 msgid "" ":guilabel:`Duration`: Choose whether the subscription plan has no end date " "(:guilabel:`Forever`) or a :guilabel:`Fixed` duration." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:52 msgid "" "If the duration is :guilabel:`Forever`, then the subscription plan will " "continually renew until either the customer or the company manually ends the" " subscription." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:54 msgid "" "If the duration is :guilabel:`Fixed`, then enter an :guilabel:`End After` " "date, which determines the amount of time after which the subscription will " "automatically end." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:57 msgid "" ":guilabel:`Self Closable`: Check this box to enable the customer to " "terminate their subscription from the :doc:`customer portal " "`." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:60 msgid "" ":guilabel:`Automatic Closing`: Enter the number of days after which *unpaid*" " subscriptions *past* the due date are automatically closed." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:62 msgid "" ":guilabel:`Invoicing Journal`: Select the accounting journal in which " "invoices for this subscription plan are recorded. Leave this field blank to " "use the sales journal with the lowest sequence." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst-1 msgid "Subscription plan with Recurrence selected." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:70 msgid "" "In the :guilabel:`Lines` tab, create the order lines for the quotation. " "Click :guilabel:`Add a product`, select a product to include in the plan, " "and then enter the :guilabel:`Quantity` and :guilabel:`Unit of Measure`. Add" " as many products as desired to the order lines." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:74 msgid "" "In the :guilabel:`Optional Products` tab, enter any optional products that " "the customer can add to their quotation before confirming the order." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:77 msgid "" "If the subscription plan has unique :doc:`terms and conditions " "`, add " "them in the :guilabel:`Terms & Conditions` tab. If terms conditions are " "specified on a plan, these will be used instead of the default terms and " "conditions set up in the *Sales* app settings." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst-1 msgid "Subscription plan Terms & Conditions tab." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:87 msgid "Use subscription plans on quotations" msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:89 msgid "" "Quotations for subscription products can be created in both the " "*Subscriptions* app and the *Sales* app." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:92 msgid "" "From the :guilabel:`Subscriptions` dashboard, click :guilabel:`New` to " "create a new quotation. Then, select a subscription plan in the " ":guilabel:`Subscription Plan` field." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:95 msgid "" "The :guilabel:`Recurrence`, products, and other information from the plan " "are automatically filled in. The quotation can then be modified further as " "needed." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:98 msgid "" "From the :guilabel:`Sales` dashboard, click :guilabel:`New` to create a new " "quotation. Then, select a subscription plan in the :guilabel:`Quotation " "Template` field." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:101 msgid "" "All subscription orders will appear on the :guilabel:`Subscriptions` " "dashboard regardless of whether they were created in the *Subscriptions* app" " or the *Sales* app." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:3 msgid "Subscription products" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:5 msgid "" "By closely integrating with the Odoo *Sales* app, the *Subscriptions* app " "enables users to sell subscription products alongside regular sales " "products. While regular products are sold on a one-time basis, subscription " "products are sold on a renewing basis, generating recurring revenue." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:9 msgid "In Odoo, subscription products are also called *recurring* products." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:12 msgid "Configure recurrence periods" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:14 msgid "" "To get started with subscriptions, the *recurrence periods* must be properly" " configured, as needed." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:16 msgid "" "Recurrence periods are the time periods in which subscriptions renew. They " "designate how often the customer pays for (and receives) subscription " "products." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:19 msgid "" "To configure recurrence periods, go to :menuselection:`Subscriptions app -->" " Configuration --> Recurrence periods`." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst-1 msgid "The recurrence periods page in Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:26 msgid "" "The *Subscriptions* app comes with some basic recurrence periods already " "configured:" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:28 msgid ":guilabel:`Monthly`" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:29 msgid ":guilabel:`Quarterly`" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:30 msgid ":guilabel:`Weekly`" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:31 msgid ":guilabel:`2 Weeks`" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:32 msgid ":guilabel:`Yearly`" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:33 msgid ":guilabel:`3 Years`" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:34 msgid ":guilabel:`5 Years`" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:36 msgid "New recurrence periods can be added and/or edited at any time." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:38 msgid "" "To create a new recurrence period, click :guilabel:`New` on the " ":guilabel:`Recurrence Periods` page. Doing so reveals a blank recurrence " "period form." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst-1 msgid "A recurrence period form in Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:45 msgid "" "Then, type in the :guilabel:`Name` and :guilabel:`Duration` of the " "recurrence period, and select the :guilabel:`Unit` that defines the " "duration." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:49 msgid "" "The unit :guilabel:`Days` *cannot* be used as a recurrence period on " "subscriptions. The daily recurrence is meant for rentals, and **cannot** be " "added on recurring subscription sales orders." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:52 msgid "" "This limitation is there to avoid sales orders that would generate daily " "invoices." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:55 msgid "Product form configuration" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:57 msgid "" "To create a new subscription product, navigate to " ":menuselection:`Subscriptions app --> Products --> Products`, and click " ":guilabel:`New`." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:60 msgid "" "Doing so reveals a blank product form, which can be configured and " "customized in a number of ways." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:63 msgid "" "By default, the :guilabel:`Recurring` option is already enabled, prompting " "Odoo to recognize it as a subscription product. Be sure to leave the " ":guilabel:`Recurring` and :guilabel:`Can be Sold` options enabled." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:67 msgid "" "The :guilabel:`Product Type` field is set to :guilabel:`Service` by default," " as well. However, subscription products *can* be set to other types, if " "needed." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:71 msgid "" "When creating a physical subscription product in the Odoo **Sales** " "application, the :guilabel:`Invoicing Policy` must be set to " ":guilabel:`Ordered quantities`." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:74 msgid "" "Setting it to :guilabel:`Delivered quantities` causes issues with invoice " "creation, and disrupts the subscription process." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:77 msgid "" "Similarly, when creating a physical subscription product in the Odoo " "**Subscriptions** application, the :guilabel:`Invoicing Policy` must **not**" " be set to :guilabel:`Based on Delivered Quantity (Manual)` for the same " "reasons." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst-1 msgid "A basic subscription product form in Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:86 msgid "Time-based pricing" msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:88 msgid "" "Once the desired fields in the :guilabel:`General Information` tab have been" " entered, click the :guilabel:`Time-based pricing` tab on the product form." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst-1 msgid "" "The time-based pricing tab on a subscription product form in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:95 msgid "" "From here, click :guilabel:`Add a price` to begin defining recurring prices." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:97 msgid "" "In the :guilabel:`Period` column, select a desired recurrence period. In the" " :guilabel:`Pricelist` column, select a pricelist, if needed. Then, in the " ":guilabel:`Price` column, enter the price for that recurrence period." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:102 msgid "" ":guilabel:`Daily` and :guilabel:`Hourly` periods **cannot** be used on " "recurring products." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:0 msgid "The validation error pop-up window that appears in Odoo Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:109 msgid "" "There is *no limit* to how many lines can be added to the :guilabel:`Time-" "based pricing` table." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:112 msgid "" "An existing product can be made into a subscription product, simply by " "marking it as :guilabel:`Recurring`, and configuring :guilabel:`Time-based " "pricing` on the product form." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:118 msgid "" ":doc:`Pricelists <../sales/products_prices/prices/pricing>` can be used with" " subscription products to give special pricing to customers included in " "pricelists." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:121 msgid "" "This can be configured either in the :guilabel:`Time-based pricing` tab of " "the product form, or on the pricelist form in the *Sales* application." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:124 msgid "" "To create recurring price rules for specific pricelists in the " ":guilabel:`Time-based pricing` tab of the product form, select a pricelist " "in the :guilabel:`Pricelist` column." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst-1 msgid "Pricelists in the \"Time-based pricing\" tab of the product form." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:131 msgid "" "When pricelists are added to the :guilabel:`Time-based pricing` tab, the " "pricelist form in the *Sales* app is automatically updated." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:134 msgid "" "Time-based pricing rules can also be configured directly on the pricelist " "form." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:136 msgid "" "To do this, go to :menuselection:`Sales app --> Products --> Pricelists`, " "and select a pricelist (or click :guilabel:`New` to create a new pricelist)." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:140 msgid "" "Pricelists are also accessible through the Odoo *Subscriptions* app by " "following the same menu steps." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:143 msgid "" "Then, on the pricelist form, under the :guilabel:`Time-based rules` tab, " "click :guilabel:`Add a line`." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst-1 msgid "The time-based rules tab on a pricelist form in Odoo Sales." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:150 msgid "" "Then, select a subscription product in the :guilabel:`Products` column, and " "select a recurrence period in the :guilabel:`Period` column. Lastly, enter a" " :guilabel:`Price` for that particular product and period. Add as many lines" " as needed." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:154 msgid "" "When :guilabel:`Time-based rules` are added to the pricelist form, the " ":guilabel:`Time-based pricing` tab of the product form is automatically " "updated." msgstr "" #: ../../content/applications/sales/subscriptions/products.rst:158 msgid ":doc:`ecommerce`" msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:3 msgid "Renew subscriptions" msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:5 msgid "" "The foundation of any subscription business model is recurring payments. " "This is when customers reliably pay a regular amount at specific intervals, " "in exchange for access to a subscription product or service." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:9 msgid "" "Subscription renewal is the process customers follow when they willingly " "choose to continue participating in, and paying for, a subscription product " "or service." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:12 msgid "" "Subscribers experience the renewal process at different intervals -- weekly," " monthly, annually, etc. -- depending on the duration of the agreed-upon " "contract." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:15 msgid "" "Most companies that offer subscriptions prefer to automate the renewal " "process for customers. However, manual subscription renewals are still used " "in some cases." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:18 msgid "" "With the Odoo **Subscriptions** application, a company can manage all of its" " subscriptions in one place. Renewals can be processed automatically, or " "manually, include additional products or upsells per renewal order, and be " "filtered in batch views to quickly locate customers who need to renew their " "subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:24 msgid "Subscription renewals" msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:26 msgid "" "In order to renew a subscription, a quotation with a subscription product " "**must** be confirmed, with a configured *Recurring Plan* selected." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:29 msgid "" "To open a subscription quotation, navigate to :menuselection:`Subscriptions " "app --> Subscriptions --> Quotations`, and select the desired quotation from" " the list. Or, create a new one by clicking :guilabel:`New` to open a new " "quotation form." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:34 msgid "Only a singular product is required." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:35 msgid "" "A subscription service counts as a product, as it is considered a recurring " "product." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:37 msgid "" "Subscription quotations **must** be confirmed, and payment from the customer" " for the initial subscription **must** be invoiced and registered in order " "to successfully open a *Renewal Quotation*." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:42 msgid "" "For more information on the above process of confirming quotations and " "invoicing payments, see: - :doc:`../sales/send_quotations/create_quotations`" " - :doc:`../sales/send_quotations/get_paid_to_validate`" msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:47 msgid "" "Once the payment from the subscription quotation is confirmed, the quotation" " turns into a sales order. An :guilabel:`In Progress` tag is applied to the " "sales order form, and a series of buttons also appear at the top of the " "sales order, including a :guilabel:`Renew` button." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst-1 msgid "Renew button on subscription sales order with Odoo Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:55 msgid "" "When the :guilabel:`Renew` button is clicked, Odoo instantly presents a new " "renewal quotation, complete with a :guilabel:`Renewal Quotation` tag." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst-1 #: ../../content/applications/sales/subscriptions/renewals.rst-1 msgid "Renewal quotation in the Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:62 msgid "" "From here, a standard sales flow can occur to confirm the quotation. This " "typically begins by clicking :guilabel:`Send by Email`, which sends a copy " "of the quotation to the customer, by email, for them to confirm, and " "eventually, pay for." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:67 msgid "" "In the chatter of the :guilabel:`Renewal Quotation`, it is mentioned that " "this subscription is the renewal of the subscription from the original sales" " order." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:70 msgid "" "Once the :guilabel:`Renewal Quotation` is confirmed, it becomes a sales " "order, and a :guilabel:`Sales History` smart button appears at the top of " "the page." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst-1 msgid "Sales History smart button in the Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:77 msgid "" "When that :guilabel:`Sales History` smart button is clicked, Odoo reveals a " "separate page, showcasing the different sales orders attached to this " "subscription, along with their individual :guilabel:`Subscription Status`." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:85 msgid "" "Additionally, once the :guilabel:`Renewal Quotation` is confirmed, an " ":guilabel:`MRR` smart button also appears at the top of the sales order." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst-1 msgid "MRR smart button in the Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:92 msgid "" "When clicked, Odoo reveals an :guilabel:`MRR Analysis` page, detailing the " "monthly recurring revenue related to this specific subscription." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:96 msgid "" "On rare occasions, automatic payment can fail, which results in a *Payment " "Failure* tag on the top-right of the sales order, if there is an error in " "the payment method." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:99 msgid "" "This is done to prevent the system from charging the customer again the next" " time a scheduled action is run. Because the status of the payment is " "unknown, Odoo requests a manual operation to check if the payment has been " "made, before the payment can be used again." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:103 msgid "" "To do this, navigate to :menuselection:`Subscriptions app --> Subscriptions " "--> Quotations`. Click into the desired subscription, then check the " "*Chatter* to see if the payment was made." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:106 msgid "" "If the payment was **not** made, first enter :doc:`debug mode " "<../../general/developer_mode>`. Then, click the :guilabel:`Other Info` tab," " and untick the checkbox next to :guilabel:`Contract in exception`. Reload " "the sales order, and the :guilabel:`Payment Failure` tag is gone." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:110 msgid "" "If the payment **was** made, a new invoice must be made and posted manually." " This automatically updates the next invoice date of the subscription. Once " "created, enter :doc:`debug mode <../../general/developer_mode>`, and " "navigate to the new sales order. Click the :guilabel:`Other Info` tab, and " "untick the checkbox next to :guilabel:`Contract in exception`. Reload the " "sales order, and the :guilabel:`Payment Failure` tag is gone." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:0 msgid "" "The \"contract in exception\" option selected with the \"payment failure\" " "tag shown." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:120 msgid "" "The :guilabel:`contract in exception`` option selected with the " ":guilabel:`payment failure` tag shown." msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:123 msgid "" "In both cases, once the :guilabel:`Contract in exception` option is no " "longer selected, Odoo handles renewals automatically again. If the " "subscription remains in *payment failure*, it is skipped by Odoo until the " "sales order is closed." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:3 msgid "Subscription reports" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:8 msgid "" "The Odoo **Subscriptions** app provides a series of reporting pages to help " "companies analyze how subscriptions are performing." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:11 msgid "" "On the *Subscriptions Analysis* reporting page, users can view specific data" " related to recurring subscriptions, quantity of subscriptions, in-progress " "or paused subscriptions, and more." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:14 msgid "" "The *Retention Analysis* reporting page provides an organized table of " "subscription retention percentages over any period of time." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:17 msgid "" "The *MRR Breakdown* reporting page clearly divides |MRR| and |ARR| metrics " "for subscriptions into various graphs, lists, and charts." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:20 msgid "" "And the *MRR Analysis* reporting page offers a time-based collection of " "analytics showcasing how subscription |MRR| and |ARR| have changed over the " "course of any given period of time." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:24 msgid "Reporting page elements" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:26 msgid "" "All subscriptions-based reporting pages can be accessed via the " ":guilabel:`Reporting` header menu in the **Subscriptions** app." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:29 msgid "The following sections describe elements found on each reporting page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:32 msgid "Filters and Group By" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:34 msgid "" "*Filters* are used to narrow down metrics to show specific analytics, " "whereas groupings (via the *Group By* option) are used to gather the data " "from specific sections into groups for more organized analysis." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:38 msgid "" "This section refers to both filters and groupings, as a combination of the " "two can be saved in the *Favorites* section." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:41 msgid "" "To modify the results being shown on any reporting page, click the " ":icon:`fa-caret-down` :guilabel:`(down arrow)` icon to the right of the " "search bar. Doing so reveals a drop-down menu of detailed filter and " "grouping options." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:45 msgid "" "If desired, a filter or grouping (or combination of filters and/or " "groupings) can be saved in the :guilabel:`Favorites` section of that drop-" "down menu. To do so, click the :icon:`fa-caret-down` :guilabel:`(down " "arrow)` icon beside :guilabel:`Save current search`, located beneath the " ":guilabel:`Favorites` section." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:50 msgid "" "This reveals a field to assign a title to the favorite filter. Two options " "are also found beneath the title field: :guilabel:`Default filter` and " ":guilabel:`Shared`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:53 msgid "" "Ticking the checkbox beside :guilabel:`Default filter` makes the newly-" "favorited filter the default option for that reporting page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:56 msgid "" "Ticking the checkbox beside :guilabel:`Shared` makes the newly-favorited " "filter available to other users in the database." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:60 msgid "" "The :guilabel:`Default filter` and :guilabel:`Shared` options are **not** " "required, and only *one* of these options can be selected at a time." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:63 msgid "" "To save the filter, click :guilabel:`Save` in the :guilabel:`Favorites` " "section of the drop-down filter menu." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:66 msgid "" "When clicked, that saved filter appears beneath the :guilabel:`Favorites` " "column of the drop-down filter menu, and a :icon:`fa-star` :guilabel:`(gold " "star)` icon appears beside the favorite filter's name in the search bar." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:71 msgid "Views" msgstr "Prikazi" #: ../../content/applications/sales/subscriptions/reports.rst:73 msgid "" "On the :guilabel:`Subscription Analysis`, :guilabel:`MRR Breakdown`, and " ":guilabel:`MRR Analysis` reporting pages, three different view options are " "located in the upper-right corner." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:77 msgid "" "There are *no* other view options available on the :guilabel:`Retention " "Analysis` reporting page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:79 msgid "The available view options, from left to right, are:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:81 msgid ":guilabel:`Graph`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:82 msgid ":guilabel:`List`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:83 msgid ":guilabel:`Pivot`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "" "The different view options available on the Subscriptions Analysis page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:89 msgid "Each view has its own series of related view-specific visual options." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:94 msgid "" "With the graph view selected, the following options appear between the " "search bar and visual representation of the data. These graph-specific " "options are located to the right of the :guilabel:`Measures` and " ":guilabel:`Insert in Spreadsheet` buttons." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "The different graph view options in the Odoo Subscriptions app." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:102 msgid "" "The first three options, from left to right, represent different graph-" "related views. The remaining options represent different ways to organize " "and visualize that specific graph-related data." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:105 msgid "From left to right, the specific graph-related view options are:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:107 msgid "" ":icon:`fa-bar-chart` :guilabel:`Bar Chart`: showcases the data in a bar " "chart format." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:108 msgid "" ":icon:`fa-line-chart` :guilabel:`Line Chart`: showcases the data in a line " "chart format." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:109 msgid "" ":icon:`fa-pie-chart` :guilabel:`Pie Chart`: showcases the data in a pie " "chart format." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:111 msgid "" "Each graph view option has its own series of specific visual options, which " "are represented by the available buttons that appear to the right of the " "selected graph-related view option." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:114 msgid "" "When the :icon:`fa-bar-chart` :guilabel:`Bar Chart` graph view is selected, " "the following visual options are available:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:117 #: ../../content/applications/sales/subscriptions/reports.rst:123 msgid "" ":icon:`fa-database` :guilabel:`Stacked`: showcases the data in a stacked " "visual format." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:118 #: ../../content/applications/sales/subscriptions/reports.rst:125 msgid "" ":icon:`fa-sort-amount-desc` :guilabel:`Descending`: showcases the data in " "descending order." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:119 #: ../../content/applications/sales/subscriptions/reports.rst:126 msgid "" ":icon:`fa-sort-amount-asc` :guilabel:`Ascending`: showcases the data in " "ascending order." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:121 msgid "" "When the :guilabel:`Line Chart` graph view is selected, the following visual" " options are available:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:124 msgid "" ":icon:`fa-signal` :guilabel:`Cumulative`: showcases the data in accumulated," " increasing format." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:128 msgid "" "When the :guilabel:`Pie Chart` graph view is selected, there are no " "additional visual options." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:133 msgid "" "With the list view selected, the subscription metrics being analyzed are " "displayed in a simple list, which can be fully customized by using any of " "the available filters or groupings in the drop-down filter menu (accessible " "via the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to the right of " "the search bar)." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:139 msgid "" "With list view selected, the :guilabel:`Measures` drop-down menu and " ":guilabel:`Insert in Spreadsheet` button are *not* available." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:145 msgid "" "With the pivot view selected, the subscription metrics are displayed in a " "data table, which can be fully customized." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:148 msgid "" "The pivot data table can be customized using the options available in the " ":guilabel:`Measures` drop-down menu, and/or the filter grouping options " "available in the filter drop-down menu (accessible via the :icon:`fa-caret-" "down` :guilabel:`(down arrow)` icon to the right of the search bar)." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:153 msgid "" "Three pivot-specific options are available, located to the right of the " ":guilabel:`Measures` drop-down menu and :guilabel:`Insert in Spreadsheet` " "button." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "" "The pivot-specific view options available in the Odoo Subscriptions app." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:160 msgid "From left to right, those pivot-specific view options are:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:162 msgid "" ":icon:`fa-exchange` :guilabel:`Flip axis`: the `x` and `y` axis of the pivot" " data table flip." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:163 msgid "" ":icon:`fa-arrows` :guilabel:`Expand all`: all the available rows and columns" " of the pivot data table expand fully." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:165 msgid "" ":icon:`fa-download` :guilabel:`Download .xlsx`: the pivot data table is " "downloaded as an :file:`.xlsx` file." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:169 msgid "Measures" msgstr "Izmere" #: ../../content/applications/sales/subscriptions/reports.rst:171 msgid "" "The graph and pivot reporting pages have their own metric-specific " ":guilabel:`Measures` drop-down menu of data-related options to choose from, " "located in the upper-left corner, above the visual representation of " "metrics." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "The standard measures drop-down menu in the Odoo Subscriptions app." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:179 msgid "" "When the :guilabel:`Measures` button is clicked, a series of selectable " "measures becomes available, via a drop-down menu. When any of the options " "are selected from the :guilabel:`Measures` drop-down menu, the chosen " "metrics related to that specific measure appear on the reporting page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:184 msgid "" "For more information on the different measures that can be utilized on each " "reporting page, refer to the :ref:`specific reporting page breakdowns " "` found below in this documentation." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:189 msgid "Insert in spreadsheet" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:191 msgid "" "Beside the :guilabel:`Measures` drop-down menu, there is an " ":guilabel:`Insert in Spreadsheet` button." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:194 msgid "" "When clicked, the ability to add the configured data currently being " "showcased on the reporting page into a new or pre-existing spreadsheet or " "dashboard becomes available, via a pop-up window." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "The spreadsheet pop-up window of the Subscriptions Analysis page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:201 msgid "" "Select the desired option from this pop-up window, then click " ":guilabel:`Confirm`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:206 msgid "Reporting pages" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:208 msgid "" "In the Odoo **Subscriptions** app, there are four different reporting pages " "available." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:210 msgid "" "To access, analyze, and customize various reports related to subscriptions, " "navigate to :menuselection:`Subscriptions app`, and click the " ":guilabel:`Reporting` drop-down menu in the header to reveal the following " "reporting pages:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:214 msgid ":guilabel:`Subscriptions`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:215 msgid ":guilabel:`Retention`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:216 msgid ":guilabel:`MRR Breakdown`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:217 msgid ":guilabel:`MRR Timeline`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:219 msgid "" "Clicking any of those options reveals a separate, fully-customizable " "reporting page focusing on that particular aspect of subscription data." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:222 msgid "The following is a breakdown of those four specific reporting pages." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:225 msgid "Subscriptions analysis" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:227 msgid "" "To access the :guilabel:`Subscriptions Analysis` reporting page, navigate to" " :menuselection:`Subscriptions app --> Reporting --> Subscriptions`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:230 msgid "" "By default, the :guilabel:`Bar Chart` option, in the :guilabel:`Graph` view," " is selected on the :guilabel:`Subscriptions Analysis` reporting page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:233 msgid "" "The following filters are also present in the search bar: :guilabel:`In " "Progress or Paused` and :guilabel:`Recurring`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "" "The default view of the Subscriptions Analysis reporting page in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:240 msgid "" "When the :guilabel:`Measures` button on the :guilabel:`Subscriptions " "Analysis` page is clicked, a series of metric-related options becomes " "available as a drop-down menu." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "The measures drop-down menu of the Subscriptions Analysis page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:247 msgid "" "The metric-related options in the :guilabel:`Measures` drop-down menu on the" " :guilabel:`Subscriptions Analysis` page are:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:250 msgid ":guilabel:`Monthly Recurring`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:251 msgid ":guilabel:`Quantity`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:252 msgid ":guilabel:`Recurring Revenue`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:253 msgid ":guilabel:`Untaxed Total`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:254 msgid ":guilabel:`Yearly Recurring`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:255 #: ../../content/applications/sales/subscriptions/reports.rst:293 #: ../../content/applications/sales/subscriptions/reports.rst:349 #: ../../content/applications/sales/subscriptions/reports.rst:397 msgid ":guilabel:`Count`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:258 msgid "" "The :guilabel:`Monthly Recurring` measure option is selected by default." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:260 msgid "" "When any of those available measures are clicked, Odoo displays that " "selected data on the reporting page for further analysis." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:264 msgid "Retention analysis" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:266 msgid "" "To access the :guilabel:`Retention Analysis` reporting page, navigate to " ":menuselection:`Subscriptions app --> Reporting --> Retention`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:269 msgid "" "The :guilabel:`Retention Analysis` reporting page differs from the other " "**Subscriptions** app reporting pages, in that it does **not** provide any " "additional view options. The data on this page is only presented in a " "customizable data chart." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "" "The default view of the Retention Analysis reporting page in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:277 msgid "" "When the :guilabel:`Measures` drop-down menu on the :guilabel:`Retention " "Analysis` reporting page is clicked, a series of metric-related options " "become available." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "The measures drop-down menu of the Retention Analysis page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:284 msgid "" "The metric-related options in the :guilabel:`Measures` drop-down menu on the" " :guilabel:`Retention Analysis` reporting page are:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:287 msgid ":guilabel:`Amount to invoice`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:288 msgid ":guilabel:`Margin`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:289 msgid ":guilabel:`Margin (%)`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:290 msgid ":guilabel:`Prepayment percentage`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:291 msgid ":guilabel:`Shipping Weight`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:292 msgid ":guilabel:`Unpaid Amount`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:296 msgid "The :guilabel:`Count` measure option is selected by default." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:298 msgid "" "To the right of the :guilabel:`Measures` drop-down menu on the " ":guilabel:`Retention Analysis` page is an additional drop-down menu " "containing different time periods. The default time period is " ":guilabel:`Month`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:302 msgid "" "When clicked, a drop-down menu of various time period options become " "available." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "The time period drop-down menu of the Retention Analysis page." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:308 msgid "The time period options are:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:310 msgid ":guilabel:`Day`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:311 msgid ":guilabel:`Week`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:312 msgid ":guilabel:`Month`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:313 msgid ":guilabel:`Year`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:315 msgid "" "When a time period option from this drop-down menu is selected, the " ":guilabel:`Retention Analysis` reporting page showcases data for the " "configured measures and filters within that time period." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:318 msgid "" "To the right of the time period drop-down menu, there is a download button, " "which allows the user to download the data presented on the " ":guilabel:`Retention Analysis` page as an Excel file." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:322 msgid "MRR breakdown" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:324 msgid "" "To access the :guilabel:`MRR Breakdown` reporting page, navigate to " ":menuselection:`Subscriptions app --> Reporting --> MRR Breakdown`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:327 msgid "" "By default, the data displayed on the :guilabel:`MRR Breakdown` reporting " "page is in graph view, with the :guilabel:`Bar Chart` option and " ":guilabel:`Stacked` option selected." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:330 msgid "" "A default filter is also available in the search bar for :guilabel:`Event " "Date: Month > Event Type`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "" "The default appearance of the MRR Breakdown reporting page in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:336 msgid "" "When the :guilabel:`Measures` drop-down menu on the :guilabel:`MRR " "Breakdown` reporting page is clicked, a series of metric-related options " "become available." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:343 msgid "" "The metric-related options in the :guilabel:`Measures` drop-down menu on the" " :guilabel:`MRR Breakdown` reporting page are:" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:346 #: ../../content/applications/sales/subscriptions/reports.rst:394 msgid ":guilabel:`Active Subscriptions Change`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:347 #: ../../content/applications/sales/subscriptions/reports.rst:395 msgid ":guilabel:`ARR Change`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:348 #: ../../content/applications/sales/subscriptions/reports.rst:396 msgid ":guilabel:`MRR Change`" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:352 #: ../../content/applications/sales/subscriptions/reports.rst:400 msgid "The :guilabel:`MRR Change` measure option is selected by default." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:355 msgid "" "To make a different measure option the default, first, select the desired " "measure from the :guilabel:`Measures` drop-down menu. Then, click the " ":icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar to " "open the mega menu of filters and groupings." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:359 msgid "" "In the :guilabel:`Favorites` column, click the :icon:`fa-caret-down` " ":guilabel:`(down arrow)` icon beside :guilabel:`Save current search` to " "reveal a field, where a title can be entered, along with two " "checkboxes::guilabel:`Default filter` and :guilabel:`Shared`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:363 msgid "" "Tick the checkbox for :guilabel:`Default filter`, and click " ":guilabel:`Save`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:365 msgid "" "That newly-chosen measure option is now the default option that appears when" " this reporting page is accessed." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:369 msgid "MRR analysis" msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:371 msgid "" "To access the :guilabel:`MRR Analysis` reporting page, navigate to " ":menuselection:`Subscriptions app --> Reporting --> MRR Timeline`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:374 msgid "" "By default, the data displayed on the :guilabel:`MRR Analysis` reporting " "page is in graph view, with the :guilabel:`Line Chart` option, " ":guilabel:`Stacked` option, and :guilabel:`Cumulative` option selected." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:378 msgid "" "A default filter is also found in the search bar for :guilabel:`Event Date: " "Month`." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "" "The default appearance of the MRR Analysis reporting page in Odoo " "Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:384 msgid "" "When the :guilabel:`Measures` drop-down menu on the :guilabel:`MRR Analysis`" " reporting page is clicked, a series of metric-related options become " "available." msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst:391 msgid "" "The metric-related options in the :guilabel:`Measures` drop-down menu on the" " :guilabel:`MRR Analysis` reporting page are:" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:3 msgid "Scheduled actions" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:5 msgid "" "*Scheduled actions* are pre-configured processes that allow users to " "automate certain tasks within a database, based on a designated schedule or " "number of occurrences. These tasks can include sending emails, generating " "invoices, data clean-up, and so much more." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:9 msgid "" "In Odoo, some scheduled actions are active, by default, to ensure that " "certain functions are triggered automatically, however there are *also* many" " scheduled action options that appear in the database that are **not** " "activated by default." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:13 msgid "" "In Odoo *Subscriptions*, there are two scheduled actions that initiate the " "billing process for active recurring subscriptions, as well as when billing " "should stop due to subscription expiration." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:16 msgid "" "They are turned on, by default and can be deactivated at any time in order " "to manage subscriptions manually." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:20 msgid "Access scheduled actions" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:23 msgid "" "In order to access scheduled actions, :ref:`developer mode `" " **must** be activated." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:26 msgid "" "With developer mode activated, navigate to :menuselection:`Settings app --> " "Technical --> Scheduled Actions`." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "The scheduled actions option under the technical menu in the Odoo Settings " "application." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:33 msgid "" "Doing so reveals a dedicated :guilabel:`Scheduled Actions` dashboard. On " "this page, there is a complete list of scheduled actions for the entire " "database." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:36 msgid "" "From here, enter `Subscription` in the search bar. Doing so provides three " "subscription-specific results. The following documentation focuses on the " "last two results in the list:" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:39 msgid "" ":guilabel:`Sale Subscription: generate recurring invoices and payments`" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:40 msgid ":guilabel:`Sale Subscription: subscriptions expiration`" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "The subscription-related results on the scheduled actions page in Odoo " "Settings." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:46 msgid "" "Determine if a scheduled action is active by looking under the " ":guilabel:`Active` column, in the it's corresponding row on the " ":guilabel:`Scheduled Actions` dashboard, for a ticked checkbox; if the " "checkbox is green with a check mark, the scheduled action is active." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:50 msgid "" "If a scheduled action needs to be activated, click into the desired " "scheduled action from the list." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "The scheduled action form in the Odoo Settings application." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:55 msgid "" "Then, from the scheduled action form, toggle the switch in the " ":guilabel:`Active` field to the right. Doing so turns the switch green, " "indicating that the scheduled action is now `Active`." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:58 msgid "" "The ability to set up how often the scheduled action runs is also available " "on the scheduled action form, in the :guilabel:`Execute Every` field." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:62 msgid "" "The scheduled action does **not** function correctly if the execution time " "is less than five minutes. This is a general rule for all scheduled actions." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:65 msgid "" "For more information, read the :doc:`Frequent Technical Questions " "` " "documentation." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:69 msgid "Generate recurring invoices and payments" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:71 msgid "" "In order for the :guilabel:`Sale Subscription: generate recurring invoices " "and payments` scheduled action to properly generate recurring invoices and " "payments on subscriptions, the *Deferred Expense* and *Deferred Revenue* " "accounts **must** be set up, in order for Odoo to process various invoices " "and payments related to subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:76 msgid "" "To set up *Deferred Expense* and *Deferred Revenue* accounts, navigate to " ":menuselection:`Accounting app --> Configuration --> Settings`. Both " "accounts can be configured in the :guilabel:`Default Accounts` section." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "The necessary deferred account settings in the Odoo Accounting app's " "settings page." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:84 msgid "" "Once the correct accounts are entered in the :guilabel:`Deferred Expense` " "and :guilabel:`Deferred Revenue` drop-down menu fields, click " ":guilabel:`Save` in the upper-left corner." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:88 msgid "Create invoice" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:90 msgid "" "Elements related to the :guilabel:`Sale Subscription: generate recurring " "invoices and payments` scheduled action can be found on confirmed " "subscription sales orders." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:93 msgid "" "To examine these elements, open any confirmed sales order in the " "*Subscriptions* application to reveal the subscription sales order form." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:96 msgid "" "On a confirmed subscription sales order form, focus on the " ":guilabel:`Recurring Plan` and :guilabel:`Date of Next Invoice` fields." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "A confirmed subscription sales order in the Odoo Subscriptions application." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:103 msgid "" "The scheduled action creates an invoice when today's date is the same date " "as the :guilabel:`Date of Next Invoice`." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:106 msgid "" "Odoo uses the information in the :guilabel:`Recurring Plan` field to update " "the next invoice date accordingly." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:110 msgid "" "If the product invoicing policy is set to *Based on Delivered Quantities " "(Manual)*, and the delivered quantity is `0`, Odoo does **not** create an " "invoice, and the customer is not charged." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:113 msgid "" "Instead, the subscription is processed as a free recurring product, and is " "reflected as such in the *chatter* of the subscription sales order." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:116 msgid "" "When this occurs, the following message appears: `Automatic renewal " "succeeded. Free subscription. Next invoice:[date]. No email sent.`" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:119 msgid "" "Once the invoice for the subscription sales order is created, the invoice " "can be viewed by clicking the :guilabel:`Invoices` smart button that appears" " at the top of the subscription sales order." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:122 msgid "" "An email is sent to the customer notifying them of the recurring " "subscription charge, *if* there is a :guilabel:`Payment Token` on the " "account." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:125 msgid "" "To check if there is a :guilabel:`Payment Token`, open the :guilabel:`Other " "Info` tab, and look at the :guilabel:`Payment Token` field, under the " ":guilabel:`Subscription` section." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "The Payment Token field under the Other Info tab on a subscription sales " "order form." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:132 msgid "" "If there is no :guilabel:`Payment Token`, the invoice is created, and sent " "to the customer. The payment **must** be registered manually in this case." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:136 msgid "Closing invoices" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:138 msgid "" "The :guilabel:`Sale Subscription: generate recurring invoices and payments` " "scheduled action also has the ability to close a subscription, if the " "following conditions are met:" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:141 msgid "" "If the subscription has no :guilabel:`Payment Token`, create and post the " "invoice." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:142 msgid "If the subscription has a :guilabel:`Payment Token`, try to charge." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:144 msgid "If the charge is successful, create and post the invoice." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:145 msgid "If the charge fails, send reminders periodically." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:147 msgid "" "Close the subscription if it continues to fail for more than fourteen days." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:150 msgid "Subscriptions expiration" msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:152 msgid "" "The :guilabel:`Sale Subscription: subscriptions expiration` scheduled action" " checks for all other conditions that may cause a subscription to close " "automatically. If certain conditions are met, the scheduled action closes " "that subscription." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:156 msgid "" "First, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled" " action checks to see if the end date has passed, which is configured on the" " subscription sales order." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "The expiration date on a subscription sales order in Odoo Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:163 msgid "" "Then, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled " "action checks if the invoice has not been paid within the payment terms " "deadline." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:166 msgid "" "To access the invoices attached to a subscription, access the sales order " "for the subscription product, and click the :guilabel:`Invoices` smart " "button. Then, look at the :guilabel:`Invoice Date` column." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "The Invoice Date column on subscriptions invoice page in Odoo Subscriptions " "app." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:174 msgid "" "Unpaid subscriptions with an :guilabel:`Invoice Date` that are past the " "determined number of days in the :guilabel:`Automatic Closing` field of a " ":guilabel:`Recurring Plan` are automatically closed by the :guilabel:`Sale " "Subscription: subscriptions expiration` scheduled action." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst-1 msgid "" "The Automatic Closing field on a Recurring Plan form in Odoo Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:182 msgid "" "For example, if the next invoice date is July 1st, and the " ":guilabel:`Automatic Closing` is set to '30 Days', the scheduled action " "would close the subscription on August 1st." msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:189 msgid ":doc:`automatic_alerts`" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:3 #: ../../content/applications/sales/subscriptions/upselling.rst:44 msgid "Upsell subscriptions" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:5 msgid "" "Subscriptions are recurrent, and go on indefinitely. As time passes, " "customers may want to modify them. With that in mind, it's imperative to " "have the ability to adapt prices, or change quantities, to accommodate any " "need. That's where the opportunity to upsell a subscription can come into " "play." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:9 msgid "Upselling may prove beneficial to the following customer types:" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "*Loyal Customers*" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "" "These are customers who already trust the company/brand, and because they " "have established a pattern of paying for products/services, there's more " "confidence behind the attempt to sell them a more expensive product/service." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "*New Customers*" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "" "For brand new customers unfamiliar with the company/brand, a new, attractive" " tactic must be employed to entice them to purchase a more expensive " "product/service." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:19 msgid "" "In these instances, discounts can be useful. Typically, subscriptions end " "after a certain period of time." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:22 msgid "" "So, if these more expensive products/services are offered to new customers " "at a discount, it can result in a sale, while establishing a strong sense of" " trust between the customer and the company/brand. In turn, this can " "increase customer retention, as they'll grow more comfortable and " "trustworthy over time." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:28 msgid "Discount configuration" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:30 msgid "" "In order to have the ability to upsell a subscription to a new customer, " "with the aid of a discount, the *Discounts* feature **must** be activated." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:33 msgid "" "To activate the *Discounts* feature, navigate to :menuselection:`Sales app " "--> Configuration --> Settings`, scroll to the :guilabel:`Pricing` section, " "and tick the checkbox beside :guilabel:`Discounts`. Then, click " ":guilabel:`Save`." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "Activation of the discount option in Odoo Sales." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:41 msgid "" "With that feature activated, the ability to grant discounts on sales order " "lines." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:46 msgid "" "Before upselling a subscription, check out our documentation on how to " ":doc:`Create a quotation <../subscriptions>` using subscription products." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:49 msgid "" "When a quotation with a subscription is confirmed, it officially becomes a " "sales order, and a new subscription is created in the Odoo *Subscriptions* " "application." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:53 msgid "" "The subscription sales order **must** be invoiced *before* an upsell can " "occur." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:55 msgid "" "When the subscription sales order is opened, either in the *Sales* or " "*Subscriptions* application, the ability to upsell that subscription is " "available, via the :guilabel:`Upsell` button at the top of the sales order." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "Upsell button for subscription sales orders with Odoo Subscriptions." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:63 msgid "" "When the :guilabel:`Upsell` button is clicked, a new quotation form appears," " with an :guilabel:`Upsell` status banner in the upper-right corner. The " "initial subscription product is already in the :guilabel:`Order Lines` tab." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:67 msgid "" "There is also a warning reminding the user that the recurring products are " "discounted, according to the prorated period of time, located beneath the " "initial subscription product in the :guilabel:`Order Lines` tab." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:72 msgid "" "The prorated amount is **only** applied to *Service* product types. It is " "**not** applied to *Consumable* or *Storable* product types, even if the " "message appears." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:75 msgid "" "From this new upsell quotation form, add new subscription products in the " ":guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and " "selecting the desired subscription product." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "" "Adding products to your subscription via the upsell option in Odoo " "Subscriptions" msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:82 msgid "" "Once the desired upsell subscription product(s) have been added, it can be " "sent to the customer for approval by clicking the :guilabel:`Send by Email` " "button." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:86 msgid "" "When the quotation is confirmed by the customer, the upsell products are " "added to the initial subscription. Quotation prices are then prorated to the" " remaining time of the current invoicing period." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:91 msgid "" "Before sending the new quotation to the customer, the unit price, taxes, and" " even discount can be applied." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:94 msgid "" "Once the customer approves, click the :guilabel:`Confirm` button on the " "quotation, making it a sales order. When that's clicked, a :guilabel:`Sales " "History` smart button appears, displaying how many sales orders are attached" " to this initial subscription order." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst:98 msgid "" "When the :guilabel:`Sales History` smart button is clicked, Odoo reveals a " "separate page containing a list of the related sales orders, clearly " "showcasing their individual :guilabel:`Subscription Status`." msgstr "" #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "" "The related sales order viewable from the Sales History smart button in Odoo" " Subscriptions." msgstr ""