# SOME DESCRIPTIVE TITLE. # Copyright (C) Odoo S.A. # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # # Translators: # JonathanStein , 2020 # peso , 2020 # Pernille Kristensen , 2020 # lhmflexerp , 2021 # Jonathan Stein , 2021 # Martin Trigaux, 2021 # Sanne Kristensen , 2021 # Mads Søndergaard, 2021 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-05-18 07:12+0200\n" "PO-Revision-Date: 2020-09-22 14:41+0000\n" "Last-Translator: Mads Søndergaard, 2021\n" "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: da\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #: ../../content/applications/sales.rst:3 #: ../../content/applications/sales/sales.rst:4 msgid "Sales" msgstr "Salg" #: ../../content/applications/sales/crm.rst:4 msgid "CRM" msgstr "CRM" #: ../../content/applications/sales/crm/acquire_leads.rst:3 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/generate_from_website.rst:41 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:8 #: ../../content/applications/sales/crm/optimize/gamification.rst:11 #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:27 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9 #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:12 #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:9 #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:14 #: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:12 #: ../../content/applications/sales/point_of_sale/payment/six.rst:15 #: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:13 #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:14 #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:10 #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:9 #: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:17 #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:8 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:114 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:9 #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:16 #: ../../content/applications/sales/subscriptions/configuration.rst:3 #: ../../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 "Konfiguration" #: ../../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 "Flet kundeemner" #: ../../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_from_email.rst:3 msgid "Generate leads/opportunities from emails" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_email.rst:5 msgid "" "Automating the lead/opportunity generation will considerably improve your " "efficiency. By default, any email sent to *sales@database\\_domain.ext* will" " create an opportunity in the pipeline of the default sales channel." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_email.rst:11 msgid "Configure email aliases" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_email.rst:13 msgid "" "Each sales teams can have its own email alias, to generate " "leads/opportunities automatically assigned to it. It is useful if you manage" " several sales teams with specific business processes. You will find the " "configuration of sales teams under :menuselection:`Configuration --> Sales " "Teams`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:3 msgid "Generate leads/opportunities from your website contact page" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:5 msgid "" "Automating the lead/opportunity generation will considerably improve your " "efficiency. Any visitor using the contact form on your website will create a" " lead/opportunity in the pipeline." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:10 msgid "Use the contact us on your website" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:12 msgid "You should first go to your website app." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:14 msgid "|image0|\\ |image1|" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:16 msgid "" "With the CRM app installed, you benefit from a ready-to-use contact form on " "your Odoo website that will generate leads/opportunities automatically." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:23 msgid "" "To change to a specific sales channel, go to :menuselection:`Website --> " "Configuration --> Settings` under *Communication* you will find the Contact " "Form info and where to change the *Sales Channel* or *Salesperson*." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:32 #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:50 msgid "Create a custom contact form" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:34 msgid "" "You may want to know more from your visitor when they use the contact form " "to you will need to build a custom contact form on your website. These " "contact forms can generate multiple types of records in the system (emails, " "leads/opportunities, project tasks, helpdesk tickets, etc.)" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:43 msgid "" "You will need to install the free *Form Builder* module, only available in " "Odoo Enterprise." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:52 msgid "" "First, go to the page where you want to put your contact form. In edit mode," " drag the form builder onto the page, and you will be able to add all the " "fields you wish." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:59 msgid "" "By default, any new contact form will send an email. You can switch to " "lead/opportunity generation in *Change Form Parameters*." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:63 msgid "" "If the same visitor uses the contact form twice, the second entry will be " "added to the first lead/opportunity in the chatter." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:67 msgid "Generate leads instead of opportunities" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_from_website.rst:69 msgid "" "When using a contact form, you should use a qualification step before " "assigning the form to the right sales people. To do so, activate *Leads* in " "CRM settings and refer 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:4 msgid "" "In any business, getting quality leads is essential to keep the business " "growing. Lead mining allows you to generate leads from scratch directly from" " your database. Target your leads based on a set of criteria such as the " "country, the size of the company, the industry your leads are coming from to" " make them relevant to your business." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 msgid "" "For this feature to work, go to :menuselection:`CRM --> Configuration --> " "Settings` and activate the **Lead Mining** feature." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:17 msgid "Start generating leads" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:18 msgid "" "You will now have a new button **Generate Leads** available in your " "pipeline. You are also able to create lead mining requests from the " ":menuselection:`Configuration --> Lead Mining Requests` and trough " ":menuselection:`Leads --> Leads` where you have the **Generate Leads** " "button." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:27 msgid "" "From there, click on the **Generate Leads** button, a window where you will " "be able to pick your criteria will pop up." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:34 msgid "" "When choosing to target Companied and their contacts you can choose the " "contacts you are getting based on Role or Seniority. When getting contact " "information make sure to be aware of the latest EU regulation, get more " "information about General Data Protection Regulation on `Odoo GDPR " "`__," msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:39 msgid "" "You can decide to filter the leads you are getting depending on the size " "(number of employees) of the companies. You can pick the countries your " "leads are coming from. It is possible to pick multiple countries. You can " "pick the industries your leads are coming from. It is possible to pick " "multiple industries." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:43 msgid "" "You can choose the salesperson and the Salesteam the lead will be assigned " "to. You can also add tags to track your generated leads." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:47 msgid "The generated leads will have the name of the company." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:50 #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:138 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36 msgid "Pricing" msgstr "Priser" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51 msgid "" "This is an In-App Purchase feature, each generated lead will cost you one " "credit. If you choose to get contact information each contact will also cost" " us one additional credit. Here is the pricing for this `feature " "`__, To buy credits you can " "either go to :menuselection:`CRM --> Configuration --> Settings --> Buy " "Credits`; or go to :menuselection:`Settings --> In-App Purchases --> View my" " Services`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:65 msgid "" "The blue box will automatically tell you how many credits are going to be " "consumed." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:68 #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:169 msgid "" "If you are on Odoo Online (SAAS) and have the Enterprise version, you " "benefit from free trial credits to test the feature." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:71 msgid "" ":doc:`In-App Purchases (IAP) " "`" 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:3 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: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: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: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: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/outlook_extension.rst:3 msgid "Outlook Extension" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:5 msgid "" "The **Odoo CRM Extension** is a connector that bridges your Outlook mailbox " "with your Odoo database. This extension allows you to:" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:8 msgid "Create leads from emails sent to your mailbox." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:9 msgid "Centralize Prospects' emails into a CRM." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:10 msgid "Search and store insights on your contacts." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:17 msgid "" "This extension is compatible with the Web version of Outlook as well as the " "desktop apps." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:20 msgid "" "The Outlook Extension uses *Partner Autocomplete IAP credits* to search and " "store insights on your contacts. See the :ref:`Pricing section " "` below for more information." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:29 msgid "" "The Outlook Extension requires to be configured both in Odoo and in Outlook." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:34 msgid "Enable the feature on your database" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:36 msgid "" "To enable this feature on your Odoo database, go to :menuselection:`CRM --> " "Configuration --> Lead Generation`, enable **Outlook CRM Extension**, and " "click on *Save*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:42 msgid "Install the add-in on Outlook" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:44 msgid "" "You can install the Outlook Extension as a **Custom Add-in**. To do so, " "follow these steps:" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:0 msgid "URL of the **Odoo for Outlook** add-in's manifest file:" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:0 #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:0 msgid "``https://download.odoo.com/plugins/outlook/manifest.xml``" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:50 msgid "Todo" msgstr "To Do" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:50 msgid "add copy button when the feature is added to the doc" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:52 msgid "" "Connect to your Outlook mailbox, open any email, and click on the *More " "actions* button, displayed as three little dots." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:59 msgid "Click on *Get add-ins*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:65 msgid "" "In the new window, select the tab named *My add-ins*, click on *+ Add a " "custom add-in*, and then on *Add from URL...*" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:0 msgid "" "Outlook prompts you to **enter the URL of the add-in's manifest file**. To " "do so, copy the following URL, paste it in the box, and click on *OK*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:80 msgid "" "Outlook warns you that Microsoft hasn’t verified the add-in. Click on " "*Install* to complete the installation." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:84 msgid "" "The *Odoo for Outlook* add-in is not listed yet on Outlook's add-ins list. " "This is why it is currently necessary to install it as a *custom add-in*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:90 msgid "Add a shortcut to open the extension" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:92 msgid "" "By default, you can open the **Odoo for Outlook** extension from the *More " "actions* menu. This section explains how to move the launcher next to the " "other default actions." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:99 msgid "" "In your Outlook mailbox, click on *Settings*, then on *View all Outlook " "settings*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:100 msgid "" "Go to :menuselection:`Settings --> Mail --> Customize actions --> Message " "surface`, select *Odoo for Outlook*, and click on *Save*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:109 msgid "Connect to your database" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:111 msgid "" "Open **Odoo for Outlook** from any email. This opens the extension as a " "panel on the right side of your screen." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:113 msgid "Click on *login* at the bottom of the extension." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:114 msgid "Insert your database's URL then click on *Login*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:120 msgid "" "Log into your database by entering your credentials. Skip this step if you " "are already logged in with this browser." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:122 msgid "" "A message asks you if you want to let Outlook access your Odoo database. " "Click on *Allow* to complete the connection." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:126 msgid "" "Make sure first to :ref:`enable the feature on your database " "`. Failing to do so would result in an " "*error 404 message*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:130 msgid "" "The extension displays some information, even if you do not connect it to " "any Odoo database. Note that only a limited amount of contact enrichment " "requests are available as a trial, as this feature requires prepaid credits." " See the :ref:`Pricing section ` below for more " "information." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:140 msgid "" "The extension is **free** and doesn't require any purchase to be installed " "and used." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:142 msgid "" "However, this extension provides you with *Lead Enrichment* in the **Company" " Insights** section. This service is part of a paid service known as **Lead " "Generation**." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:145 msgid "" "The extension allows you to test this service for free, whether you connect " "the extension to a database or not. After a while, the extension asks you to" " buy credits to keep using this additional service." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:155 msgid "" "You can buy more *Lead Generation* credits to keep using this service or " "disregard this message and keep using the extension for free without *Lead " "Enrichment*." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:159 msgid "In-App Purchase" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:162 msgid "" "*Lead Generation* is an *In-App Purchase (IAP)* service, which requires " "prepaid credits to be used. Each request consumes one credit." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:164 #: ../../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/outlook_extension.rst:167 msgid "" "If you run out of credits, the only information populated when clicking on " "the suggested company is the website link and logo." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:171 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:48 msgid "" "Learn about our *Privacy Policy* `here " "`_." msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:174 msgid ":doc:`../../../general/in_app_purchase/in_app_purchase`" msgstr "" #: ../../content/applications/sales/crm/optimize/outlook_extension.rst:175 msgid "`Odoo Tutorials: Lead Enrichment `_" 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: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: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: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 (SAAS) and you have the Enterprise version, you " "benefit from free trial credits to test the feature." msgstr "" #: ../../content/applications/sales/crm/performance.rst:3 msgid "Analyze performance" 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:3 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 "" "While working with your opportunities, you might lose some of them. You will" " want to keep track of the reasons you lost them and also which ways Odoo " "can help you recover them in the future." 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 "" "While in your pipeline, select any opportunity you want and you will see a " "*Mark Lost* button." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 msgid "" "You can then select an existing *Lost Reason* or create a new one right " "there." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:22 msgid "Manage & create lost reasons" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:24 msgid "" "You will find your *Lost Reasons* under :menuselection:`Configuration --> " "Lost Reasons`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:26 msgid "" "You can select & rename any of them as well as create a new one from there." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:30 msgid "Retrieve lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:32 msgid "" "To retrieve lost opportunities and do actions on them (send an email, make a" " feedback call, etc.), select the *Lost* filter in the search bar." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 msgid "You will then see all your lost opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 msgid "" "If you want to refine them further, you can add a filter on the *Lost " "Reason*." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 msgid "For Example, *Too Expensive*." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:50 msgid "Restore lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:52 msgid "" "From the Kanban view with the filter(s) in place, you can select any " "opportunity you wish and work on it as usual. You can also restore it by " "clicking on *Archived*." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:59 msgid "" "You can also restore items in batch from the Kanban view when they belong to" " the same stage. Select *Restore Records* in the column options. You can " "also archive the same way." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 msgid "To select specific opportunities, you should switch to the list view." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 msgid "" "Then you can select as many or all opportunities and select the actions you " "want to take." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:78 msgid ":doc:`../performance/win_loss`" msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 msgid "Manage multiple sales teams" msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:5 msgid "" "In Odoo, you can manage several sales teams, departments or channels with " "specific sales processes. To do so, we use the concept of *Sales Channel*." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:10 msgid "Create a new sales channel" msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12 msgid "" "To create a new *Sales Channel*, go to :menuselection:`Configuration --> " "Sales Channels`." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:14 msgid "" "There you can set an email alias to it. Every message sent to that email " "address will create a lead/opportunity." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:21 msgid "Add members to your sales channel" msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:23 msgid "" "You can add members to any channel; that way those members will see the " "pipeline structure of the sales channel when opening it. Any " "lead/opportunity assigned to them will link to the sales channel. Therefore," " you can only be a member of one channel." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:28 msgid "This will ease the process review of the team manager." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:33 msgid "" "If you now filter on this specific channel in your pipeline, you will find " "all of its opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40 msgid "Sales channel dashboard" msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:42 msgid "" "To see the operations and results of any sales channel at a glance, the " "sales manager also has access to the *Sales Channel Dashboard* under " "*Reporting*." msgstr "" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46 msgid "" "It is shared with the whole ecosystem so every revenue stream is included in" " it: Sales, eCommerce, PoS, etc." msgstr "" #: ../../content/applications/sales/crm/track_leads.rst:3 msgid "Assign and track leads" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:3 msgid "Assign leads based on scoring" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5 msgid "" "With *Leads Scoring* you can automatically rank your leads based on selected" " criterias." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:8 msgid "" "For example you could score customers from your country higher or the ones " "that visited specific pages on your website." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:14 msgid "" "To use scoring, install the free module *Lead Scoring* under your *Apps* " "page (only available in Odoo Enterprise)." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:21 msgid "Create scoring rules" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:23 msgid "" "You now have a new tab in your *CRM* app called *Leads Management* where you" " can manage your scoring rules." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:26 msgid "" "Here's an example for a Canadian lead, you can modify for whatever criteria " "you wish to score your leads on. You can add as many criterias as you wish." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:33 msgid "" "Every hour every lead without a score will be automatically scanned and " "assigned their right score according to your scoring rules." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 msgid "Assign leads" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:42 msgid "" "Once the scores computed, leads can be assigned to specific teams using the " "same domain mechanism. To do so go to :menuselection:`CRM --> Leads " "Management --> Team Assignation` and apply a specific domain on each team. " "This domain can include scores." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49 msgid "" "Further on, you can assign to a specific vendor in the team with an even " "more refined domain." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:52 msgid "" "To do so go to :menuselection:`CRM --> Leads Management --> Leads " "Assignation`." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:58 msgid "" "The team & leads assignation will assign the unassigned leads once a day." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 msgid "Evaluate & use the unassigned leads" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64 msgid "" "Once your scoring rules are in place you will most likely still have some " "unassigned leads. Some of them could still lead to an opportunity so it is " "useful to do something with them." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68 msgid "" "In your leads page you can place a filter to find your unassigned leads." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:73 msgid "" "Why not using :menuselection:`Email Marketing` or :menuselection:`Marketing " "Automation` apps to send a mass email to them? You can also easily find such" " unassigned leads from there." 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:4 msgid "Point of Sale" msgstr "POS" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features.rst:3 msgid "Pricing Features" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:3 msgid "Using discount tags with a barcode scanner" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/discount_tags.rst:10 msgid "To use discount tags you will need to use a barcode scanner." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:13 msgid "Barcode Nomenclature" msgstr "Stregkode plan" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discount_tags.rst:15 msgid "To use discounts tags, we need to learn about barcode nomenclature." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/discount_tags.rst:41 msgid "Scan the products & tags" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/discounts.rst:3 msgid "Apply Discounts" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/discounts.rst:13 msgid "Apply manual discounts" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/discounts.rst:22 msgid "Apply a discount on a product" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:24 msgid "From your PoS session interface, use the *Disc* button." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:30 msgid "" "Then, you can input a discount over the product that is currently selected." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:34 msgid "Apply a global discount" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/discounts.rst:39 msgid "" "Once on your PoS form, select *Global Discounts*, under the *Pricing* " "category." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:45 msgid "Now, you have a new *Discount* button appearing on your PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/discounts.rst:51 msgid "Click on it and enter the wanted discount." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/discounts.rst:62 msgid "Apply time-limited discounts" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/discounts.rst:77 msgid "Create a pricelist" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/discounts.rst:92 msgid "Using a pricelist with the PoS interface" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/loyalty.rst:3 msgid "Manage a loyalty program" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/loyalty.rst:19 msgid "From there you can create and edit your loyalty programs." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/loyalty.rst:30 msgid "Use the loyalty program in your PoS interface" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/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/advanced_pricing_features/pricelists.rst:3 msgid "Using Pricelists in Point of Sale" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:5 msgid "" "You probably know the concept of happy hour: during a certain period of " "time, the barman gives a discount on some drinks (usually 50% off or a buy " "one get one free). When the period is over, prices go back to normal. But " "how does that relate with Odoo?" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:10 msgid "" "In Odoo, you can set up happy hours. It’s one of the many possible uses of " "*Pricelists*. Those *Pricelists* allow the creation of multiple prices for " "the same product: a regular one and a special one for happy hours. Available" " in the *PoS* app, those are really convenient." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:17 msgid "Set up Pricelists" msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:19 msgid "" "To set up a *Pricelist*, go to :menuselection:`Point of Sale --> " "Configuration --> Configuration` and enable the *Pricelist* feature. Then, " "go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and" " enable *Pricelist* for the *PoS*." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:26 msgid "" "Now, you can create *Pricelists* by clicking on the *Pricelists* link. Then," " set it up by choosing the product category you want to include in your " "happy hour and the discount." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:33 msgid "" "Go back to your *PoS* settings and add the Happy Hour pricelist to the list." " You can even choose a default pricelist if needed." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:39 msgid "" "From now on, on the *PoS* interface, a new button is available, allowing you" " to choose among the different *pricelists* you added before." msgstr "" #: ../../content/applications/sales/point_of_sale/advanced_pricing_features/pricelists.rst:46 msgid ":doc:`../../sales/products_prices/prices/pricing`" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm.rst:3 msgid "Fiscal Data Modules" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:3 msgid "Setting up the Fiscal Data Module with the Odoo POS" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:6 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:170 msgid "Introduction" msgstr "Introduktion" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:8 msgid "" "The Belgian government requires certain businesses to use a government-" "certified device called a **Fiscal Data Module** (also known as a " "**blackbox**). This device works together with the POS application and logs " "certain transactions. On top of that, the used POS application must also be " "certified by the government and must adhere to strict standards specified by" " them. `Odoo 9 (Enterprise Edition) is a certified application " "`_. More " "information concerning the Fiscal Data Module can be found on `the official " "website `_." msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:20 msgid "Required hardware" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:22 msgid "" "A government certified `Fiscal Data Module " "`_ per POS, all of them should work, but the " "Cleancash SC-B is recommended, you will also need:" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:27 msgid "" "Serial null modem cable per FDM (`example `__)" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:29 msgid "" "Serial-to-USB adapter per FDM (`example " "`__)" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:32 msgid "A registered IoT Box per POS configuration" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:35 msgid "Setup" msgstr "Opsætning" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:38 msgid "IoT Box" msgstr "IoT Boks" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:40 msgid "" "In order to use a Fiscal Data Module, you will need a registered IoT Box. " "These IoT Boxes are similar to the regular IoT Boxes we sell, but they are " "registered with the Belgian government. This is required by law. Attempting " "to use a Fiscal Data Module on a non-registered IoT Box will not work. You " "can verify that the Fiscal Data Module is recognized by the IoT Box by going" " to the *Hardware status page* via the IoT Box homepage." msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:52 msgid "Odoo" msgstr "Odoo" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:54 msgid "" "An Odoo POS app can be given certified POS capabilities by installing the " "**Belgian Registered Cash Register** app (technical name: " "``pos_blackbox_be``). Because of government restrictions imposed on us, this" " installation cannot be undone. After this, you will have to ensure that " "each POS configuration has a unique registered IoT Box associated with it " "(:menuselection:`Point of Sale --> Configuration --> Point of Sale` and " "ensure Hardware Proxy / IoT Box and the serial number of your IoT Box is " "set). The first time you open the Point of Sale and attempt to do a " "transaction, you will be asked to input the PIN that you received with your " "VAT signing card." msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:69 msgid "Certification & On-premise" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:71 msgid "" "The certification granted by the government is restricted to the use on " "odoo.com SaaS instance. The usage of the module from the source or a " "modified version will **not** be certified. For on-premise users, we also " "support the Fiscal Data Module in such installations. The main restriction " "is that this requires an obfuscated version of the ``pos_blackbox_be`` " "module we will provide on request for Enterprise customers." msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:79 msgid "Restrictions" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:81 msgid "" "As mentioned before, in order to get certified the POS application must " "adhere to strict government guidelines. Because of this, a certified Odoo " "POS has some limitations not present in the non-certified Odoo POS." msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:86 msgid "Refunding is disabled" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:87 msgid "Modifying orderline prices" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:88 msgid "Creating/modifying/deleting POS orders" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:89 msgid "Selling products without a valid tax" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:90 msgid "Multiple Odoo POS configurations per IoT Box are not allowed" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:91 msgid "Using the POS without a connection to the IoT Box (and thus FDM)" msgstr "" #: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:92 msgid "Blacklisted modules: pos_discount, pos_reprint, pos_loyalty" msgstr "" #: ../../content/applications/sales/point_of_sale/overview.rst:3 msgid "Overview" msgstr "Oversigt" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:3 msgid "Getting started" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:5 msgid "" "When working with a Point of Sale application, employees want a simple, and " "user-friendly solution. A solution that works online or offline and with any" " device." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:9 msgid "" "A Point of Sale system is a fully integrated application that allows any " "transaction, automatically registers product moves in your stock, and gives " "you real-time statistics and consolidations across all shops." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:17 msgid "Make products available in the PoS" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:19 msgid "" "To make products available for sale, go to :menuselection:`Point of Sale -->" " Products --> Products` and open a product. In the *Sales* tab, enable " "*Available in Point of Sale*." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:28 msgid "You can also define if the product has to be weighted or not." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:31 msgid "Configure your payment methods" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:33 msgid "" "To add a payment method, you first need to create it. Go to " ":menuselection:`Point of Sale --> Configuration --> Payment Methods` and " "click on create. Then, you can name your payment method and set it up." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:43 msgid "Don’t forget your credentials for methods using a payment terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:45 msgid "" "Now, you can select the payment method in your PoS settings. To do so, go to" " :menuselection:`Point of Sale --> Configuration --> Point of Sale` and open" " the PoS in which you want to include the payment method. Then, add the " "payment method." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:55 msgid "" "*Configuration* is the menu where you can edit all your point of sale " "settings. Some more features are available for restaurants." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:59 msgid "Your first PoS session" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:62 msgid "Your first order" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:64 msgid "Open a new session from the dashboard by clicking on *New Session*." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:70 msgid "After the loading screen, you arrive on the PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:76 msgid "" "Once an order is completed, you can register the payment. All the available " "payment methods appear on the left of the screen. Select the payment method " "and enter the received amount. Then, you can validate the payment." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:82 msgid "Return and refund products" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:84 msgid "" "Having a well-thought-out return policy is key to keep customers satisfied " "and make the process of accepting returns and refunds easy for you." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:87 msgid "" "To do that, from the PoS interface, select the product and quantity (with " "the +/- button) that the customer wants to return. For multiple products, " "repeat the process individually." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:94 msgid "" "When on the payment interface, the total is negative. To end the refund, " "process the payment and validate it." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:102 msgid "Close the PoS session" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:104 msgid "" "To close your session at the end of the day, click on the close button on " "the upper right corner of your screen and confirm. Now, close the session on" " the dashboard view." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:112 msgid "" "It’s strongly advised to close your PoS session at the end of each day." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:114 msgid "" "Once a session is closed, you can see a summary of all transactions per " "payment method. Then, click on a line to see all orders that were paid " "during your PoS session. If everything is correct, validate the session and " "post the closing entries." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:123 msgid "" "To connect the PoS hardware with an Odoo IoT Box, please refer to these " "docs: :doc:`Connect an IoT Box to your database " "` and :doc:`Use the IoT Box " "for the PoS `." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:129 msgid "View your statistics" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:131 msgid "" "Keeping track of your sales is essential to get meaningful statistics. " "That’s why Odoo provides analyzes about your sales." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:134 msgid "" "To access your statistics, go to :menuselection:`Point of Sales --> " "Reporting --> Orders`. There, you can see various statistics in graph or " "pivot form." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:142 msgid "You can also access them through the dashboard." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/register.rst:3 msgid "Register customers" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/register.rst:5 msgid "" "Registering your customers will give you the ability to grant them various " "privileges such as discounts, loyalty program, specific communication. It " "will also be required if they want an invoice and registering them will make" " any future interaction with them faster." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/register.rst:11 msgid "Create a customer" msgstr "" #: ../../content/applications/sales/point_of_sale/overview/register.rst:13 msgid "From your session interface, use the customer button." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/register.rst:18 msgid "Create a new one by using this button." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/register.rst:23 msgid "" "You will be invited to fill out the customer form with their information." msgstr "" #: ../../content/applications/sales/point_of_sale/overview/register.rst:29 msgid "" "Use the save button when you are done. You can then select that customer in " "any future transactions." msgstr "" #: ../../content/applications/sales/point_of_sale/payment.rst:3 msgid "Payment Terminals" msgstr "Betaling terminaler" #: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:3 msgid "Connect an Ingenico Payment Terminal to your PoS" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/ingenico.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/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/ingenico.rst:15 msgid "Connect an IoT Box" msgstr "Forbind til en IoT boks" #: ../../content/applications/sales/point_of_sale/payment/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 " "`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:22 msgid "Configure the Lane/5000 for Ingenico BENELUX" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/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/ingenico.rst:27 msgid "" "Now, click on connexion 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/ingenico.rst:36 msgid "Configure the payment method" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/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/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/ingenico.rst:53 msgid "Pay with a payment terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/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/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/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 connexion between the terminal and Odoo has issues." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:73 msgid "" "This option will only be available if you received an error message telling " "you the connexion failed." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/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/six.rst:3 msgid "Connect a SIX Payment Terminal to your PoS" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/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/six.rst:9 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/six.rst:18 #: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:16 msgid "Configure the Payment Method" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/six.rst:20 msgid "" "First, make sure that the POS Six module is installed. For this, go to " "*Apps*, remove the \"Apps\" filter and search for \"POS Six\"." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/six.rst:26 msgid "" "Back in :menuselection:`Point of Sale --> Configuration --> Payment " "Methods`, Create a new payment method for SIX, select the payment terminal " "option \"SIX without IoT Box\", and enter your payment terminal IP address." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/six.rst:34 #: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:40 msgid "Pay with a Payment Terminal" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/six.rst:36 msgid "" "In your PoS 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 *Send*. If " "you want to cancel the payment request, click on cancel." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/six.rst:44 msgid "" "When the payment is done, the status will change to *Payment Successful*. " "You can always reverse the last transaction by clicking on *Reverse*." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/six.rst:51 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 connexion between the terminal and Odoo encounters issues." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:3 msgid "Connect a Vantiv Payment Terminal to your PoS" msgstr "" #: ../../content/applications/sales/point_of_sale/payment/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/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/vantiv.rst:18 msgid "" "First, go in the general settings of the POS app, and activate the Vantiv " "setting." msgstr "" #: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:24 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/vantiv.rst:32 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/vantiv.rst:42 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/restaurant.rst:3 msgid "Restaurant Features" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 msgid "Print the Bill" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5 msgid "" "Use the *Bill Printing* feature to print the bill before the payment. This " "is useful if the bill is still subject to evolve and is thus not the " "definitive ticket." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 msgid "Configure Bill Printing" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 msgid "" "To activate *Bill Printing*, go to :menuselection:`Point of Sale --> " "Configuration --> Point of sale` and select your PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:15 msgid "" "Under the Bills & Receipts category, you will find *Bill Printing* option." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:22 msgid "Split a Bill" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:24 msgid "On your PoS interface, you now have a *Bill* button." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:29 msgid "When you use it, you can then print the bill." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:3 msgid "Using fiscal positions in PoS" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/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/restaurant/fiscal_position.rst:11 msgid "Set up fiscal positions for PoS" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/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/restaurant/fiscal_position.rst:21 msgid "You need to create your fiscal positions before using this feature." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:24 msgid "Using fiscal positions" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/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/restaurant/fiscal_position.rst:33 msgid "Set up a default fiscal position" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/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/restaurant/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/restaurant/kitchen_printing.rst:3 msgid "Print orders at the kitchen or bar" 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/restaurant.rst:3 msgid "Manage your tables" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:5 msgid "" "Restaurants have specific needs that shops don’t have. That’s why Odoo gives" " restaurant owners several unique features to help them manage their " "business in the best possible way." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:9 msgid "" "Floor and table management, bill splitting, or even the possibility to print" " orders from the kitchen, everything is there to help your business shine " "and your employees to work efficiently." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:16 msgid "" "To activate the bar/restaurant features, go to :menuselection:`Point of Sale" " --> Configuration --> Point of Sale` and open your PoS. Now, select *Is a " "Bar/Restaurant*." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:24 msgid "" "New features are shown with a fork and a knife next to it, indicating that " "they are restaurant-specific." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:32 msgid "Add a floor" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:34 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/restaurant.rst:47 msgid "Don’t forget to link your floor to your point of sale." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:50 msgid "Add tables" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:52 msgid "" "To add tables, you can also open your PoS interface to see your floor(s)." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:59 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/restaurant.rst:67 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/restaurant.rst:72 msgid "Register your table(s) orders" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:74 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/restaurant.rst:82 msgid "Transfer customer(s)" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:84 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/restaurant.rst:88 msgid "To do so, select the table your customer is currently on." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:94 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/restaurant.rst:103 msgid "Register an additional order" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:105 msgid "" "When registering an order, use the + button to simultaneously proceed to " "another one." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:108 msgid "" "Then, you can shift between your orders and process the payment when needed." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:116 msgid "The - button allows you to remove the order you are currently on." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:3 msgid "Offer a bill-splitting option" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:5 msgid "" "Offering an easy bill splitting solution to your customers will leave them " "with a positive experience. That's why this feature is available out-of-the-" "box in the Odoo Point of Sale application." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:12 msgid "" "To activate the *Bill Splitting* feature, go to :menuselection:`Point of " "Sales --> Configuration --> Point of sale` and select your PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:16 msgid "" "Under the Bills & Receipts category, you will find the Bill Splitting " "option." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:23 msgid "Split a bill" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:25 msgid "In your PoS interface, you now have a *Split* button." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/split.rst:30 msgid "" "When you use it, you will be able to select what that guest should had and " "process the payment, repeating the process for each guest." msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3 msgid "Integrate a tip option into payment" 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:3 msgid "Shop Features" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:3 msgid "Using barcodes in PoS" 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 and helps you to save time for you and your customers." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:11 msgid "" "To use a barcode scanner, go to :menuselection:`Point of Sale --> " "Configuration --> Point of sale` and select your PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:14 msgid "" "Under the IoT Box / Hardware category, you will find *Barcode Scanner* " "select it." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:21 msgid "Add barcodes to product" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:23 msgid "" "Go to :menuselection:`Point of Sale --> Catalog --> Products` and select a " "product." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:26 msgid "" "Under the general information tab, you can find a barcode field where you " "can input any barcode." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:33 msgid "Scanning products" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:35 msgid "" "From your PoS interface, scan any barcode with your barcode scanner. The " "product will be added, you can scan the same product to add it multiple " "times or change the quantity manually on the screen." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:3 msgid "Set-up Cash Control in Point of Sale" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:5 msgid "" "Cash control allows you to check the amount of the cashbox at the opening " "and closing. You can thus make sure no error has been made and that no cash " "is missing." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:10 msgid "Activate Cash Control" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:12 msgid "" "To activate the *Cash Control* feature, go to :menuselection:`Point of Sales" " --> Configuration --> Point of sale` and select your PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:16 msgid "Under the payments category, you will find the cash control setting." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:21 msgid "" "In this example, you can see I want to have 275$ in various denomination at " "the opening and closing." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:24 msgid "" "When clicking on **Opening/Closing Values** you will be able to create those" " values." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:31 msgid "Start a session" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:33 msgid "" "You now have a new button added when you open a session, *Set opening " "Balance*" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:42 msgid "" "By default it will use the values you added before, but you can always " "modify it." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:46 msgid "Close a session" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:48 msgid "" "When you want to close your session, you now have a *Set Closing Balance* " "button as well." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:51 msgid "" "You can then see the theoretical balance, the real closing balance (what you" " have just counted) and the difference between the two." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_control.rst:57 msgid "" "If you use the *Take Money Out* option to take out your transactions for " "this session, you now have a zero-sum difference and the same closing " "balance as your opening balance. You cashbox is ready for the next session." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:3 msgid "Cash Rounding" msgstr "Kontantafrunding" #: ../../content/applications/sales/point_of_sale/shop/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/shop/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/shop/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/shop/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/shop/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/shop/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/shop/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/shop/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/shop/cash_rounding.rst:46 msgid "" "Odoo Point of Sale only support the *Add a rounding line* rounding " "strategies and *Half-up* rounding methods." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:3 msgid "Invoice from the PoS interface" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:5 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/shop/invoice.rst:9 msgid "Activate invoicing" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:11 msgid "" "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and" " select your Point of Sale:" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:17 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/shop/invoice.rst:25 msgid "Select a customer" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:27 msgid "From your session interface, use the customer button" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:32 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/shop/invoice.rst:38 msgid "" "You will be invited to fill out the customer form with its information." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:41 msgid "Invoice your customer" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:43 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/shop/invoice.rst:49 msgid "You can then print the invoice and move on to your next order." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:52 msgid "Retrieve invoices" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/invoice.rst:54 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/shop/multicashiers.rst:3 msgid "Log in with employee" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.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/shop/multicashiers.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/shop/multicashiers.rst:13 msgid "" "To manage multiple cashiers, you need several employees (at least two)." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:16 msgid "Set up log in with employees" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:18 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/shop/multicashiers.rst:25 msgid "Now, you can switch cashier easily." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:28 msgid "Switch without pin codes" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:30 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/shop/multicashiers.rst:36 msgid "Now, you just have to click on your name." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:42 msgid "Switch cashier with pin codes" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:44 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/shop/multicashiers.rst:50 msgid "Now, when switching cashier, a PIN password will be asked." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:56 msgid "Switch cashier with barcodes" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:58 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/shop/multicashiers.rst:67 msgid "Find who was the cashier" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:69 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/shop/multicashiers.rst:75 msgid "Now, you can open the order and have a summary of the sold products." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:3 msgid "Reprint Receipts" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:5 msgid "" "Use the *Reprint receipt* feature if you have the need to reprint a ticket." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:10 msgid "" "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> " "Configuration --> Point of sale`. and select your PoS interface." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:13 msgid "" "Under the Bills & Receipts category, you will find *Reprint Receipt* option." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:17 msgid "" "In order to allow the option reprint receipt, you need to activate the " "receipt printer." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:23 msgid "Reprint a receipt" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:25 msgid "On your PoS interface, you now have a *Reprint receipt* button." msgstr "" #: ../../content/applications/sales/point_of_sale/shop/reprint.rst:30 msgid "When you use it, you can then reprint your last receipt." msgstr "" #: ../../content/applications/sales/sales/advanced.rst:3 msgid "Advanced Topics" msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:3 msgid "How to give portal access rights to my customers?" msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:6 msgid "What is Portal access/Who is a portal user?" msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:8 msgid "" "A portal access is given to a user who has the necessity to have access to " "Odoo instance, to view certain documents or information in the system." msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:12 msgid "For Example, a long term client who needs to view online quotations." msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:14 msgid "" "A portal user has only read/view access. He or she will not be able to edit " "any document in the system." msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:18 msgid "How to give portal access to customers?" msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:21 msgid "From Contacts Module" msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:23 msgid "" "From the main menu, select **Contacts** menu. If the contact is not yet " "created in the system, click on the create button to create new contact. " "Enter details of the contact and click \"save\"." msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:33 msgid "" "Choose a contact, click on the **Action** menu in the top-center of the " "interface and from the drop down." msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:36 msgid "Select **Portal Access Management**. A pop up window appears." msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:41 msgid "" "Enter the login **email ID**, check the box under **In Portal** and add the " "content to be included in the email in the text field box below. Click on " "**Apply** when you're done." msgstr "" #: ../../content/applications/sales/sales/advanced/portal.rst:47 msgid "" "An email will be sent to the specified email address, indicating that the " "contact is now a portal user of the respective instance." msgstr "" #: ../../content/applications/sales/sales/amazon_connector.rst:3 msgid "Amazon Connector" msgstr "Amazon forbinder" #: ../../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 #: ../../content/applications/sales/sales/amazon_connector/features.rst:34 msgid "Charges" msgstr "Gebyrer" #: ../../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 `." 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 "Canada" #: ../../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 "Mexico" #: ../../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 "Tyskland" #: ../../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 "Spanien" #: ../../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 "Frankrig" #: ../../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 "Italien" #: ../../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 "Holland" #: ../../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:98 msgid ":doc:`setup`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:89 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:162 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 :doc:`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:26 msgid "" "To synchronize immediately the orders of your Amazon account switch to " ":doc:`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:31 msgid "Manage deliveries in FBM" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:33 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:37 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:41 msgid "Follow deliveries in FBA" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:43 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:50 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:55 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:63 msgid "Issue invoices and register payments" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:65 msgid "" "You can issue invoices for Amazon orders in Odoo. Click **Create Invoice** " "in the sales order to do so. You can also do it in batch from the list view " "of orders. Then, confirm and send the invoices to your customers." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:70 msgid "" "To display only Amazon-related orders on the list view, you can filter " "orders based on the sales team." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:73 msgid "" "As the customer has paid Amazon as an intermediary, you should register " "invoice payments in a payment journal dedicated to Amazon (e.g. Amazon " "Payments, with a dedicated intermediary account). You can do the same with " "the vendor bill received from Amazon and dedicated to commissions. When you " "receive the balance on your bank account at the end of the month and record " "your bank statements in Odoo, you simply credit the Amazon intermediary " "account by the amount received." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:80 msgid "Follow your Amazon sales in sales reporting" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:82 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:86 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:90 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:97 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:161 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 "Generate an Authorization Token in Seller Central" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:10 msgid "" "The Amazon Connector uses an Authorization Token that allows Odoo to fetch " "data from your Amazon Seller Central account. This token can be obtained " "directly through Seller Central in a few clicks and needs to be set up in " "your Odoo database configuration." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:14 msgid "" "Connect to your Seller Central account for the marketplace you initially " "signed up (e.g. if you created your account on Amazon Germany, go to `Amazon" " Seller Central for Germany `_) with an " "administrator account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:19 msgid "" "You might need to use the *main* (or first) administrator account and not " "one added subsequently." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:22 msgid "" "In the main menu, select :menuselection:`Apps & Services --> Manage Your " "Apps`; in the page that displays, click on the ``Authorize new developper`` " "button:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:28 msgid "Fill in the form depending on your Marketplace:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:33 msgid "" "If your seller account is registered in the **North America** region, use " "these values:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:35 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:40 msgid "Developer's Name: ``Odoo S.A.``" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:36 msgid "Developer ID: ``586127723692``" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:38 msgid "For the **Europe** region, use these values:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:41 msgid "Developer ID: ``579095187166``" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:43 msgid "" "Amazon will then inform you that by submitting the form, you are giving " "access to your Seller Central Information to Odoo S.A." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:47 msgid "" "Odoo S.A. is unable to access your Amazon account's information without the " "Authorization Token which is stored in your Odoo database - we do not store " "these tokens on our platform directly and are therefore unable to access " "your account's information outside of the Amazon Connector normal flows." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:53 msgid "Register your Amazon account in Odoo" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:57 msgid "" "To register your seller account in Odoo, navigate to :menuselection:`Sales " "--> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon " "Accounts` and click on **CREATE**." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:60 msgid "" "The **Seller ID** can be found in Seller Central under the link **Your " "Merchant Token** on the **Seller Account Information** page. The " "**Authorization Token** is the one you generated in the :ref:`previous step " "`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:64 msgid "" "Upon saving, your credentials are checked. In case of issues, an error will " "be displayed - the information cannot be saved until your credentials are " "recognized by Amazon." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:67 msgid "" "Once the account is registered, the marketplaces available to this account " "are synchronized and listed under the **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:72 msgid "Match database products in Amazon" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:74 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:80 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:84 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 `." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:90 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:95 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:100 msgid "" "To modify the default products, activate the :doc:`Developer mode " "` and navigate to " ":menuselection:`Sales --> Configuration --> Settings --> Connectors --> " "Amazon Sync --> Default Products`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:106 msgid "Configure taxes of products" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:108 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:114 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:121 msgid "Add an unsupported marketplace" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:123 msgid "" "Some Amazon Marketplaces, such as Amazon Brazil, 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 ` for the exhaustive list of " "natively supported marketplaces." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:129 msgid "" "To find out if a marketplace is eventually compatible, check the `Amazon " "Documentation " "`_." " The marketplace must belong to the same region as that of your seller " "account." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:133 msgid "" "To add a new marketplace, you must first enable :doc:`Developer mode " "`." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:136 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:139 msgid "" "From there, you can create a new marketplace record. You will need the " "Marketplace ID and Endpoint for your marketplace as described in the `Amazon" " Documentation " "`_." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:143 msgid "" "Set the name of the record to ``Amazon.`` to easily retrieve it (for" " instance: ``Amazon.se``). The **Code**, **Domain** and **API Identifier** " "fields should respectively hold the *Country Code*, *Amazon MWS Endpoint* " "and *MarketplaceId* values from the Amazon Documentation." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:147 msgid "" "Once the marketplace is saved, you should then 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 " "**Marketplaces** tab and click on **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:156 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/ebay_connector.rst:3 msgid "eBay Connector" msgstr "eBar forbinder" #: ../../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 sligthly 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 theses 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 `_. 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 "Using the updated synchronisation method" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:42 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:45 msgid "" "To fix this issue, a new implementation mechanism has been developped; " "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:49 msgid "To switch to the new synchronization mechanism:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:51 msgid "" "Enable the :doc:`Developer mode `." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:52 msgid "Go to :menuselection:`Settings --> Technical --> Scheduled Actions`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:53 msgid "" "Archive the old synchronization actions (both are named *Ebay: update " "product status*)" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:54 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:55 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:57 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:3 msgid "Invoicing Method" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 msgid "Request a down payment" 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' full commitment (seller and buyer) " "to honor the contract. With a down payment, the buyers show their will to " "acquire the product and agree to pay the rest later, while the sellers are " "obliged to provide the goods by accepting it." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:10 msgid "" "Sometimes a down payment is required for expensive orders or projects. That " "way, you can protect yourself and make sure that your customer is reliable." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:14 msgid "First time you request a down payment" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:16 msgid "" "When a sales order is confirmed, you then have the possibility to create an " "invoice. Invoices are automatically created in drafts so that you can review" " them before validation. To create an invoice, Odoo Sales offers you 3 " "options:" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:20 msgid "Regular invoice" msgstr "Almindelig faktura" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:21 msgid "Down payment (percentage)" msgstr "Aconto (procent)" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:22 msgid "Down payment (fixed amount)" msgstr "Aconto (fast beløb)" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:24 msgid "" "In terms of down payment, it can either be a fixed amount or a percentage of" " the total amount. The first time you request a down payment, you can set a " "percentage or a fixed amount of your choice, and select the right income " "account and taxes. These settings will be reused for future down payments." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 msgid "" "When you request your first down payment, a new product called **Down " "payment** will be created. This product will be registered as a **service** " "product with an invoicing policy of **ordered quantities**. As a reminder, " "you can edit this product and modify it at any time. Please note that if you" " choose **delivered quantities** as invoicing policy, **you will not be able" " to create an invoice**." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:41 msgid "Basic sales flow using down payments" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:43 msgid "" "For this first example, we will use a 50% amount down payment with a product" " using **ordered quantities** as invoicing policy. Make sure to check out " "our documentation about invoicing policies here: :doc:`invoicing_policy` , " "before requesting your first down payment. When it comes to create and view " "the invoice, you will only have access to a draft invoice mentioning the " "down payment (as you can see below)." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:53 msgid "" "There, you can post the invoice and register the payment of your customer. " "But, we all know that in real life this flow does not happen immediately. " "So, for now, you can return to the sales order. There, you will have the " "possibility to see the order as a customer with the **Customer preview** " "button or to reach easily the previous draft invoice with the **Invoice** " "button. In any case, the down payment will be mentioned on both (sales order" " and draft invoice)." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:63 msgid "" "To complete the flow, when the customer wants to pay the rest of his sales " "order, you must create another invoice. Once again, you will have the choice" " to make another down payment or to deduct all the down payments and so, " "paying the rest of the invoice as a regular invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:71 msgid "" "This flow is also possible with a down payment taking into account a fixed " "amount." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:74 msgid "" "Be careful that if you do a down payment with a product using **delivered " "quantities** as invoicing policy, you won’t be able to deduct all the down " "payments when it comes to invoicing your customer. Indeed, you have to " "deliver a product before creating the final invoice. If nothing has been " "delivered, you create a **credit note** that cancels the draft invoice " "created after the down payment. To do so, you have to install the " "**Inventory App** to confirm the delivery. Otherwise, you can enter the " "delivered quantity manually on the sales order." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:82 msgid "Modify the income account and customer taxes" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:84 msgid "From the products list, search for the **Down Payment** product." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:90 msgid "" "You can edit it and under the **General Information Tab** you will be able " "to change the customer taxes. Now, to change the income account, you will " "need to install the **Accounting App** to have the possibility to see the " "**Accounting Tab** on the product form." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 msgid ":doc:`invoicing_policy`" 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 an " "consultant paying an 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: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: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: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: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 #: ../../content/applications/sales/sales/invoicing/proforma.rst:22 msgid "Send a pro-forma invoice" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:5 msgid "" "A pro-forma invoice is an abridged or estimated invoice 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. Pro-" "forma invoices are commonly used as preliminary invoices with a quotation, " "or for customs purposes in importation. They differ from a normal invoice in" " not being a demand or request for payment." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:13 #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 msgid "Activate the feature" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:15 msgid "" "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the" " *Pro-Forma Invoice* feature." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:24 msgid "" "From any quotation or sales order, you know have an option to send a pro-" "forma invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:30 msgid "" "When you click on send, Odoo will send an email with the pro-forma invoice " "in attachment." 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:3 msgid "Products & Prices" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices.rst:3 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 critarias 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:9 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:19 msgid "" "*Different prices per customer segment :* you will set several prices per " "products ;" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20 msgid "" "*Advanced pricing based on formula :* will let you apply discounts, margins " "and roundings." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:23 msgid "Several prices per product" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:25 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:30 msgid "Prices per customer segment" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:32 msgid "" "Create pricelists for your customer segments: e.g. registered, premium, etc." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:37 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:45 msgid "Temporary prices" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:47 msgid "Apply deals for bank holidays, etc. Enter start and end dates dates." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:53 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:57 msgid "Prices per minimum quantity" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:63 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:67 msgid "Discounts, margins, roundings" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:69 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 (minumum 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:76 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:84 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:91 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:93 msgid "Make sure at least one pricelist item covers all your products." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:95 msgid "There are 3 modes of computation: fix price, discount & formula." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:100 msgid "Here are different price settings made possible thanks to formulas." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:103 msgid "Discounts with roundings" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:105 msgid "e.g. 20% discounts with prices rounded up to 9.99." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111 msgid "Costs with markups (retail)" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:113 msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119 msgid "Prices per country" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120 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:123 msgid "The default pricelist can be replaced when creating a sales order." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:125 msgid "You can change the pricelists sequence by drag & drop in list view." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128 msgid "Compute and show discount % to customers" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:130 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:132 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:133 msgid "Apply the option in the pricelist setup form." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:140 msgid ":doc:`currencies`" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:141 msgid ":doc:`/applications/websites/ecommerce/maximizing_revenue/pricing`" msgstr "" #: ../../content/applications/sales/sales/products_prices/products.rst:3 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" " of 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/variants.rst:3 msgid "Using product variants" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 msgid "" "Product variants are used to manage products having different variations, " "like size, color, etc. It allows managing the product at the template level " "(for all variations) and at the variant level (specific attributes)." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:10 msgid "" "As an example, a company selling t-shirts may have the following product:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:13 msgid "B&C T-shirt" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:15 msgid "Sizes: S, M, L, XL, XXL" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:16 msgid "Colors: Blue, Red, White, Black" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:18 msgid "" "In this example, **B&C T-Shirt** is called the product template and **B&C " "T-Shirt, S, Blue** is a variant. Sizes and color are **attributes**." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:22 msgid "" "The above example has a total of 20 different products (5 sizes x 4 colors)." " Each one of these products has its own inventory, sales, etc." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:26 msgid "Impact of variants" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:28 msgid "" "**Barcode**: the code and barcode is associated to a variant, not the " "template. Every variant may have its own barcode / SKU." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:31 msgid "" "**Price**: every product variant has its own public price that is computed " "based on the template price ($20) with an optional extra for every variant " "(+$3 for color red). However, you can define pricelist rules that apply on " "the template or the variant." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:36 msgid "" "**Inventory**: the inventory is managed by product variant. You don't own " "t-shirts, you only own \"T-shirts, S, Red\", or \"T-Shirts, M, Blue\". For " "information purpose, on the product template form, you get the inventory " "that is the sum of every variant. (but the actual inventory is computed by " "variant)" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:42 msgid "" "**Picture**: the picture is related to the variant, every variation of a " "product may have its own primary picture." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:45 msgid "" "**Other fields**: most of the other fields belongs to the product template. " "If you update them, it updates automatically all the variants. (example: " "Income Account, Taxes)" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:50 msgid "Should you use variants?" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:53 msgid "When should you use variants?" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:55 msgid "Using variants has the following impacts:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:57 msgid "" "**eCommerce**: in your online shop, the customer will only see product " "templates in the catalog page. Once the visitor click on such a product, he " "will have options to choose amongst the variants (colors, sizes, …)" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:62 msgid "" "**Manufacturing**: Using variants allows to define only one bill of material" " for a product template and slight variations for some of the variants. " "Example: instead of creating a Bill of Material for \"T-shirt, Red, S\", you" " create a bill of material for \"T-shirt\" and add some lines that are " "specific to the dimension S, and other lines specific to the color Red." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:69 msgid "" "**Pricing**: The default price of a product is computed using the price of " "the product template and add the optional extra price on each dimension of " "the variant. This way, variant prices are easier to maintain since you don't" " have to set the price for every variant. However, it's possible to create " "pricelist rules to fix price per variants too." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:77 msgid "When should you avoid using variants?" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:79 msgid "" "Using variants may add a level of complexity on the way you use Odoo. You " "should consider using variants only if you need it to reduce the complexity " "of managing lots of products that are similars." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:83 msgid "" "As an example, importing your initial product catalog is more complex if you" " use variants. You can't just import a list of products, you must import " "product templates and all their related variations." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:87 msgid "" "In addition to that, you should also carefully select the dimensions that " "you manage as separate product templates and those as variants. As an " "example, a company having these products:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:91 msgid "Quality: T-Shirts, Polos, Shirts" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:93 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:105 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:110 msgid "Color: Red, Blue" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:95 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:106 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:111 msgid "Size: S, M, L, XL" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:97 msgid "" "In such a use case, you could create 1 template with three dimensions of " "variants (Layout, T-Shirts, Polos). But, it's recommended to create two " "different product templates as T-shirts may highly differ from polos or " "shirts and customer expect to see these as two different products in the " "e-Commerce:" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:103 msgid "Product Template: T-shirt" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:108 msgid "Product Template: Polos" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:117 msgid "Activate the variant feature" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:119 msgid "" "Before you can use product variants, you must first activate the product " "variants in the settings. To do so, you must go to the Sales app. In the " "menu :menuselection:`Configuration --> Settings`, locate the **Products " "Variants** line, and tick the option **Products can have several " "attributes**, then click on **Apply**." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:129 msgid "Creating products with variants" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:131 msgid "" "Once you have activated the variant option, you can add variants to your " "products. To do so, go to the Sales module, :menuselection:`Sales --> " "Products`. It is also accessible from the Purchase and inventory modules." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:135 msgid "Now, click on the product you wish to add variants to." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 msgid "" "In the product page, a new tab called Variants has appeared. The number in " "purple written on top is the number of variants this product currently has. " "To add new variants, click on the tile. In the new window, click on " "**Create**." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:142 msgid "" "In **Attributes**, click on the rolldown menu and select the type of " "variance you wish to add. If the variant does not yet exist, you can create " "it on the fly by clicking on Create and edit…" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:149 msgid "" "In the Attributes window, the **Value** field is the description of the " "attribute such as Green, Plastic or 32GB. The **Attribute** field is the " "type of variant such as Color, Material or Memory." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:156 msgid "" "You can add a cost for the variant on the fly by adding it in the " "**Attribute Price Extra** field, or choose to modify it later. Click on " "**Save**." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:160 msgid "" "You can also add a different barcode and internal reference to the variant." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:163 msgid "" "When you have entered all the specifications of the variant, click on " "**Save**." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:167 msgid "Managing Product Variants" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:172 msgid "" "The examples below are all based on this product template that has two " "variant attributes :" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:175 msgid "T-Shirt B&C" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:177 msgid "Color: Red, Blue, White" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:179 msgid "Size: S, M, L, XL, XXL" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:182 msgid "Managing combination possibilities" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:184 msgid "" "By default, with the above product template, you get 15 different products " "(3 colors, 5 sizes). If the XXL size only exists for red and blue t-shirts, " "you can deactivate the white product variant." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:188 msgid "" "To do this, click on the **Variants** button, select the XXL, White T-shirt." " From the product form, uncheck the **Active** box of the T-shirt White, " "XXL." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:197 msgid "" "That deactivating a product is different than having an inventory of 0." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:200 msgid "Setting a price per variant" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:202 msgid "" "You can add a cost over the main price for some of the variants of a " "product." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:205 msgid "" "Once you have activated the variant option, you can add variants to your " "products. To do so, go to the Sales module, open :menuselection:`Sales --> " "Products` and click on the product you want to modify. Click on the " "**Variant Prices** button to access the list of variant values." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:213 msgid "" "Click on the variant name you wish to add a value to, to make the 3 fields " "editable. In the **Attribute Price Extra** field, add the cost of the " "variant that will be added to the original price." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:220 msgid "When you have entered all the extra values, click on **Save**." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:223 msgid "" "`Accounting Memento: Details of Journal Entries " "`_" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:225 msgid "" ":doc:`/applications/finance/accounting/overview/process_overview/supplier_bill`" msgstr "" #: ../../content/applications/sales/sales/products_prices/taxes.rst:3 msgid "Set taxes" msgstr "Opsæt moms" #: ../../content/applications/sales/sales/send_quotations.rst:3 msgid "Send Quotations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:3 msgid "Use quotations deadline to stimulate your customers" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:5 msgid "" "When sending quotations, it is important to set a deadline to encourage your" " customers to act. Indeed, this will stimulate them because they will be " "afraid of missing a good deal and it will also allow you to protect yourself" " in case you have to fulfill an order at a price that is no longer " "profitable for you." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:11 msgid "Set a deadline" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:13 msgid "" "With Odoo Sales, it is possible to instantly add an **Expiration Date** from" " the quotation or the sales order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:22 msgid "Use deadline in your quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:24 msgid "" "It is also possible to add a deadline to every quotation template created. " "Whenever a specific quotation template is used in a quote, its associated " "deadline will be automatically applied. Be sure to check out our " "documentation about :doc:`quote_template` to excel in their use." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:34 msgid "" "By clicking on the **Customer Preview** button, you will be able to see when" " the offer expires. For your information, the number of days will be the " "same as those mentioned in the quotation template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/deadline.rst:44 #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:50 #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:115 msgid ":doc:`quote_template`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:3 msgid "Deliver and invoice to different addresses" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:5 msgid "" "With Odoo Sales, you can configure different addresses for delivery and " "invoicing. For some customers, it will be very practical to define specific " "billing and shipping addresses. Indeed, not everyone will have the same " "delivery location as the invoicing location." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12 msgid "" "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the" " **Customer Addresses** feature." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:21 msgid "Add addresses from a quotation" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23 msgid "" "When you create a quotation, you must add a customer. This customer can be a" " company or a person with specific billing and shipping addresses already " "defined and registered in the system, or it can be a new customer. In this " "case, you have to **Create and edit** the contact form for your new customer" " and link it, if necessary, to a company. In this contact form, you will be " "able to add, delete and modify invoice and delivery addresses." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:35 msgid "" "If you select a customer with defined invoice and delivery addresses, Odoo " "will automatically use them to fill in the fields. Now, if you want to " "change it instantly, it is possible to do so directly from the quotation or " "the sales order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:40 msgid "Add addresses from a contact form" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:42 msgid "" "Previously, we talked about the contact form that you can fill in directly " "from a quotation or a sales order to add billing and shipping addresses to " "customers. But, if you go to :menuselection:`Sales --> Orders --> " "Customers`, you can create or modify every customer you want and add, delete" " or modify invoice and delivery addresses instantly there, before creating a" " quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:54 msgid "Deal with different addresses" msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:56 msgid "" "Like for the previous example, go to :menuselection:`Sales --> Orders --> " "Customers` and create a new customer. There, you can add company information" " but, more importantly, you can enter billing and shipping addresses under " "the **Contacts & Addresses** tab." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:65 msgid "" "Once done, you can return to your Sales dashboard and create a new " "quotation. Now, if you enter your new customer, you will see that the other " "fields will fill in by themself with the information previously saved for " "billing and shipping addresses." msgstr "" #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:74 msgid "" "With Odoo Sales, it is now very convenient to play with various addresses in" " terms of invoice and delivery features." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 msgid "Get paid to confirm an order" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:5 msgid "" "In general, online payments are considered as a fast and secure alternative " "to traditional payment methods. It is generally cheaper, easier and faster " "than other payment methods. It is particularly useful and efficient for " "international transactions. With Odoo Sales, you can use online payments to " "get automatic orders confirmation. Online payments are made instantly, so " "it's very convenient and saves lots of time in a basic sales process." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:12 msgid "Enable online payment" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:14 msgid "" "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the" " **Online Payment** feature." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:22 msgid "" "There, you will have direct access to the **Payment Acquirers** page. It " "will allow you to select and configure your acquirers of choice. Before " "creating or modifying a payment acquirer, be sure to check out our " "documentation about how to be paid with payment acquirers such as " ":doc:`/applications/general/payment_acquirers/paypal`, " ":doc:`/applications/general/payment_acquirers/authorize`, and others in the " ":doc:`/applications/general/payment_acquirers` documentation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:30 msgid "" "If you are familiar with this documentation: :doc:`quote_template`; you can " "activate or not the **Online Payment** feature for each template you use, " "under their confirmation tab." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35 msgid "Register a payment" msgstr "Registrer en betaling" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:37 msgid "" "After opening quotations from their received email, your customers will have" " different possibilities to make their online payments. For example:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:46 msgid "" "By clicking on the **Customer Preview** button, you will be able to see what" " your customers will have to choose when it comes to payment." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:51 msgid ":doc:`/applications/general/payment_acquirers`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:52 msgid ":doc:`/applications/general/payment_acquirers/paypal`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:53 msgid ":doc:`/applications/general/payment_acquirers/authorize`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 msgid "Get a signature to confirm an order" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:5 msgid "" "Online signatures are like electronic \"fingerprints\". By using them on " "Odoo, you will get automatic orders confirmation. You and your customers " "will save a lot of time by using this feature compared to a traditional " "process." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:10 msgid "Activate online signature" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:12 msgid "" "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the" " **Online Signature** feature." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:21 msgid "" "If you are familiar with this documentation: :doc:`quote_template`, you can " "activate or not the **Online Signature** feature for each quotation template" " you use, under their confirmation tab. Example:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:31 msgid "Confirm an order with a signature" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:33 msgid "" "When you send quotations to clients, they can instantly accept and sign it " "online. When they click on **Sign & Pay**, they have the choice to draw " "their own signature, automatically fill in the field with an automated " "signature or load a file from their computer. Here below, it is an example " "of an automated signature:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:43 msgid "" "Once signed, you will have the possibility to choose your payment methods. " "Then, when the quotation will be paid and confirmed, a delivery order will " "be created automatically by Odoo." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:47 msgid "" "Be careful that delivery orders are only generated for storable products and" " if the **Inventory app** is already installed." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3 msgid "Add optional products" msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:5 msgid "" "The use of optional products is a marketing strategy for cross-selling " "products along with a core product. The aim is to offer useful and related " "products to your customers. For instance, if a customer wants to buy a car, " "he has the choice to order an automatic opening trunk and massaging seats, " "or not to order such high-quality products and simply buy his car." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:11 msgid "Add optional products to your quotations" msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:13 msgid "" "With Odoo Sales, it is possible to add or modify optional products directly " "on quotations (under the **Optional Products** tab, as you can see below)." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:22 msgid "" "By clicking on the **Customer Preview** button, you will be able to see what" " your customers will have as possibilities after opening a quotation from " "their received email." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:30 msgid "" "In practice, your customers will be able to add different optional products " "to their order by using associated carts, with a user-friendly layout. More " "than that, if a customer selects all the optional products suggested, these " "additional items will automatically fill in the quotation managed by the " "salesman." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:40 msgid "" "Like this, salespeople will see each movement made by the customer and " "tracking the order will be all the better." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:49 msgid "Add optional products to your quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:51 msgid "" "Be sure to check out our documentation about :doc:`quote_template` to " "understand how you can enable, create, design and manage your own quotation " "templates before reading this part." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:54 msgid "" "For quotation templates, you also have an **Optional Products** tab where " "you can add related products or services." msgstr "" #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:62 msgid "" "With Odoo Sales, it is now very easy to understand your customer's needs." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 msgid "Use quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5 msgid "" "By creating custom quotation templates, you will save a lot of time. Indeed," " with the use of templates, you will be able to send complete quotations at " "a fast pace." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:11 msgid "" "To enable this feature, go to :menuselection:`Sales --> Configuration --> " "Settings` and activate **Quotation Templates**." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 msgid "" "For even more convenience, it is also recommended to add the **Quotation " "Builder** feature which will help you design your quotation templates very " "easily. This option will automatically install the Odoo Website App." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:29 #: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:47 msgid "Create your first template" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:31 msgid "" "Quotation templates are under :menuselection:`Sales --> Configuration`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33 msgid "" "You can create a new template or edit an existing one. Once named, you will " "be able to select products and quantities as well as the expiration time of " "the quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:42 msgid "" "On each template, you can also specify discounts if the option is activated " "in the **Sales** settings." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:46 msgid "Design your template" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:48 msgid "" "You will have the possibility to design your template and edit the customer " "interface in order to manage what clients will see before accepting and " "paying the quotation. For example, you will be able to describe your " "company, your services and your products. To do so, you can click on " "**Edit** and you will be brought to the quotation builder." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:58 msgid "" "You can easily edit the content of your template by dragging & dropping " "different building blocks to organize your quotation. For example, you can " "add a content block to describe your products." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:67 msgid "Use a quotation template" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 msgid "When creating a quotation, you can choose a specific template." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:77 msgid "" "You can select any template of your choice and suggest it as the default " "template in the **Sales** settings." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:81 msgid "Confirm the quotation" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:83 msgid "" "Templates facilitate the confirmation process by allowing customers to sign " "electronically or to pay online. You can activate these two options directly" " in the quotation template itself." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:92 msgid "" "Every quotation will now have this setting. Of course you can always change " "it and make it specific for each quotation." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:96 #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:116 msgid ":doc:`get_signature_to_validate`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:97 #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:117 msgid ":doc:`get_paid_to_validate`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:3 msgid "Add terms & conditions" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:5 msgid "" "Specifying terms and conditions is essential to set out important " "contractual points such as payment terms, limitation of liability and " "delivery terms between customers and sellers. Every seller must declare all " "formal information concerning products and company policy. On the other " "hand, each customer must take note of all these conditions before committing" " to anything. With Odoo Sales, it is very easy to include your default terms" " and conditions on every quotation, sales order, and invoice that you " "manage." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:13 msgid "Default Terms & Conditions" msgstr "Standard salgs- og leveringsbetingelser" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:18 msgid "" "Go to :menuselection:`Accounting --> Configuration --> Settings` and " "activate *Default Terms & Conditions*." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:27 msgid "" "Please note that this feature is activated via the settings of the " "**Invoicing App** and **not** via the settings of the **Sales App**. " "Moreover, you don't need to install the invoicing application since it is " "done automatically with the installation of the sales application." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:32 msgid "DT&C on your quotations, sales orders, and invoices" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:34 msgid "" "In the settings of the **Invoicing App**, you have the possibility to insert" " your default terms and conditions." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:42 msgid "They appear subsequently on every quotation, sales order, and invoice." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:45 msgid "DT&C on your quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:47 msgid "" "According to your business needs, you can specify your terms and conditions " "on your quotation templates. This is interesting if you have different terms" " and conditions within your company." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:56 msgid "" "Be sure to check out our documentation about quotation templates: " ":doc:`quote_template`, to master each step of this amazing feature." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:60 msgid "General Terms & Conditions" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:63 msgid "GT&C on your website" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:65 msgid "" "Use the **Website App** and create your own general terms and conditions " "page. For example, here is the Odoo terms and conditions page:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:73 msgid "" "You can refer to this page in the footer of all your documents. The layout " "is available in the **General Settings** under the **Business Documents** " "category. For example, this footer appears in every document from Odoo." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:83 msgid "GT&C as attachment in your emails" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:85 msgid "" "Attach an external document with your general terms and conditions when you " "are about to send your quotation by email to your customers." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:94 msgid "GT&C as attachment in your quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:96 msgid "" "Create and edit email templates to set a default attachment for all " "quotation emails that you will send in the future. To do so, you have to go " "to :menuselection:`Sales --> Configuration --> Quotation templates` and " "create a new quotation template or modify an existing one. Under the " "confirmation tab, you are now able to activate online signatures, online " "payments and to set a confirmation mail in which you have the possibility to" " configure the default attachment. There, you can put your general terms & " "conditions." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:109 msgid "" "To customize your email templates, activate the **developer mode** and go to" " :menuselection:`Settings --> Technical --> Email --> Templates`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:112 msgid "With Odoo Sales it is now very simple to deal with terms & conditions." msgstr "" #: ../../content/applications/sales/subscriptions.rst:3 msgid "Subscriptions" msgstr "Abonnementer" #: ../../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: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: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: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: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: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: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:3 msgid "Follow-up" msgstr "Opfølgning" #: ../../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: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: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: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.rst:3 msgid "Reporting" msgstr "Rapportering" #: ../../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: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:39 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: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: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: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: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: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/sales_flow.rst:3 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: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: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: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: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: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: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: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: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: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: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: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: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: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: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/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: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: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: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: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: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 ""