documentation/locale/sources/sales.pot
Martin Trigaux (mat) f4d1c04ee7 [I18N] *: export 16.0 translations
closes 

X-original-commit: aecf49d6c8
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
2024-01-21 09:07:20 +00:00

12697 lines
691 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-01-19 15:28+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../content/applications/sales.rst:5
#: ../../content/applications/sales/sales.rst:8
msgid "Sales"
msgstr ""
#: ../../content/applications/sales/crm.rst:8
msgid "CRM"
msgstr ""
#: ../../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 <https://www.odoo.com/slides/crm-16>`_"
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 qualifying steps before an opportunity is created. This provides additional time before a potential opportunity is assigned to a sales person."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:9
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10
#: ../../content/applications/sales/crm/optimize/gamification.rst:11
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12
#: ../../content/applications/sales/point_of_sale/configuration.rst:6
#: ../../content/applications/sales/point_of_sale/employee_login.rst:13
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:11
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.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:12
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:12
#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17
#: ../../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:52
#: ../../content/applications/sales/point_of_sale/restaurant.rst:20
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10
#: ../../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/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:31
msgid "Configuration"
msgstr ""
#: ../../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, :guilabel:`Leads`, to the header menu bar at the top of the screen."
msgstr ""
#: ../../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 the record, and uncheck the :guilabel:`Leads` box. Once done, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:35
msgid "Convert a lead into an opportunity"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:37
msgid "To convert a lead into an *opportunity*, navigate to :menuselection:`CRM --> Leads`, and click on a :guilabel:`Lead` from the list to open it."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:40
msgid "In the upper-left corner of the screen, click the :guilabel:`Convert to Opportunity` button, which opens a :guilabel:`Convert to opportunity` pop-up window."
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:47
msgid "On the :guilabel:`Convert to opportunity` pop-up window, in the :guilabel:`Conversion action` field, select the :guilabel:`Convert to opportunity` option."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:51
msgid "If a lead, or an opportunity, already exists in the database for this customer, Odoo automatically suggests merging both leads/opportunities. For more information on merging leads and opportunities, see the section on how to :ref:`merge leads <sales/crm/acquire_leads/merge-leads>` below."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:56
msgid "Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which the opportunity should be assigned."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:59
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:66
msgid "Under the :guilabel:`Customer` heading, choose from the following options:"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:68
msgid ":guilabel:`Create a new customer`: Choose this option to use the information in the lead to create a new customer."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:70
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 the existing customer record."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:72
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:75
msgid "Lastly, when all configurations are complete, click :guilabel:`Create Opportunity`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:80
msgid "Merge leads and opportunities"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:82
msgid "Odoo automatically detects similar leads and opportunities by comparing the email addresses of the associated contacts. If a similar lead/opportunity is found, a :guilabel:`Similar Lead` smart button appears at the top of the lead/opportunity record."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1
msgid "Similar leads smart button."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:90
msgid "To compare the details of the similar leads/opportunities, click the :guilabel:`Similar Leads` button. This opens a kanban view with only the similar leads/opportunities. Click into each card to view the details for each lead/opportunity, and confirm if they should be merged."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:95
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:100
msgid "After confirming that the leads/opportunities should be merged, return to the kanban view using breadcrumbs, or by clicking the :guilabel:`Similar Lead` smart button. Click the :guilabel:`☰ (three vertical lines)` icon to change to list view."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:104
msgid "Check the box on the left of the page for the leads/opportunities to be merged. Then, click the :guilabel:`Action ⚙️ (gear)` 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/acquire_leads/convert.rst:108
msgid "When :guilabel:`Merge` is selected from the :guilabel:`Action ⚙️ (gear)` drop-down menu, a :guilabel:`Merge` pop-up window appears. In that pop-up window, decide to :guilabel:`Assign opportunities to` a :guilabel:`Salesperson` and/or :guilabel:`Sales Team`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:112
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/acquire_leads/convert.rst:116
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/acquire_leads/convert.rst:-1
msgid "Merge option from action menu in list view."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3
msgid "Generate leads/opportunities"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:5
msgid "Two key ways to generate new leads or opportunities for your business are through email aliases and website contact forms. Odoo automatically creates leads in your CRM whenever someone sends a message to a Sales Team email alias or fills out a contact form on your website."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:10
msgid "Configure email aliases"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:12
msgid "Each Sales Team can use its own unique email alias to generate leads/opportunities. Any email sent to a Sales Team's email alias will automatically create a lead (if leads are activated in your CRM settings) or an opportunity in the pipeline for that particular team. Configure custom email aliases on the configuration page for each Sales Team by navigating to :menuselection:`CRM --> Configuration --> Sales Teams`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1
msgid "Configuring Sales Teams"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:23
msgid "Use Contact Forms on your website"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:25
msgid "By default, your website's *Contact Us* page displays Odoo's ready-to-use Contact Form. Whenever someone submits this form, a lead or an opportunity is generated in your database."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1
msgid "Default Contact Us page"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:32
msgid "The Contact Form can be activated or deactivated at any time by going to :menuselection:`Website --> Go to Website --> Customize --> Contact Form`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1
msgid "Contact Form toggle"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:39
msgid "When the Form is deactivated, the *Contact Us* page simply displays a button to email your company directly. Any email sent this way will generate a lead/opportunity."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1
msgid "Contact Us Page using email"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:46
msgid "Choose which Sales Team or salesperson is automatically assigned to the leads/opportunities created from the Contact Form by going to :menuselection:`Website --> Configuration --> Settings --> Communication`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1
msgid "Contact Form settings"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:55
msgid "Customize Contact Forms"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:57
msgid "Contact Forms can be customized for the specific information your team needs, using the free *Form Builder* module."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:60
msgid "The *Form Builder* module is installed automatically when a Form element is added to a web page via the Website Builder. It can also be installed manually from the :guilabel:`Apps` page."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1
msgid "Form Builder building blocks"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:68
msgid "Forms can be created from scratch to serve a wide variety of purposes. However, Odoo's default *Contact Us* page is designed to fit most users' needs. Start with the default form and modify from there."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:73
msgid "Edit Contact Form fields"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:75
msgid "In Edit mode on your website, click on any field to start editing it. The following information can be edited for each field on the Contact Form:"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:78
msgid ":guilabel:`Type`: Choose a custom field option or an existing field. Examples include phone, file upload, language, etc."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:80
msgid ":guilabel:`Input Type`: Determine the type of entry customers should input. Available options are text,email, telephone, and URL."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:82
msgid ":guilabel:`Input Placeholder`: Type in an example to guide users how to input information where formatting is important, such as a phone number or email address."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:84
msgid ":guilabel:`Label Name`: Type in the display name to show users what information is needed from them."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:86
msgid ":guilabel:`Label Position`: Choose the way the label is aligned with the rest of the form. The label can be hidden, above the field, to the far left of the field, or right adjusted and closer to the field."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:89
msgid ":guilabel:`Required`: Toggle this option for information that you absolutely need entered."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:90
msgid ":guilabel:`Hidden`: Toggle this option to hide the field without deleting it."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:91
msgid ":guilabel:`Shown on Mobile`: Toggle this option to show the field to users on mobile devices."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1
msgid "Editable field options"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:97
msgid "By default, when a Form is submitted, it sends you an email with the customer's inputted information. To have it automatically generate a lead/opportunity instead, edit the Form and select :guilabel:`Create an Opportunity` as the Action."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:102
msgid "If leads are activated in your CRM settings, selecting :guilabel:`Create an Opportunity` generates a lead instead. To learn more about activating leads in the CRM settings, head over to :doc:`convert`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:3
msgid "Lead mining"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:5
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:12
msgid "To get started, go to :menuselection:`CRM --> Configuration --> Settings` and activate :guilabel:`Lead Mining`."
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:20
msgid "Generate leads"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:22
msgid "After the :guilabel:`Lead Mining` setting is activated, a new button called :guilabel:`Generate Leads` is available to use in the :guilabel:`CRM` pipeline. Lead mining requests are also available through :menuselection:`CRM --> Configuration --> Lead Mining Requests`, or through :menuselection:`CRM --> 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:32
msgid "Click on the :guilabel:`Generate Leads` button, and a window will appear 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:39
msgid "Choose to generate leads for :guilabel:`Companies` to get company information only, or choose :guilabel:`Companies and their Contacts` to get company information as well as individual employee contact information. When targeting :guilabel:`Companies and their Contacts`, there is an option to filter contacts based on :guilabel:`Role` or :guilabel:`Seniority`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44
msgid "Additional filtering options include:"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:46
msgid ":guilabel:`Size`: filter leads based on the number of employees at the company"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:47
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:48
msgid ":guilabel:`States`: further filter leads based on the state they are located in, if applicable"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:49
msgid ":guilabel:`Industries`: filter leads based on the specific industry they work in"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:50
msgid ":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned to"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51
msgid ":guilabel:`Salesperson`: choose which person(s) on the Sales Team the leads will be assigned to"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:52
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:55
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 <http://odoo.com/gdpr>`_."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36
#: ../../content/applications/sales/rental.rst:88
msgid "Pricing"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61
msgid "Lead mining is an *In-App Purchase* feature and each generated lead costs one credit."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:63
msgid "Choosing to generate :guilabel:`Companies and their Contacts` costs one additional credit for each contact generated."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:67
msgid "See here for full pricing information: `Lead Generation by Odoo IAP <https://iap.odoo.com/iap/ in-app-services/167?>`_."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:70
msgid "To buy credits, navigate to :menuselection:`CRM --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Mining` feature, click on :guilabel:`Buy Credits`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1
msgid "Buy credits from the lead mining settings."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:78
msgid "Credits may also be purchased by navigating to the :menuselection:`Settings --> General Settings`. In the :guilabel:`In-App Purchases` section, under the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1
msgid "Buy credits in the Odoo IAP settings."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:88
msgid "Users of Odoo Online (SaaS) Enterprise automatically have free trial credits in their database to test any IAP features."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92
msgid ":doc:`../../../general/in_app_purchase`"
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
msgid "Qualified lead form with New Quotation button emphasized."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:29
msgid "The :guilabel:`Customer` field is **not** required on the opportunity form."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:31
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:35
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:37
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:39
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:42
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:45
msgid ":guilabel:`Customer`: the company or contact for whom this quotation was created."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:46
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:48
msgid ":guilabel:`Invoice Address`: physical address where the invoice should be sent."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:49
msgid ":guilabel:`Delivery Address`: physical address where any products should be delivered."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:50
msgid ":guilabel:`Quotation Template`: if applicable, select a pre-configured :doc:`quotation template </applications/sales/sales/send_quotations/quote_template>` from this field."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:52
msgid ":guilabel:`Expiration`: date when this quotation is no longer valid."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:53
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) </applications/general/developer_mode>` is active."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:56
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:58
msgid ":guilabel:`Pricelist`: select a pricelist to be applied to this order."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:59
msgid ":guilabel:`Payment Terms`: select any applicable payment terms for this quotation."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:66
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:69
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:73
msgid "When the desired changes are complete, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:75
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:79
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:83
msgid "Order lines"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:85
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:88
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:90
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:94
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:97
msgid "To remove a line from the quotation, click the :guilabel:`🗑️ (trash can)` icon."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:99
msgid "Repeat the steps above until the quotation is complete."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:102
msgid "Preview and send quotation"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:104
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:107
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:110
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:112
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:116
msgid "A PDF of the quotation is added as an attachment to the email."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:119
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:123
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:125
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:128
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:132
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:138
msgid "`Quotation templates </applications/sales/sales/send_quotations/quote_template/>`_"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:139
msgid "`Optional products </applications/sales/sales/send_quotations/optional_products/>`_"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:140
msgid "`Quotation deadlines </applications/sales/sales/send_quotations/deadline/>`_"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:143
msgid "Mark an opportunity won or lost"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:145
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:148
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:152
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:154
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:157
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:160
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:165
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:170
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:174
msgid "Additional notes and comments can be added in the :guilabel:`Closing Note` field."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:176
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:179
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:183
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:186
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:191
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/acquire_leads/send_quotes.rst:196
msgid "`Manage lost opportunities </applications/sales/crm/pipeline/lost_opportunities>`_"
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 "How to motivate and reward my salespeople?"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:5
msgid "Challenging your employees to reach specific targets with goals and rewards is an excellent way to reinforce good habits and improve your salespeople productivity. The Gamification module gives you simple and creative ways to motivate and evaluate your employees with real-time recognition and badges inspired by game mechanics."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:13
msgid "Install the *Gamification* module, or the *CRM gamification* one, which adds some useful data (goals and challenges) that can be used on *CRM/Sale*."
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:21
msgid "Create a challenge"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:23
msgid "Now, create your first challenge by going to :menuselection:`Settings --> Gamification Tools --> Challenges`."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:27
msgid "As the gamification tool is a one-time technical setup, you need to activate the technical features in order to access the configuration. To do so, go to *Settings* and *Activate the developer mode*."
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:35
msgid "A challenge is a mission that you send to your sales team. It can include one or several goals, set for a specific period of time. Configure your challenge as follows:"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:38
msgid "Assign the salespeople to be challenged;"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:39
msgid "Assign a responsible;"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:40
msgid "Set up the periodicity along with the start and the end date;"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:41
msgid "Select your goals;"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:42
msgid "Set up your rewards (badges)."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:45
msgid "Badges are granted when a challenge is finished. This is either at the end of a running period (eg: end of the month for a monthly challenge), at the end date of a challenge (if no periodicity is set), or when the challenge is manually closed."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:49
msgid "In the example below, 2 employees are being challenged with a *Monthly Sales Target*. The challenge is based on 2 goals: the total amount invoiced and number of new leads generated. At the end of the month, the winner will be granted with a badge."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:-1
msgid "View of the challenge form and a challenge being created for Odoo Sales"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:58
msgid "Set up goals"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:60
msgid "The users can be evaluated using goals and numerical objectives to reach."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:62
msgid "**Goals** are assigned through *challenges* that evaluate (see image above) and compare members of a team throughout time."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:66
msgid "You can create a new goal on the fly from a *Challenge* by clicking on *Add new item*, under *Goals*. Select the business object according to your company's needs. Examples: number of new leads, time to qualify a lead, total amount invoiced in a specific week, month or any other time frame based on your management preferences, etc."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:-1
msgid "View of the goal definition form and a goal definition being created for Odoo Sales"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:73
msgid "Goals may include your database setup as well (e.g. set your company data and a timezone, create new users, etc.)."
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:77
msgid "Set up rewards"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:79
msgid "For non-numerical achievements, **Badges** can be granted to users. From a simple thank you to an exceptional achievement, a badge is an easy way to express gratitude to a user for their good work. To create and grant badges to your employees based on their performance, go 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/partner_autocomplete.rst:3
msgid "Enrich your contacts base with Partner Autocomplete"
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:5
msgid "Partner Autocomplete helps you to enrich your contacts database with corporate data. Select one of the companies suggested in the dropdown, and quickly get all the information you need."
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:11
msgid "Go to :menuselection:`Settings --> Contacts` and activate the *Partner Autocomplete* feature."
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:18
msgid "Enrich your contacts with corporate data"
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:22
msgid "From any module, once you start to create a new contact typing the name of it, the system will suggest a potential match. If you select it, the contact will be populated with corporate data."
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:23
msgid "For example, after typing *Odoo*, you will get the following information:"
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:-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:33
msgid "Partner Autocomplete also works if you enter a VAT number instead of a company name."
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:39
msgid "*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires prepaid credits to be used. Each request will consume one credit."
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:41
msgid "To buy credits, go to :menuselection:`Settings --> Contacts --> Partner Autocomplete or Odoo IAP --> View My Services` and select a package."
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:44
msgid "If you run out of credits, the only information that will be populated when clicking on the suggested company will be the website link and the logo."
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:46
msgid "If you are on Odoo Online and you have the Enterprise version, you benefit from free trial credits to test the feature."
msgstr ""
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:48
msgid "Learn about our *Privacy Policy* `here <https://iap.odoo.com/privacy#header_2>`_."
msgstr ""
#: ../../content/applications/sales/crm/performance.rst:5
msgid "Analyze performance"
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:3
msgid "Pipeline Analysis"
msgstr ""
#: ../../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 <win_loss/save_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 <win_loss/search>` 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 <win_loss/view>` 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 <win_loss/measure>` 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 ""
#: ../../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 <win_loss/custom_filters>` for more information)"
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:129
msgid "Group By"
msgstr ""
#: ../../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 <win_loss/custom_filters>` for more information)"
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:164
msgid "Comparison"
msgstr ""
#: ../../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 ""
#: ../../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:279
msgid "View options"
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 ""
#: ../../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 <win_loss/measure>` 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 ""
#: ../../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
msgid "Create reports"
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:398
msgid "After understanding how to :ref:`navigate the pipeline analysis page <win_loss/pipeline>`, 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 <win_loss/save_reports>`."
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 <win_loss/win_loss>`, 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 <win_loss/reports>`, 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 all opportunities result in successful sales. In order to keep the pipeline up to date, lost opportunities need to be identified. Specifying the reason 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 a lead as lost"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12
msgid "To mark a lead as lost, open the :menuselection:`CRM` application, and select a lead from the pipeline, by clicking on its corresponding kanban card. Doing so reveals that lead's detail form."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15
msgid "Then, click :guilabel:`Lost`, located at the top of the lead'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:21
msgid "This opens the :guilabel:`Lost Reason` popup. From the drop-down, 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:25
msgid "Additional notes and comments can be added below the lost reason designated in the :guilabel:`Lost Reason` field."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:28
msgid "When all the desired information has been entered in the :guilabel:`Lost Reason` pop-up window, click :guilabel:`Submit`."
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:35
msgid "Upon clicking :guilabel:`Submit`, the pop-up window disappears, and Odoo returns to the lead detail form, where a new red :guilabel:`Lost` banner is now present in the upper-right corner of the lead."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39
msgid "Create/edit lost reasons"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41
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:44
msgid "To edit an existing reason, click on the reason that should be modified. When clicked, that reason becomes highlighted. Once highlighted, change the description of the selected lost reason by editing the :guilabel:`Description` field. When done, click :guilabel:`Save` in the upper-left corner."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:48
msgid "To create a new lost reason, click :guilabel:`Create` in the upper-left corner of the :guilabel:`Lost Reasons` page. Doing so reveals a new blank line in the :guilabel:`Description` field. Then, proceed to type in the new lost reason in that new line. Once ready, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:54
msgid "Retrieve lost opportunities"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56
msgid "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM app` to the main :guilabel:`Pipeline` dashboard. Then, click the :guilabel:`Filters` drop-down menu, located beneath the search bar."
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:64
msgid "From the :guilabel:`Filters` drop-down menu, select the :guilabel:`Lost` option. Upon selecting :guilabel:`Lost`, only the leads that have been marked as `Lost` appear on the :guilabel:`Pipeline` page."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68
msgid "To filter leads by a specific lost reason, select :menuselection:`Filters --> Add Custom Filter`. Doing so reveals another drop-down menu with three fields."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71
msgid "In the top field drop-down menu, select :guilabel:`Lost Reason`. In the second field drop-down menu, select :guilabel:`Contains`. Then, in the third field of the :guilabel:`Add Custom Field` sub menu, type in the specific keyword(s). Lastly, click :guilabel:`Apply`. Upon clicking :guilabel:`Apply`, Odoo reveals all the lost leads with a reason that contains that specified keyword(s)."
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:81
msgid "Restore lost opportunities"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83
msgid "To restore a lost opportunity, navigate to the main :guilabel:`Pipeline` dashboard on the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option. Doing so reveals all the lost opportunities on the :guilabel:`Pipeline` page."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:87
msgid "Then, click on the kanban card of the desired lost opportunity to restore, which opens that lead's detail form."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90
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:-1
msgid "Lost opportunity with emphasis on the Restore button."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:98
msgid "Restore multiple opportunities at once"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:100
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:103
msgid "Next, select the list view option, which is represented by the three-line :guilabel:`☰ (list)` icon in the upper-right corner. Doing so places all the leads from the :guilabel:`Pipeline` page in a list form. With the list form chosen, select the checkbox to the left of each desired opportunity/lead to be restored."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108
msgid "Once the desired opportunities/leads have been selected, click the :guilabel:`⚙️ Action (gear)` drop-down menu at the top of the :guilabel:`Pipeline` page. From the :guilabel:`⚙️ Action (gear)` drop-down menu, select :guilabel:`Unarchive`."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:112
msgid "Doing so removes those selected lost opportunities from the :guilabel:`Pipeline` page because they no longer fit into the `Lost` filter criteria. To reveal these newly-restored leads, delete the `Lost` filter from the search bar."
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:121
msgid ":doc:`../performance/win_loss`"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3
msgid "Multiple sales teams"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:5
msgid "Use the *Sales Teams* feature to manage several sales teams, departments, or channels, each with their own unique sales processes."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:10
msgid "Create a new sales team"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12
msgid "To create a new sales team, go to :menuselection:`CRM --> Configuration --> Sales Teams`, then click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:15
msgid "On the creation page, set an :guilabel:`Email Alias` to automatically generate a lead/opportunity for this sales team every time a message is sent to that unique email address. Choose whether to accept emails from :guilabel:`Everyone`, :guilabel:`Authenticated Partners`, or :guilabel:`Followers Only`."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:20
msgid "Set an :guilabel:`Invoicing Target` if this team has specific monthly revenue goals. Set a :guilabel:`Domain` to assign leads/opportunities to this sales team based on specific filters, such as country, language, or campaign."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1
msgid "Create a sales team in Odoo CRM."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:29
msgid "Add members to a sales team"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:31
msgid "To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab when editing the sales team's configuration page. Select a salesperson from the drop-down menu or create new salesperson. Set a maximum number of leads that can be assigned to this salesperson in a 30-day period to ensure that they do not overwork."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1
msgid "Add a salesperson in Odoo CRM."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40
msgid "One person can be added as a team member or :guilabel:`Team Leader` to multiple sales teams, allowing them to access all of the pipelines that they need to."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44
msgid "Sales team dashboard"
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46
msgid "To view the sales team dashboard, go to :menuselection:`CRM --> Sales --> Teams`. Odoo users will see any teams that they are a part of as dashboard tiles."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:49
msgid "Each tile 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/multi_sales_team.rst:-1
msgid "Sales team overview dashboard in Odoo CRM."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:57
msgid "Click on the three dots in the corner of a tile to open a navigational menu that lets users quickly view documents or reports, create new quotations or opportunities, pick a color for this team, or access the team's configuration page."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1
msgid "Click the Three Dot Menu in Odoo CRM dashboard to view documents and create opportunities."
msgstr ""
#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:65
msgid "Click on the :guilabel:`Pipeline` button to go directly to that team's CRM pipeline."
msgstr ""
#: ../../content/applications/sales/crm/track_leads.rst:5
msgid "Assign and track leads"
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 "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:40
msgid "When an opportunity moves to the next stage, its probability of success automatically increases according to the predictive lead scoring algorithm."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:46
msgid "Predictive lead scoring is always active in Odoo *CRM*. However, the variables used to calculate the probability of success can be customized in the settings."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49
msgid "To customize the variables used by predictive lead scoring, go to :menuselection:`CRM --> Configuration --> Settings`. Under :guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update Probabilities` button."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53
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:60
msgid "Any number of the following variables can be activated:"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62
msgid ":guilabel:`State`: the geographical state from which the opportunity originates"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:63
msgid ":guilabel:`Country`: the geographical country from which the opportunity originates"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64
msgid ":guilabel:`Phone Quality`: whether or not a phone number is listed for the opportunity"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65
msgid ":guilabel:`Email Quality`: whether or not an email address is listed for the opportunity"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:66
msgid ":guilabel:`Source`: the source of an opportunity (e.g. search engine, social media)"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:67
msgid ":guilabel:`Language`: the spoken language specified on the opportunity"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68
msgid ":guilabel:`Tags`: the tags placed on the opportunity"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:71
msgid "The variables `Stage` and `Team` are always in effect. `Stage` refers to the CRM pipeline stage that an opportunity is in. `Team` refers to the sales team that is assigned to an opportunity. Predictive lead scoring *always* takes into account these two variables, regardless of which optional variables are selected."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76
msgid "Next, click on the date field next to the option :guilabel:`Consider leads created as of the:` to select the date from which predictive lead scoring will begin its calculations."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79
msgid "Lastly, click :guilabel:`Confirm` to save changes."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82
msgid "Change the probability manually"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84
msgid "An opportunity's probability of success can be changed manually on the opportunity form. Click on the probability number to edit it."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:88
msgid "Manually changing the probability removes the automatic probability updates for that opportunity. The probability will no longer update automatically as the opportunity moves through each stage of the pipeline."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92
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:99
msgid "Assign leads based on probability"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:101
msgid "Odoo *CRM* can assign leads/opportunities to sales teams and salespeople based on specified rules. Create assignment rules based on the leads' probability of success to prioritize those that are more likely to result in deals."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106
msgid "Configure rule-based assignment"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108
msgid "To activate *rule-based assignment*, navigate to :menuselection:`CRM --> Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111
msgid "The rule-based assignment feature can be set to run :guilabel:`Manually`, meaning an Odoo user must manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo will automatically trigger the assignment according to the chosen time period."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115
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:123
msgid "If rule-based assignment is set to run :guilabel:`Repeatedly`, the assignment can still be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings (or using the :guilabel:`Assign Leads` button on the sales team configuration page)."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128
msgid "Configure assignment rules"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130
msgid "Next, configure the *assignment rules* for each sales team and/or salesperson. These rules determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM --> Configuration --> Sales Teams`, and select a sales team."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134
msgid "On the sales team configuration form, under :guilabel:`Assignment Rules`, click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to determine lead assignment for this sales team. The rules can include anything that may be relevant for this company or team, and any number of rules can be added."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139
msgid "Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :guilabel:`+` sign on the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to remove the line."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143
msgid "To create an assignment rule based on an opportunity's probability of success, click on the far left drop-down menu of an assignment rule line, and select :guilabel:`Probability`."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146
msgid "From the middle drop-down menu, select the desired equation symbol—most likely the symbol for *greater than*, *less than*, *greater than or equal to*, or *less than or equal to*."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149
msgid "In the far right space, enter the desired number value of the probability. Finally, click :guilabel:`Save` to save changes."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:153
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:160
msgid "Separate assignment rules can also be configured for individual team members. From the sales team configuration page, click on a team member in the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click :guilabel:`Save` to save changes."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164
msgid "If automatic lead assignment is configured in the settings, both the sales team and individual team members have the option to :guilabel:`Skip auto assignment`. Check this box to omit a particular sales team or salesperson from being assigned leads automatically by Odoo's rule-based assignment feature. If :guilabel:`Skip auto assignment` is activated, the sales team or salesperson can still be assigned leads manually."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170
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/prospect_visits.rst:3
msgid "Track your prospects visits"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:5
msgid "Tracking your website pages will give you much more information about the interests of your website visitors."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:8
msgid "Every tracked page they visit will be recorded on your lead/opportunity if they use the contact form on your website."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:14
msgid "To use this feature, install the free module *Lead Scoring* under your *Apps* page (only available in Odoo Enterprise)."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:21
msgid "Track a webpage"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:23
msgid "Go to any static page you want to track on your website and under the *Promote* tab you will find *Optimize SEO*"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:29
msgid "There you will see a *Track Page* checkbox to track this page."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:35
msgid "See visited pages in your leads/opportunities"
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:37
msgid "Now each time a lead is created from the contact form it will keep track of the pages visited by that visitor. You have two ways to see those pages, on the top right corner of your lead/opportunity you can see a *Page Views* button but also further down you will see them in the chatter."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:43
msgid "Both will update if the viewers comes back to your website and visits more pages."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:52
msgid "The feature will not repeat multiple viewings of the same pages in the chatter."
msgstr ""
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:55
msgid "Your customers will no longer be able to keep any secrets from you!"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:6
msgid "Point of Sale"
msgstr ""
#: ../../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 <https://www.odoo.com/slides/point-of-sale-28>`_"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:14
msgid ":doc:`IoT Boxes Documentations </applications/productivity/iot>`"
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 <point_of_sale/employee_login>` 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:52
msgid "Set customers"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:54
msgid "Registering your customer is necessary to :doc:`collect their loyalty points and grant them rewards <point_of_sale/pricing/loyalty>`, automatically apply the :doc:`attributed pricelist <point_of_sale/pricing/pricelists>`, or :ref:`generate and print an invoice <receipts-invoices/invoices>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:59
msgid "You can create customers from an :ref:`open POS session <pos/session-start>` 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:64
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:71
msgid "Customer notes"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:73
msgid "You can add **customer notes** about specific products directly from an open :ref:`POS session <pos/session-start>`. 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:77
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:81
msgid "Product notes from an :doc:`imported SO <point_of_sale/shop/sales_order>` 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:87
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:96
msgid "Return and refund products"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:98
msgid "To return and refund a product,"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:100
msgid ":ref:`start a session <pos/session-start>` from the **POS dashboard**;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:101
msgid "click :guilabel:`Refund` and select the corresponding order;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:102
msgid "select the product and the quantity to refund using the keypad;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:103
msgid "click :guilabel:`Refund` to go back to the previous screen;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:104
msgid "once the order is completed, click :guilabel:`Payment` to proceed to the refund;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:105
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:111
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:113
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:120
msgid "Manage the cash register"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:122
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:129
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:135
msgid "Close the POS session"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:137
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:140
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:143
msgid "the number of orders made and the total amount made during the session;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:144
msgid "the expected amounts grouped by payment method."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:146
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:155
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:159
msgid "To reach the backend without closing the session, click :guilabel:`Backend` on the dropdown menu."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:161
msgid "To abort, click :guilabel:`Discard` on the pop-up window."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:162
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:167
msgid "It is strongly advised to close your POS session at the end of each day."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:168
msgid "To look at all your previous sessions, go to :menuselection:`Point of Sale --> Orders --> Sessions`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:11
msgid "Access 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 </applications/general/users/manage_users>` :guilabel:`Administration` set as :guilabel:`Settings`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:25
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:28
msgid ":doc:`Enable multiple employees to log in. <employee_login>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:29
msgid ":doc:`Connect and set up an IoT box. <../../productivity/iot/config/pos>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:30
msgid ":doc:`Connect and set up an ePOS printer. <configuration/epos_ssc>`"
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:36
msgid "These settings are available to users with the :doc:`access rights </applications/general/users/manage_users>` :guilabel:`Point of Sale` set as :guilabel:`Administrator`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:41
msgid "Make products available"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:43
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/epos_ssc.rst:5
msgid "Self-signed certificate for ePOS printers"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7
msgid "ePOS printers are designed to work seamlessly with Point of Sale systems. Once connected, the two devices automatically share information, enabling the direct printing of tickets from the POS system to the ePOS printer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:12
msgid "These `Epson ePOS printers <https://c4b.epson-biz.com/modules/community/index.php?content_id=91>`_ are compatible with Odoo:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:15
msgid "TM-H6000IV-DT (Receipt printer only)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:16
msgid "TM-T70II-DT"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:17
msgid "TM-T88V-DT"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:18
msgid "TM-L90-i"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:19
msgid "TM-T20II-i"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:20
msgid "TM-T70-i"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:21
msgid "TM-T82II-i"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22
msgid "TM-T83II-i"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:23
msgid "TM-T88V-i"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24
msgid "TM-U220-i"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:25
msgid "TM-m10"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:26
msgid "TM-m30"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:27
msgid "TM-P20 (Wi-Fi® model)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28
msgid "TM-P60II (Receipt: Wi-Fi® model)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:29
msgid "TM-P60II (Peeler: Wi-Fi® model)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:30
msgid "TM-P80 (Wi-Fi® model)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:32
msgid "To work with Odoo, some models that can be used without an :doc:`IoT box <../../../productivity/iot/config/connect>` may require :doc:`the HTTPS protocol <https>` 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 <epos_ssc/instructions>`, 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:40
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 <epos_ssc/instructions>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47
msgid "Generate, export, and import self-signed certificates"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49
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:53
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:58
msgid "Windows 10 & Linux OS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:191
msgid "Generate a self-signed certificate"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193
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:72
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201
msgid "Warning page on Google Chrome, Windows 10"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:203
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:78
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:207
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:85
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214
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:89
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218
msgid "Export a self-signed certificate"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220
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:96
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:225
msgid "If you are using **Google Chrome**,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227
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:104
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233
msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:234
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:106
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:235
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:108
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254
msgid "save, and the certificate is exported."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111
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:114
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:243
msgid "If you are using **Mozilla Firefox**,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245
msgid "click the **lock-shaped** icon on the left of the address bar;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:246
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:123
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:252
msgid "scroll down to the :guilabel:`Miscellaneous` section;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:253
msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127
msgid "Import a self-signed certificate"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129
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:134
msgid "Windows 10"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136
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:139
msgid "open the Windows File Explorer and locate the downloaded certification file;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140
msgid "right-click on the certification file and click :guilabel:`Install Certificate`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142
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:145
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:151
msgid "click :guilabel:`Finish`, accept the pop-up security window;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152
msgid "restart the computer to make sure that the changes are applied."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154
msgid "Linux"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158
msgid "open Chrome;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159
msgid "go to :menuselection:`Settings --> Privacy and security --> Security --> Manage certificates`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161
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:163
msgid "accept all warnings;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164
msgid "click :guilabel:`ok`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175
msgid "restart your browser."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170
msgid "open Firefox;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171
msgid "go to :menuselection:`Settings --> Privacy & Security --> Security --> View Certificates... --> Import`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173
msgid "select the exported certification file;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174
msgid "tick the checkboxes and validate;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177
msgid "Mac OS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179
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:181
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:182
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:184
msgid "reboot the printer so you can use it with any other browser."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186
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:240
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:256
msgid "Android OS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258
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:262
msgid "open the settings and search for `certificate`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:263
msgid "click :guilabel:`Certificate AC` (Install from device storage);"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:264
msgid "select the certificate file to install it on the device."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267
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:270
msgid "iOS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272
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:276
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:279
msgid "go to the **Settings App** on the iOS device;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280
msgid "click :guilabel:`Profile Downloaded` under the user's details box;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:281
msgid "locate the downloaded `.crt` file and select it;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282
msgid "click :guilabel:`Install` on the top right of the screen;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:283
msgid "if a passcode is set on the device, enter the passcode;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:284
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:286
msgid "click :guilabel:`Done`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:290
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:292
msgid "go to :menuselection:`Settings --> General --> About > Certificate Trust Settings`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:293
msgid "enable the installed certificate using the **slide button**;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:294
msgid "click :guilabel:`Continue` on the pop-up window."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:297
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:300
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:305
msgid "Check if the certificate was imported correctly"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307
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 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 <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/configuration/https.rst:22
msgid ":doc:`epos_ssc`"
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 <employee_login/use>` and :ref:`keep track of the employees involved in each order <employee_login/analytics>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:15
msgid ":ref:`Access the POS settings <configuration/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:26
msgid "Practical application"
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 <employee_login/badge>` or selecting their name from the list of allowed employees to :ref:`open the session <pos/session-start>`."
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 <pos/session-start>`, 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 ""
#: ../../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 ""
#: ../../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 <payment_methods/terminals>`."
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
msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings <configuration/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:13
msgid "Go to the :doc:`application settings <../configuration>`, 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:19
msgid "Then, follow the corresponding documentation to configure your device:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21
msgid ":doc:`Adyen configuration <terminals/adyen>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22
msgid ":doc:`Ingenico configuration <terminals/ingenico>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23
msgid ":doc:`SIX configuration <terminals/six>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24
msgid ":doc:`Stripe configuration <terminals/stripe>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25
msgid ":doc:`Vantiv configuration <terminals/vantiv>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26
msgid ":doc:`Worldline configuration <terminals/worldline>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28
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 ""
#: ../../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 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:15
msgid "Start by creating your Adyen account on `Adyen's website <https://www.adyen.com/>`_. 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:19
msgid "`Adyen Docs - Payment terminal quickstart guides <https://docs.adyen.com/point-of-sale/user-manuals>`_."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:23
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63
msgid "Configure the payment method"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:25
msgid "First, go to :menuselection:`Point of Sale --> Configuration --> Settings --> Payment Terminals`, and enable :guilabel:`Adyen`. Then, go to :menuselection:`Configuration --> Payment Methods` and create a new payment method. Select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31
msgid "The selected journal **must** be a bank journal for the :guilabel:`Use a payment terminal` field to appear."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:34
msgid "Finally, fill the mandatory fields with an :guilabel:`Adyen API key`, and an :guilabel:`Adyen Terminal Identifier`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:38
msgid "Generate an Adyen API key"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40
msgid "The **Adyen API key** is a key used to authenticate your requests. To generate an API key, go to your **Adyen account**."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:43
msgid "Then, go to :menuselection:`Developers --> API credentials`. Create a new credential or click on an existing one."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46
msgid "Click on :guilabel:`Generate an API key` and copy-paste that key onto the Odoo mandatory field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:49
msgid "`Adyen Docs - API credentials <https://docs.adyen.com/development-resources/api-credentials#generate-api-key>`_."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:53
msgid "Locate the Adyen terminal identifier"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:55
msgid "The **Adyen Terminal Identifier** is your terminal's serial number, which is used to identify the hardware."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:58
msgid "To find this number, go to your **Adyen account**. Then, go to :menuselection:`Point of Sale --> Terminals`, select the terminal to link, and copy-paste its serial number onto the Odoo mandatory field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:63
msgid "Set the Event URLs"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65
msgid "For Odoo to know when a payment is made, you must set the terminal **Event URLs**. To do so,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:67
msgid "log in to `Adyen's website <https://www.adyen.com/>`_;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68
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:70
msgid "from the terminal settings, click :guilabel:`Integrations`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:71
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:72
msgid "click the **pencil icon** button and enter your server address, followed by `/pos_adyen/notification` in the :guilabel:`Event URLs` field; and"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:74
msgid "click :guilabel:`Save` at the bottom of the screen to save the changes."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:77
msgid "Add a new payment method"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:79
msgid "To add a new **payment method** to a point of sale, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, select the POS and go to :menuselection:`Payments --> Payment Methods`, and add your new method for Adyen."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:65
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:86
msgid "Pay with a payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:86
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/stripe.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/stripe.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:95
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/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:8
msgid "Please note that Ingenico is currently only available for customers in the Benelux."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:15
msgid "Connect an IoT Box"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:17
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 </applications/productivity/iot/config/connect>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:22
msgid "Configure the Lane/5000 for Ingenico BENELUX"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:24
msgid "Click on the F button of the terminal, then go in the :menuselection:`PoS Menu --> Settings` and enter the settings password."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27
msgid "Now, click on connection change and TCP/IP. Type the IP of your *IoT Box* (you can find it on the form view of your IoT Box). Then, enter 9000 as port. The terminal will restart. Once it is done, go on your *IoT Box* form in Odoo and verify that the terminal has been found."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:38
msgid "First, go in the general settings of the POS app, and activate the Ingenico setting."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:44
msgid "Go back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Ingenico, select the payment terminal option Ingenico, and select your payment terminal device."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55
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:64
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:67
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:73
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:76
msgid "Once your payment is processed, on the payment record, youll find the type of card that has been used and the transaction ID."
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 </applications/productivity/iot/config/connect>`."
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 "From your database, go to :menuselection:`Point of Sale --> Configuration --> Payment Methods` to create a new payment method specifically for Six. Click :guilabel:`New`, enter a :guilabel:`Name`, set the :guilabel:`Journal` field as :guilabel:`Bank`, the :guilabel:`Use a Payment Terminal` field as :guilabel:`SIX IOT`, and select the corresponding 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:67
msgid "When processing a payment, select :ref:`your Six payment method <six/configure>` 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:76
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91
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:78
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:80
msgid "By default, the port used by the Six terminal is `7784`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:83
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 ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:9
msgid ":doc:`Use Stripe as payment provider. <../../../../finance/payment_providers/stripe>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:17
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:20
msgid "Then, create the payment method:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22
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:24
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:26
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:27
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
msgid "payment method creation form"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:34
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:37
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:39
msgid "Find your payment terminal serial number under the device or on `Stripe's dashboard <https://dashboard.stripe.com>`_."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:43
msgid "Connect Stripe to Odoo"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:45
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:57
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:59
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:61
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 <https://dashboard.stripe.com>`_, type `API` in the search bar, and click :guilabel:`Developers > API`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:67
msgid "Configure the payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:69
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:73
msgid "The device must be connected to a secured WI-FI network."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:74
msgid "Your Odoo database and payment terminal must share the same network."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:75
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:79
msgid "Link the payment method to a POS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:81
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:88
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:97
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:98
msgid "The device does not work for payments under €0.50."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:101
msgid "Troubleshooting"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104
msgid "Payment terminal unavailable in your Stripe account"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:106
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:108
msgid "Log into your `Stripe's dashboard <https://dashboard.stripe.com>`_ and go to :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:110
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:111
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:115
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:20
msgid "Configure the Payment Method"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22
msgid "First, go in the general settings of the POS app, and activate the Vantiv setting."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28
msgid "Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36
msgid "To create new Vantiv credentials, fill in your merchant ID and password, then save. Make sure the credentials you just created are selected, then save the payment method."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44
msgid "Pay with a Payment Terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46
msgid "In your PoS interface, at the moment of the payment, select your Vantiv payment method and… thats all."
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 "Please note that Worldline is currently only available in the Benelux."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:17
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 </applications/productivity/iot/config/connect>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:22
msgid "Configure the protocol"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:24
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:31
msgid "Set the IP address"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:33
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:38
msgid "Finally, set up the hostname and port number."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:41
msgid "Hostname"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:44
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:45
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:53
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:56
msgid "Port number"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:58
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:65
msgid "From the Point of Sale application, go to :menuselection:`Configuration --> Settings --> Payment terminals` and activate the *Worldline* payment terminal."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:71
msgid "Then, go to :menuselection:`Configuration --> Payment methods` and create a new payment method for *Worldline*. Select the payment terminal *Worldline* and your payment terminal device on your *Payment Method form*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:78
msgid "Technician password: `1235789`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:79
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:81
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:82
msgid "To avoid blocking the terminal, check the initial configuration beforehand."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:83
msgid "Set a fixed IP to your IoT Boxs router to prevent losing the connexion."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:88
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:98
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:101
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 ""
#: ../../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 ""
#: ../../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
msgid "Discounts"
msgstr ""
#: ../../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/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 <fiscal_positions/mapping>`."
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 <pos/session-start>` 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:108
msgid "Pricelists"
msgstr ""
#: ../../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 <configuration/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 <pricelists/simple>` is the default pricelist option for setting simple fixed price rules per product. Select :ref:`Advanced price rules (discounts, formulas) <pricelists/advanced>` 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 <ecommerce/pricelists>` 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 <pricelists/configuration>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234
msgid "Multiple prices per product"
msgstr ""
#: ../../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:312
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 <cash_rounding>` 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 <configuration/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 <pos/session-start>`, 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 <pos/customers>`. 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 <ecommerce/pricelists>`"
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 ""
#: ../../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:21
msgid ":doc:`restaurant/bill_printing`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:24
msgid "Reprint a receipt"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26
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:34
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:40
msgid "Invoices"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42
msgid "Point of Sale allows you to issue and print invoices for :ref:`registered customers <pos/customers>` upon payment and retrieve all past invoiced orders."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46
msgid "An invoice created in a POS creates an entry into the corresponding :ref:`accounting journal <cheat_sheet/journals>`, previously :ref:`set up <receipts_invoices/invoice_configuration>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:54
msgid "To define what journals will be used for a specific POS, go to the :ref:`POS' settings <configuration/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:63
msgid "Invoice a customer"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65
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:68
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:72
msgid "To be able to issue an invoice, a :ref:`customer <pos/customers>` must be selected."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:75
msgid "Retrieve invoices"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:77
msgid "To retrieve invoices from the **POS dashboard**,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79
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:81
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:88
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:90
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:94
msgid "QR codes to generate invoices"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:96
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:105
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 ""
#: ../../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 <restaurant/floors_tables>`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant.rst:13
msgid ":ref:`take orders <floors_tables/orders>`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant.rst:14
msgid ":doc:`communicate with the kitchen or the bar through the POS <restaurant/kitchen_printing>`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant.rst:15
msgid ":doc:`print bills in advance and split them <restaurant/bill_printing>`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant.rst:16
msgid ":doc:`collect tips <restaurant/tips>`; and"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant.rst:17
msgid ":doc:`set different taxes for takeaway food <pricing/fiscal_position>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant.rst:22
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:25
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/bill_printing.rst:3
msgid "Bills"
msgstr ""
#: ../../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 management"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:6
msgid "Add a floor"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:8
msgid "Once your *Point of Sale* has been configured, select *Table Management* under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, click on *Floors* to create and name your floor and tables."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "View of the table management feature. Way to manage and create floors for a pos"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "Backend view of a restaurant floor. Table name and number of sits for each table"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:21
msgid "Dont forget to link your floor to your point of sale."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:24
msgid "Add tables"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:26
msgid "To add tables, you can also open your PoS interface to see your floor(s)."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "View of the floors menu to manage several floors at the same time"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:33
msgid "Then, click on *Edit Mode* (pencil icon on the upper right corner) to be allowed to create, move, modify tables, etc."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "View of the floor management. Add tables, the number of sits, their name and their shape"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:41
msgid "To make your table easier to be found, you can rename them, change their shape, size or even color. It is also possible to add the maximum number of sits the table can have."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:48
msgid "Register your table(s) orders"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:50
msgid "To register an order, click on the respective table. By doing so, you are taken to your main interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "View of the pos interface to register orders"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:58
msgid "Transfer customer(s)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:60
msgid "If your customers want to move to another table after they already ordered, use the transfer button. This way, the order is also moved to the new table."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:64
msgid "To do so, select the table your customer is currently on."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "View of the restaurant tables, one having a pending order"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:70
msgid "Now, click on the transfer button and select the table to which you are transferring your customer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "View of the pos interface and transfer button. How to transfer customers from one table\n"
"to another"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:79
msgid "Register an additional order"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:81
msgid "When registering an order, use the + button to simultaneously proceed to another one."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84
msgid "Then, you can shift between your orders and process the payment when needed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:-1
msgid "View of the - button, allowing employees to close/remove an order"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:92
msgid "The - button allows you to remove the order you are currently on."
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 <kitchen_printing/enable>`, 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:`../../../productivity/iot/config/connect`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44
msgid ":doc:`../../../productivity/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 ""
#: ../../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 <pos/sell>`, :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 <configuration>` 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 <configuration>`."
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 <pos/sell>` 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 <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 </applications/inventory_and_mrp/barcode/setup/hardware>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22
msgid ":doc:`Activate barcode scanners </applications/inventory_and_mrp/barcode/setup/software>`"
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 ""
#: ../../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 <employee_login/configuration>` to the POS and :ref:`use barcodes to log your employees in <employee_login/badge>` your 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
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/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 <https://www.odoo.com/app/rental>`_"
msgstr ""
#: ../../content/applications/sales/rental.rst:12
msgid "`Odoo Tutorials: Rental <https://www.odoo.com/slides/rental-48>`_"
msgstr ""
#: ../../content/applications/sales/rental.rst:17
msgid "Dashboard"
msgstr ""
#: ../../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 ""
#: ../../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
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 ""
#: ../../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 <../finance/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 <https://www.odoo.com/slides/sign-61>`_"
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 <https://www.odoo.com/slides/sales-17>`_"
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
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:73
msgid "Supported marketplaces"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:75
msgid "The Amazon Connector supports all the current marketplaces."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:77
msgid "If a marketplace is not listed in your Amazon marketplaces, it's possible to :ref:`add a new marketplace <amazon/add-new-marketplace>`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:81
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:196
#: ../../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:82
#: ../../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:20
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:24
msgid "Force synchronization"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:26
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 <developer-mode>`. This includes changes on either end (Amazon or Odoo)."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:30
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:34
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:39
msgid "To immediately synchronize the orders of an Amazon account, switch to :ref:`developer mode <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:44
msgid "Manage deliveries in FBM"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:46
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:50
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:54
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:57
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:61
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:70
msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:75
msgid "Manage errors when synchronizing deliveries"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:77
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:81
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:85
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:94
msgid "Follow deliveries in FBA"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:96
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:99
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:102
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:107
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:110
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:114
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:117
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:122
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:125
msgid "Lastly, assign another stock location to the second registration of the account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:128
msgid "Invoice and register payments"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:131
msgid "Issue invoices"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:133
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:137
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:141
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:146
msgid "TaxCloud integration will be decommissioned in Odoo 17+."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:149
msgid "Register payments"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:151
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:154
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:157
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:160
msgid "Then, select all the generated payments, and click :menuselection:`Actions --> Create batch payment --> Validate`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:164
msgid "This same action can be performed with vendor bills from Amazon dedicated to commissions."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:166
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:170
msgid "Follow Amazon sales in sales reporting"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:172
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:175
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:178
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:182
msgid "It is also possible to perform reporting on a per-marketplace basis."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:184
msgid "First, remove the desired marketplace from the list of synchronized marketplaces."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:186
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:189
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:192
msgid "Lastly, assign another sales team to one of the two registrations of the account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:195
#: ../../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 <https://www.amazon.com/b/?node=12766669011>`_"
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 <amazon/matching>`."
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 <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 <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 <https://developer-docs.amazon.com/amazon-shipping/docs/marketplace-ids>`_, and the :guilabel:`Seller Central URL` as described in the `Amazon Documentation for seller central URLs <https://developer-docs.amazon.com/amazon-shipping/docs/seller-central-urls>`_."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:140
msgid "Set the :guilabel:`Name` of the record to `Amazon.<country code>` 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 ""
#: ../../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 <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`. This action will populate the :menuselection:`Sales --> Configuration --> eBay Categories` menu item with all standard eBay product categories."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:59
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:62
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:67
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:71
msgid "Link eBay listings"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:73
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:77
msgid "For more information on listing a product from scratch visit: :ref:`How to list a product? <ebay-connector/listing>`"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:81
msgid "Manual listing link"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:83
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:87
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:91
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:97
msgid "Turn on eBay scheduled Actions"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:99
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 <developer-mode>` and go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:104
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:107
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:111
msgid ":guilabel:`eBay: synchronize stock`: eBay will display the stock on hand in Odoo."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:112
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:116
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:122
#: ../../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:123
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:153
msgid ":doc:`/applications/sales/sales/ebay_connector/troubleshooting`"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:124
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:155
#: ../../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 "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 "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 will be the Odoo *Forecast Quantity* (Odoo *Inventory* app)."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:51
msgid "The :guilabel:`Description Template` allows the administrator to use templates in listings. The default template only use 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:58
msgid "To use images in the listing, another option is to add them as *Attachments* on the product template."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:62
msgid "For more information on template configuration in Odoo visit: :doc:`../../../general/email_communication/email_template`."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:66
msgid "Listing with variations"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:68
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:73
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:83
msgid "Product identifiers"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:85
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:88
msgid "EAN and UPC identifiers"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:90
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:94
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:99
msgid "Listing with item specifics"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:101
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:108
msgid "Process invoices and payments"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:111
msgid "Posting payment"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:113
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:118
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:124
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:132
msgid "Reconciling payments"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:134
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:138
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:143
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:148
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:154
#: ../../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 ""
#: ../../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 <linking_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 ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:31
msgid "Title"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:32
msgid "Subtitle"
msgstr ""
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
#: ../../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 <https://sandbox.ebay.com/>`_ at `https://sandbox.ebay.com/`. eBay's production environment can be accessed by navigating to `eBay.com portal <https://www.ebay.com/>`_ 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 Odoo 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/management/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 <https://go.developer.ebay.com/>`_. 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 <https://go.developer.ebay.com/>`_. 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 <https://go.developer.ebay.com/>`_. 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 <https://developer.ebay.com/sandbox/register>`_. Detailed instructions can be found on eBay's help pages: `Create a test Sandbox user <https://developer.ebay.com/api-docs/static/gs_create-a-test-sandbox-user.html>`_."
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 <https://developer.ebay.com/DevZone/build-test/test-tool/default.aspx>`_ 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 ""
#: ../../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 <https://go.developer.ebay.com/>`_ 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 <manage>`"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:402
msgid ":doc:`Link existing listings <linking_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 <ebay/subscribe-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 <ebay/retrieve-endpoint-details>`."
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 </administration/maintain/update>` 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 <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 <https://go.developer.ebay.com/>`_. 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 ""
#: ../../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:86
msgid "Example: request 50% down payment"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:89
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:97
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:260
#: ../../content/applications/sales/sales/invoicing/expense.rst:226
#: ../../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:99
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:102
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:105
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:112
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:116
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:120
msgid "For more information, check out the documentation on :ref:`customer taxes modification on down payments <sales/invoicing/customer-tax-modification-down-payments>` and :ref:`income account modification on down payments <sales/invoicing/income-account-modification>`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:124
msgid "Lastly, click :guilabel:`Create Draft Invoice` to create and view the invoice draft."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126
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:129
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:137
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:143
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:151
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
msgid "Customer Invoice with a green In Payment banner located in the upper-right corner."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158
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:161
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:168
msgid "Next, click the :guilabel:`Create Invoice` button."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170
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:177
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:181
msgid "Once ready, click :guilabel:`Create Draft Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:183
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:187
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:190
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:197
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:205
msgid "At this point, the flow is now complete."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:208
msgid "This flow is also possible with the :guilabel:`Fixed amount` down payment option."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:211
msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, 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:215
msgid "This is because, due to the invoicing policy, the product(s) would have to be delivered *before* creating the final invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:218
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:221
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:228
msgid "Customer taxes modification on down payments"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:230
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:234
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
msgid "How to modify the income account link to down payments."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:244
msgid "Income account modification on down payments"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:246
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:249
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:252
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 "Reinvoice expense"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:161
msgid "With those steps completed, it's time to return to the sales order to complete the reinvoice of the expense to the customer."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:164
msgid "To do that, navigate to :menuselection:`main Odoo dashboard --> Sales app`, and select the appropriate sales order that should be reinvoiced for the expense."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:167
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:174
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:181
msgid "From this pop-up window, leave the :guilabel:`Create Invoice` field on the default :guilabel:`Regular invoice` option, and click :guilabel:`Create Draft Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:184
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:191
msgid "If all the information related to the expense is correct, click :guilabel:`Confirm` to confirm the invoice. Doing so moves the status of the invoice from :guilabel:`Draft` to :guilabel:`Posted`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:194
msgid "To send the invoice to the customer, click :guilabel:`Send \\& Print`. Doing so reveals a :guilabel:`Send` pop-up window, with a preconfigured message and PDF invoice in the body of the message. The message can be reviewed and modified, if needed."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:198
msgid "Once ready, click :guilabel:`Send \\& Print` to send the invoice to the customer. When clicked, the pop-up window disappears, and Odoo sends the message/invoice to the customer. Additionally, a PDF of the invoice is automatically downloaded for record-keeping and/or printing purposes."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:202
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:209
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
msgid "A register payment pop-up window on a customer invoice in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:217
msgid "Once :guilabel:`Create Payment` is clicked, the pop-up window disappears, and a green :guilabel:`In Payment` banner is in the upper-right corner of the invoice, signifying this invoice is paid for in full. Thus, completing the workflow."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:227
#: ../../content/applications/sales/sales/invoicing/milestone.rst:236
msgid ":doc:`time_materials`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:228
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
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 <sales/invoicing/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 <sales/invoicing/add-expenses-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 <sales/invoicing/add-purchase-to-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 <ewallet_gift/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 </applications/sales/sales/products_prices/prices/pricing>`."
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:40
msgid "The program form contains the following options:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:42
msgid ":guilabel:`Program Name`: Enter the name of the program. The program name is *not* visible to the customer."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:44
msgid ":guilabel:`Program Type`: Select the desired :ref:`program type <sales/pricing_management/program-types>`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:46
msgid ":guilabel:`Currency`: Select the currency used for the program."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:47
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:50
msgid ":guilabel:`Validity`: Select the date until which the program is valid. Leave this field blank for no end date, meaning the program is always valid and does not expire."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:52
msgid ":guilabel:`Limit Usage`: Check this box and enter a number to limit the number of times the program can be used during the :guilabel:`Validity` period."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:54
msgid ":guilabel:`Company`: In the case of multiple companies, choose the company for which the program is available."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:56
msgid ":guilabel:`Available On`: Select the app(s) on which the program is available."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:57
msgid ":guilabel:`Website`: Select the website(s) 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:59
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:-1
msgid "Program options on the loyalty program form."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:67
msgid "The options available on the program form vary depending on the :ref:`Program Type <sales/pricing_management/program-types>` selected."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:70
msgid "All of the existing cards, codes, coupons, etc. that have been generated for the program are accessible through the smart button located in the upper-right corner 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:80
msgid "Program types"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:82
msgid "The different :guilabel:`Program Types` available on the program form are:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:84
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:86
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:88
msgid ":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates points to exchange for rewards on future orders."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:90
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:92
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:94
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:98
msgid "Conditional rules"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:100
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:103
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:112
msgid "The options for :guilabel:`Conditional rules` vary depending on the selected :ref:`Program Type <sales/pricing_management/program-types>`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:115
msgid "The following options are available for configuring conditional rules:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:117
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:120
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:123
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:127
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:129
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:131
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:132
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:140
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:144
msgid "Rewards"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:146
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:151
msgid "The options for :guilabel:`Rewards` vary depending on the selected :ref:`Program Type <sales/pricing_management/program-types>`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:154
msgid "The following options are available for configuring rewards:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:156
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:160
msgid ":guilabel:`Free Product`:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:162
msgid ":guilabel:`Quantity Rewarded`: Select the number of free products rewarded to the customer."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:163
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:165
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:168
msgid ":guilabel:`Discount`:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:170
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:174
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:179
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:177
msgid ":guilabel:`Free Shipping`:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:182
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:184
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
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:328
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
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:267
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:55
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:63
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:66
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:71
msgid "Price rules tab"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:73
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:77
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:81
msgid "Price rules tab (multiple prices per product)"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:83
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:87
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:91
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:95
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:98
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:102
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:105
msgid "For more information, check out the following section: :ref:`Multiple prices per product <sales/multiple-prices-per-product>`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:109
msgid "Price rules tab (advanced price rules)"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111
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:115
msgid "Check out the :ref:`Advanced price rules (discounts, formulas) <sales/advanced-price-rules>` section for detailed steps on how to add advanced price rules to a pricelist."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119
msgid "Time-based rules tab"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:121
msgid "Time-based rules are used specifically with :doc:`subscription products </applications/sales/subscriptions/products>`. Be sure to check out the Odoo *Subscriptions* :doc:`documentation </applications/sales/subscriptions>`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:125
msgid "Under the :guilabel:`Time-based rules` tab, the same functionality of the :guilabel:`Price Rules` tab is present, with the only difference being that a repeating time period can be applied in the :guilabel:`Period` column."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:129
msgid "After a :guilabel:`Product` and potential :guilabel:`Variant` are selected in the :guilabel:`Time-based rules` tab, select the blank field in the :guilabel:`Period` 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:133
msgid "New recurrence periods can also be directly created from this column, by typing in the new name for the :guilabel:`Period` and then selecting :guilabel:`Create` to create the time period, which can be edited later. Or, select :guilabel:`Create and edit...` to reveal a pop-up form, in which the new recurrence period can be directly configured."
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:142
msgid "From this :guilabel:`Create Period` pop-up form, add a :guilabel:`Name`, :guilabel:`Duration`, then a :guilabel:`Unit` (e.g. `Days`, `Weeks`, etc.). When finished, click :guilabel:`Save and Close`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145
msgid "Lastly, add the desired price for this time-based rule in the :guilabel:`Price` column."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:148
msgid ":doc:`/applications/sales/subscriptions`"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:151
msgid "Configuration tab"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:153
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:160
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:165
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:167
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 will be applied to all websites in the database."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:172
msgid "Click 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 unchecked, customers **cannot** select this pricelist for themselves as they shop."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:176
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:181
msgid "Show discount percentage to customers"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:183
msgid "With Odoo *Sales*, the option to show the public price *and* the computed discount percentage on the product catalog is available."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:186
msgid "To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Pricing` section, click the checkbox next to the :guilabel:`Discounts` feature, and then click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:190
msgid "After activating the :guilabel:`Discounts` feature, navigate to the pricelists page, either by clicking the :guilabel:`Pricelists` link from the :guilabel:`Settings` page, or by going to :menuselection:`Sales app --> Products --> Pricelists`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:194
msgid "On the :guilabel:`Pricelists` page, select the desired pricelist to edit. On the pricelist form, click into the :guilabel:`Configuration` tab. In the :guilabel:`Configuration` tab, at the bottom, a :guilabel:`Discounts` section is now available."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1
msgid "What the discount options are on the configuration tab of a pricelist in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:202
msgid "The options available in this section are:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:204
msgid ":guilabel:`Discount included in the price`: shows the customer only the final price with the discount already included."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:206
msgid ":guilabel:`Show public price & discount to the customer`: shows the customer the public price *and* the discount they're earning."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:210
msgid "Customer pricelist application"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:212
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:215
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:223
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:236
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:240
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:245
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:252
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:259
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:263
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:270
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:276
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:280
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:285
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:288
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:292
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:295
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:298
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:304
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:314
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:318
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:323
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:331
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:334
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:343
msgid "Price computation"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:345
msgid "On this form, first choose one of the three :guilabel:`Computation` options:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:347
msgid ":guilabel:`Fixed Price`: the price computation is based on a fixed price."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:348
msgid ":guilabel:`Discount`: the price computation is based on a discount."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:349
msgid ":guilabel:`Formula`: the price computation is based on a formula."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352
msgid "Each :guilabel:`Computation` option reveals its own computation-specific fields on the form."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354
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:358
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:364
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:368
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:372
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:380
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:385
msgid "Rounding is applied *after* the discount and *before* the surcharge."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388
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:391
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:393
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:397
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:406
msgid "Conditions"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:408
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:411
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:413
msgid ":guilabel:`All Products`: the advanced pricelist rule will be applied to all products."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414
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:416
msgid ":guilabel:`Product`: the advanced pricelist rule will be applied to a specific product."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417
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:420
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:424
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:428
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:433
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:437
msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438
msgid ":doc:`/applications/websites/ecommerce/managing_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
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:174
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 <https://console.developers.google.com/>`_ 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 <https://programmablesearchengine.google.com/>`_, 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 <https://cloud.google.com/billing/docs/how-to/manage-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/managing_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 ""
#: ../../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 :guilabel:`Product Configurator`, :guilabel:`Point of Sale` dashboard, and :guilabel:`eCommerce` pages."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:61
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:68
msgid "First, create an :guilabel:`Attribute Name`, such as `Color` or `Size`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:70
msgid "Next, in the optional :guilabel:`Category` field, select a category from a drop-down menu to group similar attributes under the same section for added specificity and organization."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:74
msgid "To view the details related to the attribute category selected, click the internal link :guilabel:`➡️ (arrow)` icon to the far-right of the :guilabel:`Category` field. Doing so reveals that attribute category's detail form."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "A standard attribute category detail page accessible via its internal link arrow icon."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:82
msgid "Here, the :guilabel:`Category Name` and :guilabel:`Sequence` is displayed at the top. Followed by :guilabel:`Related Attributes` associated with the category. These attributes can be dragged-and-dropped into a desirable order of priority."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:86
msgid "Attributes can be directly added to the category, as well, by clicking :guilabel:`Add a line`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:89
msgid "To create an attribute category directly from this field, start typing the name of the new category, then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:93
msgid "Clicking :guilabel:`Create` creates the category, which can be modified later. Clicking :guilabel:`Create and edit...` creates the category and reveals a :guilabel:`Create Category` pop-up window, in which the new attribute category can be configured and customized."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:97
msgid "Beneath the :guilabel:`Category` field are the :guilabel:`Display Type` options. The :guilabel:`Display Type` determines how this product is shown on the online store, :guilabel:`Point of Sale` dashboard, and :guilabel:`Product Configurator`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:101
msgid "The :guilabel:`Display Type` options are:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:103
msgid ":guilabel:`Radio`: options appear in a bullet-style list on the product page of the online store."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:104
msgid ":guilabel:`Pills`: options appear as selectable buttons on the product page of the online store."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:105
msgid ":guilabel:`Select`: options appear in a drop-down menu on the product page of the online store."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:106
msgid ":guilabel:`Color`: options appear as small, colored squares, which reflect any HTML color codes set, on the product page of the online store."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "Display Types on Product Configurator on the online store in Odoo."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:113
msgid "The :guilabel:`Variants Creation Mode` field informs Odoo when to automatically create a new variant once an attribute is added to a product."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:116
msgid ":guilabel:`Instantly`: creates all possible variants as soon as attributes and values are added to a product template."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:118
msgid ":guilabel:`Dynamically`: creates variants **only** when corresponding attributes and values are added to a sales order."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:120
msgid ":guilabel:`Never (option)`: never automatically creates variants."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:123
msgid "Once added to a product, an attribute's :guilabel:`Variants Creation Mode` cannot be edited."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:125
msgid "Lastly, the :guilabel:`eCommerce Filter Visibility` field determines whether these attribute options are visible to the customer on the front-end, as they shop on the online store."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:128
msgid ":guilabel:`Visible`: the attribute values are visible to customers on the front-end."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:129
msgid ":guilabel:`Hidden`: the attribute values are hidden from customers on the front-end."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:132
msgid "Attribute values"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:134
msgid "Attribute values should be added to the :guilabel:`Attribute Values` tab. Values can be added to an attribute at any time, if needed."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137
msgid "To add a value, click :guilabel:`Add a line` in the :guilabel:`Attribute Values` tab."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:139
msgid "Then, enter the name of the value in the :guilabel:`Value` column. Next, check the box in the :guilabel:`Is custom value` column, if the value is custom (i.e. the customer gets to provide unique specifications that are specific to this particular value)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:144
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:152
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:159
msgid "In this pop-up window, select a specific color by dragging the color slider to a particular hue, and clicking on the color portion directly on the color gradient window."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:162
msgid "Or, choose a specific color by clicking the *dropper* icon, and selecting a desired color that's currently clickable on the screen."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:166
msgid "Attributes can also be created directly from the product template by adding a new line and typing the name into the :guilabel:`Variants` tab."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169
msgid "Once an attribute is added to a product, that product is listed and accessible, via the attribute's :guilabel:`Related Products` smart button. That button lists every product in the database currently using that attribute."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:176
msgid "Once an attribute is created, use the attribute (and its values) to create a product variant. To do that, go to :menuselection:`Sales app --> Products --> Products`, and select an existing product to view that desired product's form. Or, click :guilabel:`Create` to create a new product, to which a product variant can be added."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:181
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:188
msgid "To add an attribute to a product, and subsequent attribute values, click :guilabel:`Add a line` in the :guilabel:`Attributes \\& Variants` tab. Then, choose the desired attribute from the drop-down menu that appears."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:193
msgid "Attributes can be created directly from the :guilabel:`Attributes \\& Variants` tab of a product form. To do that, start typing the name of the new attribute in the blank field, and select either :guilabel:`Create` or :guilabel:`Create and edit...` from the mini drop-down menu that appears."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:198
msgid "Clicking :guilabel:`Create` creates the attribute, which can be customized later. Clicking :guilabel:`Create and edit...` creates the attribute, and a :guilabel:`Create Attribute` pop-up form appears. In the pop-up form, proceed to modify the attribute in a number of ways."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:202
msgid "Once an attribute is selected in the :guilabel:`Attribute` column, proceed to select the specific attribute values to apply to the product, via the drop-down menu available in the :guilabel:`Values` column."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:207
msgid "There is no limit to how many values can be added."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:210
msgid "Similar product variant creation processes are accessible through the Purchase, Inventory, and eCommerce applications."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:214
msgid "Configure variants"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:216
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:223
msgid "Here, the specific :guilabel:`Value` name, :guilabel:`HTML Color Index` (if applicable), and :guilabel:`Value Price Extra` are viewable."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:227
msgid "The :guilabel:`Value Price Extra` represents the increase in the sales price if the attribute is selected."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:230
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:237
msgid "On the specific product variant detail page, the :guilabel:`Value` and :guilabel:`Value Price Extra` fields can be found, along with an :guilabel:`Exclude for` field."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:240
msgid "In the :guilabel:`Exclude for` field, different :guilabel:`Product Templates` and specific :guilabel:`Attribute Values` can be added. When added, this specific attribute value will be excluded from those specific products."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:245
msgid "Variants smart button"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:247
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:255
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:263
msgid "Impact of variants"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:265
msgid "In addition to offering more detailed product options to customers, product variants have their own impacts that can be taken advantage of throughout the Odoo database."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:268
msgid ":guilabel:`Barcode`: barcodes are associated with each variant, instead of the product template. Each individual variant can have its own unique barcode/SKU."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:270
msgid ":guilabel:`Price`: every product variant has its own public price, which is the sum of the product template price *and* any extra charges for particular attributes."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:274
msgid "A red shirt's sales price is $23 -- because the shirt's template price is $20, plus an additional $3 for the red color variant. Pricelist rules can be configured to apply to the product template, or to the variant."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:278
msgid ":guilabel:`Inventory`: inventory is counted for each individual product variant. On the product template form, the inventory reflects the sum of all variants, but the actual inventory is computed by individual variants."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:281
msgid ":guilabel:`Picture`: each product variant can have its own specific picture."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:284
msgid "Changes to the product template automatically apply to every variant of that product."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:287
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/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:21
msgid "Contact form configuration"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23
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:28
msgid "Contact forms can be accessed in the *Contacts* application, as well."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:30
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:38
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:41
msgid "Select any of the following options:"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:43
msgid ":guilabel:`Contact`: adds another contact to the existing contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:44
msgid ":guilabel:`Invoice Address`: adds a specific invoice address to the existing contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:45
msgid ":guilabel:`Delivery Address`: adds a specific delivery address to the existing contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:46
msgid ":guilabel:`Other Address`: adds an alternate address to the existing contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:47
msgid ":guilabel:`Private Address`: adds a private address to the existing contact form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49
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:56
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:60
msgid "Address added to quotations"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:62
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:70
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:74
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:77
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
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 ""
#: ../../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_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/get_paid_to_validate.rst:90
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:245
msgid ":doc:`get_signature_to_validate`"
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/get_signature_to_validate.rst:78
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:246
msgid ":doc:`get_paid_to_validate`"
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:162
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:179
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:182
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
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] <https://www.youtube.com/watch?v=tQNydBZt-VI>`_"
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 <pdf_quote_builder/pdfquotebuilderexamples.zip>` for added reference."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3
msgid "Quotation templates"
msgstr ""
#: ../../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:127
msgid "If the desired product isn't readily visible, type the name of the desired product in the :guilabel:`Product` field, and the option appears in the drop-down menu. Products can also be found by clicking :guilabel:`Search More...` from the drop-down menu."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:132
msgid "When a product is added to a quotation template, the default :guilabel:`Quantity` is `1`, but that can be edited at any time."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:135
msgid "Then, drag-and-drop the product to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138
msgid "To add a *section*, which serves as a header to organize the lines of a sales order, click :guilabel:`Add a section` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired name of the section can be typed. When the name has been entered, click away to secure the section name."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:143
msgid "Then, drag-and-drop the section name to the desired position, via the :guilabel:`six squares` icon, located to the left of each line item."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:146
msgid "To add a note, which would appear as a piece of text for the customer on the quotation, click :guilabel:`Add a note` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired note can be typed. When the note has been entered, click away to secure the note."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:150
msgid "Then, drag-and-drop the note to the desired position, via the :guilabel:`six squares` icon."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:152
msgid "To delete any line item from the :guilabel:`Lines` tab (product, section, and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right side of the line."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:156
msgid "Optional Products tab"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:158
msgid "The use of *optional products* is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:166
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:173
msgid "In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each cross-selling product related to the original items in the :guilabel:`Lines` tab, if applicable. The products added here ideally complement the original offering as added value for the prospective buyer."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:177
msgid "Clicking :guilabel:`Add a line` reveals a blank field in the :guilabel:`Product` column."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:186
msgid "Optional products are **not** required to create a quotation template."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:189
msgid "Terms \\& Conditions tab"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:191
msgid "The :guilabel:`Terms \\& Conditions` tab provides the opportunity to add terms and conditions to the quotation template. To add terms and conditions, simply type (or copy/paste) the desired terms and conditions in this tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:196
msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:199
msgid "Terms and conditions are **not** required to create a quotation template."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:202
msgid "PDF Quote Builder tab"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:204
msgid "The :guilabel:`PDF Quote Builder` tab provides options to compose an attractive quotation, with more information and visually-pleasing elements, to highlight products and/or services."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:207
msgid "To upload customer :guilabel:`Header pages` and :guilabel:`Footer pages`, click the :guilabel:`✏️ (pencil)` icon to the right of the respective pages. Click the :guilabel:`🗑️ (trash)` icon to delete an uploaded PDF."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:212
msgid ":doc:`/applications/sales/sales/send_quotations/pdf_quote_builder`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:215
msgid "Use quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:217
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:224
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:233
msgid "Quotation template design uses the same methodology and functionality with design building blocks as a typical web page design with Odoo *Website*. Be sure to check out the :doc:`../../../websites/website` documentation to learn more."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:237
msgid "When all blocks and customizations are complete, click the :guilabel:`Save` button to put those configurations into place."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:240
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/subscriptions.rst:5
msgid "Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:7
msgid "Odoo *Subscriptions* is used to run recurring businesses: :ref:`sell new contracts <subscriptions/quotations>`, :doc:`upsell customers </applications/sales/subscriptions/upselling>`, keep the churn under control, and :doc:`generate reports </applications/sales/subscriptions/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 <https://www.odoo.com/slides/subscription-20>`_"
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/reports`"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:28
msgid "Subscription quotations"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:31
msgid "Sales orders with a defined recurrence become subscriptions."
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:33
msgid "To create a new subscription, click on :guilabel:`New` from the *Subscription* or the :doc:`Sales </applications/sales>` app. You can either:"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:36
msgid "Select a :doc:`subscription plan </applications/sales/subscriptions/plans>` to prefill the quotation instantly, or"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:38
msgid "Fill out the quotation normally, making sure to select a recurrence and an end date if necessary and adding :doc:`recurrent products </applications/sales/subscriptions/products>`."
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:42
msgid "You can define different invoice and delivery addresses by enabling the :doc:`Customer Addresses </applications/finance/accounting/customer_invoices/customer_addresses>` feature."
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:48
msgid "Confirmation"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:50
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:54
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:60
msgid "Automatic payments"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:62
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:67
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:72
msgid "If the online confirmation requires a pre-payment, your customer can select only the :ref:`payment providers <payment_providers/supported_providers>` that have the :ref:`tokenization feature <payment_providers/features/tokenization>`. This ensures that the customer is automatically charged at each new period."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:3
msgid "Automatic alerts"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:5
msgid "Now that your subscriptions are up and running, you want to stay up-to-date with your customers. Some automation would be appreciated since you would not want to go through the list of all your subscribers to check how things are going. This is what the *Automatic Alerts* feature is for."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:9
msgid "For example, when customers subscribe to your magazine, you would probably want to send them an email to welcome them and express your gratitude. Or, if the satisfaction rate of your customers drops below 50%, you would probably want to schedule a call with them to understand the reasons for their dissatisfaction."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:14
msgid "With **Odoo Subscriptions**, you can set automatic emails, create a \"Call\" task for one of your salespeople so that he/she can try to understand your customer's dissatisfaction, and finally, why not automatically send satisfaction surveys so customers can evaluate your services? All of that is now possible."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:20
msgid "Create a new automatic alert"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:22
msgid "The following example shows how to create a new automatic alert to send satisfaction surveys to your customers, by email, after one month of subscription. To do so, go to :menuselection:`Subscriptions --> Configuration --> Alerts`, and create a new alert."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:-1
msgid "New automatic alert in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:30
msgid "On the *Apply on* section, first give the alert a name. Then, you can choose to apply this alert on a subscription template, on a specific customer, or even on a specific product. If you want to add more specifications, you can also specify the value of your MRR, the change rate of your MRR over a certain period of time, the value of the satisfaction rate, and even the stage to which you want to apply this alert."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:37
msgid "In this example, the alert is applied to a specific product, and the stage goes from *Undefined* to *In Progress*."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:40
msgid "For the *Action* section, specify the *Action* and the *Trigger on*. If the *Trigger on* is set to *Modification*, the action is triggered every time there is a change or anything added to the subscription, and all the conditions on the *Apply on* section are met. Now, if the *Trigger on* is set to *Timed condition*, it means that the action is triggered based on the type of *Trigger date*. After that, you can choose your *Action*. You have the choice between *Create next activity*, *Set a tag on the subscription*, *Set a stage on the subscription*, *Mark as To Renew*, *Send an email to the customer* and *Send an SMS Text Message to the customer*."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:50
msgid "In the example above, the *Trigger on* is set to *Timed condition*, therefore, a *Trigger date* and *Delay after trigger* need to be specified. And because the *Send an email to the customer* action was adopted, an *Email template* can be chosen."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:54
msgid "As a result, this alert will send a rating survey after one month, to the customers who have purchased that specific product. The survey will appear in the chatter of your respective subscription."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:-1
msgid "Satisfaction survey in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:63
msgid "Modify an existing automatic alert"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:65
msgid "By default, Odoo suggests you an automatic alert called *Take action on less satisfied clients*."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:-1
msgid "Modify an existing automatic alert in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:71
msgid "This alert is applied to the *Rating Satisfaction* of your customers, and the action is triggered on *Timed condition*. If their satisfaction rate is lower than 50%, a salesperson contacts the customer. This action is automatically assigned to the salesperson who manages the subscription, and the due date is 5 days after the triggering of this action. This alert ensures that your clients are happy and that you are taking actions if they are not. It helps to keep your customer retention rates very high."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:79
msgid "By editing the alert, you can modify the *Apply on*, the *Action* and *Activity* sections, and adapt them to your own needs."
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:83
#: ../../content/applications/sales/subscriptions/closing.rst:105
#: ../../content/applications/sales/subscriptions/renewals.rst:85
#: ../../content/applications/sales/subscriptions/reports.rst:120
#: ../../content/applications/sales/subscriptions/upselling.rst:103
msgid ":doc:`../subscriptions`"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:84
#: ../../content/applications/sales/subscriptions/closing.rst:106
#: ../../content/applications/sales/subscriptions/renewals.rst:86
#: ../../content/applications/sales/subscriptions/reports.rst:121
#: ../../content/applications/sales/subscriptions/upselling.rst:104
msgid ":doc:`plans`"
msgstr ""
#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:85
#: ../../content/applications/sales/subscriptions/closing.rst:107
#: ../../content/applications/sales/subscriptions/renewals.rst:87
#: ../../content/applications/sales/subscriptions/reports.rst:122
#: ../../content/applications/sales/subscriptions/upselling.rst:105
msgid ":doc:`products`"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:3
msgid "Close a subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:5
msgid "Losing a customer is always difficult, especially if you put a lot of effort into getting them to sign up for your products/services. However, many companies come up with dubious methods to reduce the probability of this happening."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:14
msgid "If you adopt such methods, you are among companies that actively and indirectly spread the phobia of subscriptions, who do not think about how negatively dissatisfied customers could impact their business and, who frustrate the customers in a way or another. However, at some point, it is understandable that you do not want your customers to be involved in your subscription status."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:19
msgid "If you do not adopt such methods, you are among companies that continue to evolve in a long-term subscription business model, especially in an era of ultra-fast communications between dissatisfied customers, and who retain their customers by making it easier for them to leave if they want to. By giving them the opportunity to close their own subscriptions, your customers do not feel trapped because they subscribed to your products/services."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:25
msgid "In summary, the **Odoo Subscriptions** application gives you the **possibility to choose what you want to apply**. Indeed, you can decide whether to give your customers the option to close their subscriptions whenever they want to or to restrict this possibility. It depends on you and we will show you how to do that in our amazing application."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:33
msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. From there, you can create a new *Subscription template* or modify an existing one. When editing your template, underneath the Invoicing tab, you have the possibility to activate the option *Closable by customer*. Once enabled, this option gives your customers the right to close their own subscriptions."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:-1
msgid "Configuration to close your subscription with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:43
msgid "Be sure to check out our documentation on how to :doc:`Use subscription templates <plans>` to fully understand the importance of this feature in a basic flow using the **Odoo Subscriptions** application."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:49
msgid "Close your first subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:52
msgid "Administrator view"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:54
msgid "Once confirmed, a quotation becomes a sales order and a new subscription is automatically created. Therefore, this subscription has the status *In progress*. From there, you have the possibility to close the subscription."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:-1
msgid "Close your subscription from an administration point of view with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:62
msgid "By using the smart button *Close*, you have to enter a close reason. For example, \"Subscription too expensive\", \"Subscription does not meet my requirements\", \"Subscription reached its end date\", etc. Immediately after confirming your close reason, you can observe that the status of the subscription is now *Closed* and that the close reason is mentioned on the subscription."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:-1
msgid "What happens when you close your subscription with Odoo Subscriptions?"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:72
msgid "Customer view"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:74
msgid "As previously explained in the *Administrator view* part, from the subscription form, you also have the possibility to visualize what your customers see when managing their subscriptions thanks to the *Customer preview* button. In this example, the customer has the choice to close his/her subscription whenever he/she wants to, due to the *Close Subscription* button."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:-1
msgid "Close your subscription from a customer point of view with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:83
msgid "By using this button, the customer can specify the reason for cancelling his/her subscription and he/she can even leave a message."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:-1
msgid "What happens when customers close their subscription with Odoo Subscriptions?"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:90
msgid "By confirming the cancellation, the customer is redirected to his/her portal. The administrator is informed of this modification. Indeed, the status of the subscription becomes *Closed* and a note appears in the chatter with the new stage, the end date, the close reason, and the closing text added by the customer."
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:-1
msgid "What happens when customers close their subscription in Odoo Subscriptions?"
msgstr ""
#: ../../content/applications/sales/subscriptions/closing.rst:100
msgid "Before closing a subscription, check out our documentation on how to :doc:`Create a quotation using subscription products <../subscriptions>` to understand how subscriptions are managed in the **Odoo Subscriptions** application."
msgstr ""
#: ../../content/applications/sales/subscriptions/ecommerce.rst:3
msgid "Use 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:`Time-based pricing` tab of the product form. For example, if a subscription product has *monthly* and *yearly* 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:12
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:16
msgid ":doc:`Configure subscription products </applications/sales/subscriptions/products>`"
msgstr ""
#: ../../content/applications/sales/subscriptions/ecommerce.rst:17
msgid ":doc:`Product variants </applications/sales/sales/products_prices/products/variants>`"
msgstr ""
#: ../../content/applications/sales/subscriptions/ecommerce.rst:20
msgid "Create recurrence periods as product variants"
msgstr ""
#: ../../content/applications/sales/subscriptions/ecommerce.rst:22
msgid "To set up each recurrence period as a product variant, go to :menuselection:`Subscriptions --> Subscriptions --> Products` and select a product. In the :guilabel:`Attributes & Variants` tab, click :guilabel:`Add a line`."
msgstr ""
#: ../../content/applications/sales/subscriptions/ecommerce.rst:26
msgid "Create an :guilabel:`Attribute` called `Billing Period` (or something similar) by typing in the name and clicking :guilabel:`Create`. This attribute name appears as the option heading on the product page of the eCommerce shop."
msgstr ""
#: ../../content/applications/sales/subscriptions/ecommerce.rst:30
msgid "Next, create :guilabel:`Values` that correspond to the recurrence periods that are configured in the :guilabel:`Time-based pricing` tab of the product form. Type in the name of the recurrence period, then click :guilabel:`Create`. 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:40
msgid "Click on the :guilabel:`☁️ (cloud)` icon at the top of the page to save manually. After saving, a :guilabel:`Product Variants` column appears on the :guilabel:`Time-based pricing` tab. Assign the product variants to their corresponding recurrence periods and prices."
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:48
msgid "The product variants are now 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/plans.rst:3
msgid "Subscription plans"
msgstr ""
#: ../../content/applications/sales/subscriptions/plans.rst:5
msgid "*Subscription plans* are :doc:`quotation templates </applications/sales/sales/send_quotations/quote_template>` 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 </applications/general/email_communication/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 </applications/websites/ecommerce/ecommerce_management/customer_accounts>`."
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 </applications/finance/accounting/customer_invoices/terms_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:-1
msgid "A basic subscription product form in Odoo Subscriptions application."
msgstr ""
#: ../../content/applications/sales/subscriptions/products.rst:75
msgid "Time-based pricing"
msgstr ""
#: ../../content/applications/sales/subscriptions/products.rst:77
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:84
msgid "From here, click :guilabel:`Add a price` to begin defining recurring prices."
msgstr ""
#: ../../content/applications/sales/subscriptions/products.rst:86
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:91
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:98
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:101
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:104
msgid "A subscription product can still be sold as a regular product, by adding it to a quotation and *not* selecting a :guilabel:`Recurrence` on the quotation."
msgstr ""
#: ../../content/applications/sales/subscriptions/products.rst:110
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:113
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:116
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:123
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:126
msgid "Time-based pricing rules can also be configured directly on the pricelist form."
msgstr ""
#: ../../content/applications/sales/subscriptions/products.rst:128
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:132
msgid "Pricelists are also accessible through the Odoo *Subscriptions* app by following the same menu steps."
msgstr ""
#: ../../content/applications/sales/subscriptions/products.rst:135
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:142
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:146
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:150
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. That's 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 "The renewal of a subscription is the process followed by customers when they willingly choose to continue their participation (and payment) 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 renewals process for customers, but, in some cases, manual subscription renewals are still used."
msgstr ""
#: ../../content/applications/sales/subscriptions/renewals.rst:18
msgid "With the Odoo *Subscriptions* application, a company can manage all of their 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 :guilabel:`Recurring Plan` selected, which turns it into a sales order."
msgstr ""
#: ../../content/applications/sales/subscriptions/renewals.rst:30
msgid "Only a singular product is required."
msgstr ""
#: ../../content/applications/sales/subscriptions/renewals.rst:31
msgid "A subscription service is still a product (albeit a digital, recurring one)"
msgstr ""
#: ../../content/applications/sales/subscriptions/renewals.rst:33
msgid "Then, that sales order needs to be confirmed, and payment from the customer for the initial subscription has to be invoiced and registered."
msgstr ""
#: ../../content/applications/sales/subscriptions/renewals.rst:36
msgid "When those steps are complete, an :guilabel:`In Progress` tag is applied to the sales order form, and a series of buttons appear at the top of the sales order -- including a button titled, :guilabel:`Renew`."
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:44
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
msgid "Renewal quotation in the Odoo Subscriptions application."
msgstr ""
#: ../../content/applications/sales/subscriptions/renewals.rst:51
msgid "From here, a standard sales flow can occur in order to confirm the quotation. This typically begins by clicking :guilabel:`Send by Email`. This 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:56
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:59
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:66
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:74
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:81
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/reports.rst:3
msgid "Reports"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:5
msgid "As we know, understanding how our business is going, and where it is going, is key to success. And particularly so when we offer subscription services or products."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:8
msgid "Before getting to the heart of the matter, it is very important to recall certain essential concepts to the proper understanding of the following reports:"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:11
msgid "**Monthly Recurring Revenue (MRR)**: MRR is arguably the most important metric for subscription businesses. It shows the monthly revenue earned with subscription-based products or services. It is a consistent number used to track all recurring revenue over time, in monthly increments."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:15
msgid "**Annual Run-Rate (ARR)**: ARR is the yearly version of MRR, which is based on the current MRR, to estimate the coming year's performance. However, this estimation does not take variations and growth into account."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:-1
msgid "Difference between MRR and ARR in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:23
msgid "**Non-Recurring Revenue (NRR)**: NRR shows the revenue earned for everything else than subscription-based products or services. This includes gains of a rare or unique nature that are unlikely to occur in the ordinary course of businesses."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:27
msgid "**Customer Retention**: Practices to engage existing customers to continue buying products or services from your business. Customer retention can be a challenge, because you must prove you are worthy of your customers' trust."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:31
msgid "**Churn Rate**: Also known as the Rate of Attrition or Customer Churn, the churn rate can be defined, in this case, as the percentage of subscribers who discontinued their subscriptions within a given time period. We can distinguish two types of Churn:"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:35
msgid "**Logo Churn**: It corresponds to the subscription cancellation rate."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:37
msgid "**Revenue Churn**: It corresponds to the monthly recurring revenue loss rate."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:40
msgid "Let's imagine a 2$ increase in a subscription service."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:42
msgid "We lost 3 customers out of the initial 20, which generates a **Logo Churn** of 15%."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:0
msgid "Therefore, the 56$ of MRR difference out of the initial 600$ causes a **Revenue Churn**"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:0
msgid "of 9,33%."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:0
msgid "Difference between logo churn and revenue churn in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:50
msgid "Reminder: even though they seem to evolve in the same direction most of the time, it might not be the case all the time."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:53
msgid "**Customer Lifetime Value (CLV)**: Indicates how much revenue can be expected for a customer during his/her entire contract. This approach emphasizes the importance of customer retention, shifting our focus from a quarterly or yearly approach to a long-term one."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:57
msgid "Check out the different kinds of reports you can access from the **Odoo Subscriptions** application."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:61
msgid "Subscriptions analysis report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:63
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Subscriptions`. From there, you can change the *Measures*. By default, Odoo uses the *Monthly Recurring Revenue*. In addition to that, you can choose *Quantity*, *Recurring Price*, *Yearly Recurring Revenue* and *Count*. For this example, *Quantity* is added. This way, you can review both of these measures at the same time. You can even *Group By Start Date* and, more precisely, by *Week*, to get a clear view of your report."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:-1
msgid "Subscriptions analysis report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:74
msgid "Retention analysis report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:76
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Retention`. The default measure applied is *Count*, but you can change to the appropriate one for you. For the example below, *Monthly Recurring Revenue* was chosen, and the *Month* periodicity remains intact. By using these criteria, you can see the progression of the retention from its start."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:-1
msgid "Retention analysis report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:86
msgid "Revenue KPIs report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:88
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Revenue KPIs`. From there, you can check different KPIs: *Monthly Recurring Revenue*, *Net Revenue*, *Non-Recurring Revenue*, *Revenue per Subscription*, *Annual Run-Rate*, *Lifetime Value*, and more. You can also filter this information on subscriptions, companies, and sales teams. This is useful if you are looking for specific information."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:-1
msgid "Revenue KPIs report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:98
msgid "The example below shows the *Monthly Recurring Revenue* detailed report. At the moment, there is no data, which is the typical scenario for a new business. But, as your company grows over the months, these graphs get populated with more and more data. Once again, you can filter these specific KPIs on subscriptions, companies, and sales teams."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:-1
msgid "Detailed MRR report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:108
msgid "Salesperson dashboard report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:110
msgid "Go to :menuselection:`Subscriptions --> Reporting --> Salesperson Dashboard`. This page gives you a summary of your *Monthly Recurring Revenue*, *Non-Recurring Revenue*, *Subscription modifications*, and *Non-Recurring Invoices* for each of your salespeople. You can choose the period you want to apply and the salesperson you want to analyze."
msgstr ""
#: ../../content/applications/sales/subscriptions/reports.rst:-1
msgid "Salesperson dashboard report in Odoo Subscriptions"
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:71
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:78
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:82
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:87
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:90
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:94
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 ""