NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
cc6e1e6b34
documentation/locale/sources/sales.pot
Martin Trigaux 0101876db6 [I18N] *: export saas-15.2 translations 
closes 

X-original-commit: fd2da98f0e
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
2023-12-19 08:15:39 +00:00

7121 lines
379 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 saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-12-19 07:46+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 "The system can generate leads instead of opportunities, in order to add a qualification step before converting a *Lead* into an *Opportunity* and assigning to the right sales people."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:9
msgid "You can activate this mode from the CRM Settings. It applies to all your sales channels by default. But you can make it specific for specific channels from their configuration form."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:14
#: ../../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/performance/google_spreadsheets.rst:10
#: ../../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/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:16
#: ../../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/loyalty.rst:9
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:12
#: ../../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/shop/barcode.rst:10
#: ../../content/applications/sales/rental.rst:20
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:13
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:9
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:13
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:18
#: ../../content/applications/sales/subscriptions/configuration.rst:5
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:16
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:32
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:31
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:25
msgid "Configuration"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:16
msgid "For this feature to work, go to :menuselection:`CRM --> Configuration --> Settings` and activate the *Leads* feature."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:22
msgid "You will now have a new submenu *Leads* under *Leads* where they will aggregate."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:29
msgid "Convert a lead into an opportunity"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:31
msgid "When you click on a *Lead* you will have the option to convert it to an opportunity and decide if it should still be assigned to the same channel/person and if you need to create a new customer."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:38
msgid "If you already have an opportunity with that customer Odoo will automatically offer you to merge with that opportunity. In the same manner, Odoo will automatically offer you to link to an existing customer if that customer already exists."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:44
msgid "Merge opportunities"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:46
msgid "Odoo will also automatically propose to merge opportunities if they have the same email address. When merging opportunities, Odoo merges the information into the opportunity which was created first, giving priority to the information present on the first opportunity."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:51
msgid "No information is lost: data from the other opportunity is logged in the chatter and the information fields for easy access."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:57
msgid "Would you find a duplicate yourself, ...you can also merge opportunities or leads even if the system doesn't propose it."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:60
msgid "Here’s how, from the list view. Select the opportunities or leads you want to merge and the action button will appear. Then, you can select merge."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:67
msgid "It is also possible to merge more than 2 opportunities or leads."
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
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 "Send quotations"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:5
msgid "When you qualify a lead into an opportunity you will most likely need to send them a quotation. You can directly do this in the CRM App with Odoo."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:12
msgid "Create a new quotation"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:14
msgid "By clicking on any opportunity or lead, you will see a *New Quotation* button, it will bring you into a new menu where you can manage your quote."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:21
msgid "You will find all your quotes to that specific opportunity under the *Quotations* menu on that page."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:28
msgid "Mark them won/lost"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:30
msgid "Now you will need to mark your opportunity as won or lost to move the process along."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:33
msgid "If you mark them as won, they will move to your *Won* column in your Kanban view. If you however mark them as *Lost* they will be archived."
msgstr ""
#: ../../content/applications/sales/crm/optimize.rst:5
msgid "Optimize your Day-to-Day work"
msgstr ""
#: ../../content/applications/sales/crm/optimize/gamification.rst:3
msgid "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 "Parter 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/google_spreadsheets.rst:3
msgid "How to use Google Spreadsheet in Addition to my Data?"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:5
msgid "Create custom dashboards in Google Spreadsheet that retrieves data directly from Odoo using spreadsheet formula. You can use it to create sales commission plans, budgets, project forecasts, etc. Formulas are written in Python but programming skills are not required."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:12
msgid "From the *General Settings*, activate *Google Drive* and *Google Spreadsheet*. The options *Authorization Code* and *Get Authorization Code* are now available."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1
msgid "Enable the Google Drive and Google Spreadsheet features in Odoo"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:19
msgid "Now, link your Google account with Odoo by following these steps:"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:21
msgid "Get Authorization Code"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:22
msgid "Select your Google account"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:23
msgid "Enter your password"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:24
msgid "Copy the code"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:25
msgid "Paste it into the Authorization Code field"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:28
msgid "Create a new Spreadsheet"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:30
msgid "From the *CRM* app, for example, go to *Favorites* and click on *Add to Google Spreadsheet*."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1
msgid "From the CRM application, for example, click on add to Google Spreadsheet in Odoo"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:36
msgid "A new spreadsheet will be automatically created in your Google Drive."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:39
msgid "When you opening this new file, a second sheet is created automatically by Odoo with a tutorial/documentation on *How to use Google Spreadsheet*."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:43
msgid "Link a Spreadsheet with Odoo"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:45
msgid "From this new file, configure your database."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:46
msgid "Go to :menuselection:`Odoo --> Server Settings --> Database Name --> Username --> Password`."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1
msgid "Menu called Odoo is shown on the settings bar in the Spreadsheet"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:53
msgid "Applications"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:55
msgid "You have two different formulas available when using Google Spreadsheet in Odoo: *retrieve data* and *retrieve grouped sums*."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:59
msgid "Google Drive limits the execution time of scripts; if the data you requested takes too long to be delivered, you might get an error. There is no specific size limit, since the time for Odoo to respond depends on several factors - although reading data regarding several thousand records is usually fine."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:66
msgid "Retrieve Data"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:70
msgid "The theoretical formula is :command:`= oe_browse (table;columns;filters;orderby:limit)`. Used it if you want to display the information without grouping it (e.g.: each sales order in the database)."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:71
msgid "Find some the arguments in the table below."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1
msgid "Table with examples of arguments to use in Odoo"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:78
msgid "Retrieve Grouped Sums"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:81
msgid "The theoretical formula is :command:`= oe_read_group (table;columns;group_by;filters;orderby:limit)`. Use it when you want to display a sum of data (e.g.: total invoiced)."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:82
msgid "Find some arguments in the table below."
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:-1
msgid "Table with examples of grouped sum arguments to use in Odoo"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:89
msgid "Other uses"
msgstr ""
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:91
msgid "Mix Odoo data with spreadsheet data, add traditional formulas, and create Dynamic Tabled and Graphs."
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:3
msgid "Check your Win/Loss Ratio"
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:5
msgid "To see how well you are doing with your pipeline, take a look at the Win/Loss ratio."
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:8
msgid "To access this report, go to your *Pipeline* view under the *Reporting* tab."
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:11
msgid "From there you can filter to which opportunities you wish to see, yours, the ones from your sales channel, your whole company, etc. You can then click on filter and check Won/Lost."
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:18
msgid "You can also change the *Measures* to *Total Revenue*."
msgstr ""
#: ../../content/applications/sales/crm/performance/win_loss.rst:23
msgid "You also have the ability to switch to a pie chart view."
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:47
msgid "You can use both `,` and `.` on your keyboard as decimal separators."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:48
msgid "**Cash** is selected by default if you enter the amount without choosing a payment method."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:53
msgid "Set customers"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:55
msgid "You can create and set customers from an :ref:`open POS session <pos/session-start>`. 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:61
msgid "To access the list of customers, click :guilabel:`Customer` on the POS interface. Then, select a customer or create a new one by clicking :guilabel:`Create`, completing the form, and saving. Lastly, click :guilabel:`Set Customer` to set the selected customer."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:68
msgid "Customer notes"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:70
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:74
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:78
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:84
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:93
msgid "Return and refund products"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:95
msgid "To return and refund a product,"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:97
msgid ":ref:`start a session <pos/session-start>` from the **POS dashboard**;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:98
msgid "click :guilabel:`Refund` and select the corresponding order;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:99
msgid "select the product and the quantity to refund using the keypad;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:100
msgid "click :guilabel:`Refund` to go back to the previous screen;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:101
msgid "once the order is completed, click :guilabel:`Payment` to proceed to the refund;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:102
msgid "click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next customer."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:105
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:107
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:114
msgid "Close the POS session"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:116
msgid "To close your session, click :guilabel:`Close` in the upper right corner of your screen; 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:120
msgid "the number of orders made and the total amount made during the session;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:121
msgid "the total of all the transactions made during the session grouped by payment method;"
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:122
msgid "the expected amounts grouped by payment method."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:124
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:134
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:138
msgid "You can let the session open by clicking :guilabel:`Keep Session Open` or abort and keep selling by clicking :guilabel:`Continue Selling`."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:140
msgid "Depending on your setup, you might not be allowed to close a session if the expected cash revenue does not equal the counted cash. To close the session, check :guilabel:`Accept payments difference and post a profit/loss journal entry`."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:145
msgid "It is strongly advised to close your POS session at the end of each day."
msgstr ""
#: ../../content/applications/sales/point_of_sale.rst:146
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`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:16
msgid "To access the settings of a specific point of sale, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Alternatively, from the Point of Sale dashboard, click the vertical ellipsis (:guilabel:`⋮`) button on a POS card, then on :guilabel:`Settings`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:21
msgid "Make products available"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration.rst:23
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 "Log in with employee"
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:5
msgid "With Odoo *Point of Sale*, you can manage multiple cashiers. This feature allows you to keep track of who is working, when and how much each cashier made for that session."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:9
msgid "There are three ways to switch cashiers in Odoo: by *selecting the cashier*, by *entering a PIN code* or by *scanning a barcode*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:13
msgid "To manage multiple cashiers, you need several employees (at least two)."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:18
msgid "Set up log in with employees"
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:20
msgid "To enable the feature, go to your *PoS settings* and check log in with employees on your *PoS form*. Then, add the employees that have access to the cash register."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:27
msgid "Now, you can switch cashier easily."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:30
msgid "Switch without pin codes"
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:32
msgid "The easiest way to switch cashiers is without a code. To do so, click on the cashier name in your PoS interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:38
msgid "Now, you just have to click on your name."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:46
msgid "Switch cashier with pin codes"
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:48
msgid "You can set a pin code on each cashier. To set up a pin code, go to the employee form and add a security PIN, in the *HR settings tab*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:54
msgid "Now, when switching cashier, a PIN password will be asked."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:62
msgid "Switch cashier with barcodes"
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:64
msgid "You can ask your employees to log themselves with their badges. To do so, set up a barcode at the same place you add the PIN code. Print the badge and when they will scan it, the cashier will be switched to that employee."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:73
msgid "Find who was the cashier"
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:75
msgid "Once you have closed your *PoS session*, you can have an overview of the amount each cashier sold for. To do so, go to the orders menu."
msgstr ""
#: ../../content/applications/sales/point_of_sale/employee_login.rst:81
msgid "Now, you can open the order and have a summary of the sold products."
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 --> Create`, 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:`Vantiv configuration <terminals/vantiv>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25
msgid ":doc:`Worldline configuration <terminals/worldline>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:27
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/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/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
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
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/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, you’ll find the type of card that has been used and the transaction ID."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/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 "Starting in July 2022, it will **not** be possible anymore to connect and use a Six payment terminal in PoS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:11
msgid "Even though Worldline has recently acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are therefore not compatible with this integration."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20
msgid "Configure the Payment Method"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:21
msgid "First, make sure that the :guilabel:`POS Six` module is installed. For this, go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for *POS Six*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1
msgid "The POS Six module."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:28
msgid "Back in :menuselection:`Point of Sale --> Configuration --> Payment Methods`, click :guilabel:`Create` to create a new payment method for SIX, select the payment terminal option :guilabel:`SIX`, and enter the payment terminal IP address."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1
msgid "Create a new payment method for the SIX payment terminal."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37
#: ../../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/six.rst:39
msgid "In the :abbr:`PoS (Point of Sale)` interface, at the moment of the payment, select a payment method using a payment terminal. Verify that the amount in the tendered column is the one that has to be sent to the payment terminal and click on :guilabel:`Send`. To cancel the payment request, click on :guilabel:`Cancel`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1
msgid "The PoS interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:48
msgid "When the payment is done, the status will change to :guilabel:`Payment Successful`. If needed, reverse the last transaction by clicking on :guilabel:`Reverse`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1
msgid "The Reverse button on the PoS interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55
msgid "If there is any issue with the payment terminal, you can still force the payment using the :guilabel:`Force Done` button. This will allow you to validate the order in Odoo even if there are connection issues between the payment terminal and Odoo."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:3
msgid "Vantiv"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:5
msgid "Connecting a Vantiv payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:9
msgid "Please note MercuryPay only operates with US and Canadian banks, making this procedure only suitable for North American businesses."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13
msgid "Vantiv card readers should be purchased exclusively from Vantiv, as certain Vantiv terminals bought on Amazon do not include the correct encryption needed to be used with an Odoo database."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22
msgid "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:46
msgid "In your PoS interface, at the moment of the payment, select your Vantiv payment method and… that’s 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 Box’s 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: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/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 "Tax rates (fiscal positions)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:5
msgid "In Odoo, *Fiscal Positions* let you apply different taxes based on the customer location. In a *Point of Sale*, such as a restaurant, it can be used to apply different taxes depending if the customer eats in or takes away."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:11
msgid "Set up fiscal positions for PoS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:13
msgid "To enable this feature, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and check *Fiscal Position per Order*. Now, you can choose the fiscal positions you want for your *PoS*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:21
msgid "You need to create your fiscal positions before using this feature."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:24
msgid "Using fiscal positions"
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:26
msgid "Once on your *PoS* interface, click on the *Tax* button. Now, choose the fiscal position you need for the current order."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:33
msgid "Set up a default fiscal position"
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:35
msgid "If you want to use a default fiscal position, meaning that a preexisting value is always automatically assigned, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and enable *Fiscal Position*. Now, choose one to set as the default one."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:43
msgid "Now, the *tax* button is replaced by a *on site* button when on the *PoS* interface."
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
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:`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 <multi_website/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:`Create` 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
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
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>` to set its :guilabel:`Default Pricelist`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:112
msgid "To be able to choose between different pricelists during a POS session, enable :guilabel:`Advanced Pricelists` and add all the desired pricelists using the :guilabel:`Available` field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:116
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:123
msgid "Multiple pricelists must be selected for the **pricelist button** to be displayed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:124
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:128
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:133
msgid ":doc:`../../sales/products_prices/prices/pricing`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:134
msgid ":ref:`How to use pricelists in a multi-website environment <multi_website/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 "Some of your customers might request an invoice when buying from your Point of Sale, you can easily manage it directly from the PoS interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46
msgid "Activate invoicing"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:48
msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select your Point of Sale:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:53
msgid "Under the *Bills & Receipts* you will see the invoicing option, tick it. Don't forget to choose in which journal the invoices should be created."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:60
msgid "Select a customer"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:62
msgid "From your session interface, use the customer button"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:66
msgid "You can then either select an existing customer and set it as your customer or create a new one by using this button."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:71
msgid "You will be invited to fill out the customer form with its information."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:74
msgid "Invoice your customer"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:76
msgid "From the payment screen, you now have an invoice option, use the button to select it and validate."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81
msgid "You can then print the invoice and move on to your next order."
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:84
msgid "Retrieve invoices"
msgstr ""
#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:86
msgid "Once out of the PoS interface (:menuselection:`Close --> Confirm` on the top right corner) you will find all your orders in :menuselection:`Point of Sale --> Orders --> Orders` and under the status tab you will see which ones have been invoiced. When clicking on a order you can then access the invoice."
msgstr ""
#: ../../content/applications/sales/point_of_sale/reporting.rst:3
#: ../../content/applications/sales/subscriptions/reporting.rst:5
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 activate the features, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, and click :menuselection:`Edit --> Is a Bar/Restaurant --> Save`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant.rst:26
msgid "These specific features can be identified by the cutlery-shaped icon located to the right of the feature name."
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 bill printing and splitting features, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your POS. Then, scroll down to the :guilabel:`Bills & Receipts` section and enable :guilabel:`Bill Printing` and :guilabel:`Bill Splitting`."
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 "Don’t 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 "To ease the workflow between the front of house and the back of the house, printing the orders taken on the PoS interface right in the kitchen or bar can be a tremendous help."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10
msgid "Activate the bar/kitchen printer"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:12
msgid "To activate the *Order printing* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:16
msgid "Under the IoT Box / Hardware Proxy category, you will find *Order Printers*. Note that you need an IoT Box to connect your Printer to the PoS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:20
msgid "Add a printer"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:22
msgid "In your configuration menu you will now have a *Order Printers* option where you can add the printer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:29
msgid "Print a kitchen/bar order"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:34
msgid "Select or create a printer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:37
msgid "Print the order in the kitchen/bar"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:39
msgid "On your PoS interface, you now have a *Order* button."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44
msgid "When you press it, it will print the order on your kitchen/bar printer."
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 "As it is customary to tip in many countries all over the world, it is important to have the option in your PoS interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:9
msgid "Configure Tipping"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11
msgid "To activate the *Tips* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:14
msgid "Under the Bills & Receipts category, you will find *Tips*. Select it and create a *Tip Product* such as *Tips* in this case."
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:21
msgid "Add Tips to the bill"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:23
msgid "Once on the payment interface, you now have a new *Tip* button"
msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:28
msgid "Add the tip your customer wants to leave and process to the 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<../../../inventory_and_mrp/inventory/barcode/setup/hardware>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22
msgid ":doc:`Activate barcode scanners<../../../inventory_and_mrp/inventory/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 <restrict-employee-pos>` to the POS and :ref:`use barcodes to log your employees in <employee-barcode>` 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/management/lots_serial_numbers/serial_numbers`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:60
msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`"
msgstr ""
#: ../../content/applications/sales/rental.rst:3
msgid "Rental"
msgstr ""
#: ../../content/applications/sales/rental.rst:5
msgid "**Odoo Rental** is a comprehensive solution to manage your rentals."
msgstr ""
#: ../../content/applications/sales/rental.rst:7
msgid "From a single view, you can send out quotations, confirm orders, schedule rentals, register when products are picked up and returned, and invoice your customers."
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 "Rental Pricing"
msgstr ""
#: ../../content/applications/sales/rental.rst:22
msgid "Go to :menuselection:`Rental --> Products`, select or create a product, and click on the product's *Rental* tab. Under *Rental Pricing*, click on *Add a price*. Then choose a *Unit* of time (hours, days, weeks, or months), a *Duration*, and a *Price*. You can add as many price lines as necessary, usually to give out discounts for longer rental durations."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "Example of rental pricing configuration in Odoo Rental"
msgstr ""
#: ../../content/applications/sales/rental.rst:32
msgid "Under *Reservations*, you can add fines for any *Extra Hour* or *Extra Day*. You can also set a *Security Time*, expressed in hours, to make the product temporarily unavailable between two rental orders."
msgstr ""
#: ../../content/applications/sales/rental.rst:37
msgid "If you want to rent a product created outside of the Rental app, do not forget to tick *Can be Rented* under the product's name. By default, this option is ticked when you create a product directly from the Rental app."
msgstr ""
#: ../../content/applications/sales/rental.rst:42
msgid "Computing"
msgstr ""
#: ../../content/applications/sales/rental.rst:44
msgid "Odoo always uses two rules to compute the price of a product when you create a rental order:"
msgstr ""
#: ../../content/applications/sales/rental.rst:46
msgid "Only one price line is used."
msgstr ""
#: ../../content/applications/sales/rental.rst:47
msgid "The cheapest line is selected."
msgstr ""
#: ../../content/applications/sales/rental.rst:50
msgid "Consider the following rental pricing configuration for a product:"
msgstr ""
#: ../../content/applications/sales/rental.rst:52
msgid "1 day: $100"
msgstr ""
#: ../../content/applications/sales/rental.rst:53
msgid "3 days: $250"
msgstr ""
#: ../../content/applications/sales/rental.rst:54
msgid "1 week: $500"
msgstr ""
#: ../../content/applications/sales/rental.rst:56
msgid "A customer wants to rent this product for eight days. What price will they pay?"
msgstr ""
#: ../../content/applications/sales/rental.rst:58
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:64
msgid "Customer signature"
msgstr ""
#: ../../content/applications/sales/rental.rst:66
msgid "You can ask your customers to sign a rental agreement outlining the arrangement between you and your customers before they pick up products to make sure your products are returned on time and in their original condition. To do so, go to :menuselection:`Rental --> Configuration --> Settings`, activate *Digital Documents*, and *Save*."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "Digital Documents settings in Odoo Rental"
msgstr ""
#: ../../content/applications/sales/rental.rst:76
msgid "This feature requires the :doc:`Sign <../finance/sign>` app. If necessary, Odoo installs it after activating *Digital Documents*."
msgstr ""
#: ../../content/applications/sales/rental.rst:79
msgid "Once the app settings are saved, you have the option to change the default *Rental Agreement* from the dropdown menu. You can pick any document already uploaded to the *Sign* app, or upload a new one to the *Sign* app by clicking on *Upload Template*."
msgstr ""
#: ../../content/applications/sales/rental.rst:83
msgid "To request a customer signature, select a confirmed rental order, click on *Sign Documents*, choose the document template and click on *Sign Documents* again. On the next window, select your customer and click on *Sign Now* to start the signing process with your customer. Once the document is completed, click on *Validate & Send Completed Document*."
msgstr ""
#: ../../content/applications/sales/rental.rst:89
msgid "`Odoo Tutorials: Sign <https://www.odoo.com/slides/sign-61>`_"
msgstr ""
#: ../../content/applications/sales/rental.rst:94
msgid "Pickup and Return receipt"
msgstr ""
#: ../../content/applications/sales/rental.rst:96
msgid "You can print and give your customers receipts when they pick up and/or return products. To do so, open any rental order, click on *Print* and select *Pickup and Return Receipt*. Odoo then generates a PDF detailing all information about the current status of the rented items: which were picked up, when they are expected to be returned, which were returned, and potential rental delay costs."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "Printing a Pickup and Return receipt in Odoo Rental"
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 the orders between Amazon and your Odoo database, which reduces considerably the amount of time spent on your Amazon Seller Central dashboard, making your daily routine a lot easier."
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 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 "the product’s name, description and quantity"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:18
msgid "the shipping costs for the product"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:19
msgid "the gift wrapping charges"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:21
msgid "Create on Odoo any missing partner related to an order (contact types supported: contact and delivery)."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:23
msgid "Notify Amazon of a shipping confirmed on Odoo (FBM) in order to get paid."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:25
msgid "Support multiple seller accounts."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:26
msgid "Support multiple marketplaces per seller account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:29
msgid "Fulfilled By Amazon (FBA)"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:29
msgid "Fulfilled By Merchant (FBM)"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:31
msgid "**Orders**"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:31
msgid "Synchronize shipped and canceled orders"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:31
msgid "Synchronize unshipped and canceled orders"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:34
msgid "**Shipping**"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:34
msgid "Charges"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:35
msgid "Delivery created"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:37
msgid "**Gift Wrapping**"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:37
#: ../../content/applications/sales/sales/amazon_connector/features.rst:43
msgid "Handled by Amazon"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:37
msgid "Gift wrapping charges"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:38
msgid "Gift message"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:40
msgid "**Stock Management**"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:40
msgid "One stock move created per sales order item"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:40
msgid "Handled by the delivery"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:43
msgid "**Confirmation**"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:43
msgid "Notify Amazon when confirming delivery"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:48
msgid "The connector is designed to synchronize orders' data as detailed above. Other actions, such as downloading monthly fees reports, handling disputes, or issuing refunds must be managed from Amazon Seller Central, as usual."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:55
msgid "Supported Marketplaces"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:57
msgid "The Amazon Connector currently supports 9 marketplaces. If a marketplace is not listed below, it may be possible for you to :ref:`add it as an unsupported marketplace <amazon/add-unsupported-marketplace>`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:62
msgid "**North America region**"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:64
msgid "Canada"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:64
msgid "Amazon.ca"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:66
msgid "Mexico"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:66
msgid "Amazon.com.mx"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:68
msgid "US"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:68
msgid "Amazon.com"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:72
msgid "**Europe region**"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:74
msgid "Germany"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:74
msgid "Amazon.de"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:76
msgid "Spain"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:76
msgid "Amazon.es"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:78
msgid "France"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:78
msgid "Amazon.fr"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:80
msgid "UK"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:80
msgid "Amazon.co.uk"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:82
msgid "Italy"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:82
msgid "Amazon.it"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:84
msgid "Netherlands"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:84
msgid "Amazon.nl"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:88
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:132
#: ../../content/applications/sales/sales/amazon_connector/update.rst:59
msgid ":doc:`setup`"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/features.rst:89
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:119
#: ../../content/applications/sales/sales/amazon_connector/update.rst:60
msgid ":doc:`manage`"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:3
msgid "Manage Amazon orders in Odoo"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:6
msgid "Synchronization of orders"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:8
msgid "Orders are automatically fetched from Amazon and synchronized in Odoo at regular intervals. The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and **Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the same is done for **Unshipped** and **Canceled** orders. For each synchronized order, a sales order and a customer are created in Odoo if they are not yet registered."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:15
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:19
msgid "To force the synchronization of an order whose status has not changed since the last synchronization, activate the :ref:`developer mode <developer-mode>`, navigate to your Amazon account and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior to the last status change of the order that you wish to synchronize and save."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:25
msgid "To synchronize immediately the orders of your Amazon account switch to :ref:`developer mode <developer-mode>`, head to your Amazon account and click on **SYNC ORDERS**. The same can be done with pickings by clicking on **SYNC PICKINGS**."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:30
msgid "Manage deliveries in FBM"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:32
msgid "When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a picking is created along with the sales order and the customer. You can either ship all the ordered products to your customer at once or ship products partially by using backorders."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:36
msgid "When a picking related to the order is confirmed, a notification is sent to Amazon who will, in turn, notify the customer that the order (or a part of it) is on its way."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:40
msgid "Amazon requires to provide a tracking reference with each delivery. You'll need to assign a carrier. If the carrier doesn't automatically provide a tracking reference, you'll need to set one manually. This concerns all marketplaces."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:45
msgid "If your chosen carrier isn't one supported by Odoo, you can still create a carrier bearing its name (e.g. create a carrier named `Colissimo`). This name is case insensitive, but be careful about typos, as Amazon won't recognize them."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:48
msgid "Create a delivery carrier named `Self Delivery` to inform Amazon that you make your own deliveries. You still have to enter a tracking reference."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:50
msgid "Keep in mind that the customer is notified by email about the delivery, and the carrier and tracking reference are displayed in the email to the customer."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:54
msgid ":doc:`../../../inventory_and_mrp/inventory/shipping/setup/third_party_shipper`"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:57
msgid "Follow deliveries in FBA"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:59
msgid "When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded for each sales order item so that it is saved in your system. Inventory managers can find such moves in :menuselection:`Inventory --> Reporting --> Product Moves`. They pick up products in a specific inventory location called **Amazon**. This location represents your stock in Amazon's warehouses and allows you to manage the stock of your products under the FBA program."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:66
msgid "To follow your Amazon (FBA) stock in Odoo, you can make an inventory adjustment after replenishing it. You can also trigger an automated replenishment from reordering rules on the Amazon location."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:71
msgid "The Amazon location is configurable by Amazon account managed in Odoo. All accounts of the same company use the same location by default. It is however possible to follow the stock by marketplace. First, remove the marketplace for which you want to follow the stock separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another stock location to the second registration of your account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:79
msgid "Issue invoices and register payments"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:82
msgid "Issue invoices"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:84
msgid "Sending invoices to Amazon customers directly from Odoo is not feasible due to Amazon's policy of not sharing customer email addresses. Instead, it is possible to manually upload the invoices generated on Odoo to the Amazon backend."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:88
msgid "In addition, for your B2B clients, it is currently required to manually retrieve VAT numbers from the Amazon backend before creating the invoice in Odoo."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:92
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. (decommissioning TaxCloud integration in Odoo 17+)"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:97
msgid "Register payments"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:99
msgid "As customers pay Amazon as an intermediary, creating a dedicated *Bank* journal (for example, named `Amazon payments`) with a dedicated *Bank and Cash* intermediary account is recommended."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:102
msgid "In addition, as Amazon makes a single monthly payment, selecting all the invoices linked to a single payment is necessary when registering payments. Use the dedicated `Amazon payments` :guilabel:`Journal` and select :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`. Then, select all the payments generated and click :menuselection:`Actions --> Create batch payment --> Validate`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:109
msgid "The same can be done with vendor bills from Amazon dedicated to commissions. When the balance is received in the bank account at the end of the month and the banks statements are recorded, credit the Amazon intermediary account by the amount received."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:114
msgid "Follow your Amazon sales in sales reporting"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:116
msgid "As a sales team is set on your account under the tab **Order Follow-up**, this helps you give quick glances at the figures in just a few clicks in Sales reporting. By default, your account's sales team is shared between all of your company's accounts."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:120
msgid "If you wish, you can change the sales team on your account for another to perform a separate reporting for the sales of this account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:124
msgid "It is also possible to perform reporting on a per-marketplace basis in a similar fashion. First, remove the marketplace you wish to track separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another sales team to one of the two registrations of your account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:131
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:118
#: ../../content/applications/sales/sales/amazon_connector/update.rst:58
msgid ":doc:`features`"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:3
msgid "Configure Amazon Connector in Odoo"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:6
msgid "Register your Amazon account in Odoo"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:10
msgid "To register your seller account in Odoo, navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts` and click on :guilabel:`CREATE`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:13
msgid "Choose a meaningful name for your account (e.g. `Europe`), and select your :guilabel:`Sign-up Marketplace`. This is the original sign-up marketplace of your seller account (e.g. if you created your account on Amazon Germany, your sign-up marketplace will be `amazon.de`)"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:17
msgid "Upon saving, a button to :guilabel:`link with Amazon` appears. Click on it to be redirected to the Amazon login page, or directly to the consent page if you are already logged in. There, confirm that you want Amazon to give Odoo access to your account and related data."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:21
msgid "Amazon redirects you to Odoo, with your account registered."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:23
msgid "Once the account is registered, the marketplaces available to this account are synchronized and listed under the :guilabel:`Marketplaces` tab. If you wish, you can remove some items from the list of synchronized marketplaces to disable their synchronization."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:28
msgid "Match database products in Amazon"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:30
msgid "When an Amazon order is synchronized, up to three sales order items are created in Odoo for each product sold on Amazon: one for the marketplace product, 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:36
msgid "The selection of a database product for a sales order item is done by matching its **internal reference** with the **SKU** for marketplace items, the **shipping code** for delivery charges, and the **gift wrapping** code for gift wrapping charges."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:40
msgid "For marketplace products, pairings are saved as **Amazon Offers** which are listed under the **Offers** stat button on the account form. Offers are automatically created when the pairing is established and are 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:46
msgid "It is possible to force the pairing of a marketplace item with a specific product by changing either the product or the SKU of an offer. The offer can be manually created if it was not automatically done yet. This is useful if you do not use the internal reference as the SKU or if you sell the product under different conditions."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:51
msgid "If no database product with a matching internal reference is found for a given SKU or gift wrapping code, a default database product **Amazon Sale** is used. The same is done with the default product **Amazon Shipping** and the shipping code."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:56
msgid "To modify the default products, activate the :ref:`developer mode <developer-mode>` and navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Default Products`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:61
msgid "Configure taxes of products"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:63
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. Make sure to have set the correct taxes on your products in Odoo or to have it done by a fiscal position, to avoid discrepancies in the subtotals between Seller Central and Odoo."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:69
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 from that on 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:76
msgid "Add an unsupported marketplace"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:78
msgid "Some Amazon Marketplaces, such as Amazon Brazil, are not created by default as they are not officially supported by Odoo but might be compatible with your seller account. These marketplaces can be added manually should you wish to use them. See :ref:`here <amazon/supported-marketplaces>` for the exhaustive list of natively supported marketplaces."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:84
msgid "To find out if a marketplace is eventually compatible, check the `Amazon Documentation <https://developer-docs.amazon.com/amazon-shipping/docs/seller-central-urls>`_. The marketplace must belong to the same region as that of your seller account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:88
msgid "To add a new marketplace, activate the :ref:`developer mode <developer-mode>`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:90
msgid "Once that is done, go to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Marketplaces`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:93
msgid "From there, create a new marketplace record. Enter the Marketplace ID and select the Amazon Region for your marketplace as described in the `Amazon Documentation for marketplace IDs <https://developer-docs.amazon.com/amazon-shipping/docs/marketplace-ids>`_, and the 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:99
msgid "Set the 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 *MarketplaceId*, the selected Amazon region and the *Seller Central URL* values from the Amazon Documentation."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:104
msgid "Once the marketplace is saved, update the Amazon Account configuration by going to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`. Open the account on which you wish 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 your seller account."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/setup.rst:113
msgid "As manually added marketplaces are not officially supported by Odoo, there is no guarantee that adding one as described above will work, nor can this be considered as a bug when contacting Odoo Support."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:3
msgid "Install the Amazon Selling Partner API Update"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:5
msgid "Starting July 2022, due to a change in Amazon's API, the Amazon Connector needs to be updated to continue to exchange information with Amazon. This also makes it easier for you to set up the Connector."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:10
msgid "If your Odoo database is created after the update was released, the update module is installed automatically. To check if this module is already installed, go to :guilabel:`Apps`, remove the ``Apps`` filter and search for ``Amazon``. If the module :guilabel:`Amazon/Selling Partner API Patch` is present and marked as installed, your Odoo database is already up-to-date and you can proceed with the :doc:`setup <setup>` step of the Amazon Connector."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:17
msgid "Update Odoo to the latest release"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:19
msgid "The new authentication mechanism is made available through a new Odoo module; to be able to install it, you must make sure that your Odoo source code is up-to-date."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:22
msgid "If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-date and you can proceed to the next step."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:25
msgid "If you use Odoo with an on-premise setup or through a partner, then you must update your installation as detailed in :doc:`this documentation page </administration/maintain/update>` or by contacting your integrating partner."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:31
msgid "Update the list of available modules"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:33
msgid "New modules must be *discovered* by your Odoo instance to be available in the **Apps** menu."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:36
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/amazon_connector/update.rst:40
msgid "Install the Amazon/Selling Partner API Patch"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:43
msgid "You should never install new modules in your production database without first 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, you should use a staging or duplicate database. For on-premise users, you should use a staging environment---contact your integrating partner for more information regarding how to test a new module in your particular setup."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:49
msgid "The module should now be available in your :guilabel:`Apps` menu. Remove the ``Apps`` filter and search for ``Amazon``; the module :guilabel:`Amazon/Selling Partner API Patch` should be available for installation. If you cannot find the module after having updated the list of available modules, it means your Odoo source code is not up-to-date; refer to step one of this page."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/update.rst:54
msgid "Once the module is installed, link your Amazon account by following the instructions on the :doc:`setup <setup>` page."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector.rst:5
msgid "eBay Connector"
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:6
msgid "Listing without variation"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:8
msgid "In order to list a product, you need to check the **use eBay** field on a product form. The eBay tab will be available."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:14
msgid "When the **Use Stock Quantity** field is checked, the quantity sets on eBay will be the Odoo **Forecast Quantity**."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:17
msgid "The **Description Template** allows you to use templates for your listings. The default template only use the **eBay Description** field of the product. You can use html inside the **Description Template** and in the **eBay Description**."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:21
msgid "To use pictures in your listing, you need to add them as **Attachments** on the product template."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:24
msgid "Listing with variations"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:26
msgid "When the **use eBay** on a product with variations is checked and with **Fixed Price** as **Listing Type**, the eBay form is slightly different. In the variants array, you can choose which variant will be listed on eBay as well as set the price and the quantity for each variant."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:35
msgid "Listing with item specifics"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:37
msgid "In order to add item specifics, you should create a product attribute with one value in the **Variants** tab on the product form."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:44
msgid "Product Identifiers"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:46
msgid "Products identifiers such as EAN, UPC, Brand or MPN are required in most of the eBay category. The module manages the EAN and UPC identifiers with the **Barcode** field of the product variant. If the **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. The Brand and MPN values are working as item specifics and should be define in the **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/setup.rst:3
msgid "How to configure eBay in Odoo?"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:6
msgid "Create eBay tokens"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:8
msgid "In order to create your tokens, you need to create a developer account on the `developer portal <https://go.developer.ebay.com/>`_. Once you are logged in, you can create **Sandbox Keys** and **Production Keys** by clicking on the adequate buttons."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:16
msgid "After the creation of the keys, you can get the user token. To do so, click on the **Get a User Token** link in the bottom of the page. Go through the form, log in with you eBay account and you will get the keys and token needed to configure the module in Odoo."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:22
msgid "Set up tokens in Odoo?"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:24
msgid "To set up the eBay integration, go to :menuselection:`Sales --> Configuration --> Settings`."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:29
msgid "First choose if you want to use the production or the sandbox eBay Site. Then fill in the fields **Developer Key**, **Token**, **App Key**, **Cert Key**. Apply the changes."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:33
msgid "Once the page is reloaded, you need to synchronize information from eBay. Push on **Sync countries and currencies**, then you can fill in all the other fields."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:36
msgid "When all the fields are filled in, you can synchronize the categories and the policies by clicking on the adequate buttons."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:40
msgid "Accept account deletion notifications"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:42
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/setup.rst:46
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/setup.rst:51
msgid "Make sure to correctly :ref:`set up your 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/setup.rst:58
msgid "Retrieve endpoint details from Odoo"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:60
msgid "The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`. Click on *Generate Token* to retrieve your **Verification Token**."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1
msgid "Button to generate an eBay verification token in Odoo"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:70
msgid "Subscribe to account deletion notifications"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:72
msgid "Log in on the `developer portal of eBay <https://go.developer.ebay.com/>`_ and go to **Alerts & Notifications**."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1
msgid "Overview of the Alerts & Notifications dashboard of eBay"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:79
msgid "To subscribe to deletion/closure notifications, eBay needs a few details:"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:81
msgid "An **email address** to send notifications to if the endpoint is unreachable."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:82
msgid "The **endpoint details**:"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:84
msgid "The URL to Odoo's account deletion notification endpoint"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:85
msgid "A verification token"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1
msgid "Dedicated fields to enter the endpoint details"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:92
msgid "You can edit the last two fields once the email address field is filled out."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:95
msgid "Verify the connectivity with the endpoint"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:97
msgid "After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity with the **Send Test Notification** button."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:100
msgid "You should get the following confirmation message: \"A test notification was sent successfully!\""
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1
msgid "Button to send test notification"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:107
msgid "Using the updated synchronisation method"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:109
msgid "If you have a lot of products, the eBay API can sometimes refuse some synchronization calls due to a time-based limit on the number of requests that eBay enforces."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:112
msgid "To fix this issue, a new implementation mechanism has been developed; however this updated mechanism is disabled by default to avoid having the 2 systems running in parallel in existing installations."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:116
msgid "To switch to the new synchronization mechanism:"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118
msgid "Activate the :ref:`developer mode <developer-mode>`."
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:119
msgid "Go to :menuselection:`Settings --> Technical --> Scheduled Actions`"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:120
msgid "Archive the old synchronization actions (both are named *Ebay: update product status*)"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:121
msgid "Activate the new synchronization actions (*Ebay: get new orders* which runs every 15min by default and *Ebay: synchronise stock (for 'get new orders' synchronisation)* which runs once a day per default)"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:124
msgid "Ensure that the **Next Execution Date** for both these actions are in the near future"
msgstr ""
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:126
msgid "Starting with the next execution date, the new method will be used instead of the old one."
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 "Initial down payment request"
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:20
msgid "Invoices are automatically created in drafts, so they can be reviewed before validation."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:22
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:27
msgid ":guilabel:`Regular invoice`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27
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:29
msgid ":guilabel:`Down payment (percentage)`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30
msgid ":guilabel:`Down payment (fixed amount)`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:32
msgid "In terms of a down payment, it can either be a fixed amount or a percentage of the total amount."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:34
msgid "Once the desired down payment option is selected in the :guilabel:`Create Invoice` field, designate the desired amount (either as a percentage or fixed amount) in the :guilabel:`Down Payment Amount` field."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:38
msgid "Then, select the appropriate income account for the invoice in the :guilabel:`Income Account` field, and add a tax amount, if necessary, in the :guilabel:`Customer Taxes` field. These settings will be reused for future down payments."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How to configure a down payment on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:47
msgid "When a down payment is first requested, a new product called :guilabel:`Down payment` is created. This product is registered as a :guilabel:`Service` product, with an invoicing policy of :guilabel:`Ordered quantities`. This product can be edited and modified at any time."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:52
msgid "If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an invoice will **not** be able to be created."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56
msgid "Request a 50% down payment"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:58
msgid "For the following example, the flow involves a 50% amount down payment on a product with :guilabel:`Ordered quantities` as the invoicing policy."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:62
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:184
msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:64
msgid "When the order is confirmed (via the :guilabel:`Confirm` button), it's time to create/view the invoice, by clicking :guilabel:`Create Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:67
msgid "Then, 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. Lastly, click :guilabel:`Create and View Invoice` to create and view the invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "Create invoices pop up window in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:75
msgid "Doing so reveals the draft invoice, which mentions the down payment."
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:81
msgid "From there, the invoice can be confirmed/posted, and the payment can be registered. Return to the sales order, via the breadcrumbs."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:84
msgid "On the sales order, the option to view what the customer will see is available, via the :guilabel:`Customer Preview` smart button, and the :guilabel:`Invoice` button reveals the drafted invoice. In either case, the down payment is mentioned on both the sales order and draft invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How the down payment is mentioned on the sales order in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:92
msgid "To confirm and register the first payment of the down payment, click the :guilabel:`Invoices` smart button to return to the invoice. On the :guilabel:`Customer Invoice` page, click :guilabel:`Confirm`, then :guilabel:`Register Payment` to open a :guilabel:`Register Payment` pop-up form."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How the register payment pop up looks in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:101
msgid "On this form, select the appropriate :guilabel:`Journal` and confirm that the down payment amount is correct in the :guilabel:`Amount` field. Then, make any other modifications to the other fields, if necessary, before clicking :guilabel:`Create Payment`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105
msgid "Odoo returns to the invoice, which now has a green :guilabel:`In Payment` banner visible in the upper-right corner."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "How the initial down payment invoice has a green paid banner in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112
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, and click :guilabel:`Create Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:115
msgid "On the :guilabel:`Create invoices` pop-up window, there is now an option to :guilabel:`Deduct down payments`, which is selected by default."
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:122
msgid "If the remaining amount is ready to be paid, the :guilabel:`Regular Invoice` option should be selected, and the :guilabel:`Deduct down payments` option should *stay* selected. Then, click :guilabel:`Create and View Invoice`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126
msgid "Doing so reveals a separate :guilabel:`Invoices` page, listing all the invoices for that specific sales order. Each invoice line item displays all the necessary information related to each invoice, along with the current :guilabel:`Payment Status`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1
msgid "The down payment invoices page in Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:134
msgid "To complete the flow, select the invoice with the :guilabel:`Not Paid` status, which opens that invoice. On the invoice page, click :guilabel:`Confirm`, then :guilabel:`Register Payment`, and confirm that the remaining :guilabel:`Amount` is correct. Then, click :guilabel:`Create Payment`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:138
msgid "That pop-up window disappears, and a green :guilabel:`In Payment` banner is now present on the invoice. The line items on the invoice show that the total amount has been paid, including mentions of the down payment, and the flow is complete."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:142
msgid "This flow is also possible with the :guilabel:`Fixed amount` down payment option."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:145
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. 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:150
msgid "If nothing has been delivered, a :guilabel:`Credit Note` is created, which cancels the draft invoice that was created after the down payment. 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:156
msgid "Income account and customer taxes modifications"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158
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:162
msgid "On the :guilabel:`Down Payment` product page, click :guilabel:`Edit`, then scroll down to the :guilabel:`General Information` tab. In this 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:170
msgid "To change or adjust the income account attached to the :guilabel:`Down Payment` product page, the *Accounting* app **must** be installed. 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:175
msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, in the :guilabel:`Receivables` section. Once all desired changes are complete, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:3
msgid "Re-invoice expenses to customers"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:5
msgid "It often happens that your employees have to spend their personal money while working on a project for your client. Let's take the example of a consultant paying for a hotel to work on the site of your client. As a company, you would like to be able to invoice that expense to your client."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:12
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:64
msgid "Expenses configuration"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:14
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:66
msgid "To track & invoice expenses, you will need the expenses app. Go to :menuselection:`Apps --> Expenses` to install it."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:17
msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Invoicing --> Configuration --> Settings` and activate *Analytic Accounting*."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:22
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:74
msgid "Add expenses to your sales order"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:24
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:76
msgid "From the expense app, you or your consultant can create a new one, e.g. the hotel for the first week on the site of your customer."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:27
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:79
msgid "You can then enter a relevant description and select an existing product or create a new one from right there."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:33
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:85
msgid "Here, we are creating a *Hotel* product:"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:38
msgid "Under the invoicing tab, select *Delivered quantities* and either *At cost* or *Sales price* as well depending if you want to invoice the cost of your expense or a previously agreed on sales price."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:45
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:97
msgid "To modify or create more products go to :menuselection:`Expenses --> Configuration --> Expense products`."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:48
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:100
msgid "Back on the expense, add the original sale order in the expense to submit."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:54
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:106
msgid "It can then be submitted to the manager, approved and finally posted."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/expense.rst:65
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:117
msgid "It will then be in the sales order and ready to be invoiced."
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 **default mode** in Odoo Sales, which means that customers will be invoiced once the sales order is confirmed."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:10
msgid "The **Invoice what is delivered** rule will invoice customers once the delivery is done. This rule concerns businesses that sell materials, liquids or food in large quantities. In these cases, the quantity might diverge a little bit and it is, therefore, preferable to invoice the quantity actually delivered."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:15
msgid "Being able to have different invoicing options allow you more flexibility. Indeed, you need to know exactly how to invoice your customers for different situations."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:19
msgid "Activate these features"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:21
msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and under **Invoicing policy** choose the rule you want to apply."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:-1
msgid "How to choose your invoicing policy on Odoo Sales?"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:30
msgid "If you decide to choose the **Invoice what is delivered** rule, you will not be able to activate the feature called **Automatic invoice**, which automatically generates invoices when the online payment is confirmed."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:35
msgid "Choose an invoicing policy on a product form"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:37
msgid "From any product page, under the **Sales tab**, you will find the invoicing policy, which can be manually changed."
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:46
msgid "Impact on sales flow"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:48
msgid "On Odoo Sales, the basic sales flow will be to create a quotation, send it to your customer, wait for confirmation, confirm the sales order and create an invoice."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:51
msgid "**Invoice what is ordered**: No impact on this basic sales flow. Indeed, you can invoice as soon as the sale is confirmed."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:54
msgid "**Invoice what is delivered**: Small impact on sales flow because you will have to manually enter the delivered quantity on the sales order or to install the **Inventory App** to confirm the delivered quantity before creating an invoice, with the **Sales App**. Indeed, if you try to create an invoice without validating the delivered quantity, you will receive an error message as below."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:0
msgid "How the choice of your invoicing policy impacts your sales flow on Odoo Sales?"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:65
msgid "Once the quotation is confirmed and that the status went from **Quotation sent** to **Sales order**, you are able to see your delivered and invoiced quantities directly from your sales order (it is true for both rules)."
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:74
msgid "Odoo will automatically add the quantities to the invoice (even if it is a partial delivery)."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:76
msgid "Finally, to create an invoice, you will have different possibilities: regular invoice or down payment (percentage or fixed amount)."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:80
msgid "Be sure to check out our documentation about down payment here: :doc:`down_payment`, to master this incredible feature."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:3
msgid "Invoice project milestones"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:5
msgid "Milestone invoicing can be used for expensive or large-scale projects, with each milestone representing a clear sequence of work that will incrementally build up to the completion of the contract. This invoicing method is comfortable both for the company which is ensured to get a steady cash flow throughout the project lifetime and for the client who can monitor the project's progress and pay in several installments."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:13
msgid "Create milestone products"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:15
msgid "In Odoo, each milestone of your project is considered as a product. To configure products to work this way, go to any product form."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:18
msgid "You have to set the product type as *Service* under general information and select *Milestones* in the sales tab."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:25
msgid "Invoice milestones"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:27
msgid "From the sales order, you can manually edit the quantity delivered as you complete a milestone."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/milestone.rst:33
msgid "You can then invoice that first milestone."
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 for customs purposes during importation. 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:14
msgid "Activate the feature"
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. To do that, 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:26
msgid "Send a pro-forma invoice"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:28
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:35
msgid "When the :guilabel:`Send Pro-Forma Invoice` button is clicked, an email pop-up appears. The :guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation. Then, if needed, modify the :guilabel:`Subject` field and the body of the email. The pro-forma invoice is automatically added as an attachment to the email."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/proforma.rst:40
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:48
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/subscriptions.rst:3
msgid "Sell subscriptions"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:5
msgid "Selling subscription products will give you predictable revenue, making planning ahead much easier."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:9
msgid "Make a subscription from a sales order"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:11
msgid "From the sales app, create a quotation to the desired customer, and select the subscription product your previously created from the Subscriptions App."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:14
msgid "When you confirm the sale the subscription will be created automatically. You will see a direct link from the sales order to the Subscription in the upper right corner."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:3
msgid "Invoice based on time and materials"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:5
msgid "Time and Materials is generally used in projects in which it is not possible to accurately estimate the size of the project, or when it is expected that the project requirements would most likely change."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:9
msgid "This is opposed to a fixed-price contract in which the owner agrees to pay the contractor a lump sum for the fulfillment of the contract no matter what the contractors pay their employees, sub-contractors, and suppliers."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:14
msgid "For this documentation I will use the example of a consultant, you will need to invoice their time, their various expenses (transport, lodging, ...) and purchases."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:19
msgid "Invoice time configuration"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:21
msgid "To keep track of progress in the project, you will need the *Project* app. Go to :menuselection:`Apps --> Project` to install it."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:24
msgid "In *Project* you will use timesheets, to do so go to :menuselection:`Project --> Configuration --> Settings` and activate the *Timesheets* feature."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:32
msgid "Invoice your time spent"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:34
msgid "From a product page set as a service, you will find two options under the invoicing tab, select both *Timesheets on tasks* and *Create a task in a new project*."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:41
msgid "You could also add the task to an existing project."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:43
msgid "Once confirming a sales order, you will now see two new buttons, one for the project overview and one for the current task."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:49
msgid "You will directly be in the task if you click on it, you can also access it from the *Project* app."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:52
msgid "Under timesheets, you can assign who works on it. You can or they can add how many hours they worked on the project so far."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:58
msgid "From the sales order, you can then invoice those hours."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:69
msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Accounting --> Configuration --> Settings` and activate *Analytic Accounting*."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:90
msgid "under the invoicing tab, select *Delivered quantities* and either *At cost* or *Sales price* as well depending if you want to invoice the cost of your expense or a previously agreed on sales price."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:120
msgid "Invoice purchases"
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:122
msgid "The last thing you might need to add to the sale order is purchases made for it."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:125
msgid "You will need the *Purchase Analytics* feature, to activate it, go to :menuselection:`Invoicing --> Configuration --> Settings` and select *Purchase Analytics*."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:129
msgid "While making the purchase order don't forget to add the right analytic account."
msgstr ""
#: ../../content/applications/sales/sales/invoicing/time_materials.rst:135
msgid "Once the PO is confirmed and received, you can create the vendor bill, this will automatically add it to the SO where you can invoice it."
msgstr ""
#: ../../content/applications/sales/sales/products_prices.rst:5
msgid "Products & Prices"
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 "How to sell in foreign currencies"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:5
msgid "Pricelists can also be used to manage prices in foreign currencies."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:7
msgid "Check *Allow multi currencies* in :menuselection:`Invoicing/Accounting --> Settings`. As admin, you need *Adviser* access rights on Invoicing/Accounting apps."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:10
msgid "Create one pricelist per currency. A new *Currency* field shows up in pricelist setup form."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13
msgid "To activate a new currency, go to :menuselection:`Accounting --> Configuration --> Currencies`, select it in the list and press *Activate* in the top-right corner. Now it will show up in currencies drop-down lists."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:17
msgid "Prices in foreign currencies can be defined in two fashions."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:20
msgid "Automatic conversion from public price"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:22
msgid "The public price is in your company's main currency (see :menuselection:`Accounting --> Settings`) and is set in product detail form."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:28
msgid "The conversion rates can be found in :menuselection:`Accounting --> Configuration --> Currencies`. They can be updated from Yahoo or the European Central Bank at your convenience: manually, daily, weekly, etc. See :menuselection:`Accounting --> Settings`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:40
msgid "Set your own prices"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:42
msgid "This is advised if you don't want your pricing to change along with currency rates."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:49
msgid ":doc:`pricing`"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:3
msgid "How to adapt your prices to your customers and apply discounts"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:5
msgid "Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business. A pricelist is a list of prices or price rules that Odoo searches to determine the suggested price. You can set several criteria to use a specific price: periods, min. sold quantity (meet a minimum order quantity and get a price break), etc."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:10
msgid "As pricelists only suggest prices, they can be overridden by vendors completing sales orders. Choose your pricing strategy from :menuselection:`Sales --> Settings`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:18
msgid "*A single sale price per product:* doesn't let you adapt prices, it use default product price ;"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20
msgid "*Different prices per customer segment:* you will set several prices per products ;"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:21
msgid "*Advanced pricing based on formula:* will let you apply discounts, margins and roundings."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:24
msgid "Several prices per product"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:26
msgid "To apply several prices per product, select *Different prices per customer segment* in :menuselection:`Sales --> Settings`. Then open the *Sales* tab in the product detail form. You can settle following strategies."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:31
msgid "Prices per customer segment"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:33
msgid "Create pricelists for your customer segments: e.g. registered, premium, etc."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38
msgid "The default pricelist applied to any new customer is *Public Pricelist*. To segment your customers, open the customer detail form and change the *Sale Pricelist* in the *Sales & Purchases* tab."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:46
msgid "Temporary prices"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:48
msgid "Apply deals for bank holidays, etc. Enter start and end dates dates."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:54
msgid "Make sure you have default prices set in the pricelist outside of the deals period. Otherwise you might have issues once the period over."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:58
msgid "Prices per minimum quantity"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:64
msgid "The prices order does not matter. The system is smart and applies first prices that match the order date and/or the minimal quantities."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:68
msgid "Discounts, margins, roundings"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:70
msgid "*Advanced pricing based on formula* allows to set price change rules. Changes can be relative to the product list/catalog price, the product cost price, or to another pricelist. Changes are calculated via discounts or surcharges and can be forced to fit within floor (minimum margin) and ceilings (maximum margins). Prices can be rounded to the nearest cent/dollar or multiple of either (nearest 5 cents, nearest 10 dollars)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:77
msgid "Once installed go to :menuselection:`Sales --> Configuration --> Pricelists` (or :menuselection:`Website Admin --> Catalog --> Pricelists` if you use e-Commerce)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:85
msgid "Each pricelist item can be associated to either all products, to a product internal category (set of products) or to a specific product. Like in second option, you can set dates and minimum quantities."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:92
msgid "Once again the system is smart. If a rule is set for a particular item and another one for its category, Odoo will take the rule of the item."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:94
msgid "Make sure at least one pricelist item covers all your products."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:96
msgid "There are 3 modes of computation: fix price, discount & formula."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:101
msgid "Here are different price settings made possible thanks to formulas."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:104
msgid "Discounts with roundings"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:106
msgid "e.g. 20% discounts with prices rounded up to 9.99."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:112
msgid "Costs with markups (retail)"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:114
msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120
msgid "Prices per country"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:122
msgid "Pricelists can be set by countries group. Any new customer recorded in Odoo gets a default pricelist, i.e. the first one in the list matching the country. In case no country is set for the customer, Odoo takes the first pricelist without any country group."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:126
msgid "The default pricelist can be replaced when creating a sales order."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128
msgid "You can change the pricelists sequence by drag & drop in list view."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:131
msgid "Compute and show discount % to customers"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133
msgid "In case of discount, you can show the public price and the computed discount % on printed sales orders and in your eCommerce catalog. To do so:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:136
msgid "Check *Allow discounts on sales order lines* in :menuselection:`Sales --> Configuration --> Settings --> Quotations & Sales --> Discounts`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:138
msgid "Apply the option in the pricelist setup form."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145
msgid ":doc:`currencies`"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:146
msgid ":doc:`/applications/websites/ecommerce/maximizing_revenue/pricing`"
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 "How to import Products with Categories and Variants"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:5
msgid "Import templates are provided in the **Import Tool** of the most common data to import (contacts, products, bank statements, etc.). You can open them with any spreadsheet software (Microsoft Office, OpenOffice, Google Drive, etc.)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:11
msgid "How to customize the file"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:13
msgid "Remove columns you don't need. However, we advise you to not remove the *ID* column (see why below)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:15
msgid "Set a unique ID to every single record by dragging down the ID sequencing."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:16
msgid "Don't change the labels of columns you want to import. Otherwise, Odoo won't recognize them anymore, and you will have to map them on your own in the import screen."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:18
msgid "Feel free to add new columns, but the fields need to exist in Odoo. If Odoo fails in matching the column name with a field, you can match it manually when importing by browsing a list of available fields."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:24
msgid "Why an “ID” column?"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:26
msgid "The ID is a truly unique identifier for the line item. Feel free to use one from your previous software to ease the transition into Odoo."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:29
msgid "Setting an ID is not mandatory when importing, but it helps in many cases:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:31
msgid "Update imports: you can import the same file several times without creating duplicates."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:32
msgid "Import relation fields (see here below)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:35
msgid "How to import relation fields"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:37
msgid "An Odoo object is always related to many other objects (e.g., a product is linked to product categories, attributes, vendors, etc.). To import those relations, you need to import the records of the related object first from their own list menu."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/import.rst:41
msgid "You can do this using the name of the related record or its ID. The ID is expected when two records have the same name. In such a case, add \" / ID\" at the end of the column title (e.g., for product attributes: Product Attributes / Attribute / ID)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3
msgid "Automatically get product images with Google Images"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5
msgid "The product images are very useful in Odoo, for example, to quickly find a product or check if you scanned the right one, but it can be a bit painful to set up especially if you have a lot of products. **Google Custom Search** allows finding images automatically for your product, based on their barcode, keeping your focus on what matters in your business."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:15
msgid "This functionnality requires configuration both on Google and on Odoo."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:17
msgid "With a free Google account, you can get up to 100 free images per day. If you need a higher rate, you'll have to upgrade to a billing account."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:23
msgid "Google API dashboard"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:25
msgid "Go to the `Google Cloud Platform API & Services <https://console.developers.google.com/>`_ page to generate Google Custom Search API credentials. Log in with your Google account."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28
msgid "Select or create an API project to store the credentials. Give it an explicit name (e.g. Odoo Images)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:31
msgid "In the credentials section, click on **Create Credentials** and select **API Keys**."
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:37
msgid "Save your **API Key**. You'll need it for the next step in Odoo!"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:39
msgid "Use the search bar to look for **Google 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:45
msgid "Enable the API."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0
msgid "\"Custom Search API\" tile with Enable button highlighted on Google Cloud Platform"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:54
msgid "Google Programmable Search dashboard"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56
msgid "Go to `Google Programmable Search Engine <https://programmablesearchengine.google.com/>`_ and click on **Get Started**. Log in with your Google account."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0
msgid "Google Programmable Search Engine page with the **Get Started** button on the up-right\n"
"of the page"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:64
msgid "Fill the language and the name of the search engine. Give it an explicit name (e.g. Odoo Images)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:68
msgid "Google doesn't allow to create a search engine without having entered at least one specific site to search on. You can put any website (e.g. www.google.com) for this step, we will remove it later."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:72
msgid "Validate the form by clicking on **Create**. Then, go to the edition mode of the search engine that you created (either by clicking on **Control Panel** on the confirmation page or by clicking on the name of your Search Engine on the Home page)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:76
msgid "In the **basics** tab, make sure to enable **Image search**, **SafeSearch** and **Search the entire web**."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:80
msgid "Once **Search the entire web** is enabled, you can safely delete the site that you put at the previous step."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83
msgid "Save your **Search Engine Id**. You’ll need it for the next step in Odoo!"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:88
msgid "Odoo"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:90
msgid "Go to :menuselection:`Settings --> General Settings --> Integrations`, activate **Google Images** and save."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:93
msgid "Go back to :menuselection:`Settings --> General Settings--> Integrations`, enter your **API Key** and **Search Engine ID** in **Google Images** settings and save again."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:99
msgid "Automatically get your product images in Odoo"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:101
msgid "The action to automatically get your product images in Odoo appears in any Products or Product Variants list view. Here is a step-by-step guide from the Inventory app."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104
msgid "Go to the Products menu (:menuselection:`Products --> Products` or :menuselection:`Products --> Product Variants`) from any application that uses products like Inventory or Sales."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:107
msgid "On the list view, select the products that needs an image."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:110
msgid "Only the 10,000 first selected products or product variants will be processed."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:113
msgid "Only the products or product variants with a barcode and without an image will be processed."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:114
msgid "If you select a product that has one or more variants from the Products view, each variant matching the previous criteria will be processed."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:117
msgid "In the action menu, select **Get Pictures from Google Images** and validate by clicking on **Get picture**."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120
msgid "You should see your images appearing incrementally."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:123
msgid "Only the 10 first images are fetched immediatly. If you selected more than 10, the rest will be fetched as a background job."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:125
msgid "The background job process about 100 images in a minute. If you reach the quota authorized by Google (either with a free or a paid plan), the background job will put itself on hold for 24 hours and continue where it stopped the day before."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:130
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:3
msgid "Product variants"
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, such as size and color. Products using variants can be managed at the product template level (for all attributes and variants of that product), and/or at the variant level (for individual variants)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:9
msgid "As an example, a company selling t-shirts may have the following product:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:11
msgid "T-shirt"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:13
msgid "Color: Blue, Red, White, Black"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:14
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:131
msgid "Size: S, M, L, XL, XXL"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:16
msgid "In this example, the **T-Shirt** is the product template, and **T-Shirt, S, Blue** is a product variant. **Color** and **size** are the attributes. **S** and **Blue** are values."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:19
msgid "The above example has a total of 20 different product variants (5 sizes x 4 colors). Each one of these has its own inventory, sales, etc."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:26
msgid "Activating product variants"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:28
msgid "To use product variants, go to :menuselection:`Sales --> Configuration --> Settings --> Product Catalog`, and enable the :guilabel:`Variants` feature. Finally, click :guilabel:`Save` to apply the setting."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "Activating product variants."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:37
msgid "Creating attributes"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:39
msgid "Attributes need to be created before product variants can be set up. Attributes can be accessed via :menuselection:`Sales --> Configuration --> Products --> Attributes`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:43
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:47
msgid "To create a new attribute, click :guilabel:`Create`. First, choose an attribute name, such as \"Color\" or \"Size.\""
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "Attribute creation window."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:54
msgid "Then, select a :guilabel:`Display Type`, which determines how this product will be shown on the :guilabel:`eCommerce` page, :guilabel:`Point of Sale` dashboard, and :guilabel:`Product Configurator`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:58
msgid ":guilabel:`Radio`: options appear in a bullet style list."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:59
msgid ":guilabel:`Select`: options appear in a dropdown menu."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:60
msgid ":guilabel:`Color`: options appear as small colored squares, which reflect any HTML color codes set."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "Display Types on Product Configurator."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:67
msgid "The :guilabel:`Variants Creation Mode` 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:70
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:72
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:74
msgid ":guilabel:`Never`: never automatically creates variants."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:77
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:79
msgid "Values should be added to an attribute before saving, but more values can be added at any time, if needed. To add a value, click :guilabel:`Add a line`. From there, you can:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:82
msgid "Type in the value's name."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:83
msgid "Check a box to indicate whether or not the value is custom (i.e. the customer provides unique specifications)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:85
msgid "Specifically for colors, add an HTML color code to make it even easier for salespeople and customers to know what they're selecting."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:88
msgid "A color code can be selected either by dragging the slider around or by entering a specific HTML color code (e.g. #FF0077)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "Selecting a color."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:95
msgid "Finally, click :guilabel:`Save` to finish creating the attribute."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:98
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:101
msgid "After an attribute is added to a product, a new tab appears on the attribute's page called :guilabel:`Related Products`. This tab lists every product in the database that is currently using the attribute."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:106
msgid "Creating product variants"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:108
msgid "After creating an attribute, use the attribute to create a product variant by going to :menuselection:`Sales --> Products --> Products`. Then, select an existing product and click :guilabel:`Edit`, or create a new product by clicking :guilabel:`Create`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:112
msgid "The :guilabel:`Variants` smart button at the top of the product template indicates the number of currently configured variants on the product."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:115
msgid "To add a new variant, click on the :guilabel:`Variants` tab, then click on :guilabel:`Add a line` to add any attributes and values. When all the attributes and values have been added, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:120
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:124
msgid "Managing product exclusions"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:126
msgid "The following examples are all based on a product template that has two attributes:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:128
msgid "T-Shirt"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:130
msgid "Color: Blue, Red, White"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:133
msgid "With the above product template, there are 15 different t-shirt variants in three different colors and five different sizes. If the white t-shirts are not available in the XXL size, then that variant can be deactivated."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137
msgid "To deactivate a particular product variant, go to :menuselection:`Sales --> Products --> Products` and select the relevant product. Next, click on the :guilabel:`Configure` button next to the relevant attribute value. Then select the relevant value (in this example, the :guilabel:`White Color` attribute), and then click on :guilabel:`Edit`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:142
msgid "In the :guilabel:`Exclude for` section, click :guilabel:`Add a line` and select any product(s) and/or specific attribute values that are currently unavailable. Finally, click :guilabel:`Save` to apply the setting, and Odoo will automatically show the product variant as unavailable on the eCommerce page."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "Excluding attributes."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:152
msgid "Setting a price per variant"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:154
msgid "Extra costs can be added to a product's standard price for specific product variants."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:156
msgid "To do this, open :menuselection:`Sales --> Products --> Products`, and click on the relevant product. Next, click on :guilabel:`Configure Variants` to access the list of product variant values."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:160
msgid "Then, click on a variant value, and :guilabel:`Edit`. In the :guilabel:`Value Price Extra` field, type in the additional cost for this particular value. This amount is added to the standard price. Finally, click :guilabel:`Save` to apply the extra price to the value."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1
msgid "Value Price Extra setting."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169
msgid "Impact of variants"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:171
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:174
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. For example, a red shirt's cost 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:180
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:184
msgid ":guilabel:`Picture`: each product variant can have its own specific picture."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:187
msgid "Changes to the product template automatically apply to every variant of that product."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:3
msgid "Process returns and refunds"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:5
msgid "The :guilabel:`Sales` app provides two different ways to process returns based on whether an invoice has been sent or not."
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 :guilabel:`Inventory` app must also be installed."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:17
msgid "To start a return, open the :guilabel:`Sales` app, navigate to the customer's 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:20
msgid "On the validated delivery order, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window. By default, the :guilabel:`Quantity` matches the validated quantities from the delivery order. Update the quantities if necessary. Click on the 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:29
msgid "Next, click :guilabel:`Return` to confirm the return. This generates a new warehouse operation for the incoming returned product(s). Upon receiving the return, the warehouse team validates the warehouse operation. Then, on the original sales order, the :guilabel:`Delivered` quantity will 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:38
msgid "When an invoice is created, the customer receives an invoice only for the products they are keeping."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:42
msgid "After invoicing"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:44
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. 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:49
msgid "To start a return, navigate to the relevant sales order. If there is a payment registered on the sales order, then the payment details will appear in the Chatter, and the invoice (accessible through the :guilabel:`Invoices` smart button) will have a green banner across it."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:53
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. Next, edit the :guilabel:`Product` or :guilabel:`Quantity` as needed for the return, and 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. Then, on the sales order, the :guilabel:`Delivered` quantity will reflect the difference between the initial validated quantities and the returned quantities."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:61
msgid "To process a refund, navigate to the relevant invoice (from the sales order, click on the :guilabel:`Invoices` smart button). Click :guilabel:`Add Credit Note` from the validated invoice."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:-1
msgid "The \"Credit Note\" pop-up window, to issue a credit to the customer after invoicing."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:68
msgid "A :guilabel:`Reason` for the credit and a :guilabel:`Specific Journal` to use to process the credit can be specified. If a :guilabel:`Specific Reversal Date` is selected, then a :guilabel:`Refund Date` must also be selected."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:72
msgid "After the information is filled in, click :guilabel:`Reverse`. Then, :guilabel:`Edit` the draft as needed, and finally, click :guilabel:`Confirm` to confirm the credit note."
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 "Expiration date deadlines"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:13
msgid "On an Odoo *Sales* quotation, add an expiration date in the :guilabel:`Expiration` field located at the top of the quotation or sales order form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:16
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:`Create`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:19
msgid "On the quotation form, click :guilabel:`Edit` (if modifying a pre-existing quotation), and click the :guilabel:`Expiration` field. Doing so reveals a drop-down calendar, in which the month and date can be designated as the expiration date of the quotation."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:-1
msgid "How to configure deadlines on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:27
msgid "Once the expiration date is selected, click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:30
msgid "Deadlines in quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:32
msgid "The Odoo *Sales* application also makes it possible to add a deadline to every quotation template. Whenever a specific quotation template is used in a quote, its associated deadline is automatically applied."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:36
msgid "To add a deadline 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:`Create` to build a new quotation template from scratch."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:40
msgid "On the quotation template detail page, click the :guilabel:`Edit` button to edit the quotation."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:42
msgid "Then, 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. When done, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:-1
msgid "How to use deadline in a quotation template on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/deadline.rst:51
msgid "By clicking the :guilabel:`Customer Preview` button on a quotation, Odoo clearly displays when that specific offer expires. As a reminder, the number of days is the same as those mentioned in the quotation template (if a quotation template was used for the initial quotation)."
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:60
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:52
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:90
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:68
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:149
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:10
msgid "Settings"
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 "With Odoo *Sales*, online payments can be used to get automatic confirmation on orders."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:8
msgid "Enable online payment"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:10
msgid "Go to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& Orders` heading, and activate the :guilabel:`Online Payment` feature by checking the box next to it, and clicking :guilabel:`Save`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1
msgid "How to enable online payment on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:18
msgid "After checking the box beside the :guilabel:`Online Payment` feature, a link to the :guilabel:`Payment Acquirers` appears beneath it. Click that link to reveal the entire :guilabel:`Payment Acquirers` page."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1
msgid "Payment acquirers page in the Odoo Sales application."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:26
msgid "On the :guilabel:`Payment Acquirers` page, payment acquirers can be selected and configured. Before creating (or modifying) a payment acquirer, be sure to review the documentation related to the ways payment acquirers can be used with Odoo, such as:"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:30
msgid ":doc:`../../../finance/payment_acquirers/paypal`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:31
msgid ":doc:`../../../finance/payment_acquirers/authorize`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:32
msgid ":doc:`../../../finance/payment_acquirers`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35
msgid "On quotation templates, the :guilabel:`Online Payment` feature is located under the :guilabel:`Confirmation` tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:38
msgid "On standard quotations, the :guilabel:`Online Payment` feature is located under the :guilabel:`Other Info` tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:42
msgid "Register a payment"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:44
msgid "After opening quotations from the email they receive, customers are presented with different options 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 Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:52
msgid "Clicking the :guilabel:`Customer Preview` smart button on the quotation form provides a preview of the quotation as the customer sees it, along with the various online payment options they can choose from."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:57
msgid ":doc:`quote_template`"
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 automatically 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 "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. Then, click the :guilabel:`Save` button in the top-left corner."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:-1
msgid "How to enable online signature in Odoo Sales settings."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:23
msgid "On quotation templates, the :guilabel:`Online Signature` feature is located under the :guilabel:`Confirmation` tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0
msgid "How to enable online signature on a quotation template."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:30
msgid "On standard quotations, the :guilabel:`Online Signature` feature is located under the :guilabel:`Other Info` tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0
msgid "How to enable online signature on standard quotations."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:38
msgid "Order confirmations with online signatures"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:40
msgid "When quotations are sent to clients, there's an option for them to :guilabel:`Sign & Pay` directly on the quotation in the online customer portal. When clicked, clients have the option to draw a signature, fill in the field with an automated signature, or load a file from their computer."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:-1
msgid "How to confirm an order with a signature on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:48
msgid "Once signed, the various payment method options become available. Then, when the quotation is paid and confirmed, a delivery order is automatically created (if the Odoo *Inventory* app is installed)."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3
msgid "Optional products"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:5
msgid "The use of optional products is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:9
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:24
msgid "Click the :guilabel:`Customer Preview` button to reveal a preview of the quotation customers would receive via email, along with the optional products they have a chance of adding to their order."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:0
msgid "Preview your quotations on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:32
msgid "In practice, 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. If a customer selects all the optional products suggested, these additional items are automatically filled in on the quotation that is managed by the salesperson."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1
msgid "How to select optional products on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:41
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:-1
msgid "How to follow each movement made by your customers on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:51
msgid "Optional products on quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:54
msgid "Be sure to review the documentation on how to :doc:`/applications/sales/sales/send_quotations/quote_template` to better understand how quotation templates work before reading the following information."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:58
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:61
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:65
msgid "On the quotation form, click :guilabel:`Edit`, then 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:70
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:74
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:77
msgid "When the desired optional product(s) have been added, click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:80
msgid "There is no limit to how many optional products can be added to a quotation template."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:82
msgid "The products added in the :guilabel:`Optional Products` tab are present in the quotation, by default, whenever that particular quotation template is used."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1
msgid "How to add optional products to your quotation templates on Odoo Sales."
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 "Product variants can be added to quotations and sales orders using the *product configurator*, *variant grid entry*, or both."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:11
msgid "To enable product variants on quotations and sales orders, go to :menuselection:`Sales app --> Configuration --> Settings`, and under the :guilabel:`Product Catalog` heading, activate one (or both) of the :guilabel:`Product Configurator` and :guilabel:`Variant Grid Entry` settings. Finally, click :guilabel:`Save` to apply the settings."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1
msgid "Activating entry type settings."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:20
msgid "After saving the settings, it's time to configure the product form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:22
msgid "To do that, navigate to :menuselection:`Sales app --> Products --> Products`, and select the desired product to configure (or click :guilabel:`Create` to open a blank product form, and create a new one)."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:26
msgid "On the product form, click :guilabel:`Edit`, and select the :guilabel:`Variants` tab. Click :guilabel:`Add a line` to add an attribute in the :guilabel:`Attribute` column, like `Color` or `Size`, for example."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:30
msgid "Once the attribute is chosen, select the desired values to apply to that attribute in the :guilabel:`Values` column. To select the desired values, click into the blank field beneath the :guilabel:`Values` column."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:34
msgid "Then, select an option from the drop-down menu that appears. Or, create a new value by typing in the new value, and click :guilabel:`Create` from the drop-down menu that appears beneath the new value."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37
msgid "When a product has *at least* two variants (one attribute with two values), the :guilabel:`Sales Variant Selection` option appears at the bottom of the :guilabel:`Variants` tab. That is the **only** way to make that option appear, so keep that in mind."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:41
msgid "Under :guilabel:`Sales Variant Selection`, choose either :guilabel:`Product Configurator` or :guilabel:`Order Grid Entry`. This selection determines which method is used to add the product to quotations or sales orders."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:45
msgid ":guilabel:`Product Configurator`: choose attribute values to add the matching product variant to the order."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:47
msgid ":guilabel:`Order Grid Entry`: add several variants at once from the grid of attribute values."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:49
msgid "Once a selection is made, click :guilabel:`Save` on the product form to apply the setting."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1
msgid "Sales variant selection."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:56
msgid "Product configurator"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:58
msgid "The *product configurator* appears on a quotation or sales order when products that have **both** variants configured are added, and the :guilabel:`Product Configurator` option is selected on the product form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:62
msgid "The product configurator lets salespeople choose exactly which product variant to add to the quotation or sales order, using a format similar to online shopping. Color options display any HTML color codes set up in the :guilabel:`Color` attribute."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:66
msgid "Features with an additional cost display the additional cost next to their name. Once the desired product variant attributes are selected, click :guilabel:`Add` to add the product variant to the quotation or sales order."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1
msgid "Product Configurator and Price Extras."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74
msgid "By default, the product variant attributes are displayed on the quotation or sales order in the :guilabel:`Description` column, but a dedicated :guilabel:`Product Variant` column can be added, via the additional options menu (represented by the :guilabel:`⋮ (3 vertical dots)` icon, on the far-right side of the columns, in the :guilabel:`Order Lines` tab)."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1
msgid "Product variant column option in order lines tab of quotation."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:83
msgid "Just click the checkbox next to :guilabel:`Product Variant`, and that column appears in the :guilabel:`Order Lines` tab."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:87
msgid "Variant grid entries"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:89
msgid "*Variant grid entries* appear on a quotation or sales order when products that have both variants configured are added, and the :guilabel:`Order Grid Entry` option is selected on the product form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:92
msgid "The grid entry feature streamlines the process of creating large, varied quotations by letting salespeople enter exact quantities of each product variant all at once."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:95
msgid "The :guilabel:`Choose Product Variants` pop-up form that appears, displays a grid of every variant available for that specific product."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:98
msgid "From the :guilabel:`Choose Product Variants` pop-up form, choose the exact quantities of each product variant for a quotation or sales order by typing in the number or using the arrows in each column. The :guilabel:`Not Available` warning is displayed when a particular variant has been deactivated in the database."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:103
msgid "Once all the product variants and their quantities have been set in the pop-up form, click :guilabel:`Confirm` to add them to the quotation or sales order."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1
msgid "Variant Grid Entry pop-up form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:110
msgid "Each product variant appears as an individual line item on the quotation or sales order with the chosen quantity from the :guilabel:`Choose Product Variants` pop-up form, because each of these items has its own stock."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1
msgid "Line items for grid variants."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:45
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 product or service offerings that the business offers. 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:15
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:18
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:26
msgid "Also, upon activating the :guilabel:`Quotation Template` feature, an internal :guilabel:`➡️ Quotation Templates` link appears beneath the :guilabel:`Default Template` field. 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:32
msgid "Consider activating the :guilabel:`Quotation Builder` option in the :guilabel:`Settings`, as well, which is located in the right column beside the :guilabel:`Quotation Templates` option. This feature aides in the design and customization of quotation templates."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:36
msgid "**Note:** enabling this feature also automatically installs the Odoo *Website* application."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "How to enable quotation builder on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:42
msgid "Before leaving the :guilabel:`Settings` page, don't forget to click the :guilabel:`Save` button to activate the feature(s) and save all changes made during the session."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:46
msgid "Create quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:48
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:52
msgid "To create a new quotation template, click the :guilabel:`Create` 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:59
msgid "Start by entering a name for the template in the :guilabel:`Quotation Template` field. Then, in the :guilabel:`Quotation expires after` 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:63
msgid "In the :guilabel:`Company` field, designate to which company this quotation template applies, if working in a multi-company environment."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:66
msgid "Beneath those fields are three tabs: :guilabel:`Lines`, :guilabel:`Optional Products`, :guilabel:`Confirmation`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69
msgid "In the :guilabel:`Lines` tab, products can be added to the quotation template by clicking :guilabel:`Add a product`, organized by clicking `Add a section` (and dragging/dropping section headers accordingly), 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:74
msgid "In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each compatible cross-selling product related to the original items in the :guilabel:`Lines` tab, if applicable. The products added here ideally compliment the original offering as added value for the prospective buyer."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:78
msgid "Lastly, in the :guilabel:`Confirmation` tab, enable options, as needed, to require an :guilabel:`Online Signature` and/or an :guilabel:`Online Payment`, which each allow buyers to confirm orders automatically using the web portal view after the required action is taken."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:82
msgid "There's also an option to add a :guilabel:`Confirmation Mail` to the quotation template, as well - meaning whenever this template is used, and an order is confirmed, an email is sent to the customer informing them that their order has been confirmed."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Allow customers to sign electronically or to pay online on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:91
msgid "Design quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:94
msgid "The following section on designing quotation templates only applies to databases that have the *Quotation Builder* feature enabled, which is accessible by following the :ref:`configuration steps above <sales/send_quotations/templates>`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:98
msgid "In the upper-left corner of the quotation template form, there's a :guilabel:`Design Template` button. When clicked, Odoo reveals a preview of the quotation template, as it will appear on the front-end of the website, with a :guilabel:`Template Header` specifying that this content will appear on all quotations using this specific template."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:103
msgid "To edit the content, look, and overall design of the quotation template, click the :guilabel:`Edit` button in the upper-right corner. Doing so reveals a variety of design elements and feature-filled building blocks."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Design quotation template on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:111
msgid "Drag and drop any desired building blocks onto the blank quotation template, and proceed to further customize the content to fit any business need. 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:-1
msgid "Drag and drop building blocks to create your quotation template on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:120
msgid "Use quotation templates"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:122
msgid "When creating a quotation (:menuselection:`Sales app --> Create`), choose a preconfigured template in the :guilabel:`Quotation Template` field drop-down menu."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1
msgid "Select a specific template on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:129
msgid "To view what the customer will see, click the :guilabel:`Customer Preview` smart button to see how the quotation template will look on the front-end of the website."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:133
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:150
msgid ":doc:`/applications/sales/sales/send_quotations/get_signature_to_validate`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:134
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:151
msgid ":doc:`/applications/sales/sales/send_quotations/get_paid_to_validate`"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:3
msgid "Terms and conditions"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:5
msgid "Specifying terms and conditions is essential to establish important contractual points, such as payment terms, limitations of liability, and delivery terms between customers and sellers."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:8
msgid "Sellers must declare all formal information concerning products and company policy. Conversely, customers must take note of all these conditions before committing to a purchase."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:11
msgid "With Odoo *Sales*, it's very easy to include default terms and conditions on every quotation, sales order, and invoice."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:15
msgid "Default terms and conditions"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:20
msgid "Go to :menuselection:`Accounting app --> Configuration --> Settings`, scroll to the :guilabel:`Customer Invoices` heading, and check the box beside the :guilabel:`Default Terms & Conditions` feature to activate it."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "How to enable Default Terms and Conditions on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:29
msgid "Please note that this feature is activated via the settings of the *Accounting* app, and **not** in the settings of the *Sales* app."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:32
msgid "In the :guilabel:`Settings` of the :menuselection:`Accounting` application, after activating the :guilabel:`Default Terms & Conditions` feature, a field appears beneath the feature. In this field, specific terms and conditions can be entered."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Default Terms and Conditions on quotation on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:40
msgid "Click :guilabel:`Save` to save the terms and conditions."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:42
msgid "These terms and conditions appear on every quotation, sales order, and invoice."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:47
msgid "Default terms and conditions can be applied to quotation templates, as well, depending on the specific needs of the business. This is useful when various terms and conditions are used within a company."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:52
msgid "When a quotation template is used on a quotation, the quotation uses the terms and conditions specified on that template, over the terms and conditions specified in the settings."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:55
msgid "First, navigate to the :menuselection:`Sales app --> Configuration --> Quotation Templates` to view all the quotation templates. From here, either select a template or create a new one, via the :guilabel:`Create` button."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:59
msgid "Once on the desired quotation template form, click :guilabel:`Edit`, and enter in specific terms and conditions that should be applied to this quotation template, at the bottom of the :guilabel:`Lines` tab. Once done, click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Add Default Terms and Conditions to quotation templates on Odoo Sales."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:71
msgid "Attachment on confirmation emails"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:73
msgid "Terms and conditions can also be sent as an attachment on the confirmation email of a quotation template."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:76
msgid "To do so, navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates` and create a new quotation template (via the :guilabel:`Create` button), or modify an existing one."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:79
msgid "On the desired quotation template form, click :guilabel:`Edit`. Under the :guilabel:`Confirmation` tab, there are options to activate an :guilabel:`Online Signature`, :guilabel:`Online Payment`, and :guilabel:`Confirmation Mail`."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:83
msgid "Click on the :guilabel:`Confirmation Mail` field to reveal a drop-down menu from which an email template can be chosen or created. To create a new email template from here, start typing the name of this new template, and then select :guilabel:`Create and Edit...`, which reveals a :guilabel:`Create: Confirmation Mail` pop-up form."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:88
msgid "On this pop-up form, customize the email message in a number of different ways, but be sure to click :guilabel:`Attachments` at the bottom of the :guilabel:`Content` tab to add the desired terms and conditions attachment to the mailing. Once done, click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Terms and conditions as attachment in quotation templates."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:97
msgid "Website page"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:99
msgid "Use the Odoo *Website* application to create a terms and conditions page. To do that, first navigate to the front-end of the website, via :menuselection:`Website app --> Go to Website`. From here, click :guilabel:`+ New` in the top right corner of the page, then select :guilabel:`Page`. Give the terms and conditions page a title in the pop-up form that appears."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:104
msgid "Then, decide if this page should be accessible via the main website header menu, using the :guilabel:`Add to menu` toggle in the pop-up form, and click :guilabel:`Continue` to create the new page."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:108
msgid "Doing so reveals a blank page on the website that can be fully customized and edited with Odoo's drag-and-drop building blocks. Use those building blocks to add the terms and conditions to the page, and click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:112
msgid "Don't forget to publish the page, via the :guilabel:`Unpublished` / :guilabel:`Published` toggle at the top of the page. Unpublished pages will **not** be accessible to website visitors."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Terms and Conditions on a website."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:119
msgid "This terms and conditions page can be linked in the footer of all documents, if desired. To do that, access the document layout by navigating to the :menuselection:`Settings` app. In the :guilabel:`General Settings`, under the :guilabel:`Business Documents` heading, click :guilabel:`Configure Document Layout` (located beneath :guilabel:`Document Layout`)."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:124
msgid "Doing so reveals a :guilabel:`Configure your document layout` pop-up form. On this form, in the :guilabel:`Footer` field, enter the URL for the terms and conditions page on the website."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:127
msgid "It's good practice to also provide a brief title prefacing the URL, so customers know what the link leads to when they see it on the footer of documents."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Terms and Conditions in business documents."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:135
msgid "Email attachments"
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:137
msgid "Odoo provides the ability to attach an external document, such as one containing terms and conditions, when quotations are sent by email to customers."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:140
msgid "On a quotation, sales order, or other document, click the :guilabel:`Send by Email` button to send an email to the customer. Then, on the email form, click :guilabel:`Attach a File` to attach the terms and conditions document."
msgstr ""
#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1
msgid "Terms and conditions as attachment in emails."
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:8
msgid "Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:10
msgid "**Odoo Subscriptions** is used to run recurring businesses: sell new contracts, upsell customers, keep the churn under control and have reporting on the main KPIs: MRR, ARR, retention, churn, upselling, etc."
msgstr ""
#: ../../content/applications/sales/subscriptions.rst:15
msgid "`Odoo Tutorials: Subscriptions <https://www.odoo.com/slides/subscription-20>`_"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:3
msgid "Add subscription products"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:5
msgid "To properly sell your subscriptions using our amazing **Odoo Subscriptions** application, you must follow these steps:"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:8
msgid "**Create your own subscription templates**"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:9
msgid "**Create your own subscription products with the right settings**"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:11
msgid "As a result, you will be able to manage your subscriptions like any other product, create your quotations and continue the sales flow to track the number of subscriptions you sell and manage the revenue they generate."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:18
msgid "Go to :menuselection:`Subscriptions --> Subscription products` to learn how you can configure your own subscription products. You have the possibility to create a new product or edit an existing one. Once named, be careful to select the option *Can be sold* and deselect *Can be purchased*. For the product type, it is recommended to use *Service* for subscription products as they are non-material products that you provide to your customers. Finally, you can adapt your prices and also add an internal reference."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:-1
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:0
msgid "View of a subscription product form in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:30
msgid "In the Sales tab, underneath the Subscriptions section, make sure the *Subscription products* option is activated. In fact, if you create a subscription product from the **Odoo Subscriptions** application, this option is selected by default. However, if you create a product from another application, it is not the case."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:39
msgid "You can also choose the subscription templates you want to use."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:46
msgid "Be sure to check out our documentation on how to create, edit and manage your own :doc:`Subscription templates <../../subscriptions/configuration/subscription_templates>` before creating your own subscription products. Once created, check out our documentation on how to :doc:`Create a quotation using subscription products <../../subscriptions/sales_flow/create_a_quotation>`, to complete the sales flow."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:53
#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:83
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:120
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:105
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:79
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:80
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:83
msgid ":doc:`../../subscriptions/configuration/subscription_templates`"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:54
#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:85
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:122
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:107
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:82
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:85
msgid ":doc:`../../subscriptions/sales_flow/create_a_quotation`"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:3
msgid "Use subscription templates"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:5
msgid "The subscription business model is becoming more popular. Are you wondering why?"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:7
msgid "For **customers**, value lies in **convenience**:"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:9
msgid "Subscriptions simplify the business process. Indeed, subscribers never have to remember to renew their orders every month, which gives them the assurance that they will have everything they need before they actually need it."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:12
msgid "Subscriptions help customers stay on budget."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:14
msgid "For **businesses**, value lies in the **ability to predict recurring revenue**:"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:16
msgid "Subscriptions reduce customer churn rate and significantly increase customer retention."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:17
msgid "Subscriptions provide much higher payment security for your business. They stabilize and maintain recurring revenue streams by guaranteeing monthly revenues and adding value to your business."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:27
msgid "**Odoo Subscriptions** help you save time and money. Subscription templates can help you generate recurring invoices and manage renewals at a fast pace. With Odoo you have the possibility to create, edit, and manage your own subscription templates."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:34
msgid "Go to :menuselection:`Subscriptions --> Configuration --> Subscription templates`. By default, Odoo suggests you two types of subscription (MON - Monthly subscription *vs* YEA - Yearly subscription). You can also create your own ones."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:-1
msgid "Default subscription templates on Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:43
msgid "The **Odoo Subscriptions** application automatically installs **Odoo Sales** and **Odoo Invoicing** as they work integrated."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:47
msgid "Create your first template"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:49
msgid "You can create a new template or edit an existing one. The first thing you need to do is give your template a name. After that, choose an *Invoicing period* and specify whether you would like to invoice your customers per *Days*, *Weeks*, *Months* or *Years*. On *Duration*, determine if the subscription must go on *Forever* (until it’s manually closed), or for a *Fixed amount* of time. Among the payment options, an additional field called *Invoice email* appears when you choose *Send*, *Send & try to charge* or *Send after successful payment*. This field allows you to add an invoice email template to your subscription templates."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:-1
msgid "Create your own subscription templates on Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:61
msgid "For each template, you can also choose if you want your customers to be able to close their subscriptions or not. If enabled, you can set an *Automatic closing* limit and specify the *Group of subscription* and *Journal* options."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:66
msgid "On each template, you can add your **Terms and Conditions**. Specifying terms and conditions is essential to set out important contractual points between the customers and the sellers (payment, refund policy, cancellation, complaints, etc.)."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:0
msgid "Terms & conditions on Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:74
msgid "Finally, if you want to know the basic running health status of your subscriptions, you also have access to a specific tab called **Health Check**. There, you can edit and create your own filters to define what is a subscription in good health *vs* bad health. The system automatically summarizes all the records corresponding to these filters and you are able to manage them in one click."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:0
msgid "Health check on Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:85
msgid "After creating your own subscription templates, be sure to check out our documentation on how to create, edit and manage your own :doc:`Subscription products <../../subscriptions/configuration/subscription_products>`, to complete the sales flow."
msgstr ""
#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:91
#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:84
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:121
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:106
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:80
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:81
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:84
msgid ":doc:`../../subscriptions/configuration/subscription_products`"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up.rst:5
msgid "Follow-up"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:3
msgid "Set up automatic alerts"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up/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/follow_up/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/follow_up/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/follow_up/automatic_alerts.rst:20
msgid "Create a new automatic alert"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up/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/follow_up/automatic_alerts.rst:-1
msgid "New automatic alert in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up/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/follow_up/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/follow_up/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/follow_up/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/follow_up/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/follow_up/automatic_alerts.rst:-1
msgid "Satisfaction survey in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:63
msgid "Modify an existing automatic alert"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up/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/follow_up/automatic_alerts.rst:-1
msgid "Modify an existing automatic alert in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/follow_up/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/follow_up/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/follow_up/automatic_alerts.rst:86
msgid ":doc:`../../subscriptions/reporting/subscription_reports`"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:3
msgid "Generate subscription reports"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_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/reporting/subscription_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/reporting/subscription_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/reporting/subscription_reports.rst:-1
msgid "Difference between MRR and ARR in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_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/reporting/subscription_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/reporting/subscription_reports.rst:35
msgid "**Logo Churn**: It corresponds to the subscription cancellation rate."
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:37
msgid "**Revenue Churn**: It corresponds to the monthly recurring revenue loss rate."
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:40
msgid "Let's imagine a 2$ increase in a subscription service."
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_reports.rst:0
msgid "Therefore, the 56$ of MRR difference out of the initial 600$ causes a **Revenue Churn**"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:0
msgid "of 9,33%."
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:0
msgid "Difference between logo churn and revenue churn in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_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/reporting/subscription_reports.rst:57
msgid "Check out the different kinds of reports you can access from the **Odoo Subscriptions** application."
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:61
msgid "Subscriptions analysis report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_reports.rst:-1
msgid "Subscriptions analysis report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:74
msgid "Retention analysis report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_reports.rst:-1
msgid "Retention analysis report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:86
msgid "Revenue KPIs report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_reports.rst:-1
msgid "Revenue KPIs report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_reports.rst:-1
msgid "Detailed MRR report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:108
msgid "Salesperson dashboard report"
msgstr ""
#: ../../content/applications/sales/subscriptions/reporting/subscription_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/reporting/subscription_reports.rst:-1
msgid "Salesperson dashboard report in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow.rst:5
msgid "Sales flow"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:3
msgid "Close a subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/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/sales_flow/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/sales_flow/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/sales_flow/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/sales_flow/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/sales_flow/closing.rst:-1
msgid "Configuration to close your subscription with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:43
msgid "Be sure to check out our documentation on how to :doc:`Use subscription templates <../../subscriptions/configuration/subscription_templates>` to fully understand the importance of this feature in a basic flow using the **Odoo Subscriptions** application."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:49
msgid "Close your first subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:52
msgid "Administrator view"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/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/sales_flow/closing.rst:-1
msgid "Close your subscription from an administration point of view with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/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/sales_flow/closing.rst:-1
msgid "What happens when you close your subscription with Odoo Subscriptions?"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:72
msgid "Customer view"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/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/sales_flow/closing.rst:-1
msgid "Close your subscription from a customer point of view with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/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/sales_flow/closing.rst:-1
msgid "What happens when customers close their subscription with Odoo Subscriptions?"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/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/sales_flow/closing.rst:-1
msgid "What happens when customers close their subscription in Odoo Subscriptions?"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:100
msgid "Before closing a subscription, check out our documentation on how to :doc:`Create a quotation using subscription products <../../subscriptions/sales_flow/create_a_quotation>` to understand how subscriptions are managed in the **Odoo Subscriptions** application."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:3
msgid "Create a quotation using subscription products"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:5
msgid "Selling a digital product or service gives instant gratification. However, you have to work hard for a new customer to make a purchase. It costs time and money. By convincing customers to sign up for a subscription, you maximize your income and streamline your cash flow. You can sell any type of product or service through a subscription business model."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:15
msgid "Here is a scenario using **Odoo Subscriptions** to create a quotation including subscription products."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:19
msgid "Create your first quotation"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:21
msgid "Before creating your first quotation, be sure to check out our documentation on how to create and manage your own :doc:`Subscription templates <../../subscriptions/configuration/subscription_templates>` and on how to add :doc:`Subscription products <../../subscriptions/configuration/subscription_products>` to your templates."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:30
msgid "These steps are **mandatory** to make a basic sales flow using **Odoo Subscriptions**."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:32
msgid "Go to **Odoo Sales** and create a new quotation. Then, choose a customer and add a product. Be careful to select a product that you previously configured as a *Subscription product*."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1
msgid "View of a quotation form in Odoo Sales"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:39
msgid "When your quotation is ready, you have the possibility to send it to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers to have their confirmation and, then, *Confirm* it in **Odoo Sales**. By clicking on *Customer preview*, you have an idea of what your customers will see when receiving your quotation."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1
msgid "Customer preview of a quotation form in Odoo Sales"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:48
msgid "From there, your customers have three choices: *Sign & Pay* the quotation, give you a *Feedback* or *Reject* the quotation. It appears that they are very happy and accept the option *Sign & Pay*. Then, they have to validate the order with a signature and by choosing a payment method. When it is done, you can check out the quotation in **Odoo Sales** and *Confirm* it."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:54
msgid "Manage your subscriptions from your SO"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:56
msgid "Once confirmed, the quotation becomes a sales order and a new button appears, *Subscriptions*. Indeed, a subscription is automatically created."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1
msgid "Quotation form in Odoo Sales with a button \"Subscriptions\""
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:63
msgid "By clicking on the *Subscriptions* button, you can see that the status of the subscription is *In progress*. From there, you will have three options: :doc:`Renew <../../subscriptions/sales_flow/renewals>`, :doc:`Close <../../subscriptions/sales_flow/closing>` or :doc:`Upsell <../../subscriptions/sales_flow/upselling>` your subscription."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:-1
msgid "Use of the intelligent button \"Subscriptions\" in Odoo Sales"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:73
msgid "In the top-right corner, you can see the status of the subscription. When a subscription is new and created from **Odoo Subscriptions**, the status is *Draft*. When a sales order has been validated, the status is *In progress*. Finally, when a customer decides to close his subscription, the status becomes *Closed*."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:81
msgid ":doc:`../../subscriptions/sales_flow/renewals`"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:82
msgid ":doc:`../../subscriptions/sales_flow/closing`"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:83
msgid ":doc:`../../subscriptions/sales_flow/upselling`"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:3
msgid "Renew a subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:5
msgid "The key feature of a subscription business model is the recurring nature of payments. In this model, customers pay a recurring amount in exchange for access to a product or a service."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:14
msgid "Each subscriber experiences this renewal process monthly, annually, or sometimes more, depending on the duration of the contract. Most subscription companies choose to automate their renewal processes but, in some cases, manual subscription renewals are still the preferred option."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:18
msgid "With **Odoo Subscriptions**, you can have all your subscriptions in one application, suggest an automatic subscription renewal to your customers (as well as a manual one) and, finally, filter all your subscriptions and easily find those to renew (with the help of the tag *To renew*)."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:23
msgid "Renew your first subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:25
msgid "Before renewing a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, 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 renew the subscription. In the Other Info tab, underneath the To Renew section, you can activate the *To renew* option. When activated, a yellow tag automatically appears in the upper right corner of the subscription."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:-1
msgid "Renew your subscription with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:38
msgid "The *To renew* tag is automatically ticked when a payment fails. This indicator also appears on the customer portal. To visualize that, you just have to click on the *Customer preview* button. The tag *To renew* appears on the top right corner."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0
msgid "Customer preview of a renewal with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:46
msgid "When a subscription needs to be renewed, you have the possibility to use a new button called *Renewal quotation*. By clicking on it, a new quotation is created. From there, start a basic sales flow allowing you to send the quotation by email to your customers or to confirm it. It is better to first *Send by email* the quotation to your customers in order to have their confirmation and, then, *Confirm* it in **Odoo Sales**."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:53
msgid "In the Chatter of this new quotation, it is mentioned that \"This renewal order has been created from the previous subscription\". Once confirmed by your customers, this quotation becomes a sales order and a new sale is mentioned in the upper right corner of the subscription."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0
msgid "Renew a quotation with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:61
msgid "By clicking on the *Sales* button, you have a summary of your sales orders in a list view. The only difference between your two quotations is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your renewal."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0
msgid "Renewal as Subscription Management form in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:70
msgid "Visualize your subscriptions to renew"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:72
msgid "Finally, if you want to visualize all your subscriptions and easily find those to renew, you can go to your *Subscriptions dashboard* and use the filter *To renew*."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:-1
msgid "List view of all subscriptions and use of the filter to renew in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:3
msgid "Upsell a subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:5
msgid "Subscriptions are recurrent and go on indefinitely. As time passes by, our customers may want to modify them. We must then be able to adapt the prices or change the products’ quantities to accommodate their needs. Two situations can happen:"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:9
msgid "**Loyal customers:** This kind of customers already trust you as a brand. Therefore, you are confident regarding what you offer since they keep paying for your products and services. Consequently, it is easier to sell them something additional than it would be to a new customer."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:14
msgid "**New customers:** For this kind of customers, you have to come with something new, something attractive. What about discounts? Typically, every subscription ends after a certain given time. Making these types of offers for new customers strengthens your relationships with them and also increases their retention."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:27
msgid "As previously explained, to upsell a subscription to new customers, it is recommended to offer *Discounts*. To activate this option, go to :menuselection:`Sales --> Configuration --> Settings` and, under the *Pricing* category, you have the possibility to grant discounts on sales order lines."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1
msgid "Activation of the discount option in Odoo Sales"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:36
msgid "Upsell your first subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:38
msgid "Before upselling a subscription, be sure to check out our documentation on how to :doc:`Create a quotation <../../subscriptions/sales_flow/create_a_quotation>` using subscription products. Indeed, 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 upsell your subscription."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1
msgid "Upsell your subscription with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:48
msgid "By using the smart button *Upsell*, you are able to create a new quotation with new subscription products and send it to your customers for approval."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1
msgid "Add products to your subscription via the upsell option in Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:56
msgid "When the quotation is confirmed by your customers, the 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/sales_flow/upselling.rst:60
msgid "Of course, before sending this new quotation to your customers, you can change the unit price, taxes, and, even the discount you want to offer. The smart button *Customer preview* is useful for mimicking the customer's reaction. In this case, we can confidently say that the customer will *Sign and pay* this new quotation. When it is done, you have to go back in edit mode, confirm the quotation, and click on the smart button *Subscriptions* to visualize all updates. From there, you can see that an additional line has been added to the subscription with the new extra service the customer wanted to purchase."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1
msgid "Visualize all your subscriptions updates with Odoo Subscriptions"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:72
msgid "In addition, by clicking on the *Sales* button, you have a summary of your sales orders in a list view."
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:-1
msgid "List view of all sales orders created for a subscription"
msgstr ""
#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:79
msgid "The only difference between your two sales orders is the description underneath the *Subscription Management* category. There, you can easily visualize which one is your upselling."
msgstr ""
Reference in New Issue View Git Blame Copy Permalink