msgid "**Odoo CRM** helps you organize your sales activities: track leads, close opportunities and get accurate forecasts. Keep opportunities organized with the pipeline and manage your day-to-day activities with meetings and next activities."
msgid "*Leads* act as a qualifying step before an opportunity is created. This provides additional time to review its potential, and gauge its viability, before the opportunity is assigned to a salesperson."
msgid "Once the *Leads* setting has been activated, it applies to all sales teams by default. To turn off leads for a specific team, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`. Then, select a team from the list to open that team's configuration page. Clear the :guilabel:`Leads` checkbox, located beneath the :guilabel:`Sales Team` field, then click :guilabel:`Save`."
msgid "If a :guilabel:`Similar Leads` smart button appears at the top of the page for the lead, it indicates a similar lead or opportunity already exists in the database. Before converting this lead, click the smart button to confirm if the lead should be merged."
msgid "This opens a :guilabel:`Convert to opportunity` pop-up modal. Here, in the :guilabel:`Conversion Action` field, select the :guilabel:`Convert to opportunity` option."
msgid "To merge this lead with an existing similar lead or opportunity, select :guilabel:`Merge with existing opportunities` in the :guilabel:`Conversion Action` field. This generates a list of the similar leads/opportunities to be merged."
msgid "When merging, Odoo gives priority to whichever lead/opportunity was created in the system first, merging the information into the first created lead/opportunity. However, if a lead and an opportunity are being merged, the resulting record is referred to as an opportunity, regardless of which record was created first."
msgid "Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which the opportunity should be assigned. Neither field is required, though if a selection is made in the :guilabel:`Salesperson` field, the :guilabel:`Sales Team` field is populated automatically, based on the salesperson's team assignments."
msgid ":guilabel:`Link to an existing customer`: choose this option, then select a customer from the resulting drop-down menu, to link this opportunity to an existing customer record."
msgid "Leads can be added to the *CRM* app from custom email aliases, and by manually creating new records. This is in addition to the leads and opportunities created in the app through the :doc:`website contact form <opportunities_form>`."
msgid "First, ensure the *Leads* feature is enabled in the database by navigating to :menuselection:`CRM app --> Configuration --> Settings`. Tick the :guilabel:`Leads` checkbox, then click :guilabel:`Save`."
msgid "Each sales team has the option to create and utilize their own unique email alias. When messages are sent to this address, a lead (or opportunity), is created with the information from the message."
msgid "To create or update a sales teams' email alias, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`. Click on a team from the list to open the team's details page."
msgid "In the :guilabel:`Email Alias` field, enter a name for the email alias, or edit the existing name. In the :guilabel:`Accept Emails From` field, use the drop-down menu to choose who is allowed to send messages to this email alias:"
msgid ":guilabel:`Followers only`: only accepts messages from those who are following a record related to the team, such as a lead or opportunity. Messages are also accepted from team members."
msgid "Leads created from email alias messages can be viewed by navigating to :menuselection:`CRM app --> Leads`. Click a lead from the list to open it, and view the details."
msgid "The email received by the alias is added to the *chatter* thread for the lead. The subject line of the message is added to the title field, and the :guilabel:`Email` field is updated with the contact's email address."
msgid "Leads can be added directly to the *CRM* app by manually creating a new record. Navigate to :menuselection:`CRM app --> Leads` to view a list of existing leads."
msgid "If a lead is :doc:`converted to an opportunity <convert>`, the :guilabel:`Company Name` field is used to either link this opportunity to an existing customer, or to create a new customer."
msgid "To manually create an opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. At the top-left of the page, click :guilabel:`New` to create a new opportunity Kanban card. In the :guilabel:`Organization/Contact` field, enter the name of the company the opportunity is for."
msgid "Choose a name, and enter it in the :guilabel:`Opportunity` field. *This is a required field.* When manually creating an opportunity, it is helpful to add a name that relates to the details of the opportunity."
msgid "In the example below, the opportunity is named `5 VP Chairs`. This identifies the product the customer is interested in, as well as the potential number of products."
msgid "The information in the :guilabel:`Expected Revenue` and priority fields can be used to track performance for individual salespeople, and on a team basis. See :doc:`../performance/expected_revenue_report` and :doc:`../track_leads/lead_scoring` for more information."
msgid "*Lead mining* is a feature that allows *CRM* users to generate new leads directly into their Odoo database. To ensure lead qualification, lead mining output is determined by a variety of filtering criteria, such as the country, the company size, and the industry."
msgid "To get started, go to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Lead Mining` checkbox to activate the feature. Then, click :guilabel:`Save`."
msgid "After the *Lead Mining* setting is activated, a new button called *Generate Leads* is available to use in the upper-left corner of the *CRM* *Pipeline* (:menuselection:`CRM app --> Sales --> My Pipeline`)."
msgid "Lead mining requests are also available through :menuselection:`CRM app --> Configuration --> Lead Mining Requests`, or through :menuselection:`CRM app --> Leads --> Leads`, where the :guilabel:`Generate Leads` button is also available."
msgid "Choose to generate leads for :guilabel:`Companies` to get company information only, or choose |CC| to get company information and individual employee contact information."
msgid ":guilabel:`Filter on Size`: tick this checkbox to specify the number of employees at the company. This generates a field labeled :guilabel:`Size`. Fill in the blanks to create a range for the desired company size."
msgid "Make sure to be aware of the latest EU regulations when receiving contact information. Get more information about the General Data Protection Regulation on `Odoo GDPR <http://odoo.com/gdpr>`_."
msgid "After leads are generated, they are assigned to the designated salesperson and team. To view additional information regarding the lead, select one from the list, and click to open it."
msgid "In the chatter thread for the lead, additional information is provided. This can include the number of employees, the technology used by the company, the timezone, and direct contact information."
msgid "If :guilabel:`Leads` are **not** enabled for the database, then leads are generated as *opportunities*, and added to the pipeline for the designated salesperson."
msgid "Generating |CC| costs one additional credit for each contact generated. See here for complete pricing information: `Lead Generation by Odoo IAP <https://iap.odoo.com/iap/in-app-services/167?>`_."
msgid "To buy credits, navigate to :menuselection:`CRM app --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Mining` feature, click :guilabel:`Buy Credits`."
msgid "Credits may also be purchased by navigating to the :menuselection:`Settings app`. In the :guilabel:`Contacts` section, under the :guilabel:`Odoo IAP` feature, click :guilabel:`View My Services`."
msgid "Enterprise Odoo users with a valid subscription get free credits to test |IAP| features before purchasing more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases."
msgid "Adding a contact form to a website makes it easy to convert visitors into leads and opportunities. After a visitor submits their information, an opportunity can be created automatically, and assigned to a designated sales team and salesperson."
msgid "By default, the *Contact Us* page on an Odoo website displays a preconfigured contact form. This form can be customized, as needed, to suit the needs of a specific sales team."
msgid "Navigate to :menuselection:`Website app --> Contact Us`, then click :guilabel:`Edit` in the top-right of the screen to open the web editor. Click on the form building block in the body of the webpage to open the form configuration settings on the right sidebar. The following options are available to customize the contact form from the :guilabel:`From` section of the right sidebar:"
msgid ":guilabel:`Action`: the default action for a contact form is :guilabel:`Send an Email`. Select :guilabel:`Create an Opportunity` from the drop-down list to capture the information in the *CRM* app."
msgid ":guilabel:`Sales Team`: choose a sales team from the drop-down menu that the opportunities from this form should be assigned to. This field **only** appears if the :guilabel:`Action` field is set to :guilabel:`Create an Opportunity`."
msgid ":guilabel:`Salesperson`: if the opportunities should be assigned to a specific salesperson, select them from the drop-down menu. If no selection is made in this field, the opportunities are assigned based on the team's existing rules."
msgid ":guilabel:`Marked Fields`: use this field to alter how the form handles marked fields. The default option is to treat marked fields as :guilabel:`Required`, which is the recommended setting."
msgid ":guilabel:`On Success`: select how the webpage reacts after a customer successfully submits a form. :guilabel:`Nothing` keeps the customer on the same screen, with the addition of a confirmation message that the form was submitted successfully. :guilabel:`Redirect` sends the customer to a new webpage, based on the address provided in the :guilabel:`URL` field below. :guilabel:`Show Message` replaces the form with a preconfigured message that informs the customer someone should respond to them as soon as possible."
msgid ":guilabel:`URL`: if :guilabel:`Redirect` is selected in the :guilabel:`On Success` field, enter the URL for the webpage, where customers should be directed after successfully submitting a form."
msgid "If *leads* are activated in *CRM* settings, selecting :guilabel:`Create an Opportunity` generates a lead instead. To activate leads, navigate to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`."
msgid "In addition to the settings for the form, the settings for each field can be customized, as well. With the web editor menu still open, click into a field to open the :guilabel:`Field` configuration settings section on the sidebar. The following options are available to customize a field:"
msgid ":guilabel:`Input Type`: determine the type of information customers should input. Available options are :guilabel:`Text`, :guilabel:`Email`, :guilabel:`Telephone`, or :guilabel:`Url`. The selection made in this field limits the format that customers can use when entering information."
msgid ":guilabel:`Position`: choose the way the label is aligned with the rest of the form. The label can be hidden, above the field, to the left of the field, or right adjusted and closer to the field."
msgid ":guilabel:`Description`: slide the toggle to add a description for the field, which can provide additional instructions to customers. Click under the field on the form to add the description."
msgid ":guilabel:`Placeholder`: enter an example to help users know how to input information where formatting is important, such as a phone number or email address."
msgid ":guilabel:`Default Value`: enter a value to include in the form, by default, if the customer does not provide information in the field. *It is not recommended to include a default value for required fields*."
msgid ":guilabel:`Visibility`: select when this field should be visible. Use the button on the left to choose whether to show or hide this field on a desktop users. Use the button on the right to choose whether to show or hide this field to mobile users."
msgid "After a customer submits a contact form, and an opportunity is created, it is assigned based on the :ref:`form settings <crm/customize-contact-form>`. To view opportunities, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`."
msgid "If leads are activated on the database, contact form submissions are generated as leads, not opportunities. To activate leads, navigate to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`."
msgid "On the :guilabel:`My Pipeline` dashboard, click on an opportunity card in the Kanban view to open the opportunity record. The information submitted by the customer is visible on the opportunity record."
msgid "If the preconfigured contact form is used, the *Subject* field is added to the :guilabel:`Title` field, and the content in the :guilabel:`Notes` field, which is labeled as :guilabel:`Your Question`, is added to the :guilabel:`Internal Notes` tab."
msgid "Once a qualified lead has been converted into an opportunity, the next step is to create and deliver a quotation. This process can be easily handled through Odoo's *CRM* application."
msgid "If a quotation has already been created for this opportunity, it can be found by clicking on the :guilabel:`Quotations` smart button at the top of the top of the form. The number of existing quotations is listed on the smart button, as well."
msgid "However, customer information must be added or linked before a quotation can be sent. If the :guilabel:`Customer` field is left blank on the opportunity, clicking the :guilabel:`New Quotation` button opens a pop-up window with the following options:"
msgid ":guilabel:`Link to an existing customer`: opens a drop-down field with existing customer names. Select a name to link this new quotation to an existing customer record."
msgid ":guilabel:`Do not link to a customer`: the quotation will **not** be linked to a customer, and no changes are made to the customer information."
msgid "Once this button is clicked, a new quotation form appears. Confirm the information in the top half of the form, and update any missing or incorrect fields:"
msgid ":guilabel:`Quotation Template`: if applicable, select a pre-configured :doc:`quotation template </applications/sales/sales/send_quotations/quote_template>` from this field."
msgid ":guilabel:`Quotation Date`: creation date of draft/sent orders, confirmation date of confirmed orders. Note that this field is only visible if :doc:`Developer mode (debug mode) </applications/general/developer_mode>` is active."
msgid "To update the default validity time frame, navigate to :menuselection:`Sales app --> Configuration --> Settings --> Quotations & Orders` and update the :guilabel:`Default Quotation Validity` field. To disable automatic expiration, enter `0` in this field."
msgid "When using a quotation template, the expiration date is based off of the :guilabel:`Quotation Validity` field on the template. To alter the validity date computation on a template, go to :menuselection:`Sales app --> Configuration --> Sales Orders --> Quotation Templates`."
msgid "After updating the customer, payment, and deadline information on the new quotation, the :guilabel:`Order Lines` tab can be updated with the appropriate product information."
msgid "Next, type the name of an item into the :guilabel:`Product` field to search through the product catalog. Then, select a product from the drop-down menu, or create a new one by selecting :guilabel:`Create` or :guilabel:`Create and Edit`."
msgid "To organize products into sections click :guilabel:`Add a section` and type a name for the section. Then, click the :icon:`oi-draggable` :guilabel:`(drag)` icon to the left of the name and drag to move the section to the appropriate location. Move each product using the same method to finish organizing the quotation order lines."
msgid "All products in the database are listed as cards and can be sorted in the left panel by :guilabel:`Product Category` and :guilabel:`Attributes`."
msgid "To add a product, click the :icon:`fa-shopping-cart` :guilabel:`Add` button on the product card. Set the quantity of the item using the :icon:`fa-plus` :guilabel:`(add)` or :icon:`fa-minus` :guilabel:`(subtract)` buttons, or type the quantity in the number field between the two buttons. To remove an item, click the :icon:`fa-trash` :guilabel:`Remove` button on the product card."
msgid "Once all product quantities are set, click the :guilabel:`Back to Quotation` button to return to the quotation. The items selected in the product catalog now appear in the :guilabel:`Order Lines` tab."
msgid "To see a preview of the quotation as the customer will see it, click the :guilabel:`Preview` button. Doing so opens a preview in the :guilabel:`Customer Portal`."
msgid "Doing so opens a pop-up window with a pre-configured email message. Information from the quotation, including the contact information, total cost, and quotation title are be imported from the quotation."
msgid "A pre-loaded template is used to create the email message. To alter the template, click the internal link to the right of the :guilabel:`Load template` field, located at the bottom of the email pop-up window."
msgid "Proceed to make any necessary changes to the email, then click :guilabel:`Send`. A copy of the message is added to the *Chatter* of the of the record."
msgid "After a quotation is sent, the originating opportunity's :guilabel:`Quotations` smart button updates with a new count. This quotation, and all other quotations can be accessed through this smart button at the top of the opportunity in the *CRM* app."
msgid "Any quotations attached to the opportunity that are confirmed, and have therefore been converted to sales orders, will be deducted from the number listed on the :guilabel:`Quotations` smart button. Instead, the value of the sales order will appear in the :guilabel:`Orders` smart button located in the same control panel."
msgid "In order to keep the pipeline up to date and accurate, opportunities need to be identified as *won* or *lost* once a customer has responded to a quotation."
msgid "To mark an opportunity as *won* or *lost*, return to the opportunity using the breadcrumbs at the top-left of the quotation form. Or navigate to :menuselection:`CRM app --> Sales --> My Pipeline` and click on the correct opportunity to open it."
msgid "Marking an opportunity as *lost*, via the :guilabel:`Lost` button opens a :guilabel:`Mark Lost` pop-up window, where a :guilabel:`Lost Reason` can be entered."
msgid "From the :guilabel:`Lost Reason` drop-down field, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`."
msgid "It's best practice to try and use pre-configured :guilabel:`Lost Reason` values as much as possible or to limit the creation of new values only to sales team leads. Using consistent values for this parameter will make pipeline analysis easier and more accurate when filtering for the :guilabel:`Lost Reason` parameter."
msgid "To set up new values for this field, navigate to :menuselection:`CRM --> Configuration --> Lost Reasons`, and click both :guilabel:`New` and :guilabel:`Save` for each new entry added to the list."
msgid "Upon clicking :guilabel:`Mark as Lost`, the pop-up window disappears, and Odoo returns to the opportunity form, where a new red :guilabel:`Lost` banner is now present in the upper-right corner of the opportunity."
msgid "In order to view a *lost* opportunity from the pipeline, click the :guilabel:`down arrow icon` to the right of the search bar, and select either :guilabel:`Lost` or :guilabel:`Archived` from the drop-down menu that appears."
msgid "While opportunities that have been marked as *lost* are considered *Archived*, be advised that, in order for an opportunity to be included as *lost* in reporting, it **must** be specifically marked as *lost*, not *Archived*."
msgid "In Odoo's *CRM* app, *gamification tools* provide the opportunity to evaluate and motivate users through customizable challenges, goals, and rewards. Goals are created to target actions within the *CRM* app, and can be tracked and rewarded automatically to participating sales teams."
msgid "To install the *CRM Gamification* module, navigate to the :menuselection:`Apps` application. Click into the :guilabel:`Search...` bar at the top of the page and remove the :guilabel:`Apps` filter. Type `CRM Gamification` to search."
msgid "On the :guilabel:`CRM Gamification` module, click :guilabel:`Install`. This module features goals and challenges related to the *CRM* and *Sales* applications."
msgid "*Badges* are awarded to users when they have completed a challenge. Different badges can be awarded based on the type of task completed, and can be issued to more than one user, depending on the time they accomplish the goal."
msgid "Some badges can be awarded outside of challenges, as well. Select the Kanban card for the desired badge, then click :guilabel:`Grant`. This opens a :guilabel:`Grant Badge` pop-up window. Select a user from the :guilabel:`Who would you like to reward?` field."
msgid "To create a new badge, click :guilabel:`New` at the top-left of the page to open a blank form. Enter a name for the :guilabel:`Badge`, followed by a description."
msgid ":guilabel:`A selected list of users`: this badge can only be granted by a select group of users. If this option is selected, it generates a new field, :guilabel:`Authorized Users`. Choose the appropriate users from this drop-down list."
msgid ":guilabel:`People having some badges`: this badge can only be granted by users who have already been awarded a specific badge. If this option is selected it generates a new field, :guilabel:`Required Badges`. Use this drop-down list to select the badge(s) a user must have before they can award this badge to others."
msgid "To limit the number of badges a user can send, tick the :guilabel:`Monthly Limited Spending` checkbox. This sets a limit on the number of times a user can grant this badge. In the :guilabel:`Limitation Number` field, enter the maximum number of times this badge can be sent per month, per person."
msgid "To create a challenge, navigate to to :menuselection:`Settings --> Gamification Tools --> Challenges`. Click :guilabel:`New` in the top-left corner to open a blank challenge form."
msgid "Click into the first field under :guilabel:`Assign Challenge to`, and select a parameter from the drop-down list to define the rule. Then, click into the next field to define the rule's operator. If necessary, click into the third field to further define the parameter."
msgid "Challenges can be based on a single goal, or can include multiple goals with different targets. To add a goal to the challenge, click :guilabel:`Add a line` on the :guilabel:`Goals` tab."
msgid "In the :guilabel:`Goal Definition` field, choose a goal from the drop-down list. The :guilabel:`Condition` field automatically updates to reflect the condition set on the goal definition."
msgid "Next, click the :guilabel:`Reward` tab. Choose the :ref:`badges <crm/create-rewards>` to be awarded :guilabel:`For 1st User` and :guilabel:`For Every Succeeding User` by selecting them from the drop-down lists."
msgid "Badges are granted when a challenge is finished. This is either at the end of a running period, at the end date of a challenge, or when the challenge is manually closed."
msgid "*Lead enrichment* is a service that provides business information for a contact attached to a lead. Lead enrichment is an In-App Purchase (IAP) that requires credits to use, and is available for existing leads in an Odoo database."
msgid "The information provided by lead enrichment can include general information about the business (including full business name and logo), social media accounts, :guilabel:`Company type`, :guilabel:`Founded` information, :guilabel:`Sectors` information, the number of :guilabel:`Employees`, :guilabel:`Estimated revenue`, :guilabel:`Phone` number, :guilabel:`Timezone`, and :guilabel:`Technologies Used`."
msgid "Enterprise Odoo users with a valid subscription get free credits to test :abbr:`IAP (In-App Purchase)` features before deciding to purchase more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases."
msgid "The *leads* feature **must** be activated in the *CRM* settings page in order to use lead enrichment. To access the *CRM* settings, navigate to :menuselection:`CRM app --> Configuration --> Settings`. Under the :guilabel:`CRM` section activate the :guilabel:`Leads` option and click :guilabel:`Save`."
msgid "To set up lead enrichment in the *CRM* application, navigate to :menuselection:`CRM app --> Configuration --> Settings`. Then, under the :guilabel:`Lead Generation` section, tick the checkbox next to :guilabel:`Lead Enrichment`, and select either :guilabel:`Enrich leads on demand only` or :guilabel:`Enrich all leads automatically`. Click the :guilabel:`Save` button to activate the changes."
msgid "Enrichment of leads is based on the domain of the email address of the customer set on the lead. There are two different ways that a lead can be enriched: *automatically* or *manually*."
msgid "During set up, if :guilabel:`Enrich all leads automatically` was selected on the *CRM* :guilabel:`Settings` page, then no action needs to be taken by the user to enrich the lead. A scheduled action runs automatically, every sixty minutes, and enrichment occurs on leads, after a remote database is contacted."
msgid "To access the cron that runs for the automatic lead enrichment, activate :ref:`developer mode <developer-mode>`, and navigate to :menuselection:`Settings app --> Technical menu --> Automation section --> Scheduled Actions`. In the :guilabel:`Search...` bar, type in `CRM`. Click into the result labeled :guilabel:`CRM: enrich leads (IAP)`, and make any necessary adjustments. In the :guilabel:`Execute Every` field, enter a value greater than, or equal to, five minutes."
msgid "If the :guilabel:`Enrich leads on demand only` option was selected on the *CRM* :guilabel:`Settings` page, when activating :guilabel:`Lead Enrichment`, each lead that a user wishes to enrich **must** be manually enriched. This is achieved by clicking the :guilabel:`Enrich` button in the top menu of the lead."
msgid "The same information will be retrieved at the same :abbr:`IAP (In-App Puchase)` credit cost (one per enrichment). This method of enrichment is useful when every lead does not need to be enriched, or cost is an issue."
msgid "Manually enrich leads in bulk using the *list* view. First, navigate to :menuselection:`CRM app --> Leads`, and click the list view button (:guilabel:`☰ (three horizontal lines)` icon). Next, tick the checkboxes for the leads that should be manually enriched. Finally, click the :guilabel:`⚙️ Action` icon, and select :guilabel:`Enrich` from the resulting drop-down menu. This can also be achieved from the *My Pipeline* page. To do so, simply open the *CRM* app, or navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. Either route reveals leads and opportunities on the :guilabel:`Pipeline` page."
msgid "To buy credits, navigate to :menuselection:`CRM app --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Enrichment` feature, click on :guilabel:`Buy Credits`."
msgid "Credits and balances may also be purchased by navigating to the :menuselection:`Settings app`. In the :guilabel:`Contacts` section, under the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`."
msgid "When collecting a company's contact information, make sure to be aware of the latest EU regulations. For more information about General Data Protection Regulation, refer to: `Odoo GDPR <http://odoo.com/gdpr>`__."
msgid "*Partner autocomplete* enriches the contacts database with corporate data. In any module, enter the new company name into the :guilabel:`Customer` field (`partner_id` technical field), and select one of the companies suggested in the drop-down menu. Instantly get valuable company information full of hard-to-find data for a desired company."
msgid "The information provided by partner autocomplete can include general information about the business (including full business name and logo), social media accounts, :guilabel:`Company type`, :guilabel:`Founded` information, :guilabel:`Sectors` information, the number of :guilabel:`Employees`, :guilabel:`Estimated revenue`, :guilabel:`Phone` number, :guilabel:`Timezone`, and :guilabel:`Technologies Used`."
msgid "When getting a company's contact information make sure to be aware of the latest EU regulations. For more information about General Data Protection Regulation refer to: `Odoo GDPR <http://odoo.com/gdpr>`_. In Odoo, individual contact information cannot be searched for with the partner autocomplete feature."
msgid "Go to :menuselection:`Settings app --> Contacts section`. Then, activate the :guilabel:`Partner Autocomplete` feature, by ticking the checkbox beside it, and clicking :guilabel:`Save`."
msgid "From any module, as the user is typing in the name of a new company contact, Odoo reveals a large drop-down menu of potential match suggestions. If any are selected, the contact is then populated with corporate data related to that specific selection."
msgid "To buy credits, go to :menuselection:`Settings app --> Contacts section`. Then, locate either the :guilabel:`Partner Autocomplete` feature and click :guilabel:`Buy credits`, or locate the :guilabel:`Odoo IAP` feature and click :guilabel:`View My Services`. From the resulting page, select a desired package."
msgid "If the database runs out of credits, the only information populated when clicking on the suggested company will be the website link and the logo."
msgid "*Activities* are follow-up tasks tied to a record in an *Odoo* database. Activities can be scheduled on any page of the database that contains a chatter thread, Kanban view, list view, or activities view of an application."
msgid "A set of preconfigured activity types is available in the *CRM* app. To view the list of available activity types, navigate to the :menuselection:`CRM app --> Configuration --> Activity Types`."
msgid "Additional activity types are available within the database, and can be utilized through different applications. To access the complete list of activity types, go to the :menuselection:`Settings app`, then scroll to the :guilabel:`Discuss` section, and click :guilabel:`Activity Types`."
msgid ":guilabel:`Upload Document`: adds a link on the activity where an external document can be uploaded. Note that the *Documents* app is **not** required to utilize this activity type."
msgid "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open their calendar to schedule a time for this activity."
msgid "If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the chatter that opens a signature request pop-up window."
msgid "To automatically assign this activity to a specific user when this activity type is scheduled, choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the activity is assigned to the user who creates the activity."
msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved."
msgid "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to select any activities to recommend as follow-up tasks to this activity type."
msgid "In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so, configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity deadline`."
msgid "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations for activities as next steps."
msgid "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the next activity once the previous one is completed."
msgid "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select the activity that should be launched once this activity is completed."
msgid "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`, marking the activity as *Done* immediately launches the next activity listed in the :guilabel:`Trigger` field."
msgid "To keep the pipeline up to date with the most accurate view of the status of activities, as soon as a lead is interacted with, the associated activity should be marked as *Done*. This ensures the next activity can be scheduled as needed. It also prevents the pipeline from becoming cluttered with past due activities."
msgid "*Activity plans* are preconfigured sequences of activities. When an activity plan is launched, every activity in the sequence is scheduled automatically."
msgid "To create a new plan, navigate to :menuselection:`CRM app --> Configuration --> Activity Plan`. Click :guilabel:`New` at the top-left of the page to open a blank :guilabel:`Lead Plans` form."
msgid "Enter a name for the new plan in the :guilabel:`Plan Name` field. On the :guilabel:`Activities to Create` tab, click :guilabel:`Add a line` to add a new activity."
msgid "Select an :guilabel:`Activity Type` from the drop-down menu. Click :guilabel:`Search More` to see a complete list of available activity types, or to create a :ref:`new one <crm/create-new-activity-type>`."
msgid "Next, in the :guilabel:`Summary` field, enter any details to describe the specifics of the activity, including instructions for the salesperson or information due upon the completion of the activity. The contents of this field are included with the scheduled activity, and can be edited later."
msgid "Next, configure the timeline for the activity. Activities can be scheduled to occur either before the plan date or after. Use the :guilabel:`Interval` and :guilabel:`Units` fields to set the deadline for this activity. Lastly, in the :guilabel:`Trigger` field, select whether the activity should occur before or after the plan date."
msgid "An activity plan is created to handle high priority leads. Specifically, these leads should be contacted quickly, with a meeting scheduled within two days of the initial contact. The plan is configured with the following activities:"
msgid "This sets the *plan date* as the meeting deadline, which is the objective of the plan. Before that date, there is lead time to contact the customer and prepare for the meeting. After that date, the salesperson has time to create a quote, upload the document, and follow-up."
msgid "To launch an activity plan on a *CRM* opportunity, navigate to :menuselection:`CRM app` and click on the Kanban card of an opportunity to open it."
msgid "In the :guilabel:`Plan` field, select the desired activity plan to launch. This generates a :guilabel:`Plan summary`, listing out the activities included in the plan. Select a :guilabel:`Plan Date` using the calendar popover. This updates the :guilabel:`Plan summary` with deadlines based on the intervals configured on the :ref:`activity plan <crm/activity-plans>`."
msgid "Select a user in the :guilabel:`Assigned To` field. This user is assigned to any of the activities on the plan were configured with :guilabel:`Ask at launch` in the :guilabel:`Assignment` field."
msgid "An *expected revenue report* compiles all active leads in a sales pipeline that have a set expected closing date, and compares how sales teams are performing in a given time frame."
msgid "By pulling a monthly expected revenue report, sales managers can see which team members are reaching their goals, and who may need additional assistance to close valuable deals."
msgid "To create an expected revenue report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline`. This opens the :guilabel:`Pipeline Analysis` dashboard."
msgid "The *Pipeline Analysis* dashboard includes several filters in the search bar by default. Remove these before adding any additional custom filters."
msgid "At the top of the page, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Under the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window."
msgid ":ref:`Expected closing date <expected_revenue_report/closing-date>`: limits results to only include leads expected to close within a specific time frame."
msgid ":ref:`Specific sales teams <expected_revenue_report/sales-team>`: limits results to only include leads assigned to one or more sales teams. This filter is optional and should not be included if the report is intended for the entire company."
msgid "On the :guilabel:`Add Custom Filter` pop-up window, click into the first field of the new rule. Type `Expected Closing` into the :guilabel:`Search...` bar, or scroll to select it from the list. Click in the second field and select :guilabel:`is set`. This limits the results to only include leads where an estimated closing date is listed."
msgid "In the second field of the new rule, select :guilabel:`is between` from the drop-down menu. This creates a set time frame during which the expected closing date must occur for leads to be included in the results."
msgid "Click in each date field, one at a time, and use the calendar popover window to add both a start and end date to the rule. This is usually the beginning and ending of the current month, or fiscal quarter."
msgid "After filtering for the expected closing date, add a :guilabel:`New Rule`. Then, click into the new rule's first field, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll through the list to select it. Click in the rule's second field and select :guilabel:`is set` from the drop-down menu. This excludes any results without an assigned salesperson."
msgid "This filter is optional. To view results for the entire company, do **not** add this filter, and continue to :ref:`View results <expected_revenue_report/view-results>`."
msgid "To limit the results of the report to one or more sales teams, click :guilabel:`New Rule`. Next, click the first field for the new rule, and type `Sales Team` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it."
msgid "In the rule's second field, select :guilabel:`is in` from the drop-down menu. Selecting this operator limits results to the sales teams indicated in the next field."
msgid "Lastly, click into the third field, and either: make a selection from the complete list revealed in the popover menu, or type the first few characters of the specific sales team's title to quickly find and select it as a parameter."
msgid "Multiple teams can be added to the `Sales Team` rule, where each parameter is treated with an \"or\" (e.g. \"any\") operator in the search logic."
msgid "At the top of the :guilabel:`Add Custom Filter` form, there is an option to match :guilabel:`any` or :guilabel:`all` of the rules. In order to properly run the report, only records that match **all** of the following filters should be included. Before adding the filters, make sure :guilabel:`all` is selected in this field."
msgid "The expected revenue report benefits from utilizing multiple views. The default graph view can be used to identify which salespeople are expected to bring in the most revenue, while the list view and pivot view provide more detail on specific deals."
msgid "*Pie charts* are useful to show the distribution, or comparison, of data among a small number of categories or salespeople, specifically how they form the meaningful part of a whole picture."
msgid "The default view for the expected revenue report is the bar chart, stacked. To change to a different graph view, click one of the icons at the top-left of the report. While both the line chart and bar chart are available in stacked view, the pie chart is not."
msgid "The *list view* provides a list of all leads that are expected to close by the designated date. Clicking on a lead in list view opens the record for detailed analysis, but many insights can be gleaned from the basic view."
msgid "To add additional metrics to the report, click the *additional options menu* indicated by the :guilabel:`toggle` icon at the top-right of the list."
msgid "Select any additional metrics from the drop-down menu to add them to the list view. Some options that may be useful are :guilabel:`Expected Closing` and :guilabel:`Probability`."
msgid "When the pivot view is selected for this report, the X-axis lists the stages in the pipeline, while the Y-axis defaults to group the results by their creation date. To switch these groupings, click the flip access icon (:guilabel:`⇄`) at the top of the report."
msgid "To add additional measures to the report, click the :guilabel:`Measures` button at the top-left of the report. Select any additional metrics from the drop-down menu."
msgid "To add a group to a row or column to the pivot view, click the :guilabel:`➕ (plus sign)` next to :guilabel:`Total`, and then select one of the groups. To remove one, click the :guilabel:`➖ (minus sign)` and de-select the appropriate option."
msgid "Click :guilabel:`Insert in Spreadsheet` to add the pivot view into an editable spreadsheet format within the *Dashboards* app. If the Odoo *Documents* app is installed, the report can be inserted into a blank or existing spreadsheet, and exported."
msgid "The *Forecast* report in the *CRM* app allows users to view upcoming opportunities and build a forecast of potential sales. Opportunities are grouped by the month of their expected closing date, and can be dragged-and-dropped to adjust the deadline."
msgid "The default :guilabel:`Forecast` report includes opportunities assigned to the current user's pipeline, and are expected to close within four months. It also shows opportunities without an assigned expected closing date. The opportunities are grouped by month in a :icon:`oi-view-kanban` :guilabel:`(Kanban)` view."
msgid "Opportunities are grouped by the date assigned in the *Expected Closing* field on an opportunity form. To change this date directly from the :guilabel:`Forecast` page, select the Kanban card for the desired opportunity, then click and drag the card to the desired column."
msgid "The default time frame for the forecast is *month*. This can be changed by clicking the |caret| next to the :guilabel:`Search...` bar at the top of the report. Under the :guilabel:`Group By` heading in the resulting drop-down menu, click :guilabel:`Expected Closing` to expand the list of available options, and select a desired amount of time from the list."
msgid "After an opportunity is added to a new month, the *Expected Closing* field on the opportunity form is updated to the *last* date of the new month."
msgid "The *Expected Closing* field can also be manually updated on the opportunity card. To do that, click on the Kanban card for an opportunity on the :guilabel:`Forecast` page to open the opportunity's detail form. Click in the :guilabel:`Expected Closing` field, and use the calendar popover to select a new closing date."
msgid "At the top of the column for each month on the :guilabel:`Forecast` reporting page, to the right of the progress bar, is a sum of the prorated revenue for that time frame."
msgid "The first opportunity, `Global Solutions`, has an expected revenue of `$3,800`, and a probability of `90%`. This results in a prorated revenue of `$3,420`."
msgid "The second opportunity, `Quote for 600 Chairs`, has an expected revenue of `$22,500`, and a probability of `20%`. This results in a prorated revenue of `$4,500`."
msgid "Click the :icon:`fa-area-chart` :guilabel:`(area chart)` icon to change to graph view. Then, click the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`."
msgid "The :ref:`pivot view <reporting/using-pivot>` can be used to view and analyze data in a more in-depth manner. Multiple measures can be selected, and data can be viewed by month, and by opportunity stage."
msgid "The *CRM* app manages the sales pipeline as leads/opportunities move from stage to stage, origination to sale (**Won**) or archival (**Lost**)."
msgid "After organizing the pipeline, use the search options and reports available on the *Pipeline Analysis* page to gain insight into the effectiveness of the pipeline and its users."
msgid "Upon accessing the :guilabel:`Pipeline Analysis` page, a bar graph showcasing the leads from the past year automatically populates. The bars represent the number of leads in each stage of the sales pipeline, color-coded to show the month the lead reached that stage."
msgid "The interactive elements of the :guilabel:`Pipeline Analysis` page manipulate the graph to report different metrics in several views. From left-to-right, top-to-bottom, the elements include:"
msgid ":guilabel:`Actions`: represented by the :guilabel:`⚙️ (gear)` icon, located next to the :guilabel:`Pipeline Analysis` page title. When clicked, a drop-down menu appears with three options, each with their own sub-menu: :guilabel:`Knowledge`, :guilabel:`Dashboard`, :guilabel:`Spreadsheet`. (See :ref:`Save and share reports <win_loss/save_reports>` for more information)"
msgid ":guilabel:`Search...` bar: shows the filters and groupings currently being applied to the graph. To add new filters/groups, type them into the search bar, or click the :guilabel:`⬇️ (down arrow)` icon, at the end of the bar, to open a drop-down menu of options. (See :ref:`Search Options <win_loss/search>` for more information)"
msgid "In the upper-right corner, there are view options represented by different icons. (See :ref:`View Options <win_loss/view>` for more information)"
msgid ":guilabel:`Cohort` view: displays and organizes the data, based on their :guilabel:`Created on` and :guilabel:`Closed Date` week (default), day, month, or year."
msgid "Located on the far-left side of the page, beneath the :guilabel:`Pipeline Analysis` page title, there are more configurable filter and view options."
msgid ":guilabel:`Measures`: opens a drop-down menu of different measurement options that can be seen in the graph, pivot, or cohort view. The :guilabel:`Measure` drop-down menu is not available in the list view. (See :ref:`Measurement Options <win_loss/measure>` for more information)"
msgid ":guilabel:`Insert in Spreadsheet`: opens a pop-up window with options for adding a graph or pivot table to a spreadsheet in the *Documents* app or a dashboard in the *Dashboards* app. This option is not available in the cohort or list view."
msgid ":guilabel:`Stacked`: when selected, the results of each stage of the graph are stacked on top of each other. When not selected, the results in each stage are shown as individual bars."
msgid ":guilabel:`Descending`: re-orders the stages in the graph in descending order from left-to-right. Click the icon a second time to deselect it. Depending on the search criteria, this option may not be available."
msgid ":guilabel:`Ascending`: re-orders the stages in the graph in ascending order from left-to-right. Click the icon a second time to deselect it. Depending on the search criteria, this option may not be available."
msgid ":guilabel:`Expand All`: when additional groupings are selected using the :guilabel:`➕ (plus sign)` icons, this button opens those groupings under every row."
msgid "To add new search criteria, type the desired criteria into the search bar, or click the :guilabel:`⬇️ (down arrow)` icon, next to the search bar, to open a drop-down menu of all options. See the sections below for more information on what each option does."
msgid "The :guilabel:`Filters` section allows users to add pre-made and custom filters to the search criteria. Multiple filters can be added to a single search."
msgid ":guilabel:`Created On`: show leads that were created during a specific period of time. By default, this is the past year, but it can be adjusted as needed, or removed entirely."
msgid ":guilabel:`Add Custom Filter`: allows the user to create a custom filter with numerous options. (See :ref:`Add Custom Filters and Groups <win_loss/custom_filters>` for more information)"
msgid "The :guilabel:`Group By` section allows users to add pre-made and custom groupings to the search results. Multiple groupings can be added to split results into more manageable chunks."
msgid "The order that groupings are added affects how the final results are displayed. Try selecting the same combinations in a different order to see what works best for each use case."
msgid ":guilabel:`Add Custom Group`: allows the user to create a custom group with numerous options. (See :ref:`Adding Custom Filters and Groups <win_loss/custom_filters>` for more information)"
msgid "This option is only available if the search includes time-based filters, such as :guilabel:`Created On`, :guilabel:`Expected Closing`, or :guilabel:`Date Closed`. While multiple time-based filters can be added at once, only one comparison can be selected at a time."
msgid ":guilabel:`Default filter`: when saving a search, check this box to make it the default search filter when the :guilabel:`Pipeline Analysis` page is opened."
msgid "Custom filters are complex rules that further customize the search results, while custom groups display the information in a more organized fashion."
msgid "The :guilabel:`Add Custom Filter` pop-up window appears with a default rule (:guilabel:`Country is in _____`) comprised of three unique fields. These fields can be edited to make a custom rule, and multiple rules can be added to a single custom filter."
msgid "To edit a rule, start by clicking the first field (:guilabel:`Country`), and select an option from the drop-down menu. The first field determines the primary subject of the rule."
msgid "Next, click the second field, and select an option from the drop-down menu. The second field determines the relationship of the first and third fields, and is usually an **is** or **is not** statement, but can also be **greater than or less than** statements, and more."
msgid "**To create more complex rules:** click the :guilabel:`Add branch` icon to the right of the rule. This adds another modifier below the rule for adding an \"all of\" or \"any of\" statement."
msgid "By default, the :guilabel:`Pipeline Analysis` page measures the total :guilabel:`Count` of leads that match the search criteria, but can be changed to measure other items of interest."
msgid "To change the selected measurement, click the :guilabel:`Measures` button on the top-left of the page, and select one of the following options from the drop-down menu:"
msgid "After configuring filters, groupings, and measurements, the :guilabel:`Pipeline Analysis` page can display the data in a variety of ways. By default, the page uses the graph view, but can be changed to a pivot view, cohort view, or list view."
msgid "To change the pipeline to a different view, click one of the four view icons, located in the top-right of the :guilabel:`Pipeline Analysis` page."
msgid "The graph view is the default selection for the :guilabel:`Pipeline Analysis` page. It displays the analysis as either a: bar chart, line chart, or pie chart."
msgid "This view option is useful for quickly visualizing and comparing simple relationships, like the :guilabel:`Count` of leads in each stage, or the leads assigned to each :guilabel:`Salesperson`."
msgid "By default, the graph measures the :guilabel:`Count` of leads in each group, but this can be changed by clicking the :guilabel:`Measures` button, and :ref:`selecting another option <win_loss/measure>` from the resulting drop-down menu."
msgid "When using a bar chart in this view, consider deselecting the :guilabel:`Stacked` option, in order to make the breakdown of results more legible."
msgid "The pivot view displays the results of the analysis as a table. By default, the table groups the results by the stages of the sales pipeline, and measures :guilabel:`Expected Revenue`."
msgid "The pivot view is useful for analyzing more detailed numbers than the graph view can handle, or for adding the data to a spreadsheet, where custom formulas can be set up, like in an Excel file."
msgid "The :guilabel:`Stage` grouping cannot be removed, but the measurement can be changed by clicking the :guilabel:`Measures` button, and selecting another option."
msgid "The cohort view displays the analysis as periods of time (cohorts) that can be set to days, weeks, months, or years. By default, :guilabel:`Week` is selected."
msgid ":guilabel:`Measures`: the second column in the chart is the measurement of the results. By default, it is set to :guilabel:`Count`, but can be changed by clicking the :guilabel:`Measures` button, and selecting an option from the drop-down menu."
msgid ":guilabel:`Closed Date - By Day/Week/Month/Year`: this column looks at what percentage of the measured results were closed in subsequent days/weeks/months/years."
msgid "The list view displays a single list of all leads matching the search criteria. Clicking a lead opens the record for closer review. Additional details such as :guilabel:`Country`, :guilabel:`Medium`, and more can be added to the list, by clicking the :guilabel:`Filters` icon in the top-right of the list."
msgid "On the list view, clicking :guilabel:`New` closes the list, and opens the *New Quotation* page. Clicking :guilabel:`Generate Leads` opens a pop-up window for lead generation. Neither feature is intended to manipulate the list view."
msgid "After understanding how to :ref:`navigate the pipeline analysis page <win_loss/pipeline>`, the :guilabel:`Pipeline Analysis` page can be used to create and share different reports. Between the pre-made options and custom filter and groupings, almost any combination is possible."
msgid "Once created, reports can be :ref:`saved to favorites, shared with other users, and/or added to dashboards and spreadsheets <win_loss/save_reports>`."
msgid "Win/Loss is a calculation of active or previously active leads in a pipeline that were either marked as **Won** or **Lost** over a specific period of time. By calculating opportunities won over opportunities lost, teams can clarify key performance indicators (KPIs) that are converting leads into sales, such as specific teams or team members, certain marketing mediums or campaigns, and so on."
msgid "A win/loss report filters the leads from the past year, whether won or lost, and groups the results by their stage in the pipeline. Creating this report requires a custom filter, and grouping the results by :guilabel:`Stage`."
msgid "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down arrow)` icon, next to the search bar, to open a drop-down menu of filters and groupings."
msgid "In the :guilabel:`Add Custom Filter` pop-up menu, click on the first field in the :guilabel:`Match any of the following rules:` section. By default, this field displays :guilabel:`Country`."
msgid "Clicking that first field reveals a sub-menu with numerous options to choose from. From this sub-menu, locate and select the :guilabel:`Active` option. Doing so automatically populates the remaining fields."
msgid "Click :guilabel:`New Rule`, change the first field to :guilabel:`Active`, and the last field to :guilabel:`not set`. In total, the rule reads :guilabel:`Active is not set`."
msgid "The report now displays the total :guilabel:`Count` of leads, whether \"Won\" or \"Lost,\" grouped by their stage in the CRM pipeline. Hover over a section of the report to see the number of leads in that stage."
msgid "A sales manager might group wins and losses by salesperson, or sales team, to see who has the best conversion rate. Or, a marketing team might group by sources, or medium, to determine where their advertising has been most successful."
msgid "To add more filters and groups, click the :guilabel:`⬇️ (down arrow)` icon, next to the search bar, and select one or more options from the drop-down menu."
msgid ":guilabel:`Created on`: adjusting this filter to a different period of time, such as the last 30 days, or the last quarter, can provide more timely results."
msgid ":guilabel:`Add Custom Filter`: clicking this option, and scrolling through the numerous options in the drop-down menu, opens up additional search criteria, like :guilabel:`Last Stage Update` or :guilabel:`Lost Reason`."
msgid ":guilabel:`Add Custom Group > Active`: Clicking :menuselection:`Add Custom Group --> Active` separates the results into **Won** (:guilabel:`true`) or **Lost** (:guilabel:`false`). This shows at what stage leads are being marked **Won** or **Lost**."
msgid "In pivot view, the :guilabel:`Insert In Spreadsheet` button may be greyed out due to the report containing :guilabel:`duplicate group bys`. To fix this, replace the :guilabel:`Stage` grouping in the search bar with another option."
msgid "To better organize the list, click the :guilabel:`⬇️ (down arrow)` next to the search bar, and add more relevant groupings or re-organize the existing ones. To re-order the nesting, remove all :guilabel:`Group By` options and re-add them in the desired order."
msgid "After :ref:`creating a report <win_loss/reports>`, the search criteria can be saved, so the report does not need to be created again in the future. Saved searches automatically update their results every time the report is opened."
msgid "After modifying a spreadsheet and adding additional formulas, consider then adding the entire spreadsheet to a dashboard. Using this method, the spreadsheet can be added to a public dashboard instead of only :guilabel:`My Dashboard`."
msgid "Not every opportunity results in a successful sale. To keep the pipeline up-to-date, *lost* opportunities need to be identified. Specifying why an opportunity was lost provides additional insight that can prove useful for future opportunities."
msgid "To mark an opportunity as lost, first open the :menuselection:`CRM app`, and select an opportunity from the pipeline, by clicking on its corresponding Kanban card. Doing so reveals that opportunity's detail form."
msgid "This opens the :guilabel:`Mark Lost` pop-up window. From the :guilabel:`Lost Reason` drop-down menu, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`."
msgid "Neither the :guilabel:`Lost Reason` field, nor the :guilabel:`Closing Note` field, on the :guilabel:`Mark Lost` pop-up window are required. However, it is recommended to include this information for the sake of traceability, accountability, and reporting purposes."
msgid "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM app`. On the main :guilabel:`Pipeline` dashboard, click into the :guilabel:`Search...` bar at the top of the page, and remove all of the default filters."
msgid "Open the :guilabel:`Filters` drop-down menu, by clicking the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu containing :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` options, designated into respective columns."
msgid "Select the :guilabel:`Lost` option from the :guilabel:`Filters` section. Upon selecting :guilabel:`Lost`, only the opportunities marked as `Lost` appear on the :guilabel:`Pipeline` page."
msgid "To filter opportunities by a specific lost reason, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar again to open the drop-down menu. In addition to the :guilabel:`Lost` filter, under the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window."
msgid "On the :guilabel:`Add Custom Filter` pop-up window, click in the first field, and type `Lost Reason` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it. Then, click into the next field, and select :guilabel:`=` from the drop-down menu. Click into the third field, and select a lost reason from the drop-down menu. Finally, click :guilabel:`Add`."
msgid "To view results for more than one lost reason, select the operator :guilabel:`is in` in the second field of the custom filter in the :guilabel:`Add Custom Filter` pop-up window. Choosing this operator makes it possible to choose multiple lost reasons in the third field."
msgid "To restore a lost opportunity, open the :menuselection:`CRM app` to reveal the :guilabel:`Pipeline` dashboard. Or, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. From here, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns."
msgid "From the lost opportunity's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the opportunity form, signifying the opportunity has been restored."
msgid "To restore multiple opportunities at once, navigate to the main :guilabel:`Pipeline` dashboard in the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option."
msgid "Next, select the list view option, represented by the :guilabel:`≣ (list)` icon in the upper-right corner. Doing so places all the opportunities from the :guilabel:`Pipeline` page in a list view. With the list view chosen, select the checkbox to the left of each opportunity to be restored."
msgid "Once the desired opportunities have been selected, click the :guilabel:`⚙️ Actions` drop-down menu at the top of the :guilabel:`Pipeline` page. From the :guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`."
msgid "Doing so removes those selected opportunities from the :guilabel:`Pipeline` page because they no longer fit the :guilabel:`Lost` filter criteria. Delete the :guilabel:`Lost` filter from the search bar to reveal these newly-restored opportunities."
msgid "If *Leads* are enabled on a database, they can be marked as *lost* in the same manner as opportunities. Leads use the same :ref:`lost reasons <crm/lost-reasons>` as opportunities."
msgid "To enable leads, navigate to :menuselection:`CRM app --> Configuration --> Settings` and check the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`. This adds a new :guilabel:`Leads` menu to the header menu bar at the top of the page."
msgid "To mark a lead as lost, navigate to :menuselection:`CRM app --> Leads`, and select a lead from the list. Doing so reveals that lead's detail form."
msgid "To restore a lost lead, navigate to :menuselection:`CRM app --> Leads`, then click the :guilabel:`🔻 (triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains the :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns."
msgid "From the lost lead's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the lead form, signifying the lead has been restored."
msgid "To restore multiple leads at once, navigate to :menuselection:`CRM app --> Leads`, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option. Select the checkbox to the left of each lead to be restored."
msgid "Once the desired leads have been selected, click the :guilabel:`⚙️ Actions` drop-down menu at the top of the :guilabel:`Leads` page. From the :guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`."
msgid "Doing so removes those selected leads from the :guilabel:`Leads` page because they no longer fit the :guilabel:`Lost` filter criteria. Delete the :guilabel:`Lost` filter from the :guilabel:`Search...` bar to reveal these newly-restored leads."
msgid "The *Sales Teams* feature within Odoo's *CRM* app allows for the creation and management of multiple sales teams, each with their own assignment rules, invoicing targets, and roster of salespeople."
msgid "Set an :guilabel:`Email Alias` to automatically generate a lead/opportunity for this sales team whenever a message is sent to that unique email address. Choose whether to accept emails from :guilabel:`Everyone`, :guilabel:`Authenticated Partners`, :guilabel:`Followers Only`, or :guilabel:`Authenticated Employees`."
msgid "If the *Sales* app is installed on the database, an :guilabel:`Invoicing Target` field appears on the sales team form. This is the revenue target for the current month. The amount entered in this field is used to populate the invoicing progress bar on the :ref:`sales team dashboard <crm/sales-team-dashboard>`."
msgid "To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab when editing the sales team's configuration page. This opens a :guilabel:`Create Sales Team Members` pop-up window."
msgid "If the :guilabel:`Rule-Based Assignment` feature has **not** been enabled on the *CRM* app's *Settings* page, clicking :guilabel:`Add` under the :guilabel:`Members` tab opens an :guilabel:`Add: Salespersons` pop-up window. Tick the checkbox to the far-left of the salesperson to be added to the team, then click :guilabel:`Select`."
msgid "Select a user from the :guilabel:`Salesperson` drop-down list to add them to the team. To prevent this salesperson from being automatically assigned leads, tick the :guilabel:`Skip auto assignment` checkbox. If this feature is activated, the salesperson can still be assigned leads manually."
msgid "The :guilabel:`Leads (30 days)` field tracks how many leads the salesperson has been assigned in the past thirty days for this team, and the maximum number of leads they should be assigned. To edit the maximum number of leads this salesperson can be assigned, enter that amount in the :guilabel:`Leads (30 days)` field."
msgid "To allow salespeople to be assigned to more than one sales team, the *Multi Teams* setting needs to be enabled. First, navigate to :menuselection:`CRM app --> Configuration --> Settings`. Under the :guilabel:`CRM` section, tick the checkbox labeled :guilabel:`Multi Teams`. Then, click :guilabel:`Save` at the top-left of the page."
msgid "To view the sales team dashboard, go to :menuselection:`CRM app --> Sales --> Teams`. Any team the user is a member of appears in the dashboard."
msgid "Each Kanban card gives an overview of the sales team's open opportunities, quotations, sales orders, and expected revenue, as well as a bar graph of new opportunities per week, and an invoicing progress bar."
msgid "Click on the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-right corner of the Kanban card to open a drop-down menu. Then, to view or edit the team's settings, click :guilabel:`Configuration`."
msgid "Odoo automatically detects similar *leads* and *opportunities* within the *CRM* app. Identifying these duplicated records allows them to be merged without losing any information in the process. Not only does this help keep the *pipeline* organized, but it also prevents customers from being contacted by more than one salesperson."
msgid "When merging opportunities, no information is lost. Data from the other opportunity is logged in the chatter, and the information fields, for reference."
msgid "Similar leads and opportunities are identified by comparing the *email address* and *phone number* of the associated contact. If a similar lead/opportunity is found, a *Similar Leads* smart button appears at the top of the lead (or opportunity) record."
msgid "To compare the details of similar leads/opportunities, navigate to :menuselection:`CRM app --> Pipeline` or :menuselection:`CRM app --> Leads`. Open a lead or opportunity, and click the :guilabel:`Similar Leads` smart button. Doing so opens a Kanban view that only displays similar leads/opportunities. Click on a card to view the details for the lead/opportunity, and confirm if they should be merged."
msgid "After confirming that the leads/opportunities should be merged, return to the Kanban view using the breadcrumb link, or by clicking the :guilabel:`Similar Leads` smart button. Click the :icon:`oi-view-list` :guilabel:`(list)` icon to change to list view."
msgid "Check the box on the left of the page for the leads/opportunities to be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon at the top of the page, to reveal a drop-down menu. From that drop-down menu, select the :guilabel:`Merge` option to merge the selected opportunities or leads."
msgid "When :guilabel:`Merge` is selected from the :icon:`fa-cog` :guilabel:`Actions` drop-down menu, a :guilabel:`Merge` pop-up modal appears. In that pop-up modal, under the :guilabel:`Assign opportunities to` heading, select a :guilabel:`Salesperson` and :guilabel:`Sales Team` from the appropriate drop-down menus."
msgid "Below those fields, the leads/opportunities to merge are listed, along with their related information. To merge those selected leads/opportunities, click :guilabel:`Merge`."
msgid "There may be instances where a similar lead or opportunity is identified, but should *not* be merged. These circumstances vary, based on the processes of the sales team and organization. Some potential scenarios are listed below."
msgid "If a lead/opportunity has been marked as :doc:`lost <lost_opportunities>`, it can still be merged with an active lead or opportunity. The resulting lead/opportunity is marked active, and added to the pipeline."
msgid "Leads/opportunities from the same organization, but with different points of contact, may not have the same needs. In this case, it is beneficial to *not* merge these records, though assigning the same salesperson, or sales team, can prevent duplicated work and miscommunication."
msgid "If more than one lead/opportunity exists in the database, there may be multiple salespeople assigned to them, who are actively working on them independently. While these leads/opportunities may need to be managed separately, it is recommended that any affected salespeople be tagged in an internal note for visibility."
msgid "Similar leads and opportunities are identified by comparing the email addresses and phone numbers of the associated contacts. However, if the email address is *similar*, but not *exact*, they may need to remain independent."
msgid "Three different leads were added to the pipeline and assigned to different salespeople. They were identified as *Similar Leads* due to the email addresses of the contacts."
msgid "The third lead has the same email domain, but the address is different, as is the contact name. While this lead is most likely from the same organization, it is from a different contact, and should **not** be merged."
msgid "A *lead distribution report* can be used to see if active leads are being assigned equitably across sales members. It can also be used to view the distribution of good or :doc:`quality leads <quality_leads_report>`, and see how frequently each salesperson is receiving (and keeping) leads."
msgid "Lead distribution reports can be run each week to help keep salespeople on track, while providing them with ample good leads. These reports can also be used to see whether sales members are staying productive, if good leads are being lost too often by one salesperson, and what percentage of good leads are being retained overall."
msgid "To create a lead distribution report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline`, which reveals the :guilabel:`Pipeline Analysis` dashboard."
msgid ":ref:`Custom filters <search/custom-filters>` can now be added by clicking the :icon:`fa-caret-down` :guilabel:`(down caret)` icon, to the right of the search bar, to reveal a drop-down menu of search and filter options."
msgid "Three columns are displayed: :ref:`Filters <search/filters>`, :ref:`Group By <search/group>`, and :ref:`Favorites <search/favorites>`. To begin, navigate to the bottom of the :guilabel:`Filters` column, and click :guilabel:`Add Custom Filter`. This opens an :guilabel:`Add Custom Filter` pop-up window, where the essential filters can be added one at a time."
msgid "The following filter conditions are used to create a basic lead distribution report. Together they gather all leads created within a certain timespan that have an associated contact method and have been assigned to a sales team."
msgid "Click the first field, under :guilabel:`Match any of the following rules:`, that has the value :guilabel:`Country` in it. In the popover that appears, type `Created on` in the search bar, or scroll to search through the list to locate and select it."
msgid "Then, in the second field of that row, select :guilabel:`>=` from the drop-down menu. This operator **only** includes values greater than (or equal to) the value in the third, rightmost field."
msgid "Click :guilabel:`New rule` to add another row to the form, and choose :guilabel:`Sales Team` for this rule's parameter. Then, click the second field of the new rule, and select :guilabel:`contains` from the drop-down menu. Selecting this operator filters for any records that contain the words in the third, rightmost field."
msgid "For certain pre-determined, limited choices like a sales team, the :guilabel:`is in` operator helps make for an easier and more accurate selection, via a drop-down menu in the third field, instead of risking a typo or incorrect value in the text box field that accompanies the :guilabel:`contains` operator."
msgid "In this third field, enter the name of the desired sales team(s) that are to be included in the report. It is important for all :guilabel:`contains` argument values to be specific enough and spelled correctly as they exist in Odoo, otherwise this risks returning multiple (or zero) values."
msgid "By adding more than one rule to the form, a new option emerges at the top of the pop-up window above all the filters, to specify whether :guilabel:`any` :icon:`fa-caret-down` or :guilabel:`all` :icon:`fa-caret-down` of the conditions should match. This distinction is important to set correctly, as it impacts the driving logic of how the filters return data."
msgid "Click the default :guilabel:`any` :icon:`fa-caret-down` menu item and be sure the :guilabel:`all` :icon:`fa-caret-down` option is chosen instead. This setting will **only** show records that match *all* the rules contained inside the form."
msgid "The instruction below is not necessary, however, it's highly recommended to add a set contact value to the report's search criteria. A lot of spam, duplicate, or low quality leads can easily be screened out of the report simply by adding either a set :guilabel:`Phone` or :guilabel:`Email` rule."
msgid "Add another :guilabel:`New rule` to the form and set the first field to the first field to :guilabel:`Phone`. Then, select :guilabel:`is set` from the drop-down menu in the second field. Selecting this operator **only** filters for records that have a phone number associated with the lead."
msgid "Alternatively (or in addition to the above rule), click :guilabel:`New rule` and set the first field to :guilabel:`Email`. Then, select :guilabel:`is set` from the drop-down menu in the second field."
msgid "Click the :icon:`fa-sitemap` :guilabel:`(Add branch)` icon to the right of the `Phone is set` line, to add a new rule that branches from the rules above."
msgid "Two horizontal sets of fields appear below a line showing :guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:` option. This setting filters for records that match **any** of the rules contained inside. This uses the same logic as an OR (`|`) logical operator."
msgid "Active status is an important filter to include when creating a lead distribution report because it includes **all** leads regardless of won/lost or active/inactive status in the report. This provides a comprehensive view of all the leads assigned to each sales member."
msgid "Once all filters are set, click the :guilabel:`Add` button to add these filters to the search bar. To have the report grouped appropriately, click the :icon:`fa-caret-down` :guilabel:`(down caret)` icon, to the right of the search bar, and click :guilabel:`Salesperson` in the :guilabel:`Group By` section. All results are now grouped by the salesperson assigned to each lead."
msgid "Once the rules for the filter are set, click the purple :guilabel:`Confirm` button at the bottom of the pop-up menu to save the custom filter and close the pop-up menu."
msgid "Click the :icon:`fa-area-chart` :guilabel:`(Graph)` icon, to the right of the search bar, to view the report as a bar chart. Alternatively, click the :icon:`oi-view-list` :guilabel:`(List)` icon to view leads in a grouped list."
msgid "To save the filter so it can easily be re-applied, click the :guilabel:`Save current search` button in the :guilabel:`Favorites` section of the search bar drop-down menu."
msgid "Next, type a name for the filter in the text box below. Check the :guilabel:`Shared` checkbox to have the filter shared with any user with access to the pipeline. Finally, click the purple :guilabel:`Save` button below to save the filter."
msgid "The filter will now appear with the name it was given under the :guilabel:`Favorites` section of the drop-down menu and can be re-applied by clicking on it."
msgid "The following additional conditions are provided as an example of a *good*, but *not comprehensive*, set of rules for finding quality leads. These filters should be applied on top of the :ref:`crm/track_leads/essential-filters` in the order specified to achieve a heavily-detailed filter."
msgid "The Odoo *CRM* app can automatically assign leads/opportunities to sales teams and salespeople. A standard practice is to assign leads based on the probability of winning each lead. Companies can prioritize the leads that are more likely to result in successful deals by quickly assigning them to the appropriate salespeople."
msgid "As a company processes opportunities through the CRM pipeline, Odoo collects data on which opportunities are won and lost. Predictive lead scoring uses this data to predict the probability of winning each new lead or opportunity."
msgid "The term *in this case* refers to the variables that can affect a lead being successful in Odoo. This can include variables such as the assigned Salesperson, the source of the lead, the language of the lead, and other historical and demographic data."
msgid "Which variables are considered in this calculation can be :ref:`configured <lead_scoring/configuration>` to tailor the calculation to each business's needs."
msgid "The probability of success of each opportunity is displayed on the opportunity form, and it updates automatically as the opportunity progresses through the CRM pipeline."
msgid "When an opportunity moves to the next stage, its probability of success automatically increases according to the predictive lead scoring algorithm."
msgid "Predictive lead scoring is always active in Odoo *CRM*. However, the variables used to calculate the probability of success can be customized in the settings."
msgid "To customize the variables used by predictive lead scoring, go to :menuselection:`CRM --> Configuration --> Settings`. Under :guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update Probabilities` button."
msgid "The variables `Stage` and `Team` are always in effect. `Stage` refers to the CRM pipeline stage that an opportunity is in. `Team` refers to the sales team that is assigned to an opportunity. Predictive lead scoring *always* takes into account these two variables, regardless of which optional variables are selected."
msgid "Next, click on the date field next to the option :guilabel:`Consider leads created as of the:` to select the date from which predictive lead scoring will begin its calculations."
msgid "Manually changing the probability removes the automatic probability updates for that opportunity. The probability will no longer update automatically as the opportunity moves through each stage of the pipeline."
msgid "Odoo *CRM* can assign leads/opportunities to sales teams and salespeople based on specified rules. Create assignment rules based on the leads' probability of success to prioritize those that are more likely to result in deals."
msgid "The rule-based assignment feature can be set to run :guilabel:`Manually`, meaning an Odoo user must manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo will automatically trigger the assignment according to the chosen time period."
msgid "To set up automatic lead assignment, select :guilabel:`Repeatedly` for the :guilabel:`Running` section. Then, customize how often Odoo will trigger the automatic assignment in the :guilabel:`Repeat every` section."
msgid "If rule-based assignment is set to run :guilabel:`Repeatedly`, the assignment can still be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings (or using the :guilabel:`Assign Leads` button on the sales team configuration page)."
msgid "Next, configure the *assignment rules* for each sales team and/or salesperson. These rules determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM --> Configuration --> Sales Teams`, and select a sales team."
msgid "On the sales team configuration form, under :guilabel:`Assignment Rules`, click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to determine lead assignment for this sales team. The rules can include anything that may be relevant for this company or team, and any number of rules can be added."
msgid "Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :guilabel:`+` sign on the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to remove the line."
msgid "To create an assignment rule based on an opportunity's probability of success, click on the far left drop-down menu of an assignment rule line, and select :guilabel:`Probability`."
msgid "From the middle drop-down menu, select the desired equation symbol—most likely the symbol for *greater than*, *less than*, *greater than or equal to*, or *less than or equal to*."
msgid "To configure an assignment rule such that a sales team receives leads that have a probability of success of 20% or greater, create a :guilabel:`Domain` line that reads: `Probability >= 20`."
msgid "Separate assignment rules can also be configured for individual team members. From the sales team configuration page, click on a team member in the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click :guilabel:`Save` to save changes."
msgid "If automatic lead assignment is configured in the settings, both the sales team and individual team members have the option to :guilabel:`Skip auto assignment`. Check this box to omit a particular sales team or salesperson from being assigned leads automatically by Odoo's rule-based assignment feature. If :guilabel:`Skip auto assignment` is activated, the sales team or salesperson can still be assigned leads manually."
msgid "To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top of the sales team configuration page. This will assign any leads that are currently unassigned and match this team's specified domain."
msgid "Use the Odoo *CRM* app to compile a *marketing attribution report*, which analyzes the source of leads, and groups them in such a way as to calculate marketing's overall impact on lead generation, attribution, won rate, and more."
msgid "Reports can also be run on the :menuselection:`CRM app --> Leads` dashboard, which is **only** accessible if the *Leads* feature has been activated on the *Settings* page."
msgid "If the *Leads* feature has **not** been activated, the :menuselection:`CRM app --> Sales --> My Pipeline` dashboard can also be used to run reports."
msgid "The :icon:`fa-area-chart` :guilabel:`(graph)` view is shown, by default, with :guilabel:`Active or Inactive` and :guilabel:`Created on: [current year]` filters active in the :guilabel:`Search...` bar. The graph visualization displays the number of leads generated, by month and by sales team, with each sales team attributed to its own color per month shown."
msgid "Switch the view to the :icon:`oi-view-list` :guilabel:`(list)` option, by clicking the respective icon located at the top-right of the dashboard. This allows leads to easily be displayed in the grouping set by the *Group By* parameters."
msgid "*Urchin Tracking Modules (UTMs)* are snippets of text embedded in URLs that are used to track visitor data. This includes parameters relating to how a visitor reached the link, such as the type of website visited, and/or marketing campaign the visit came from."
msgid "UTMs can also be automatically generated by the :doc:`Email Marketing <../../../marketing/email_marketing>` and :doc:`Marketing Automation <../../../marketing/marketing_automation>` apps."
msgid "*Medium* is the UTM with the widest coverage, and is used to identify the medium used to access the link. This can include mediums such as social media, email, or cost per click (CPC)."
msgid "*Source* is more narrow, and is used to identify the source of traffic. For example, the name of a website, search engine used, or a specific social media platform."
msgid "*Campaign* is the most narrow, and can track specific marketing campaigns by name. This can include a contest or product name, type of sale, etc."
msgid "To start creating a report, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the :guilabel:`Search...` bar to see the list of filtering and grouping parameters."
msgid ":guilabel:`Filters`, located in the left column of the search options, can be used to keep only the results that fit the filter. For example, selecting the :guilabel:`Won` filter only shows leads that have been won in the attribution report."
msgid "Setting multiple :guilabel:`Group By` options creates nested groups, according to which option is selected first. For example, selecting :guilabel:`Medium`, followed by :guilabel:`Source`, and then :guilabel:`Campaign`, in :guilabel:`Group By` column, sorts all results *first* by medium, *then* by the specific sources in each medium, followed by the campaigns in each source."
msgid "This can be verified by looking at the direction, and order, of the selections in the group tile that appears in the :guilabel:`Search...` bar."
msgid "#. From the :guilabel:`Filters` column, select the :guilabel:`Active` filter to view only leads that are still marked as active. #. From the :guilabel:`Group By` column, select (in this specific order) :guilabel:`Source`, followed by the :guilabel:`City` or :guilabel:`Country`, depending on which grouping is more relevant."
msgid "This report contains all active leads, grouped first by the source of the lead, then by the city or country each lead is from. This is useful to see the density of active opportunities sorted by location."
msgid "With this data, marketing campaigns, such as conferences or billboards, can be targeted to the locations generating the largest amount of potential revenue. Similarly, more attention can be put toward increasing outreach in locations where existing marketing campaigns are less effective."
msgid "To set the measures of the report, begin by navigating to the :icon:`oi-view-pivot` :guilabel:`(pivot view)` on the :guilabel:`Leads Analysis` dashboard."
msgid "Click the :guilabel:`Measures` button to view the available measures of the report. Select the desired measures from the drop-down menu (multiple measures can be selected), and verify the measures, filters, and groups are all displayed correctly in the pivot table. This ensures the data is ready for export."
msgid "To quickly export the data in a list, as a .xlsx file, navigate to the :icon:`oi-view-list` :guilabel:`(list view)`. Click on the :guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` icon, located to the right of :guilabel:`Lead Analysis` in the top-left of the page, and click :icon:`fa-upload` :guilabel:`Export All`. The report downloads automatically as a .xlsx file."
msgid "For more export options, the report can be exported to the Odoo *Documents* app. From the :icon:`oi-view-list` :guilabel:`(list view)` of :guilabel:`Leads Analysis` page, begin by clicking the :guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` icon again. Now, navigate to :icon:`fa-table` :guilabel:`Spreadsheet`, and click :icon:`oi-view-list` :guilabel:`Insert list in spreadsheet`. A pop-up window titled, :guilabel:`Select a spreadsheet to insert your list.` appears."
msgid "The report can be renamed using the `Name of the list` field, if desired. The number of items on the report can be set with the field labeled: `Insert the first _ records of the list`. Next, select either a new :guilabel:`Blank spreadsheet`, or export into an existing spreadsheet. Finally, click the :guilabel:`Confirm` button."
msgid "To export the report as a .xlsx file, for use in an external spreadsheets program, click the :guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` icon, and select the :icon:`fa-upload` :guilabel:`Export All` option. If prompted, choose a file location, name the file, then click :guilabel:`Save`."
msgid "A *quality lead* is a lead that is likely to result in a sale. It should match the characteristics most commonly believed to help salespeople close a deal, in addition to more precise criteria that is specific to each organization."
msgid "The specific criteria that defines a *quality lead* is different for every organization. For more information, see :ref:`Define a quality lead <track_links/define-a-lead>`."
msgid "A quality leads *report* compares how many quality leads each salesperson has received over a specific amount of time, such as within the past 30 days. Sales managers can use such a report to make more informed decisions when assigning new leads to their team"
msgid "After running the report, the manager can see that, although everyone's ability to close a deal has varied, some members of the sales team have received a higher number of quality leads than others."
msgid "Using this information, the sales manager may decide to assign more quality leads to the sales people currently on the lower end, to balance out the distribution of quality leads."
msgid "To create a quality leads report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline` to open the :guilabel:`Pipeline Analysis` dashboard. Click into the :guilabel:`Search...` bar at the top of the page and remove any active filters."
msgid "Click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down mega menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Click :guilabel:`Add Custom Filter`. This opens a :guilabel:`Add Custom Filter` pop-up window."
msgid ":ref:`Specific sales teams <quality_leads_report/sales-team>`: limits results to only include leads for one or more sales teams. This filter is optional and should not be included if the is intended for the entire company."
msgid ":ref:`Add rules for quality leads <quality_leads_report/add-quality-rules>`: includes or excludes results based on criteria that is specific to a company or sales team."
msgid "Begin by first defining the rule's parameter with a date range, by clicking into the first field, on the left of the row, and typing `Created On` in the :guilabel:`Search...` bar, or by scrolling through the menu's list to locate it."
msgid ":guilabel:`>= (greater than or equal to)` to specify a start date and include all entries *after* that start date (as well as the initial value itself); or"
msgid ":guilabel:`is between` to more sharply define a time frame with a clear start and end date. All matching entries that fit within the defined start and end dates are included in the report."
msgid "With either option, use the pop-up calendar's day and time pickers, in the far right field, to define the respective date range. Setting these values concludes the creation of the first rule."
msgid "In the rule's second field, select :guilabel:`is in` from the drop-down menu. Selecting this operator limits results to the sales teams selected in the next field."
msgid "Lastly, in the third field, select the desired sales team from the drop-down menu. Multiple teams can be added in this field, where each parameter is treated with an \"or\" (e.g. \"any\") operator in the search logic."
msgid "Next, add a :guilabel:`New Rule`. Then, click into the first field for the new rule, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it."
msgid "In the rule's second field, select :guilabel:`is set` from the drop-down menu. Selecting this operator excludes any leads not assigned to a specific salesperson."
msgid "This filter is also optional, as it adds archived (inactive) leads to the report, however it is recommended to include this since it pulls *all* assigned leads, regardless of status, into the report. This ensures a more accurate representation of assigned leads is captured. However, to pull a report that only includes active leads, do **not** activate this feature."
msgid "As defined earlier, a *quality lead* is a lead that is likely to result in a won opportunity. Although the exact criteria for a quality lead varies from organization to organization, it is often a combination of factors commonly attributed to positive sales outcomes, in addition to factors valued by the specific organization."
msgid "In addition to the basic filters and grouping options outlined in the general :ref:`Quality leads report <track_links/create-quality-leads-report>`, consider the following filters when defining a quality lead:"
msgid ":guilabel:`Source`: this field links to the marketing and lead generation efforts from other Odoo applications, including *Live Chat*, *Social Marketing*, and *Email Marketing*."
msgid ":guilabel:`Lost Reason`: exclude leads that may appear to be quality based on various criteria, but have been marked as *lost* for specified reasons."
msgid "When adding rules to a custom filter, keep the statements preceding each rule in mind. The statement above a rule determines whether the search results must match **all** of the rules below the statement, or **any** of the rules below the statement."
msgid "After the filters are configured, click :guilabel:`Add`. The default display for the report is a bar graph, where the leads are grouped by *stage*."
msgid "To group the results by salesperson, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down mega menu. Under the :guilabel:`Group By` heading, select :guilabel:`Salesperson`. In the same column, under the :guilabel:`Group By` heading, click :guilabel:`Add a Custom Group`, then select :guilabel:`Active` on the resulting drop-down menu to layer in lead *status*, under the parent :guilabel:`Salesperson` grouping."
msgid "The report now displays the total count of *quality leads* each salesperson has received in the designated time period. Because there are layered :guilabel:`Group By` filters, the grouped leads are also color-coded to identify whether they are *active* or *marked as lost*."
msgid "To save this search for later, click the :guilabel:`🔻(triangle pointed down)` icon next to the :guilabel:`Search...` bar to open the drop-down menu. Under the :guilabel:`Favorites` heading, click :guilabel:`Save current search`."
msgid "Within Odoo's *CRM* app, leads can be forwarded to resellers (or partners). Leads can be manually assigned, or automatically assigned, based on the resellers' designated *level* and location."
msgid "To utilize the reseller features, the *Resellers* module first needs to be installed. Navigate to the :menuselection:`Apps application`, and remove the :guilabel:`Apps` filter from the :guilabel:`Search...` bar. Then, search for `Resellers`."
msgid "Click :guilabel:`Activate` on the :guilabel:`Resellers` module card that appears. Doing so installs the module, and returns to the main Odoo dashboard."
msgid "After the module is installed, navigate to the :menuselection:`CRM app`. Under the :menuselection:`Configuration` menu is a new section, titled :guilabel:`Resellers`, with three options beneath it: :guilabel:`Partner Levels`, :guilabel:`Partner Activations`, and :guilabel:`Commission Plans`."
msgid "Partner *levels* are used to differentiate between various resellers. To view the partner levels, navigate to :menuselection:`CRM app --> Configuration --> Resellers: Partner Levels`."
msgid "Existing levels can also be edited and renamed, if desired, as well. To modify a level, select it from the list, and proceed to make any desired changes from the level form page that appears."
msgid "Level weight is used to decide the probability a partner to be assigned a lead or opportunity. On the level form, assign a numerical value (greater than zero) to the :guilabel:`Level Weight` field. If the weight is zero, no leads are assigned."
msgid "*Level Weight* can be assigned on an individual contact record. The weight assigned on the individual record overwrites the default weight assigned on the level configuration form."
msgid "Partner *activations* are used to identify the status of a partner. Activations are assigned on an individual contact record, and can be used to group or filter the *Partnership Analysis* report (:menuselection:`CRM app --> Reporting --> Partnerships`)."
msgid "New partner activations can be added, as needed, by clicking :guilabel:`New`, and entering a :guilabel:`Name` on the new line that appears. Then, select the desired status in the :guilabel:`Active` column."
msgid "Existing partner activations can also be edited and renamed, if desired. To rename a status, click the :guilabel:`Name` field of a desired level, and enter a new name."
msgid "To change the active status of an activation, slide the toggle in the :guilabel:`Active` column of the desired activation to the *inactive* position."
msgid "To update an individual partner record, navigate to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for the desired partner to open the customer record."
msgid "Click the :guilabel:`Partner Level` field, and select an option from the drop-down menu to assign a level. Click the :guilabel:`Activation` field, and select a partner activation type from the drop-down list, if desired. Then, click the :guilabel:`Level Weight` field to assign a different level weight, if necessary."
msgid "With the Odoo *Website* and *Resellers* apps installed, a new webpage (`/partners`) is created to display a list of all active partners from the *CRM* app."
msgid "Next, return to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a partner. From that partner's contact form, click the :guilabel:`Go to Website` smart button at the top of the page to open that partner's webpage."
msgid "Next, click :guilabel:`Edit` at the top-right of the partner's webpage, and use the :doc:`building blocks <../../../websites/website/web_design/building_blocks>` to add any additional design elements, or information about the partner."
msgid "After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position, if needed."
msgid "*Unattended leads* are leads that have scheduled activities that are either due or past due. Whenever an activity is scheduled, Odoo tracks the due date, and sends email reminders to the users the activity is assigned to."
msgid "An *unattended leads report* compiles all active leads in the pipeline with due or past due activities, allowing a sales manager to identify which opportunities require immediate attention."
msgid "By pulling a daily unattended leads report, sales managers can remind their teams to address outstanding activities before they become past due, helping avoid neglected leads and reinforcing proactive behaviors in their salespeople."
msgid "The yellow :guilabel:`📞 (phone)` icon indicates that the `Modern Open Space` lead has a phone call activity scheduled for today. The red :guilabel:`✉️ (envelope)` icon indicates that the `5 VP Chairs` lead has an email activity scheduled that is past due."
msgid "Clicking on the `5 VP Chairs` lead, the sales manager opens the record of the lead and reviews the chatter. They see that the email was scheduled to be sent two days ago, but Mitchell never marked this activity as done."
msgid "In order to pull a unattended leads report, sales teams **must** be regularly utilizing activity in the *CRM* pipeline, on individual lead and opportunity cards."
msgid "To create an unattended leads report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline` to open the :guilabel:`Pipeline Analysis` dashboard. Click into the :guilabel:`Search...` bar at the top of the page, and remove all of the default filters."
msgid "Next, add custom filters by clicking the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Under the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window."
msgid ":ref:`Past due activities <unattended_leads_report/past-due>`: limits the results to only include leads with an assigned activity where the due date has past. This can be altered to include activities due to occur on the date the report is generated as well."
msgid ":ref:`Specific sales teams <unattended_leads_report/sales-team>`: limits results to only include leads assigned to one or more sales teams. This filter is optional and should not be included if the report is intended for the entire company."
msgid "Click the first field for the new rule, and type `Activities` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it. Then, next to :guilabel:`Activities`, click the :guilabel:`> (greater than sign)` to open a new drop-down menu with secondary conditions."
msgid "Then, click into then next field and select :guilabel:`<=` from the drop-down menu. Selecting this operator includes all activities with a due date up to, and including, the date selected in the next field."
msgid "After filtering for activities, add a :guilabel:`New Rule`. Then, click into the first field for the new rule, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it."
msgid "This filter is optional. To view results for the entire company, do **not** add this filter, and continue to :ref:`View results <unattended_leads_report/view-results>`"
msgid "After the filters are configured, click :guilabel:`Add`. The resulting report displays all leads assigned to a salesperson where an activity is past due, or is due on the current date. The default display is a bar graph, where the leads are grouped by *stage*."
msgid "To group the results by salesperson, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Under the :guilabel:`Group By` heading, select :guilabel:`Salesperson`."
msgid "The *Members* application is where all operations related to memberships can be configured and managed. The *Members* app integrates with the *Sales* and *Accounting* applications to sell and invoice memberships directly to customers."
msgid "To create a new membership product, navigate to :menuselection:`Members app --> Configuration --> Membership Products`, and click :guilabel:`New` to open a blank product record."
msgid "Membership products require a start and end date, as they are used to determine :ref:`membership status <sales/membership-status>`. Membership products can be sold *before* their active start date."
msgid "To activate a membership from the *Contacts* application, navigate to :menuselection:`Contacts app`, and click on a contact to open that specific contact's detail form."
msgid "On the :guilabel:`Join Membership` pop-up window that appears, select a :guilabel:`Membership` from the drop-down menu. Then, configure a :guilabel:`Member Price`."
msgid "Click :guilabel:`Invoice Membership` when both fields are filled in. Doing so reveals a :guilabel:`Membership Invoices` page, wherein invoices can be confirmed and completed."
msgid "To publish a list of active members on the website, the *Online Members Directory* application must first be :ref:`installed <general/install>`. After installing the module, add the `/members` page to the website's menu by :doc:`editing the website menu <../websites/website/pages/menus>`."
msgid "Return to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a member. From the resulting customer form that appears, click the :guilabel:`Go to Website` smart button at the top of the page to open the member's webpage."
msgid "Click the :icon:`fa-pencil` :guilabel:`Edit` button to reveal a sidebar of editing tools. After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position."
msgid "The default *Members Analysis* report displays a bar chart, measuring the :guilabel:`Quantity` of memberships against the amount of :guilabel:`Revenue Done`. The data is grouped by the assigned salesperson, then by the month the membership begins."
msgid ":guilabel:`Salesperson`: the internal user in charge of the contact. This information is managed in the *Salesperson* field on the *Sales & Purchase* tab on the contact's record."
msgid "Click the :icon:`fa-area-chart` :guilabel:`(graph)` icon to change to graph view. Then, click the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`."
msgid "With **Odoo Point of Sale**, run your shops and restaurants easily. The app works on any device with a web browser, even if you are temporarily offline. Product moves are automatically registered in your stock, you get real-time statistics, and your data is consolidated across all shops."
msgid "From the **POS dashboard**, click :guilabel:`New Session`, and at the :guilabel:`Opening Cash Control` screen, click :guilabel:`Open Session` to start a POS session, or click :guilabel:`Continue Selling` if the session is already opened."
msgid ":doc:`Multiple users <point_of_sale/employee_login>` can be logged into the same session at the same time. However, the session can only be opened once on the same browser."
msgid "Click on products to add them to the cart. To change the **quantity**, click :guilabel:`Qty` and enter the number of products using the keypad. To add a **discount** or modify the product **price**, click respectively :guilabel:`% Disc` or :guilabel:`Price` and enter the amounts."
msgid "Once an order is completed, proceed to checkout by clicking :guilabel:`Payment`. Select the **payment method**, enter the received amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move on to the next customer."
msgid "The system can only load a limited number of products for effective opening. Click :guilabel:`Search more` if the desired product is not loaded automatically."
msgid "Registering your customer is necessary to :doc:`collect their loyalty points and grant them rewards <point_of_sale/pricing/loyalty>`, automatically apply the :doc:`attributed pricelist <point_of_sale/pricing/pricelists>`, or :ref:`generate and print an invoice <receipts-invoices/invoices>`."
msgid "You can create customers from an :ref:`open POS session <pos/session-start>` by clicking :menuselection:`Customer --> Create`, and filling in the contact information. You can also create customers from the backend by going to :menuselection:`Point of Sale --> Orders --> Customers` and clicking :guilabel:`New`. Then, fill in the information and save."
msgid "To set a customer during an order, access the list of customers by clicking :guilabel:`Customer` on the POS interface. You can also set a customer at the payment screen by clicking :guilabel:`Customer`."
msgid "You can add **customer notes** about specific products directly from an open :ref:`POS session <pos/session-start>`. For instance, to provide cleaning and maintenance tips. They can also be used to track a customer's particular request, such as not wanting the product to be assembled for them."
msgid "To do so, select a product and click :guilabel:`Customer Note` on the pad. Doing so opens a pop-up window in which you can add or modify content for the note."
msgid "You can also refund a product by selecting the returned product from an open session, and setting a negative quantity that equals the number of returned products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by the quantity of returned products."
msgid "Once the return payment is validated, Odoo generates the required credit note, referencing the original receipt or invoice and partially or fully canceling the document."
msgid "Doing so opens a pop-up window on which you can select :guilabel:`Cash In` or :guilabel:`Cash Out`, enter the amount and the reason, and click :guilabel:`Confirm`."
msgid "Before closing this window, count your cash using the calculator icon. Doing so opens a pop-up window that computes the total amount in the cash drawer depending on the coins and bills counted and added manually. Then, click :guilabel:`Confirm` or :guilabel:`Discard` to close the window. The computed amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money Details` are specified in the **Notes** section."
msgid "Depending on your setup, you might only be allowed to close a session if the expected cash revenue equals the counted cash. To close it anyway, click :guilabel:`Ok` on the :guilabel:`Payments Difference` screen."
msgid "In the context of a restaurant, the feature enables users to create multiple-choice menus. For example, a user can define a main dish and specify various options for sides, drinks, or desserts that customers can combine with the main dish."
msgid "Name your combo and add the products you want customers to choose from by clicking :guilabel:`Add a line`. You can also include an extra price for each option in the :guilabel:`Extra Price` column."
msgid "The sales price of the combo product is fixed and does not vary based on the individual prices of included items or the quantity of items in the combo. The combo product price is only affected by the extra price optionally defined at the combo choice creation or if a variant of one of the items has a specified extra price."
msgid "Go to the :guilabel:`Combo Choices` tab, click :guilabel:`Add a line`, and select the combinations to add. You can also create a new combination at this step by clicking :guilabel:`New` on the popup window."
msgid ":ref:`Open a POS session <pos/session-start>` and select the combo product. Choose the options and click :guilabel:`Add to order`. As a reminder, the extra price appears under the related choices."
msgid "To access the general POS settings, go to :menuselection:`Point of Sale --> Configuration --> Settings`. Then, open the dropdown menu in the :guilabel:`Point of Sale` field and select the POS to configure."
msgid "These settings are available to users with the :doc:`access rights </applications/general/users>` :guilabel:`Administration` set as :guilabel:`Settings`."
msgid "You can also configure some settings from the dashboard by clicking the vertical ellipsis button (:guilabel:`⋮`) on a POS card. Doing so opens a popup window, from which you can:"
msgid "These settings are available to users with the :doc:`access rights </applications/general/users>` :guilabel:`Point of Sale` set as :guilabel:`Administrator`."
msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products`, and select a product to open the product form. In the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`."
msgid "To manage PoS categories, go to :menuselection:`Point of Sale --> Configuration --> PoS Product Categories`. To add a new category, click :guilabel:`Create`. Then, name it in the :guilabel:`Category Name` field."
msgid "To associate a category with a parent category, fill in the :guilabel:`Parent Category` field. A parent category groups one or more child categories."
msgid "Go to :menuselection:`Point of Sale --> Products --> Products` and open a product form. Then, go to the :guilabel:`Sales` tab and fill in the :guilabel:`Category` field under the :guilabel:`Point of Sale` section."
msgid "You can select one product category to display when :ref:`opening a POS session <pos/session-start>`. To configure it, go to your :ref:`POS settings <configuration/settings>` and select a PoS category from the dropdown menu of the :guilabel:`Start Category` field within the :guilabel:`PoS Interface` section."
msgid "You can also limit the categories displayed on your POS interface. To achieve this, go to your :ref:`POS settings <configuration/settings>` and choose the specific categories to display in the :guilabel:`Restrict Categories` field within the :guilabel:`PoS Interface` section."
msgid "ePOS printers are designed to work seamlessly with Point of Sale systems. Once connected, these devices automatically share information, allowing for direct printing of tickets from the POS system to the ePOS printer."
msgid "The following ePOS printers are directly compatible with Odoo without needing an :doc:`IoT system </applications/general/iot/devices/printer>`."
msgid "Epson printers using Wi-Fi/Ethernet connections and following the `EPOS SDK Javascript protocol <https://download4.epson.biz/sec_pubs/pos/reference_en/technology/epson_epos_sdk.html>`_ are compatible with Odoo **without** needing an :doc:`IoT system </applications/general/iot/devices/printer>`."
msgid "To work with Odoo, some printer models that can be used without an :doc:`IoT system </applications/general/iot>` may require :doc:`the HTTPS protocol <https>` to establish a secure connection between the browser and the printer. However, trying to reach the printer's IP address using HTTPS leads to a warning page on most web browsers. In that case, you can temporarily :ref:`force the connection <epos_ssc/instructions>`, which allows you to reach the page in HTTPS and use the ePOS printer in Odoo as long as the browser window stays open."
msgid "The connection is lost after closing the browser window. Therefore, this method should only be used as a **workaround** or as a pre-requisite for the :ref:`following instructions <epos_ssc/instructions>`."
msgid "**Generating** an SSL certificate should only be done **once**. If you create another certificate, devices using the previous one will lose HTTPS access."
msgid "Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`."
msgid "Then, sign in using your printer credentials to access the ePOS printer settings. To sign in, enter `epson` in the :guilabel:`ID` field and your printer serial number in the :guilabel:`Password` field."
msgid "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` section, and click :guilabel:`create` to generate a new **Self-Signed Certificate**. The :guilabel:`Common Name` should be automatically filled out. If not, fill it in with the printer IP address number. Select the years the certificate will be valid in the :guilabel:`Validity Period` field, click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the printer."
msgid "The self-signed certificate is generated. Reload the page and click :guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure **Selfsigned Certificate** is correctly selected in the :guilabel:`Server Certificate` section."
msgid "The export process is heavily dependent on the :abbr:`OS (Operating System)` and the browser. Start by accessing your ePOS printer settings on your web browser by navigating to its IP address (e.g., `https://192.168.1.25`). Then, force the connection as explained in the **Generate a self-signed certificate tab**."
msgid "Windows 10 manages certificates, which means that self-signed certificates must be imported from the certification file rather than the browser. To do so,"
msgid "select where to install the certificate and for whom - either for the :guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, click :guilabel:`Next`;"
msgid "on the `Certificate Store` screen, tick :guilabel:`Place all certificates in the following store`, click :guilabel:`Browse...`, and select :guilabel:`Trusted Root Certification Authorities`;"
msgid "To import an SSL certificate into an Android device, first create and export it from a computer. Next, transfer the `.crt` file to the device using email, Bluetooth, or USB. Once the file is on the device,"
msgid "To import an SSL certificate into an iOS device, first create and export it from a computer. Then, transfer the `.crt` file to the device using email, Bluetooth, or any file-sharing service."
msgid "Downloading this file triggers a warning pop-up window. Click :guilabel:`Allow` to download the configuration profile, and close the second pop-up window. Then,"
msgid "If you need to export SSL certificates from an operating system or web browser that has not been mentioned, search for `export SSL certificate` + `the name of your browser or operating system` in your preferred search engine."
msgid "Similarly, to import SSL certificates from an unmentioned OS or browser, search for `import SSL certificate root authority` + `the name of your browser or operating system` in your preferred search engine."
msgid "To confirm your printer's connection is secure, connect to its IP address using HTTPS. For example, navigate to `https://192.168.1.25` in your browser. If the SSL certificate has been applied correctly, you should no longer see a warning page, and the address bar should display a padlock icon, indicating that the connection is secure."
msgid "If **Direct Devices** is enabled in a Point of Sale settings (for example, if you use an :doc:`ePos printer <epos_printers>`), HTTP becomes the default protocol."
msgid "To do so, activate the :ref:`developer mode <developer-mode>`, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`, then create a new parameter, add the following values and click on *Save*."
msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` port or to the network, and power it on. Refer to :doc:`../restaurant/kitchen_printing`."
msgid "The barcode scanner must end barcodes with an `ENTER` character (keycode 28) in order for the barcode scanner to be compatible. This is most likely the barcode scanner's default configuration."
msgid "Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the :abbr:`PoS (Point of Sale)` order. Refer to :doc:`/applications/general/iot/devices/screen`."
msgid "The connection process depends on the terminal. Refer to the :doc:`payment terminals documentation </applications/sales/point_of_sale/payment_methods>`."
msgid ":ref:`Access the POS settings <configuration/settings>` and select your POS, or click the vertical ellipsis button (:guilabel:`⋮`) on a POS card and click :guilabel:`Edit`. Scroll down to the :guilabel:`Connected Devices` section, enable :guilabel:`IoT Box`, then select the devices to be used for the POS. Click :guilabel:`Save`."
msgid "Click :guilabel:`IoT Devices` to access the list of :doc:`/applications/general/iot/devices` for your POS and view their connection status. Click a card to access the device's form."
msgid "Odoo Point of Sale allows you to manage access to a specific POS by enabling the **Multi Employees per Session** feature. When activated, :ref:`you can select which users can log into the POS <employee_login/use>` and :ref:`keep track of the employees involved in each order <employee_login/analytics>`."
msgid ":ref:`Access the POS settings <configuration/settings>` and select your POS, or click the vertical ellipsis button (:guilabel:`⋮`) on a POS card and click :guilabel:`Edit`. Then, enable :guilabel:`Multi Employees per Session`, and add the allowed employees in the :guilabel:`Allowed Employees` field."
msgid "Once the feature is activated, cashiers can log in :ref:`by scanning their badge <employee_login/badge>` or selecting their name from the list of allowed employees to :ref:`open the session <pos/session-start>`."
msgid "To switch to another user :ref:`from an open session <pos/session-start>`, click the employee name at the top-right of the screen and select the employee to swap with from the list."
msgid "You can also require your employees to enter a pin code every time they log into a POS to prevent them from logging in as someone else. To define the code, go to the **Employees** app, open the employee form, and click the :guilabel:`HR settings` tab. Then, enter a pin code of your choice in the :guilabel:`PIN Code` field of the :guilabel:`Attendance/Point of Sale` category."
msgid "For your employees to be able to log in by scanning their badge, they must have a badge ID assigned. To do so, go to the **Employees** app, open the employee form, and click the :guilabel:`HR settings` tab. Then, enter the badge ID of your choice in the :guilabel:`Badge ID` field of the :guilabel:`Attendance/Point of Sale` category or click :guilabel:`Generate`."
msgid "To switch to another user, lock the session by clicking the lock-shaped icon (:guilabel:`🔓`) at the top-right of the screen and scan your badge."
msgid "Once you close and post the POS session, access the comprehensive report to review all session activities, including who initiated the session and who handled specific orders. To access the session's report, click the vertical ellipsis button (:guilabel:`⋮`) on the POS card and select :guilabel:`Sessions` from the :guilabel:`View` section. Then, select a specific session for more detailed information, and click the :guilabel:`Orders` button to view a list of all orders placed during that session."
msgid "To get an overview of all orders, regardless of the session, click the vertical ellipsis button (:guilabel:`⋮`) on the POS card and select :guilabel:`Orders` from the :guilabel:`View` section."
msgid "To add a payment method, you first need to create it. Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods --> New`, and set a name. Check :guilabel:`Identify Customer` to allow this payment method *exclusively* for registered customers."
msgid "Then, select the :guilabel:`Journal`. Choose :guilabel:`Cash` to use this payment method for cash payments, or :guilabel:`Bank` to use it for card payments."
msgid "Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal` field in which you can add your :doc:`payment terminal's information <payment_methods/terminals>`."
msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings <configuration/settings>`, click :guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` section."
msgid "Connecting and integrating a payment terminal with your POS system allows you to accept multiple payment options, including credit and debit cards, making the payment process more efficient."
msgid "Go to the :ref:`application settings <configuration/settings>`, scroll down to the :guilabel:`Payment Terminals` section, and tick your terminal's checkbox."
msgid "When processing a payment, select the terminal's payment method. Check the amount and click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`."
msgid "In case of connection issues between Odoo and the payment terminal, force the payment by clicking on :guilabel:`Force Done`, which allows you to validate the order."
msgid "Adyen terminals can be used in many countries, but not worldwide. Check the `List of countries supported by Adyen <https://docs.adyen.com/point-of-sale/what-we-support/supported-languages/>`_."
msgid "Start by creating your Adyen account on `Adyen's website <https://www.adyen.com/>`_. Then, board your terminal following the steps described on your terminal's screen."
msgid "The **Adyen API key** is used to authenticate requests from your Adyen terminal. To generate an API key, go to your :menuselection:`Adyen account --> Developers --> API credentials`, and **create** new credentials or select **existing** ones. Click :guilabel:`Generate an API key` and save the key to paste it into the Odoo :guilabel:`Adyen API key` field at :ref:`the payment method creation <adyen/method-creation>`."
msgid "To find this number, go to your :menuselection:`Adyen account --> Point of Sale --> Terminals`, select the terminal to link with, and save its serial number to paste it into the Odoo :guilabel:`Adyen Terminal Identifier` field at :ref:`the payment method creation <adyen/method-creation>`."
msgid "Enable the payment terminal :ref:`in the application settings <configuration/settings>` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` field."
msgid "Finally, fill in the mandatory fields with your :ref:`Adyen API key <adyen/api>`, :ref:`Adyen Terminal Identifier <adyen/identifier>`, and :guilabel:`Adyen Merchant Account`."
msgid "Connecting an Ingenico payment terminal to Odoo is a feature that requires an IoT system. For more information on how to connect an IoT system to your database, please refer to the :doc:`IoT documentation </applications/general/iot>`."
msgid "Enable the payment terminal :ref:`in the application settings <configuration/settings>` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Ingenico` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field."
msgid "Only **Point Smart** payment terminals in **Argentina**, **Brazil**, and **Mexico** are supported. They can be purchased on `Mercado Pago's website <https://www.mercadopago.com.mx/herramientas-para-vender/lectores-point>`_."
msgid "Associate your Point Smart terminal with a :guilabel:`store` and a :guilabel:`cash drawer` by following `Mercado Pago's documentation <https://vendedores.mercadolibre.com.ar/nota/locales-una-herramienta-para-mejorar-la-gestion-de-tus-puntos-de-venta/>`_."
msgid "Create a new application from Mercado Pago's `developer panel <https://www.mercadopago.com/developers>`_ by following `Mercado Pago's applications documentation <https://www.mercadopago.com.mx/ayuda/20152>`_, making sure you select :guilabel:`In person Payments`."
msgid "Retrieve the access token and webhook secret key by following `Mercado Pago's credentials documentation <https://www.mercadopago.com.mx/developers/en/docs/your-integrations/credentials>`_. Then, copy and paste them into Odoo when creating the payment method."
msgid "For the webhooks configuration, add the URL of your Odoo database (e.g., `https://mycompany.odoo.com`) followed by `/pos_mercado_pago/notification` (e.g., `https://mycompany.odoo.com/pos_mercado_pago/notification`)."
msgid ":doc:`Create the related payment method <../../payment_methods>` by going to :menuselection:`Point of Sale --> Configuration --> Payment Methods`."
msgid "Select the payment method by going to the :ref:`POS' settings <configuration/settings>` and adding it to the payment method under the :guilabel:`Payment Methods` field of the :guilabel:`Payment` section."
msgid "Any action made on the terminal should trigger a notification on the POS interface. Ensure the :ref:`webhook secret key <pos-mercado-pago-credentials>` is correctly configured if you are not notified."
msgid "Enter your username in the :guilabel:`Razorpay Username` field and your device's serial number in the :guilabel:`Razorpay Device Serial No` field."
msgid "Once the payment method is created, you can enable it for your POS. To do so, go to the :ref:`POS' settings <configuration/settings>` and add the payment method under the :guilabel:`Payment` section."
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."
msgid "To activate the POS IoT Six module, go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds the necessary driver and interface to your database to detect Six terminals."
msgid "Navigate to the IoT system's homepage, where you can find the :guilabel:`Six payment terminal` field once your database server is connected to the IoT system. Click :guilabel:`Configure`, fill in the :guilabel:`Terminal ID` field with the ID received from Six, and click :guilabel:`Connect`. Your Six terminal ID should appear in the :guilabel:`Current Terminal Id` section."
msgid "Odoo automatically restarts the IoT system when the Six terminal ID is configured. If your Six terminal is online, it will be automatically detected and connected to the database. Check the IoT system's homepage under the :guilabel:`Payments` section to confirm the connection."
msgid "Enable the payment terminal :ref:`in the application settings <configuration/settings>` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`SIX IOT` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field."
msgid "Stripe terminals can be used in many countries, but not worldwide. Check the `global availability for Stripe Terminal <https://support.stripe.com/questions/global-availability-for-stripe-terminal>`_."
msgid "Activate **Stripe** in the settings by going to :menuselection:`Point of Sale --> Configuration --> Settings --> Payment Terminals` and enabling :guilabel:`Stripe`."
msgid "Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, click :guilabel:`Create`, and complete the :guilabel:`Method` field with your payment method's name;"
msgid "Click :guilabel:`Identify Customer` to allow this payment method **exclusively** for identified customers. For any unidentified customers to be able to pay with Stripe, leave the :guilabel:`Identify Customer` field unchecked."
msgid "Click :guilabel:`Connect Stripe`. Doing so redirects you automatically to a configuration page. Fill in all the information to create your Stripe account and link it with Odoo. Once the forms are completed, the API keys (:guilabel:`Publishable Key` and :guilabel:`Secret Key`) can be retrieved on **Stripe's** website. To do so, click :guilabel:`Get your Secret and Publishable keys`, click the keys to copy them, and paste them into the corresponding fields in Odoo. Your terminal is ready to be configured in a POS."
msgid "For databases hosted **On-Premise**, the :guilabel:`Connect Stripe` button does not work. To retrieve the API keys manually, log in to your `Stripe dashboard <https://dashboard.stripe.com>`_, type `API` in the search bar, and click :guilabel:`Developers > API`."
msgid "To add a **payment method** to your point of sale, go to :menuselection:`Point of Sale --> Configuration --> Settings`. Select the POS, scroll down to the :guilabel:`Payments` section, and add your payment method for **Stripe** in the :guilabel:`Payment Methods` field."
msgid "Log into your `Stripe's dashboard <https://dashboard.stripe.com>`_ and go to :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;"
msgid "You must provide a **registration code**. To retrieve that code, swipe right on your device, enter the admin PIN code (by default: `07139`), validate, and click :guilabel:`Generate a registration code`."
msgid "Vantiv card readers should be purchased exclusively from Vantiv, as certain Vantiv terminals bought on Amazon do not include the correct encryption needed to be used with an Odoo database."
msgid "Then, go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Vantiv` in the :guilabel:`Use a Payment Terminal` field."
msgid "Type the name you want to give to your :guilabel:`Vantiv Credentials` and click :guilabel:`Create and edit`. Enter your :guilabel:`Merchant ID` and :guilabel:`Merchant Password`, then click :guilabel:`Save & Close`."
msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings <configuration/settings>` and add the payment method under the :guilabel:`Payment` section."
msgid "Connecting a **Viva Wallet** :doc:`payment terminal <../terminals>` allows you to offer a fluid payment flow to your customers and ease the work of your cashiers."
msgid "When configuring Viva Wallet in Point of Sale, you need to use specific credentials that are available in your Viva Wallet account. These credentials include your :ref:`Merchant ID <viva_wallet/id-key>`, :ref:`API key <viva_wallet/id-key>`, :ref:`POS API credentials <viva_wallet/pos-api>`, and :ref:`Terminal ID <viva_wallet/identifier>` number."
msgid "Locate your `Merchant ID and API key following the Viva documentation <https://developer.vivawallet.com/getting-started/find-your-account-credentials/merchant-id-and-api-key/>`_. Then, save the keys and paste them into the Odoo :guilabel:`Merchant ID` and :guilabel:`API Key` fields :ref:`when creating the payment method <viva_wallet/method-creation>`."
msgid "Locate and generate your `POS API credentials following the Viva documentation <https://developer.vivawallet.com/getting-started/find-your-account-credentials/pos-api-credentials/>`_. Then, save the keys and paste them in the Odoo :guilabel:`Client secret` and :guilabel:`Client ID` fields :ref:`when creating the payment method <viva_wallet/method-creation>`."
msgid "The terminal ID number is located under the :guilabel:`Terminal ID (TID)` column. Save it to paste it into the :guilabel:`Terminal ID` field :ref:`when creating the payment method <viva_wallet/method-creation>`."
msgid ":doc:`Create the related payment method <../../payment_methods>` by going to :menuselection:`Point of Sale --> Configuration --> Payment Methods` and clicking :guilabel:`New`."
msgid "Save the form and copy the generated webhook URL from the :guilabel:`Viva Wallet Webhook Endpoint` field. This URL is necessary :ref:`when configuring the webhook <viva_wallet/webhook>`."
msgid "Webhooks allow you to receive real-time notifications whenever a transaction occurs within your Viva Wallet account. Set them up for `payment transactions following the Viva documentation <https://developer.vivawallet.com/webhooks-for-payments/transaction-payment-created/>`_."
msgid "You can select the payment method in your POS settings once the payment method is created. To do so, go to the :ref:`POS' settings <configuration/settings>` and add the payment method under the :guilabel:`Payment methods` field of the :guilabel:`Payment` section."
msgid "Odoo is compatible with Worldline terminals that use the CTEP protocol (e.g., the Yomani XR and Yoximo terminals). If you have any doubts, contact your payment provider to ensure your terminal's compatibility."
msgid "Connecting a Worldline Payment Terminal to Odoo is a feature that requires an IoT system. For more information on how to connect one to your database, please refer to the :doc:`IoT documentation </applications/general/iot>`."
msgid "On the *Port number* screen, enter **9001** (or **9050** for Windows) and click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> OK`. Click on **Stop** three times; the terminal automatically restarts."
msgid "For the :doc:`Windows virtual IoT </applications/general/iot>`, the `9050` port must be added as a :ref:`Windows Firewall exception <iot/windows-iot/firewall>`."
msgid "Enable the payment terminal :ref:`in the application settings <configuration/settings>` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Worldline` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field."
msgid "To reach Wordline's technical assistance, call `02 727 61 11` and choose \"merchant\". Your call is automatically transferred to the desired service."
msgid "To edit a pre-existing preparation display, click the vertical ellipsis button (:icon:`fa-ellipsis-v`) on the display's card and select :guilabel:`Configure`."
msgid "**Stages and order count**: Displays the progress of orders across stages such as `To prepare`, `Ready`, and `Completed`, along with the number of orders in each stage."
msgid "In parallel, click :guilabel:`Open customer display` to open the customer interface. This interface, designed for customers, provides an overview of orders that are:"
msgid "**Cash rounding** is required when the lowest physical denomination of currency, or the smallest coin, is higher than the minimum unit of account."
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."
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."
msgid "Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*, then save both the Rounding Method and your Point of Sale settings."
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."
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:"
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."
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."
msgid "By default, Odoo has a *Public Pricelist* configured. To create more, go to :menuselection:`Point of Sale --> Products --> Pricelists`. Then click on create."
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."
msgid "Electronic shelf labels allow you to display product information like prices and barcodes on store shelves and to synchronize them remotely from the backend. This removes the need to print new labels when product information changes."
msgid "Create the following variables to share product information between your Odoo database system and Pricer. These variables act like placeholders on the label template."
msgid "As a pre-requisite, :ref:`activate <general/install>` the :guilabel:`POS Pricer` module *(technical name: pos_pricer)* to have all the required features to use Pricer electronic tags."
msgid "Once the module is activated, configure your :ref:`pricer stores <pricer_tags/stores>` and associate :ref:`Pricer tags <pricer_tags/tags>` with your products."
msgid "Similarly to the configuration in Pricer, you need to create one pricer store per physical location. To do so, go to :menuselection:`Point of Sale --> Configuration --> Pricer Stores`, click :guilabel:`New`, and fill in the line with the required information:"
msgid ":guilabel:`Pricer Tenant Name`: the name of your company account in Pricer, usually followed by `-country_code`. This value is provided by Pricer."
msgid "Open the product form by going to :menuselection:`Point of Sale --> Products --> Products` and clicking :guilabel:`New` or selecting an existing product."
msgid "When setting up Pricer with Odoo for the first time, it is recommended that you configure only one product first. Before configuring more products, ensure you can display their information on a Pricer tag."
msgid "If Pricer has processed and accepted the request, the status field shows :guilabel:`Update successfully sent to Pricer`. If there is any issue, the system displays an error message."
msgid "If a request sent to Pricer fails, Odoo still considers that the product has been updated. In that case, we recommend forcing the update of all tags."
msgid "When running a business, you may need to apply different taxes and record transactions on various accounts based on the location and type of business of your customers and providers."
msgid "The **fiscal positions** feature enables you to establish rules that automatically select the right taxes and accounts used for each transaction."
msgid "To enable the feature, go to :menuselection:`Point of Sale --> Configuration --> Settings`, scroll down to the :guilabel:`Accounting` section, and enable :guilabel:`Flexible Taxes`."
msgid "Then, set a default fiscal position that should be applied to all sales in the selected POS in the :guilabel:`Default` field. You can also add more fiscal positions to choose from in the :guilabel:`Allowed` field."
msgid "According to the :doc:`fiscal localization package <../../../finance/fiscal_localizations>` activated, several fiscal positions are preconfigured and can be set and used in POS. However, you can also :ref:`create new fiscal positions <fiscal_positions/mapping>`."
msgid "Open a :ref:`POS session <pos/session-start>` to use one of the allowed fiscal positions. Then, click the :guilabel:`Tax` button next to the **book-shaped** icon and select a fiscal position from the list. Doing so applies the defined rules automatically to all the products subject to the chosen fiscal position's regulations."
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*"
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."
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."
msgid "Pricelists allow you to adjust product prices depending on various criteria automatically. For example, you can set POS-specific prices, create temporary discount periods, reward specific customers, or offer discounts when set quantities are ordered."
msgid "Navigate to the :ref:`general POS app settings <configuration/settings>` and ensure :guilabel:`Flexible Pricelists` are enabled under the :guilabel:`Pricing` section."
msgid ":ref:`Multiple prices per product <pricelists/simple>` is the default pricelist option for setting simple fixed price rules per product. Select :ref:`Advanced price rules (discounts, formulas) <pricelists/advanced>` to apply price rules to multiple products at once and to compute prices dynamically using percentage discounts or more complex formulas in addition to setting fixed prices."
msgid "The selected pricelist type applies to the entire database, including the :doc:`Sales <../../sales/products_prices/prices/pricing>` and :ref:`eCommerce <ecommerce/pricelists>` apps."
msgid "Go to :menuselection:`Point of Sale --> Products --> Pricelists` and click :guilabel:`New` or select an existing pricelist. The pricelist setup differs depending on the :ref:`selected pricelist option <pricelists/configuration>`."
msgid "When pricelists are configured to use the :guilabel:`Multiple prices per product` option, it is possible to use multiple fixed prices for different products or their variants depending, if necessary, on one or several conditions. To add a new price rule to a pricelist:"
msgid "When pricelists are configured to use the :guilabel:`Advanced price rules (discounts, formulas)` option, it is possible to use percentage discounts/mark-ups and formulas in addition to using fixed prices. To add a new price rule to a pricelist, click :guilabel:`Add a line`. In the pop-up windows:"
msgid ":guilabel:`Formula` to compute the price according to a formula. It is required to define what the calculation is **based on** (:guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`). You can then:"
msgid "Define a :doc:`Rounding Method <cash_rounding>` by forcing the price after :guilabel:`Discount` to be a multiple of the value set. The :guilabel:`Extra Fee` is applied afterward."
msgid "Add conditions, such as a specific quantity to reach for the price to change by using the :guilabel:`Min. Quantity` field or a specific period during which the pricelist should be applied by using the :guilabel:`Validity` fields."
msgid "Go to the :ref:`specific POS settings <configuration/settings>` and add all the available pricelists in the :guilabel:`Available` field. Then, set its **default pricelist** in the :guilabel:`Default` field."
msgid "You can also set a pricelist to be selected automatically once a specific :ref:`customer is set <pos/customers>`. To do so, go to the customer form and switch to the preferred pricelist in the :guilabel:`Pricelist` field of the :guilabel:`Sales & Purchase` tab."
msgid "Set up receipts by going to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, selecting a POS, and scrolling down to the :guilabel:`Bills & Receipts` section."
msgid "To **customize** the **header** and **footer**, activate :guilabel:`Header & Footer` and fill in both fields with the information to be printed on the receipts."
msgid "From the POS interface, click :guilabel:`Orders`, open the dropdown selection menu next to the search bar, and change the default :guilabel:`All active orders` filter to :guilabel:`Paid`. Then, select the corresponding order and click :guilabel:`Print Receipt`."
msgid "You can filter the list of orders using the search bar. Type in your reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or :guilabel:`Customer`."
msgid "Point of Sale allows you to issue and print invoices for :ref:`registered customers <pos/customers>` upon payment and retrieve all past invoiced orders."
msgid "An invoice created in a POS creates an entry into the corresponding :ref:`accounting journal <cheat_sheet/journals>`, previously :ref:`set up <receipts_invoices/invoice_configuration>`."
msgid "To define what journals will be used for a specific POS, go to the :ref:`POS' settings <configuration/settings>` and scroll down to the accounting section. Then, you can determine the accounting journals used by default for orders and invoices in the :guilabel:`Default Journals` section."
msgid "Customers can also request an invoice by scanning the **QR code** printed on their receipt. Upon scanning, they must fill in a form with their billing information and click :guilabel:`Get my invoice`. On the one hand, doing so generates an invoice available for download. On the other hand, the order status goes from :guilabel:`Paid` or :guilabel:`Posted` to :guilabel:`Invoiced` in the Odoo backend."
msgid "To use this feature, you have to enable QR codes on receipts by going to :menuselection:`Point of Sale --> Configuration --> Settings`. Then, select the POS in the :guilabel:`Point of Sale` field, scroll down to the :guilabel:`Bills & Receipts` section and enable :guilabel:`Use QR code on ticket`."
msgid "To access your statistics, go to :menuselection:`Point of Sale --> Reporting --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis (:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`."
msgid "Managing a restaurant or a bar comes with specific needs. The Point of Sale application provides various features that allow performing all the required tasks in such businesses."
msgid "To enable the restaurant and bar-specific features, go to :menuselection:`Point of Sale --> Configuration --> Settings`, select the POS, and activate :guilabel:`Is a Bar/Restaurant`."
msgid "Click a table to access the POS interface and start taking your customer's order. The system automatically associates the orders and the table, allowing you to add more items later and generate a bill specifically for that table's orders."
msgid "As soon as you click a table, the number of guests is automatically set to one. If you mistakenly select a table, click :guilabel:`Release table` to free it or :ref:`transfer the customer <floors_tables/transfer>` to another table."
msgid "Typical practices in restaurants or bars are to request the bill before proceeding to payment or splitting it based on the items ordered. Odoo POS provides two features to perform these tasks seamlessly: **Bill Printing** and **Bill Splitting**."
msgid "To activate the features, go to :menuselection:`Point of Sale --> Configuration --> Settings`, select the POS, and activate :guilabel:`Early Receipt Printing` and :guilabel:`Allow Bill Splitting` in the :guilabel:`Restaurant & Bar` section."
msgid "From an open session, click :guilabel:`Split` to select the items to regroup. Once everything is selected, click :guilabel:`Payment` and proceed to checkout for these items. Repeat for each guest."
msgid "The **Floor plan view** enables you to manage restaurant floors and table arrangements and monitor table status in real time, including occupancy, reservations, and kitchen orders."
msgid "To create floors and tables from the backend, go to :menuselection:`Point of Sale --> Configuration --> Floor Plans`, and click :guilabel:`New` to create a floor. Name it, select the related point(s) of sales, and click :guilabel:`Add a line` to create a table. Name the table and assign a number of seats. You can also link it to an appointment resource to make the table bookable. Once done, click :guilabel:`Save & Close` or :guilabel:`Save & New` to confirm."
msgid "The POS must be opened and :ref:`edited from the frontend <floors_tables/frontend>` to create a map of your restaurant or bar reflecting your actual floor plan."
msgid "Create floors on the spot: :ref:`access your POS settings <configuration/settings>`, type your floor name in the :guilabel:`Floor` field of the :guilabel:`Floors & Tables Map` category, and press *enter*."
msgid "To create floors and tables from the frontend, :ref:`open a POS session <pos/session-start>`, click the hamburger menu icon :guilabel:`≡` in the upper right corner, then :guilabel:`Edit Plan` to enter the **edit mode**."
msgid "Once a floor is created, add a table by clicking :guilabel:`+ TABLE`. To move it, select it and drag and drop it as desired. You can also modify the attributes of the selected table, such as the number of seats by clicking :guilabel:`SEATS`, the table shape using :guilabel:`SHAPE`, the table color using :guilabel:`FILL`, or the table name by clicking :guilabel:`RENAME`. To duplicate an existing table, select it and click :guilabel:`COPY`. You can also remove the table by clicking :guilabel:`DELETE`."
msgid "To move customers from one table to another, select a table and click :guilabel:`→ Transfer` on the POS interface. This redirects you to the floor plan view, where you can choose the new table to which you want to transfer the customers."
msgid "Integrating printers in a restaurant or bar's workflow can enhance communication and collaboration between the front-of-house and back-of-house teams, leading to a more streamlined and efficient service."
msgid "To enable sending orders to a kitchen or bar printer, go to :menuselection:`Point of Sale --> Configuration --> Settings`, scroll down to the :guilabel:`Restaurant & Bar` section, and enable :guilabel:`Kitchen Printers`. Type in a name for the printer in the :guilabel:`Printers` field and click :guilabel:`Create and edit...` to open a setup form."
msgid "To get a list of all the printers already created or to modify an already created printer, click :guilabel:`--> Printers` and select the desired printer to open the setup form."
msgid "If your printer is connected to an IoT system, select :guilabel:`Use a printer connected to the IoT Box` and select the device in the :guilabel:`IoT Device` field."
msgid "If you use an Epson printer that does not require an IoT system, select :guilabel:`Use an Epson printer` and enter the printer's IP address in the :guilabel:`Epson Printer IP Address` field."
msgid "Set your printer to print specific products based on their POS category. To do so, click :guilabel:`Add a line` in the :guilabel:`Printed Product Categories` field. If you leave this field empty, all products are sent to the printer regardless of their POS category."
msgid "Tipping is customary in multiple countries. Point of Sale allows tipping in :ref:`shops <pos/sell>`, :doc:`bars <../restaurant>`, or :doc:`restaurants <../restaurant>`."
msgid "To allow tipping in your POS, activate the :guilabel:`Tips` feature in :menuselection:`Point of Sale --> Configuration --> Settings`. At the top of the page, select the POS in which you wish to allow **tipping**, scroll down to the :guilabel:`Payment` section and check :guilabel:`Tips`. Once enabled, add a :guilabel:`Tip Product` in the corresponding field, and save. The designated product will be used as a reference on customers' receipts."
msgid "**Tip products** can be created on the spot. To do so, enter a product's name in the :ref:`Tip Product <configuration>` field and click :guilabel:`Create` or press **enter**. The product is automatically configured to be used as a tip at the payment screen."
msgid "However, if you wish to be able to select the tip product in a POS session, you must activate the **Available in POS** setting. To do so, click :guilabel:`Create and edit...` to open the product configuration form. Then, go to the :guilabel:`Sales` tab, tick the :guilabel:`Available in POS` checkbox, and click :guilabel:`Save & Close`."
msgid "If you use an :doc:`Adyen <../payment_methods/terminals/adyen>` payment terminal and wish to enable **tips** using the terminal, check :guilabel:`Add tip through payment terminal (Adyen)` below the :ref:`tip settings <configuration>`."
msgid "If you use a POS system in a bar or a restaurant, you can enable :guilabel:`Add tip after payment (North America specific)`. Doing so generates a bill to print and complete manually by the customer and the waiter. That bill indicates the tip value the customer chooses to give after the payment."
msgid "To add tips to an order, :ref:`access the payment screen <pos/sell>` and click :guilabel:`♥ Tip`. Then, enter the tipping amount, click :guilabel:`Confirm` to validate, and process the payment."
msgid "Alternatively, you can select the :ref:`tip product <tip-product>` on the POS interface to add it to the cart. When selected, the product is automatically set as a tip, and its default value equals its **Sales Price**."
msgid "During checkout, select **Adyen** as the payment terminal, and send the payment request to the device by clicking :guilabel:`Send`. The customers are asked to enter the desired tipping amount on the terminal's screen before proceeding to the payment."
msgid "On the following screen, click the percentage (:guilabel:`15%`, :guilabel:`20%`, :guilabel:`25%`), :guilabel:`No Tip`, or enter the tipping amount the customer chose to give. Then, click :guilabel:`Settle` to move to the following order."
msgid "Using a barcode scanner to process point-of-sale orders improves your efficiency in providing quicker customer service. Barcode scanners can be used both to scan products or to log employees into a POS session."
msgid "To use a barcode scanner, you must enable the feature in the Inventory app. Go to :menuselection:`Inventory --> Configuration --> Settings`, in the :guilabel:`Barcode` section, tick :guilabel:`Barcode Scanner` and save."
msgid "To use this feature in POS, your products must have barcodes assigned. To do so, go to :menuselection:`Point of Sale --> Products --> Products` and open a **product form**. Add a barcode number in the :guilabel:`Barcode` field in the :guilabel:`General Information` tab."
msgid "To add an identification number to an employee, go to the **Employees** app and open an **employee form**. Choose an identification number for your employee and fill in the :guilabel:`PIN Code` field in the :guilabel:`HR Settings` tab."
msgid "Scan a product's barcode using a barcode scanner. Doing so adds it directly to the cart. To change the quantity, scan a product as many times as needed, or click :guilabel:`Qty` and enter the number of products using the keypad."
msgid "You can also use a barcode scanner to log your employees. To do so, :ref:`restrict access <employee_login/configuration>` to the POS and :ref:`use barcodes to log your employees in <employee_login/badge>` your POS."
msgid "Depending on your POS setup, the feature can be displayed :ref:`locally on a secondary screen <customer_display/local>` or on :ref:`another monitor connected to an IoT Box <customer_display/iot>`."
msgid "To activate the feature, go to the POS settings, scroll down to the :guilabel:`Connected Devices` section, and tick the :guilabel:`Customer Display` checkbox."
msgid "Connect a second screen to your POS and :ref:`open a POS session <pos/session-start>`. Then, click :guilabel:`Customer Screen` to open a new window to drag and drop onto the second screen."
msgid "Connect an IoT box to your database and the second screen to the IoT box. Then, go to :menuselection:`Point of Sale --> Configuration --> Settings`, scroll down to the :guilabel:`Connected Devices` section, tick the :guilabel:`IoT Box` checkbox, and select the second monitor in the :guilabel:`Customer Display` field."
msgid "When working in retail, you might need to order products directly from your Point of sale. Fortunately, Odoo Point of Sale is fully integrated with Odoo Sales, meaning that you can create a sales order and pay for it directly from your point of sale."
msgid "From the **Point of Sale** application, open a new session. Then, click on :guilabel:`Quotations/Orders` to get the complete list of quotations and sales orders created on the sales application."
msgid "To ease finding the right sales order, you can filter that list on the **customer** or on the **order reference**. You can also set the customer before clicking on :guilabel:`Quotations/Orders` to reduce the list to one particular customer."
msgid "Settle the order **partially**: after clicking on :guilabel:`Apply a down payment`, enter the percentage of down payment you want the customer to pay. Then, click on :guilabel:`ok` and proceed with the order."
msgid "Working with **serial numbers** and **lots** allows tracking your products' movements. When products are tracked, the system identifies their location based on their last movement."
msgid "To enable traceability, go to :menuselection:`Point of Sale --> Products --> Products`. Then, select a product and check the :guilabel:`Tracking By Unique Serial Number` or the :guilabel:`Tracking By Lots` box in the :guilabel:`Inventory` tab."
msgid "You can import serial numbers in Point of Sale. To do so, select a **sales order** or a **quotation** containing tracked products. Then, agree to load the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`."
msgid "If a tracked product is available in your POS, adding the product to the cart opens a pop-up window where you can type or scan the product's serial or lot numbers. To add more than one of the same tracked products, click on **enter** to validate and start a new line."
msgid ":guilabel:`Lot & Serial Number(s)` are :guilabel:`required` on tracked products but not mandatory. Meaning that not attributing some or any does **not** prevent from completing the sale."
msgid "The **Ship Later** feature allows you to sell products and schedule delivery at a later date. It is useful, for example, when a product is out of stock or so voluminous that it requires to be shipped, or if, for any reason, the customer needs their order to be shipped later, etc."
msgid ":ref:`Go to the POS settings <configuration/settings>`, scroll down to the :guilabel:`Inventory` section, and enable :guilabel:`Allow Ship Later`."
msgid "Define the :guilabel:`Shipping Policy`; select :guilabel:`As soon as possible` if the products can be delivered separately or :guilabel:`When all products are ready` to ship all the products at once."
msgid "Send quotations, confirm orders, schedule rentals, register products when they are picked up and returned, and invoice customers from this single platform."
msgid "Example of the Rental Orders dashboard available in the Odoo Rental application."
msgstr ""
#: ../../content/applications/sales/rental.rst:25
msgid "In the default kanban view, all rentals are visible. Each rental card displays the customer name, the price of the rental, the related sales order number, along with the status of the rental."
msgstr ""
#: ../../content/applications/sales/rental.rst:29
msgid "Rental kanban cards that do **not** display a rental status means those rentals have confirmed quotations, but have not been picked up yet."
msgid "On the left sidebar, the :guilabel:`Rental Status` for each rental can be found. Beneath that, the :guilabel:`Invoice Status` of the rentals is accessible. Clicking any option in the left sidebar filters the displayed rentals on the dashboard."
msgid "To configure additional rental delay costs, availability of rental items, or minimum time of rental, navigate to :menuselection:`Rental app --> Configuration --> Settings`."
msgid "In the :guilabel:`Rental` section, there are options to configure :guilabel:`Default Delay Costs` and :guilabel:`Default Padding Time`. There is also the option to activate :guilabel:`Rental Transfers` and :guilabel:`Digital Documents`."
msgstr ""
#: ../../content/applications/sales/rental.rst:50
msgid ":guilabel:`Default Delay Costs` are additional costs for late returns."
msgstr ""
#: ../../content/applications/sales/rental.rst:51
msgid ":guilabel:`Default Padding Time` represents the minimum amount of time between two rentals."
msgstr ""
#: ../../content/applications/sales/rental.rst:52
msgid ":guilabel:`Rental Transfers` means stock deliveries and receipts can be used for rental orders."
msgstr ""
#: ../../content/applications/sales/rental.rst:54
msgid ":guilabel:`Digital Documents` allows users to upload documents for customers to sign prior to"
msgstr ""
#: ../../content/applications/sales/rental.rst:54
msgid "confirming their rental."
msgstr ""
#: ../../content/applications/sales/rental.rst:56
msgid "In the :guilabel:`Rent Online` section, there are options to configure a :guilabel:`Minimal Rental Duration` and designate :guilabel:`Unavailability days`, or days during which pickup and return are not possible."
msgstr ""
#: ../../content/applications/sales/rental.rst:61
msgid "Rental products"
msgstr ""
#: ../../content/applications/sales/rental.rst:63
msgid "To view all products that can rented in the database, navigate to :menuselection:`Rentals app --> Products`. By default, the :guilabel:`Can be Rented` search filter appears in the search bar."
msgstr ""
#: ../../content/applications/sales/rental.rst:66
msgid "Each product kanban card displays that product's name, rental price, and product image (if applicable)."
msgstr ""
#: ../../content/applications/sales/rental.rst:70
msgid "Rental pricing"
msgstr ""
#: ../../content/applications/sales/rental.rst:72
msgid "To adjust the rental pricing on a product, go to the :guilabel:`Products` page in the *Rental* app, then select the desired product or click :guilabel:`New` to create a new product from scratch."
msgstr ""
#: ../../content/applications/sales/rental.rst:75
msgid "On the product form, ensure the :guilabel:`Can be Rented` checkbox is ticked. Then, open the :guilabel:`Rental prices` tab."
msgstr ""
#: ../../content/applications/sales/rental.rst:83
msgid "If creating a rental product outside of the *Rental* app, just ensure the :guilabel:`Can be Rented` checkbox is ticked on the product form. By default, this checkbox is ticked whenever a product is created directly in the *Rental* application."
msgstr ""
#: ../../content/applications/sales/rental.rst:90
msgid "Under the :guilabel:`Pricing` section of the :guilabel:`Rental prices` tab, designate custom rental prices and rental periods for the product."
msgstr ""
#: ../../content/applications/sales/rental.rst:93
msgid "To add pricing for a rental, click :guilabel:`Add a price`. Then, choose a *pricing period* (:dfn:`the unit of duration of the rental`) in the :guilabel:`Period` column, or create a new pricing period by typing in the name and clicking :guilabel:`Create`."
msgstr ""
#: ../../content/applications/sales/rental.rst:97
msgid "Next, decide whether or not to apply this custom rental price to a specific :guilabel:`Pricelist`."
msgstr ""
#: ../../content/applications/sales/rental.rst:99
msgid "Lastly, enter the desired :guilabel:`Price` for that specific :guilabel:`Period`."
msgid "There is no limit to how many pricing lines can be added. Multiple pricing options for rental products are typically used to give discounts for customers who agree to longer rental durations."
msgid "Under the :guilabel:`Reservations` section of the :guilabel:`Rental prices` tab, there is the option to configure additional fines for any :guilabel:`Extra Hour` or :guilabel:`Extra Day` that the customer takes to return a rental."
msgid "There is also the option to set a :guilabel:`Security Time`, expressed in hours, to make the rental product temporarily unavailable between two rental orders. Such a feature may prove useful if maintenance or cleaning is required between rentals."
msgid "After an order is created, Odoo selects the second line as this is the cheapest option. The customer has to pay three times '3 days' to cover the rental's eight days, for a total of $750."
msgid "To create a rental order in the *Rental* app, navigate to :menuselection:`Rental app --> Orders --> Orders`, and click :guilabel:`New`. Doing so reveals a blank rental order form to be filled in accordingly."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "Sample of a filled out rental order available in the Odoo Rental application."
msgid "To adjust the rental duration, click the first date in the :guilabel:`Rental period` field, and select the range of dates to represent the rental duration from the pop-up calendar form that appears."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "Sample of a rental period calendar pop-up window in the Odoo Rental application."
msgid "Once complete, click :guilabel:`Apply` in the calendar pop-up form. Following that, the pop-up form disappears, and the designated time period of the rental is represented in the :guilabel:`Duration` field."
msgid "Next, add a rental product in the :guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and selecting the desired rental product to add to the form."
msgid "If a rental product is added *before* the :guilabel:`Rental period` field has been properly configured, the user can *still* adjust the :guilabel:`Rental period` field accordingly."
msgid "Simply select the desired range of dates to represent the duration of the rental, then click :guilabel:`Update Rental Prices` in the :guilabel:`Duration` field."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "The update rental prices option that appears in the Odoo Rental application."
msgid "Doing so reveals a :guilabel:`Confirmation` pop-up window. If everything is correct, click :guilabel:`Ok`, and Odoo recalculates the rental price accordingly."
msgid "Once all the information has been entered correctly on the rental order form, click the :guilabel:`Send by Email` button to send the quotation to the customer, or click the :guilabel:`Confirm` button to confirm the order."
msgid "Upon confirming a rental order, the :guilabel:`Sign Documents` button appears. This gives the ability to request the customer sign a rental agreement, outlining the arrangement between the company and customer, *before* they pick up the rental product(s)."
msgid "The :guilabel:`Sign Documents` button/option **only** appears if the :guilabel:`Digital Documents` feature has been activated in the *Rental* application settings. To do so, navigate to :menuselection:`Rental app --> Configuration --> Settings`, activate :guilabel:`Digital Documents`, and click :guilabel:`Save`."
msgid "This feature also requires the :doc:`Sign <../productivity/sign>` app. If necessary, Odoo automatically installs it after activating the :guilabel:`Digital Documents` setting."
msgid "To request a customer signature on a rental agreement, select a confirmed rental order, and click the :guilabel:`Sign Documents` button to reveal a :guilabel:`Sign Documents` pop-up window."
msgid "From here, select the desired document from the :guilabel:`Document Template` field. Then, click :guilabel:`Sign Document`. Doing so reveals a :guilabel:`New Signature Request` pop-up window."
msgid "Upon confirming the information in the :guilabel:`New Signature Request` pop-up form, click :guilabel:`Sign Now` to initiate the signing process."
msgid "Odoo guides the customer through the signing process with clear, clickable indicators, and allows them to create electronic signatures to quickly complete the form."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "The adopt your signature pop-up window that appears in the Odoo Rental application."
msgid "Once the document has been signed and completed, click the :guilabel:`Validate & Send Completed Document` button at the bottom of the document."
msgstr ""
#: ../../content/applications/sales/rental.rst:-1
msgid "The validate and send completed document button in the Odoo Rental application."
msgid "Upon clicking the :guilabel:`Validate & Send Completed Document` button, Odoo presents the option to download the signed document for record-keeping purposes, if necessary."
msgid "When a customer picks up the product(s), navigate to the appropriate rental order, click the :guilabel:`Pickup` button, and then click :guilabel:`Validate` in the :guilabel:`Validate a pickup` pop-up form that appears."
msgid "When a customer returns the product(s), navigate to the appropriate rental order, click the :guilabel:`Return` button, and validate the return by clicking :guilabel:`Validate` in the :guilabel:`Validate a return` pop-up form that appears."
msgid "To print pickup and/or return receipts, navigate to the appropriate rental order, click the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu."
msgid "The *Amazon Connector* synchronizes orders between Amazon and Odoo, which considerably reduces the amount of time spent manually entering Amazon orders (from the Amazon Seller account) into Odoo. It also allows users to accurately keep track of Amazon sales in Odoo."
msgid "A delivery order is automatically created in Odoo for each new order. Once it has been processed in Odoo, the status is then synchronized in Amazon."
msgid "Cost is computed by Amazon, and included in the synchronized order. Gift message is added on a line of the order and on the delivery order. Then it is up to the user."
msgid "The stock synchronization does **not** currently support selling the same product as :abbr:`FBM (Fulfilled By Merchant)` *and* :abbr:`FBA (Fulfilled By Amazon)`."
msgid "At times, when stock is sent for all products, it triggers a stock problem with Amazon, where Amazon incorrectly thinks the :abbr:`FBM (Fulfilled By Merchant)` product has some quantity in :abbr:`FBM (Fulfilled By Merchant)`."
msgid "As a result, Amazon then sells it as :abbr:`FBM (Fulfilled By Merchant)`, instead of taking from their own warehouse. Odoo developers are currently working on resolving this issue to avoid future discrepancies."
msgid "The Amazon Connector is designed to synchronize the data of sales orders. Other actions, such as downloading monthly fees reports, handling disputes, or issuing refunds, **must** be managed from the *Amazon Seller Central*, as usual."
msgid "As of February 19, 2024, in North American marketplaces, :abbr:`FBA (Fulfilled by Amazon)` orders created with the *Amazon Connector*, do not get the customer's name passed onto the sales/delivery order in Odoo. This is due to the fact that Amazon now calculates, and remits, sales tax on behalf of sellers. In other words, personally identifiable customer information is not transmitted to the seller any longer, after a :abbr:`FBA (Fulfilled by Amazon)` order."
msgid "The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. This includes changes on either end (Amazon or Odoo)."
msgid "For *FBM* (Fulfilled by Merchant), the same is done for *Unshipped* and *Canceled* orders. For each synchronized order, a sales order and customer are created in Odoo (if the customer is not already registered in the database)."
msgid "In order to force the synchronization of an order, whose status has **not** changed since the previous synchronization, start by activating the :ref:`developer mode <developer-mode>`. This includes changes on either end (Amazon or Odoo)."
msgid "Then, navigate to the Amazon account in Odoo (:menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`), and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`."
msgid "Be sure to pick a date that occurs prior to the last status change of the desired order to synchronize and save. This will ensure synchronization occurs correctly."
msgid "To immediately synchronize the orders of an Amazon account, switch to :ref:`developer mode <developer-mode>`, head to the Amazon account in Odoo, and click :guilabel:`Sync Orders`. The same can be done with pickings by clicking :guilabel:`Sync Pickings`."
msgid "Whenever an FBM (Fulfilled by Merchant) order is synchronized in Odoo, a picking is instantly created in the *Inventory* app, along with a sales order and customer record. Then, decide to either ship all the ordered products to the customer at once, or ship products partially using backorders."
msgid "When a picking related to the order is confirmed, a notification is then sent to Amazon, who, in turn, notifies the customer that the order (or a part of it) is on its way."
msgid "If the chosen carrier isn't supported by Odoo, a carrier with the same name can still be created (e.g. create a carrier named `easyship`). The name used is **not** case sensitive, but be mindful to avoid typos. If there are typos, Amazon will **not** recognize them. Next, create a delivery carrier named `Self Delivery` to inform Amazon that the user will make the deliveries. Even with this route, a tracking reference still **must** be entered. Remember, the customer is notified by email about the delivery, and the carrier, along with the tracking reference, are displayed in the email to the customer."
msgid "Sometimes, Amazon can fail to correctly process all the information sent by Odoo. In this case, Odoo sends an email listing all the shipments that failed and the errors Amazon sent with them. In addition, these shipments are flagged with a :guilabel:`Synchronization with Amazon failed` tag."
msgid "Usually, the error can be corrected directly in the Amazon backend or in Odoo. If the problem is corrected in Odoo, synchronize the shipment again using the :guilabel:`Retry Amazon Sync` button."
msgid "It might happen that Odoo receives a notification from Amazon saying that some delivery information was not processed, but without specifying which shipments were affected. In that case, all the shipments in an unknown state will be treated as if they failed to synchronize. Once Odoo receives a notification from Amazon saying that a shipment was processed, its tag will change to :guilabel:`Synchronized with Amazon`. To speed up this process, on your Amazon account, click on :guilabel:`Sync Orders` to manually synchronize these orders, or click on :guilabel:`Recover Order` and enter the relevant Amazon Order Reference."
msgid "When an FBA (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded in the *Inventory* app for each sales order item. That way, it's saved in the system."
msgid "For FBA orders, the stock move is automatically created in Odoo by the Amazon connector, thanks to the shipping status of Amazon. When sending new products to Amazon, the user should manually create a picking (delivery order) to transfer these products from their warehouse to the Amazon location."
msgid "To follow *Amazon (FBA)* stock in Odoo, make an inventory adjustment after replenishing stock. An automated replenishment from reordering rules can also be triggered on the Amazon location."
msgid "The Amazon location is configurable by accessing the Amazon account managed in Odoo. To access Amazon accounts in Odoo navigate to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`."
msgid "All accounts of the same company use the same Amazon location, by default. However, it is possible to follow the stock filtered by marketplace."
msgid "To do that, first remove the marketplace, where the desired stock to follow separately can be found, from the list of synchronized marketplaces, which can be found by navigating to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`."
msgid "Next, create another registration for this account, and remove all marketplaces--- **except** the marketplace this is desired to be isolated from the others."
msgid "Due to Amazon's policy of not sharing customer email addresses, it is **not** possible to send invoices directly to Amazon customers from Odoo. However, it **is** possible to manually upload the generated invoices from Odoo to the Amazon back-end."
msgid "Additionally, for B2B clients, it is currently required to manually retrieve VAT numbers from the Amazon back-end **before** creating an invoice in Odoo."
msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud."
msgid "Since customers pay Amazon as an intermediary, creating a dedicated *Bank* journal (e.g. named `Amazon Payments`), with a dedicated *Bank and Cash* intermediary account is recommended."
msgid "Additionally, as Amazon makes a single monthly payment, selecting all the invoices linked to a single payment is necessary when registering payments."
msgid "To do that, use the appropriate :guilabel:`Journal` dedicated to Amazon payments, and select :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`."
msgid "When the balance is received in the bank account at the end of the month, and the bank statements are recorded, credit the Amazon intermediary account by the amount received."
msgid "This gives quick access to important metrics related to sales reporting. By default, the Amazon account's sales team is shared between all of the company's accounts."
msgid "Odoo allows users to register an Amazon seller account in the database, but the user **must** have a paid Amazon Seller account prior to completing the configuration."
msgid "Set up a paid Seller account on Amazon by first logging into the Amazon platform, and navigating to :menuselection:`Account \\& Lists --> Start a Selling Account` from the drop-down menu located in the header section."
msgid "Then on the :guilabel:`Sell with Amazon` page, follow the sign-up process and finally proceed to follow the instructions below to register and link that Amazon Seller account in Odoo."
msgid "Then, return to :menuselection:`Sales app --> Configuration --> Settings --> Connectors section`, and click on the :guilabel:`Amazon Accounts` link under the :guilabel:`Amazon Sync` setting."
msgid "On the blank :guilabel:`Amazon Account` form page, start by choosing a name for the account (e.g. `American Marketplace`). Then, in the :guilabel:`Credentials` tab, select the marketplace on which the seller account was initially created from the :guilabel:`Home Marketplace` drop-down menu."
msgid "Clicking that button redirects to either the Amazon login page, or directly to the required consent page, if the user is already logged in to Amazon."
msgid "With the Amazon account successfully registered, the marketplaces available to this specific account are synchronized with Odoo and listed under the :guilabel:`Marketplaces` tab."
msgid "When an Amazon order is synchronized, up to three line items are created on the sales order in Odoo. Each one represents a product sold on Amazon: one for the product that was sold on Amazon Marketplace, one for the shipping charges (if any), and one for the gift wrapping charges (if any)."
msgid "The selection of a database product for a sales order item is done by matching its :guilabel:`Internal Reference` (a customizable product reference idenifier in Odoo, like `FURN001`) with the Amazon *SKU* for marketplace items, the Amazon *Shipping Code* for delivery charges, and the Amazon *Gift Wrapping* code for gift wrapping charges."
msgid "For marketplace products, pairings are saved as *Amazon Offers*, which are listed under the :guilabel:`Offers` smart button on the account form."
msgid "Offers are automatically created when the pairing is established, and they're used for subsequent orders to lookup SKUs. If no offer with a matching SKU is found, :ref:`the internal reference is used instead <amazon/matching>`."
msgid "It's possible to force the pairing of a marketplace item with a specific product, by changing either the product or the SKU of an offer to ensure they match. The offer can be manually created if it was not automatically done yet."
msgid "If no database product with a matching internal reference is found for a given Amazon SKU or gift wrapping code, then a default database product, *Amazon Sale*, is used. The same is done with the default product *Amazon Shipping* if no database product is found for a given Amazon shipping code."
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."
msgid "Make sure to have the correct taxes set on your products in Odoo, or have it done by a fiscal position, to avoid discrepancies in the subtotals between *Amazon Seller Central* and Odoo."
msgid "As Amazon does not necessarily apply the same taxes as those configured in Odoo, it may happen that order totals differ by a few cents between Odoo and *Amazon Seller Central*. Those differences can be resolved with a write-off when reconciling the payments in Odoo."
msgid "Enter the Marketplace ID in the :guilabel:`API Idenifier` field, and select the :guilabel:`Amazon Region` for your marketplace as described in the `Amazon Documentation for marketplace IDs and regions <https://developer-docs.amazon.com/sp-api/docs/marketplace-ids>`_, and the :guilabel:`Seller Central URL` as described in the `Amazon Documentation for seller central URLs <https://developer-docs.amazon.com/sp-api/docs/seller-central-urls>`_."
msgid "Set the :guilabel:`Name` of the record to `Amazon.<country code>` to easily retrieve it (e.g. `Amazon.se`). The :guilabel:`API Identifier`, the :guilabel:`Region` and the :guilabel:`Seller Central URL` fields should respectively hold the *Marketplace ID*, the selected Amazon region, and the *Seller Central URL* values from the Amazon Documentation."
msgid "Select the account on which to use the new marketplace, go to the :guilabel:`Marketplaces` tab, and click on :guilabel:`Update available marketplaces`. An animation should confirm the success of the operation. Newly added marketplaces are automatically added to the list of synchronized marketplaces. If the new marketplace is not added to the list, it means that it is either incompatible or unavailable for the seller account."
msgid "To start linking existing listings in eBay, first turn off the eBay notifications in the scheduled actions in Odoo. The reason for this is so that no orders or eBay data syncs during this process. The :guilabel:`Scheduled Actions` can be accessed by first activating :ref:`developer mode <developer-mode>`. After doing so, go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`."
msgid "Disabling scheduled actions enables users to sync and validate eBay data before receiving orders. The following are descriptions of scheduled actions that need to be temporarily deactivated:"
msgid ":guilabel:`eBay: get new orders`: eBay pushes new orders not already in Odoo (based on :guilabel:`client_order_reference`, or :guilabel:`sales order reference` field). This command also updates existing orders, where changes we made in eBay. New and updated orders are then placed in draft mode. Customers will be created if they are not already in Odoo."
msgid ":guilabel:`eBay: update categories`: eBay will push updated monthly categories (only up to fourth layer; a manual update required for the rest)."
msgid "To toggle off the eBay notification, select the entry from the :guilabel:`Scheduled Actions` list. Then, on the page, click the :guilabel:`Active` toggle button to turn it off."
msgid "Navigate to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`. Click into the scheduled action labeled: :guilabel:`Ebay: update categories` and then click :guilabel:`Run Manually`."
msgid "Odoo only recognizes eBay category paths up to four layers deep. If a product has a listing of more than four, the category field will only populate up to the fourth layer."
msgid "If product categories beyond four paths are required, users need to manually add those paths. This has historically been done by getting a list of all product categories beyond 4 paths, manually importing them into the Product Category model in Odoo, then linking them individually to the product."
msgid "Users can import the remaining product categories into the eBay product categories manually using using the :guilabel:`Action` menu and :guilabel:`Import` feature."
msgid "To add an eBay listing to products in Odoo, begin by going to :menuselection:`Sales app --> Products --> Products` and selecting the desired product. Click on :guilabel:`Sell on eBay` (either in the :guilabel:`eBay` tab or under the :guilabel:`Product name`). Select :guilabel:`Save` if necessary."
msgid "Still the product form, click :guilabel:`link to listing` in the top menu and enter in listing ID from eBay in the pop up (the listing ID is in the eBay product URL)."
msgid "An example URL would be as such: `www.ebay.com/itm/272222656444?hash=item3f61bc17bb:g:vJ0AAOSwslJizv8u`. The listing ID is `272222656444` in this case. Once the listing ID has been entered the eBay listing information will sync into Odoo."
msgid "The next step is to turn on the eBay notifications in the scheduled actions in Odoo so that orders and data are exchanged. The :guilabel:`Scheduled Actions` can be accessed by first activating :ref:`developer mode <developer-mode>` and go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`."
msgid ":guilabel:`eBay: get new orders`: eBay will push all new orders not already in Odoo (based on client_order_reference, or sales order reference field), and will update orders if there has been a change from eBay. Orders will be put in draft mode. Customers will be created if they are not already in Odoo."
msgid ":guilabel:`eBay: update categories`: eBay will push updated monthly categories (only up to fourth layer, will need to manually update the rest)."
msgid "If an order comes in and the listing from the order is not linked to a product, eBay will create a consumable product.product in its place. These consumables should be altered on the *Sales Order* while in draft state to represent a storable product, and then the user can link to the listing as they come in."
msgid "Click :guilabel:`List Item on eBay` in the top menu of the product template. The product template can be accessed by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product."
msgid "Click :guilabel:`Link With Existing eBay Listing` in the top menu on the product template.The product template can be accessed by navigating to :menuselection:`Sales app --> Product --> Product` and selecting the individual product."
msgid "If an order comes in and the listing from the order is not linked to a product, eBay will create a consumable product.product in its place. These consumables should be altered on the *sales order* while in draft state to represent a storable product, and then the user can link to the listing as they come in."
msgid "In order to list a product, select the :guilabel:`Sell on eBay` field on a product template. :guilabel:`Sell on eBay` is either in an :guilabel:`eBay` tab or under the :guilabel:`Product name`. Click :guilabel:`Save` if necessary."
msgid "The policies need to be set in order to be able to list on eBay. A value must be selected for the following fields :guilabel:`Payment Policy`, :guilabel:`Return Policy`, and :guilabel:`Shipping Policy`. The options are imported from the eBay database. If no option appears, they can be imported by navigating to :menuselection:`Sales app --> Configuration --> Settings --> eBay`, and clicking on the :guilabel:`Policies` button in the :guilabel:`Synchronization` field. This button **only** appears once the production and sandbox credentials have been set."
msgid "The :guilabel:`Description Template` allows the administrator to use templates in listings. The default template only uses the :guilabel:`eBay Description` field of the product. HTML can be used inside the :guilabel:`Description Template`, and in the :guilabel:`eBay Description` in Odoo 14. Starting in Odoo 15, the powerbox feature is available to use in the template and description. Simply type a forward slash `/` to reveal a menu with formatting, layout, and text options. To add an image, type `/image`."
msgid "When the :guilabel:`Sell on eBay` is checked on a product containing variations with :guilabel:`Fixed Price` as :guilabel:`Listing Type`, the eBay form is slightly different. Go to the :guilabel:`Variants` tab to or click :guilabel:`Configure Variants` in the top menu to configure the variant settings. Pricing can be configured for each variation."
msgid "When the :guilabel:`Listing Type` is changed to :guilabel:`Fixed Price`, Odoo presents a variant table at the bottom of the :guilabel:`eBay` tab, in which the :guilabel:`Fixed Price` can be entered, and the decision to :guilabel:`Publish on eBay` can be made for specific variants, along with other options."
msgid "The module manages the EAN and UPC identifiers with the :guilabel:`Barcode` field of the product variant. If the :guilabel:`Barcode` field is empty or is value is not valid, the EAN and UPC values will be set as 'Does not apply' as recommended by eBay."
msgid "Barcodes can be found on the product template, under the the :guilabel:`General Information` tab. Access the product template, first, by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product."
msgid "In order to add item specifics, one should create a product attribute with a single value in the :guilabel:`Attributes & Variants` tab on the product form. Examples of item specifics include: `MPN` or `Brand`. The Brand and MPN values are working as item specifics and should be defined in the :guilabel:`Attributes & Variants` tab on the product form. If these values are not set, 'Does not apply' will be used for the eBay listing."
msgid "When eBay orders are placed they are always paid for up front, via the eBay site. At no point will users pay for items on eBay through Odoo. Therefore, once orders are synced into Odoo from eBay they are already paid for. Odoo's invoicing and payment functionalities are not utilized. However, invoices need to be created and marked as Paid to “close” the *Sales Order*."
msgid "Users can opt to mass create and post invoices in batches. To do so, navigate to Quotations in the list view by going to :menuselection:`Sales app --> Orders --> Quotations`. In the upper right corner, select the list view icon. Hover over the icons to reveal the name of each. Then check the boxes on the left that invoices should be made for and go to the :guilabel:`Action` menu or ⚙️ [Gear icon] . Click on :guilabel:`Create Invoices`."
msgid "A pop-up will appear and click on the :guilabel:`Create and view invoice` button. A new screen will populate with the newly created invoices. Next, select all of them by clicking on the box icon next to :guilabel:`Number` in the header row of the list, this will select all the records. Then navigate to the :guilabel:`Action` menu and click :guilabel:`Post entries`. Following this step, a pop-up will appear and click on :guilabel:`Post journal entries`. This will take the invoices out of *draft* and set them to *posted*."
msgid "Users typically utilize PayPal to receive payment from eBay, and then send lump sums from PayPal into their bank account. To reconcile this income, users can reconcile the one PayPal transfer with all related invoices."
msgid "First navigate to the :guilabel:`Accounting Dashboard` by going to the :menuselection:`Accounting app --> Dashboard --> Bank`. :guilabel:`Create` a new transaction and enter the :guilabel:`Label` as `eBay Sales`. Fill out the :guilabel:`Amount` and enter a :guilabel:`Statement` date in. Click on :guilabel:`Create and edit`."
msgid "For the :guilabel:`Ending Balance` field, enter the same account that was entered for the :guilabel:`Amount` above. Click on :guilabel:`Save`. Next, open the new balance that needs to be reconciled. Under the tab marked: :guilabel:`Match Existing Entries` select the entries that are included in this balance."
msgid "After adding all the necessary entries, click :guilabel:`Validate` to complete the reconciliation. To verify the payment, navigate to :menuselection:`Customers --> Invoices` and select the desired customer invoice. The *Paid* label should appear under the :guilabel:`Payment Status` column."
msgid "Odoo's eBay connector allows eBay listings to connect with Odoo products. Once connected, :doc:`updates to the listings <linking_listings>` can be made in Odoo or in eBay. When an item sells on eBay, draft *sales orders* are created in Odoo for the user to review and confirm. Once the sales order is confirmed, Odoo *Inventory* and *Sales* apps function standard to pull products out of inventory, and allow the user to create invoices."
msgid "*Variations* group multiple products into one, with variation (or variant) options. Variations can sync to Odoo's attributes and values. Variations will appear in drop down menus near the top of the page when viewing an eBay listing. These are comparable to product variants in Odoo."
msgid "*Item specifics*, located at the bottom of the listing, detail product-specific information. These specifics don't sync with Odoo fields by default; a development is required to link these fields."
msgid "*Sandbox* and *Production* are terms that are used to categorize the eBay environments as either still in development/testing (*Sandbox*) or for use in the real instance of the database with real customer information/dataset (*Production*). It is recommended to start first in the *Sandbox* to test, and then following the processes below, create a *Production* instance."
msgid "eBay's sandbox environment can be accessed by navigating to `eBay's sandbox portal <https://sandbox.ebay.com/>`_ at `https://sandbox.ebay.com/`. eBay's production environment can be accessed by navigating to `eBay.com portal <https://www.ebay.com/>`_ or `https://www.ebay.com/`."
msgid "**List**/ **Link**: generate a new eBay listing with an Odoo product by clicking :guilabel:`List Item on eBay` or :guilabel:`Link With Existing eBay Listing`."
msgid ":guilabel:`Revise item` button: after making changes to an eBay listing in Odoo, save the record, and then click the :guilabel:`Revise Item` in Odoo to update the eBay listing."
msgid "**Relist**: if an item's listing was ended early or :guilabel:`auto-relist` was not selected, a user can relist the item from Odoo. The start date will reset."
msgid "To link eBay with Odoo, install the eBay module by navigating to the Odoo dashboard and clicking into the :guilabel:`Apps` application. Search the term `eBay` and install the `eBay Connector` module."
msgid "In Odoo, create and configure products that are intended to be listed in eBay. eBay does not import new products into Odoo. All products must first be created in Odoo, and then linked to listings."
msgid "Odoo does not allow multiple eBay listings to be linked per product in Odoo. If the company sells the same product for multiple listings, follow these instructions:"
msgid "Set up one *base* product (noted in the :guilabel:`Component` field of the :abbr:`BoM (Bill of Materials)`) from which all eBay listings will pull from. This will be a storable product so stock can be kept. Highlighted in green below, this product will be included in the kit on each subsequent “linked” product below."
msgid "Set up 2+ *linked* products (noted in the :guilabel:`Product` field of the :abbr:`BoM (Bill of Materials)`, one for each eBay listing. The product type will be determined by the company's accounting settings, as explained in the Odoo documentation. Highlighted in yellow below, each product should have a :guilabel:`BoM type` equal to :guilabel:`Kit` and have the base product as a :guilabel:`Component` of the kit. When this linked eBay product is sold, the delivery order created will have the base product listed in lieu of the linked product."
msgid "eBay does not automatically create invoices for eBay orders that get pushed into Odoo. Set invoicing policy on eBay products: invoicing policy will dictate when the product can be invoiced. Since most eBay users collect payment before the product is shipped, “invoice on ordered” will allow users to mass create invoices for eBay orders every day."
msgid "When the :guilabel:`Outgoing Shipments` route is set to two or three steps, a known bug occurs: eBay wrongly marks orders as delivered when the pick operation in Odoo is confirmed. The expected behavior is to mark orders as delivered **after** the *delivery order* is confirmed. This mislabeling prevents tracking numbers in eBay from being imported onto the delivery order."
msgid "If the Accounting/Invoicing apps are installed, practice registering payment and reconciling invoices created from eBay orders with incoming eBay money."
msgid "Generate a marketplace account deletion/closure notification token. To begin, navigate to :menuselection:`Sales app --> Configuration --> Settings`. Under the :guilabel:`eBay` heading, change the mode to :guilabel:`Production`, and input random text values for the :guilabel:`Production Cert Key`. Then click the :guilabel:`Generate Token` button under the :guilabel:`eBay Marketplace Account Deletion/Closure Notifications` section. This token will be used during the setup on eBay for the deletion/closure notifications configuration."
msgid "To start, create an eBay developer account via `eBay's developer portal <https://go.developer.ebay.com/>`_. This site requires a different login and password than the eBay account, though the same email address can be used to register. The verification to create a developer account is around 24 hours."
msgid "Once the eBay developer account is created, set up an application on `eBay's developer portal <https://go.developer.ebay.com/>`_. Next, navigate to the :guilabel:`Hi [username]` heading at top right of screen, then from the drop-down menu options, click :guilabel:`Application Keysets`. Doing so opens a pop-up that prompts the user to :guilabel:`Enter Application Title` (up to fifty characters), and choose a development environment (:guilabel:`Sandbox` or :guilabel:`Production`). These two fields generate first keyset. This application title is not saved until the keyset is generated. Click on :guilabel:`Create a keyset` to generate the keyset."
msgid "The newly created *production keyset* is disabled by default. Activate it by subscribing to the eBay Marketplace 'account deletion or closure notifications' or by applying to eBay for an exemption. Once enabled, the database can make 5000 calls per day using this keyset."
msgid "To configure notifications or delete the database on a production environment, navigate to the `eBay developer portal <https://go.developer.ebay.com/>`_. Configure the account deletion/notification settings in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`Application Keysets`."
msgid "Next, click the :guilabel:`marketplace deletion/account closure notification` option under the :guilabel:`Production` keyset column. Enter an email under :guilabel:`Email to notify if marketplace account deletion notification endpoint is down`. Click :guilabel:`Save` to enable the email."
msgid "Following this action, enter the :guilabel:`Marketplace account deletion notification endpoint` URL provided by Odoo. This HTTPs endpoint is found in Odoo by navigating to :menuselection:`Sales app --> Configuration --> Settings`, in the :guilabel:`eBay Marketplace Account Deletion/Closure Notifications` field."
msgid "Clicking the :guilabel:`Generate Token` button in Odoo below this field creates a verification token for the eBay production environment. In Odoo, :guilabel:`Copy` the newly created token and navigate to eBay to fill in the :guilabel:`Verification token` field. Click :guilabel:`Save` to enable the :guilabel:`Event Notification Delivery Method`."
msgid "After completing the above fields, click :guilabel:`Send Test Notification` to test the new notifications. Proceed to the next step when the green check mark appears. Revisit the above settings if the test post is not as expected."
msgid "A successful setup of the notifications enables the ability to create Production Keysets which are needed in the remainder of the Odoo configuration. Navigate back to the :menuselection:`Application Keys` page generate a production keyset."
msgid "The administrator is prompted to :menuselection:`Confirm the Primary Contact`. Enter or confirm the account owner (the person legally responsible for the eBay API License Agreement). Fill out :guilabel:`First Name`, :guilabel:`Last Name`, :guilabel:`Email`, :guilabel:`Phone`. Then, select either the :guilabel:`Individual` or :guilabel:`Business` options."
msgid "The provided email address or phone number does **not** have to match the account's. eBay uses this information to contacting the business or individual in case of issues with user tokens. Additional contacts can be added from the :guilabel:`Profile & Contacts` page on eBay."
msgid "Click on :guilabel:`Continue to Create Keys` to confirm the primary contact. The :guilabel:`Application Keys` populates in a new screen and an email is also sent to the developer account. An :guilabel:`App ID (Client ID)`, :guilabel:`Dev ID`, and :guilabel:`Cert ID (Client Secret)` all populate."
msgid "Select the correct :guilabel:`Environment`: :guilabel:`Sandbox` for testing or :guilabel:`Production` for the live database. Maintain the same selection for all environment settings on both eBay and Odoo."
msgid "Choose :guilabel:`Sign in to Production` or :guilabel:`Sign in to Sandbox` to get a user token in the chosen environment. This button varies based on the selection made above for either :guilabel:`Sandbox` or :guilabel:`Production`."
msgid "Doing so triggers a a pop-up window to :guilabel:`Confirm your Legal Address`. Complete the required fields, which are :guilabel:`First Name`, :guilabel:`Last Name`, :guilabel:`Primary Email`, :guilabel:`Legal Address`, and :guilabel:`Account Type`. For :guilabel:`Account Type`, select either :guilabel:`Individual` or :guilabel:`Business`. To complete the confirmation, click :guilabel:`Sign into eBay to get a Token`."
msgid "eBay will contact this individual or business should there be any issues with the application keys. Other contacts can be added on the :menuselection:`Profile & Contacts` eBay page."
msgid "The administrator will be redirected to either a sandbox or production sign-in page for eBay. This login is different than the eBay developer's console, it is the eBay account where the items will be sold on. This email and/or login can differ from the eBay developer account."
msgid "Should an additional user be needed for the sandbox simulation, a test user needs to be created. Visit `eBay's Register for Sandbox form <https://developer.ebay.com/sandbox/register>`_. Detailed instructions can be found on eBay's help pages: `Create a test Sandbox user <https://developer.ebay.com/api-docs/static/gs_create-a-test-sandbox-user.html>`_."
msgid "After signing into the production or sandbox environment, eBay presents the administrator with an *agreement* to grant access to the user's eBay data."
msgid "Clicking :guilabel:`Agree` allows eBay to link the eBay account with the *application programming interface* (API). This agreement can be changed at any time by visiting eBay's account preferences."
msgid "eBay has a timed sequence between signing in and agreeing to the terms for the :abbr:`API (Application Programming Interface)` linkage to the account. Once complete a :guilabel:`User Token` will populate on the :menuselection:`User Tokens` page."
msgid "A :guilabel:`User Token` will populate on the screen. Make sure to copy this token down as it will be used in the next steps along with the :guilabel:`Application Keyset`."
msgid "Signing in to the eBay account is necessary to create to the token. The eBay developer can also revoke the token by clicking on the :guilabel:`Revoke a Token` link."
msgid "Now that the :guilabel:`Application Keyset` and :guilabel:`User Token` have been created, a test can be executed via the `API Explorer <https://developer.ebay.com/DevZone/build-test/test-tool/default.aspx>`_ to ensure that the :abbr:`API (Application Programming Interface)` is configured correctly. This test will execute a simple search using the :abbr:`API (Application Programming Interface)`."
msgid "To begin the :abbr:`API (Application Programming Interface)` test, click on :guilabel:`Get OAuth Application Token`. This will populate the key into the :guilabel:`Token` field."
msgid "A basic search function is set to execute. Click on :guilabel:`Execute` to complete the test. A successful test will respond with a :guilabel:`Call Response` of `200 OK` with a corresponding :guilabel:`Time`."
msgid "Navigate back the eBay settings in Odoo (:menuselection:`Sales app --> Configuration --> Settings --> eBay`) and paste the following credentials from eBay into the corresponding fields in Odoo."
msgid "The :guilabel:`Application Keyset` can be accessed by going to `eBay's developer portal <https://go.developer.ebay.com/>`_ and navigate to the `Hi [username]` at top right of screen, then click on :guilabel:`Application Keysets`. Get to the *User Token* in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`User Access Tokens` and click on :guilabel:`Sign in to Sandbox`. The :guilabel:`User Token` can also be accessed by clicking on :guilabel:`User Tokens` from the :menuselection:`Application Keys` page."
msgid "Confirm that the setup is correct by saving the credentials in Odoo. Once the initial setup is complete, a new menu tab in products will appear called `eBay` with the option to :guilabel:`Sell on eBay`. See the :doc:`manage` documentation on how to list products."
msgid "Sync product categories by clicking :guilabel:`Product Categories`. After syncing, a new menu item, `eBay Category`, appears available for products to be configured with. These eBay categories are imported from the Odoo database and are available when listing an item on eBay through Odoo."
msgid "If Product Categories beyond four paths are required, users will need to manually add those paths. This has historically been done by getting a list of all product categories beyond four paths, manually importing them into the Product Category model in Odoo, and then linking them individually to the product."
msgid "Since September 2021, **eBay requires supporting customer account deletion/closure notifications**. As such, when eBay receives an account request for deletion, all eBay partners must confirm the reception of the request and take further action if necessary."
msgid "Odoo has a notification endpoint to receive those notifications, confirm the reception of the request, and handle the first set of actions to anonymize the account details in *Contacts* and remove the customer's access to the portal."
msgid "Make sure to correctly :ref:`set up the subscription to the marketplace account deletion notifications <ebay/subscribe-account-deletion-notifications>` as eBay may temporarily disable the related eBay account until the subscription is completed."
msgid "In order to activate the endpoint, the module *eBay Connector - Account Deletion* must be installed. If the Odoo database was first created after September 2021, the module is installed automatically and the administrator can proceed to the :ref:`next step <ebay/retrieve-endpoint-details>`."
msgid "The notification endpoint is made available through a new Odoo module; to be able to install it, the administrator must make sure that the Odoo source code is up-to-date."
msgid "If the company uses Odoo with an on-premise setup or through a partner, then the administrator must update the installation as detailed in :doc:`this documentation page </administration/on_premise/update>` or by contacting an integrating partner."
msgid "To do so, activate the :ref:`developer mode <developer-mode>`, and go to :menuselection:`Apps -> Update Apps List`. A wizard will ask for confirmation."
msgid "**Never** install new modules in the production database without testing them in a duplicate or staging environment. For Odoo.com customers, a duplicate database can be created from the database management page. For Odoo.sh users, the administrator should use a staging or duplicate database. For on-premise users, the administrator should use a staging environment - contact the integrating partner for more information regarding how to test a new module in a particular setup."
msgid "To install the module, go to the :menuselection:`Apps` menu, remove the `Apps` search facet and search for `eBay`. If the module *eBay Connector - Account Deletion* is present and marked as installed, the Odoo database is already up-to-date and the administrator can proceed with the next step. If it is not yet installed, install it now."
msgid "The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`. First, input random text values for the :guilabel:`Production App Key` and for the :guilabel:`Production Cert Key`. Click on :guilabel:`Generate Token` to retrieve the :guilabel:`Verification Token`."
msgid "Navigate to the `eBay developer portal <https://go.developer.ebay.com/>`_. Configure the account deletion/notification settings in eBay by navigating to the `Hi [username]` at the top right of screen, then go to :guilabel:`Alerts & Notifications`."
msgid "After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity with the :guilabel:`Send Test Notification` button."
msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' (seller and buyer) full commitment to honor the contract."
msgid "With a down payment, the buyer pays a portion of the total amount owed while agreeing to pay the remaining amount at a later date. In turn, the seller provides goods or services to the buyer after accepting the down payment, trusting that the remaining amount will be paid later on."
msgid "When a sales order is confirmed, the option to create an invoice becomes available, via the :guilabel:`Create Invoice` button, located in the upper-left corner of the sales order form. When clicked, a :guilabel:`Create invoices` pop-up appears."
msgid "Once the desired down payment option is selected in the :guilabel:`Create Invoice` field on the pop-up form, designate the desired amount, either as a percentage or a fixed amount, in the :guilabel:`Down Payment Amount` field."
msgid "Then, select the appropriate income account for the invoice in the :guilabel:`Income Account` field. Next, select a tax amount, if necessary, in the :guilabel:`Customer Taxes` drop-down field."
msgid "Once all fields are filled in with the desired information, click the :guilabel:`Create Draft Invoice` button. Upon clicking this button, Odoo reveals the :guilabel:`Customer Invoice Draft`."
msgid "In the :guilabel:`Invoice Lines` tab of the :guilabel:`Customer Invoice Draft`, the down payment that was just configured in the :guilabel:`Create invoices` pop-up form appears as a :guilabel:`Product`."
msgid "By default, the :guilabel:`Product Type` of down payment products generated for invoices are set as :guilabel:`Service`, with the :guilabel:`Invoicing Policy` set to :guilabel:`Prepaid/Fixed Price`."
msgid "If :guilabel:`Based on Delivered Quantity (Manual)` is chosen as the :guilabel:`Invoicing Policy`, an invoice will **not** be able to be created."
msgid "The following example involves a 50% amount down payment on a product (:guilabel:`Cabinet with Doors`) with :guilabel:`Ordered quantities` as the :guilabel:`Invoicing Policy`."
msgid "When the order is confirmed (via the :guilabel:`Confirm` button), the quotation turns into a sales order. Once this occurs, create and view the invoice by clicking :guilabel:`Create Invoice`."
msgid "Next, on the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down Payment Amount` field."
msgid "The :guilabel:`Income Account` and :guilabel:`Customer Taxes` fields are *not* required fields, and they will *not* appear if they've already been preconfigured in previous down payment requests."
msgid "For more information, check out the documentation on :ref:`customer taxes modification on down payments <sales/invoicing/customer-tax-modification-down-payments>` and :ref:`income account modification on down payments <sales/invoicing/income-account-modification>`."
msgid "Clicking :guilabel:`Create Draft Invoice` reveals the draft invoice, which includes the down payment as a :guilabel:`Product` in the :guilabel:`Invoice Lines` tab."
msgid "From there, the invoice can be confirmed and posted by clicking :guilabel:`Confirm`. Confirming the invoice changes the status from :guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of buttons at the top of the page."
msgid "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-populated with the necessary information. Confirm the information provided is correct, and make any necessary adjustments. When ready, click the :guilabel:`Create Payment` button."
msgid "After clicking :guilabel:`Create Payment`, Odoo reveals the customer invoice, now with a green :guilabel:`In Payment` banner in the upper-right corner."
msgid "Now, when the customer wants to pay the remaining amount of the order, another invoice must be created. To do that, return to the sales order, via the breadcrumb links."
msgid "Back on the sales order, a new :guilabel:`Down Payments` section is present in the :guilabel:`Order Lines` tab, along with the down payment that was just invoiced and posted."
msgid "On the :guilabel:`Create invoices` pop-up window that appears, there are two new fields: :guilabel:`Already invoiced` and :guilabel:`Amount to invoice`."
msgid "If the remaining amount is ready to be paid, select the :guilabel:`Regular Invoice` option. Odoo will create an invoice for the exact amount needed to complete the total payment, as indicated in the :guilabel:`Amount to invoice` field."
msgid "Doing so reveals another :guilabel:`Customer Invoice Draft` page, listing *all* the invoices for that specific sales order in the :guilabel:`Invoice Lines` tab. Each invoice line item displays all the necessary information related to each invoice."
msgid "To complete the flow, click :guilabel:`Confirm`, which changes the status of the invoice from :guilabel:`Draft` to :guilabel:`Posted`. Then, click :guilabel:`Register Payment`."
msgid "Once again, the :guilabel:`Register Payment` appears, with all fields auto-populated with the necessary information, including the remaining amount left to be paid on the order."
msgid "After confirming that information, click :guilabel:`Create Payment`. Doing so reveals the final :guilabel:`Customer Invoice` with a green :guilabel:`In Payment` banner in the upper-right corner. Also, both down payments are present in the :guilabel:`Invoice Lines` tab."
msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, and the cost of the product *exceeds* the 50% down payment (as in most cases), a regular invoice is created."
msgid "However, for products that cost *less* than the 50% down payment, the down payments will **not** be able to be deducted when it comes time to invoice the customer."
msgid "This is because the product(s) would have to be delivered *before* creating the final invoice due to Odoo not allowing negative totals for invoices."
msgid "To utilize the :guilabel:`Credit Note` option, the *Inventory* application must be installed, in order to confirm the delivery. Otherwise, the delivered quantity can be entered manually directly on the sales order."
msgid "The process of requesting a 100% down payment is similar to the process of setting up a :ref:`50% down payment <sales/invoicing/50-percent-down-payments>`, but with fewer steps."
msgid "A sales order paid through the regular invoice process will not allow any additional invoices to be generated, and **will not** display the *Create Invoice* button on the Sales Order."
msgid "Following this example **will** cause the *Create Invoice* button to be displayed on the Sales Order. This is because Odoo expects another invoice to be created after the down payment to complete payment of the sales order."
msgid "Upon clicking the :guilabel:`Confirm` button, the quotation turns into a sales order. At that point, an invoice can now be created by clicking :guilabel:`Create Invoice` in the top-left corner."
msgid "On the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `100` in the :guilabel:`Down Payment Amount` field. Then, if desired, select an :guilabel:`Income Account` and :guilabel:`Customer Taxes` in their respective fields."
msgid "Next, click :guilabel:`Create Draft Invoice` to create an invoice draft. This will also bring the draft invoice into view, which includes the :guilabel:`Down payment` as a :guilabel:`Product` in the :guilabel:`Invoice Lines` tab."
msgid "The invoice can now be confirmed and posted by clicking :guilabel:`Confirm`. Confirming the invoice changes the status from :guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of buttons at the top of the page."
msgid "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-populated with the necessary information. Confirm the information provided is correct and make any necessary adjustments. When ready, click the :guilabel:`Create Payment` button."
msgid "To adjust the income account and customer taxes attached to a down payment, navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> Products --> Products`), search for the `Down Payment` product in the search bar, and select it to reveal the product detail page."
msgid "On the :guilabel:`Down Payment` product page, in the :guilabel:`General Information` tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field."
msgid "With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes available on the product page. That tab will **not** be accessible without the *Accounting* app installed."
msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, located in the :guilabel:`Receivables` section."
msgid "For example, an employee may need to use their own money to pay for a hotel, while they provide an on-site service for a client. As a company, this expense should be reinvoiced to the customer. With Odoo, these kinds of expenses can quickly be reinvoiced to the customer related to the project."
msgid "To install the *Expenses* application, navigate to :menuselection:`main Odoo dashboard --> Apps`, and click :guilabel:`Install` on the *Expenses* application block. When clicked, Odoo installs the application, refreshes the page, and returns to the main Odoo dashboard."
msgid "To begin, have a sales order confirmed in the *Sales* app to which a reinvoiced expense can be added. Or, create a new sales order from scratch. To do that, navigate to the :menuselection:`Sales app --> New`. Doing so reveals a blank quotation form."
msgid "Then, add a :guilabel:`Customer`, and add a product to the :guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`. Next, select a product from the drop-down menu."
msgid "New expense categories can be created from an expense form, by clicking the :guilabel:`Category` field drop-down menu, selecting :guilabel:`View All`, and clicking :guilabel:`New` from the :guilabel:`Search:Category` pop-up window."
msgid "For this sample workflow, which will reinvoice a customer for a brief hotel stay, the :guilabel:`Category` for this example is :guilabel:`[TRANS \\& ACC] Travel \\& Accommodation`."
msgid "Next, designate if there are any :guilabel:`Included taxes` in the :guilabel:`Total`. If a preconfigured tax amount is selected from the :guilabel:`Included taxes` field, Odoo auto-calculates the taxed amount, based on the amount entered in the :guilabel:`Total` field."
msgid "Then, choose which :guilabel:`Employee` was responsible for the expense, and choose an option in the :guilabel:`Paid By` field: :guilabel:`Employee (to reimburse)` or :guilabel:`Company`."
msgid "On the right-hand side of the expenses form, the option to add a :guilabel:`Bill Reference` is available. Beneath that, the auto-populated :guilabel:`Expense Date` and :guilabel:`Account` fields are available."
msgid "Next, in the :guilabel:`Customer to Reinvoice` field, click the blank field to reveal a drop-down menu. From this drop-down menu, select the appropriate sales order to which this expense should be attached. This field **must** be filled, in order to reinvoice a customer for an expense."
msgid "Lastly, the option to modify the :guilabel:`Analytic Distribution` and :guilabel:`Company` fields are available. These fields are *not* required to complete a reinvoiced expense to a customer, but are available to modify, if needed."
msgid "Also, at the bottom of the expense form, there is a :guilabel:`Notes...` section, wherein any notes related to this expense can be added, if needed."
msgid "If the cost of this expense needs to be split, click :guilabel:`Split Expense`. This feature can be used for a number of reasons (spitting expense with another employee, to accommodate different tax rates, etc.)."
msgid "Here, once the details related to the expense have been confirmed, click :guilabel:`Submit to Manager`. This sends the expense report to the approving manager, who will review the expense."
msgid "The manager in charge of reviewing and approving the expense will inspect the details related to the expense, and if there are no issues, they will click the :guilabel:`Approve` button — which *only* appears on the manager's view of the :guilabel:`Expense Report Summary` that's been submitted to the manager by the employee."
msgid "Once approved, the buttons at the top of the :guilabel:`Expense Report Summary` change once again. At this point, the buttons at the top of the :guilabel:`Expense Report Summary` are: :guilabel:`Post Journal Entries`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, and :guilabel:`Reset to Draft`."
msgid "Upon clicking :guilabel:`Post Journal Entries`, that button disappears, and the :guilabel:`Analytic Distribution` column in the :guilabel:`Expense` tab is filled with the sales order that was initially configured to the expense in the :guilabel:`Customer to Reinvoice` field."
msgid "By default, the :guilabel:`Customer to Reinvoice` field is enabled for the :guilabel:`[TRANS & ACC] Travel & Accommodation`, :guilabel:`[COMM] Communication`, :guilabel:`[FOOD] Meals`, and :guilabel:`[MIL] Mileage` expense category."
msgid "It should be noted that **not** all of the default expense categories that come installed with the *Expenses* application have reinvoicing policies activated. The setting may have to be manually activated."
msgid "To do that, navigate to :menuselection:`Expenses app --> Configuration --> Expenses Categories` to view a list of all expense categories in the database."
msgid "To modify an expense category, click the :icon:`fa-arrow-right` :guilabel:`(right arrow)` in the :guilabel:`Category` field, to reveal that specific expense from."
msgid "Under the :guilabel:`Invoicing` section, in the :guilabel:`Re-Invoice Expenses` field, select either :guilabel:`At cost` or :guilabel:`Sales price`."
msgid "To do that, navigate to :menuselection:`main Odoo dashboard --> Sales app`, and select the appropriate sales order that should be reinvoiced for the expense."
msgid "On the sales form, the newly-configured expense is now in the :guilabel:`Order Lines` tab, with its :guilabel:`Delivered` column filled in, and ready to be invoiced."
msgid "After confirming the details of the expense, click :guilabel:`Create Invoice` at the top of the sales order. When clicked, a :guilabel:`Create invoices` pop-up window appears."
msgid "From this pop-up window, leave the :guilabel:`Create Invoice` field on the default :guilabel:`Regular invoice` option, and click :guilabel:`Create Draft Invoice`."
msgid "If all the information related to the expense is correct, click :guilabel:`Confirm` to confirm the invoice. Doing so moves the status of the invoice from :guilabel:`Draft` to :guilabel:`Posted`."
msgid "To send the invoice to the customer, click :guilabel:`Send \\& Print`. Doing so reveals a :guilabel:`Send` pop-up window, with a preconfigured message and PDF invoice in the body of the message. The message can be reviewed and modified, if needed."
msgid "Once ready, click :guilabel:`Send \\& Print` to send the invoice to the customer. When clicked, the pop-up window disappears, and Odoo sends the message/invoice to the customer. Additionally, a PDF of the invoice is automatically downloaded for record-keeping and/or printing purposes."
msgid "When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment` pop-up window appears. In this pop-up window, the necessary fields are auto-populated with the correct information. After reviewing the information, click :guilabel:`Create Payment`."
msgid "Once :guilabel:`Create Payment` is clicked, the pop-up window disappears, and a green :guilabel:`In Payment` banner is in the upper-right corner of the invoice, signifying this invoice is paid for in full. Thus, completing the workflow."
msgid "The *Invoice what is ordered* rule is used as the default mode in Odoo *Sales*, which means customers are invoiced once the sales order is confirmed."
msgid "The *Invoice what is delivered* rule invoices customers once the delivery is done. This rule is often used for businesses that sell materials, liquids, or food in large quantities. In these cases, the ordered quantity may differ slightly from the delivered quantity, making it preferable to invoice the quantity actually delivered."
msgid "To activate the necessary invoicing policy features, go to :menuselection:`Sales app --> Configuration --> Settings`, and under the :guilabel:`Invoicing` heading, select an :guilabel:`Invoicing Policy` rule: :guilabel:`Invoice what is ordered` or :guilabel:`Invoice what is delivered`."
msgid "If the :guilabel:`Invoice what is delivered` rule is chosen, it is **not** possible to activate the :guilabel:`Automatic Invoice` feature, which automatically generates invoices when an online payment is confirmed."
msgid "On any product page, via the :menuselection:`Sales app --> Products --> Products dashboard`, locate the :guilabel:`Invoicing Policy` option located under the :guilabel:`General Information` tab. It can be changed manually using the drop-down menu."
msgid "In Odoo *Sales*, the basic sales flow starts with the creation of a quotation. Then, that quotation is sent to a customer. Next, it needs to be confirmed, which turns the quotation into a sales order. This, in turn, creates an invoice."
msgid ":guilabel:`Invoice what is delivered`: Minor impact on sales flow, because the delivered quantity needs to be manually entered on the sales order. Or, the *Inventory* app can be installed and used to confirm the delivered quantity before creating an invoice with the *Sales* app."
msgid "If a user attempts to create an invoice without validating the delivered quantity, the following error message appears: :guilabel:`There is no invoiceable line. If a product has a Delivered quantities invoicing policy, please make sure that a quantity has been delivered.`"
msgid "Once a quotation is confirmed, and the status changes from :guilabel:`Quotation sent` to :guilabel:`Sales order`, the delivered and invoiced quantities are available to view, directly from the sales order. This is true for both invoicing policy rule options."
msgid "Odoo automatically adds the quantities to the invoice, both :guilabel:`Delivered` and :guilabel:`Invoiced`, even if it's a partial delivery, when the quotation is confirmed."
msgid "Finally, there are a few different options to create an invoice: :guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)` or :guilabel:`Down payment (fixed amount)`."
msgid "Invoicing based on project milestones can be used for expensive or large-scale projects. The series of milestones in a project represent a clear sequence of work that will inevitably result in the completion of a project and/or contract."
msgid "This method of invoicing ensures the company gets a consistent flow of money throughout the lifetime of the project. Customers can closely monitor every phase of the project's development as it happens, in addition to paying a large bill in several installments, instead of all at once."
msgid "To create and/or configure products to work like this, first navigate to :menuselection:`Sales app --> Products --> Products`. Then, click on a product, or create a new one by clicking :guilabel:`New`."
msgid "On the product form, under the :guilabel:`General Information` tab, the :guilabel:`Product Type` field *must* be set on any of the following options: :guilabel:`Service`, :guilabel:`Event Ticket`, :guilabel:`Event Booth`, or :guilabel:`Course`."
msgid "With any of those :guilabel:`Product Type` options selected, choose :guilabel:`Based on Milestones` from the :guilabel:`Invoicing Policy` drop-down menu."
msgid "Leaving it on the default :guilabel:`Nothing` option won't negatively affect the desired workflow. However, a project *must* then be created directly from a sales order form with that specific product. Once a project is created *then* milestones and tasks can be created and configured."
msgid "When the :guilabel:`Create on Order` default option of :guilabel:`Nothing` is clicked, a drop-down menu is revealed with the following options:"
msgid ":guilabel:`Project \\& Task`: Odoo creates a project and task related to this milestone product in the *Projects* app when this specific product is ordered."
msgid "When :guilabel:`Task` is selected, a :guilabel:`Project` field appears. In this field, select to which existing project in the *Projects* app this created task should be connected."
msgid "When :guilabel:`Project \\& Task` or :guilabel:`Project` is selected, two new fields appear: :guilabel:`Project Template` and :guilabel:`Workspace Template`."
msgid "The :guilabel:`Project Template` field provides template options to use for the project that will be created when this specific product is ordered."
msgid "The :guilabel:`Workspace Template` field provides template options to use for the workspace (for the *Documents* app, not the *Projects* app) that will be automatically generated for the project when this specific product is ordered."
msgid "For organizational purposes, click the :guilabel:`Sales` tab on the product form, and enter a custom 'Milestone' related descriptor in the :guilabel:`Sales Description` field. This information appears in the :guilabel:`Description` column on the :guilabel:`Order Lines` tab of the sales order."
msgid "The following flow features a trio of milestone products that have :guilabel:`Service` set as their :guilabel:`Product Type`, and :guilabel:`Task` set on their :guilabel:`Create on Order` field."
msgid "To invoice milestones, create a sales order with the milestone product(s). To do that, go to :menuselection:`Sales app --> New`. Doing so reveals a blank quotation form."
msgid "From this quotation form, add a :guilabel:`Customer`. Then, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Next, add the milestone product(s) to the :guilabel:`Order Lines` tab."
msgid "Once the corresponding milestone product(s) have been added, click :guilabel:`Confirm` to confirm the order, which turns the quotation into a sales order."
msgid "When the order is confirmed, new smart buttons appear at the top of the sales order based on what was selected in the :guilabel:`Create on Order` field on the product form."
msgid "From the sales order, click the :guilabel:`Milestones` smart button. Doing so reveals a blank :guilabel:`Milestones` page. Click :guilabel:`New` to add milestones."
msgid "Enter a :guilabel:`Name` for the milestone. Next, apply it to the corresponding :guilabel:`Sales Order Item`. Lastly, assign a :guilabel:`Deadline` to the milestone, if desired."
msgid "Then, return to the sales order, via the breadcrumbs. From the sales order, click the :guilabel:`Tasks` smart button. Doing so reveals a :guilabel:`Tasks` page with a task for each sales order item with that option designated in the :guilabel:`Create on Order` field."
msgid "To manually assign a configured milestone to a task, click the desired task, which reveals the task form. On the task form, select the appropriate milestone to which this task should be connected, in the :guilabel:`Milestone` field."
msgid "With those tasks properly configured, employees log in their progress as they work on the task, in addition to adding any notes related to the task."
msgid "To invoice a milestone, first return to the sales order — either via the breadcrumb links, or by navigating to :menuselection:`Sales app --> Orders --> Orders` and picking the appropriate sales order."
msgid "Back on the sales order form, click the :guilabel:`Milestones` smart button, and check the box in the :guilabel:`Reached` column for that particular task."
msgid "Next, return to the sales order — either by clicking :guilabel:`View Sales Order` on the :guilabel:`Milestones` page, or via the breadcrumb links."
msgid "Back on the sales order, the line item for the milestone that's been reached has its :guilabel:`Delivered` column filled. That's because the milestone has been reached, and therefore delivered."
msgid "On the :guilabel:`Create invoices` pop-up window, leave the :guilabel:`Create Invoice` option on the default :guilabel:`Regular Invoice` selection, and click the :guilabel:`Create Draft Invoice` button."
msgid "From this invoice page, click the :guilabel:`Confirm` button to confirm the invoice. Then, when the customer has paid for this milestone, click :guilabel:`Register Payment`."
msgid "When clicked, the pop-up window disappears, and Odoo returns to the invoice for that milestone, which now has a green :guilabel:`In Payment` banner in the upper-right corner. This banner signifies the invoice has been paid."
msgid "Then, return to the sales order, via the breadcrumb links. Back on the sales order, in the :guilabel:`Order Lines` tab, the reached milestone that's been invoiced and paid for, now has its :guilabel:`Invoiced` column filled."
msgid "There is also a new :guilabel:`Invoices` smart button at the top of the sales order. Clicking that reveals all the invoices that are connected to this sales order."
msgid "Continue that process until the entire project has been completed, each milestone has been invoiced, and the entire order has been paid for in full."
msgid "A *pro-forma invoice* is an abridged or estimated invoice sent in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information, such as weight and transportation charges."
msgid "Pro-forma invoices are commonly used as preliminary invoices with a quotation. They are also used during importation for customs purposes. They differ from a normal invoice, in that they are *not* a demand (or request) for payment."
msgid "To enable this feature, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Quotations \\& Orders` section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, click :guilabel:`Save` to save all changes."
msgid "With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send a pro-forma invoice is now available on any quotation or sales order, via the :guilabel:`Send Pro-Forma Invoice` button."
msgid "Pro-forma invoices can **not** be sent for a sales order or quotation if an invoice for a down payment has already been sent, or for a recurring subscription."
msgid "However, pro-forma invoices **can** be sent for services, event registrations, courses, and/or new subscriptions. Pro-forma invoices are not limited to physical, consumable, or storable goods."
msgid "In the pop-up window, the :guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation. The :guilabel:`Subject` field and the body of the email can be modified, if necessary."
msgid "To preview what the pro-forma invoice looks like, click on the PDF at the bottom of the email pop-up window *before* clicking :guilabel:`Send`. When clicked, the pro-forma invoice is downloaded instantly. Open that PDF to view (and review) the pro-forma invoice."
msgid "Invoicing based on time and/or materials is typically used when accurately estimating the size of a project isn't possible, or when the requirements of a project may change."
msgid "This is different from a fixed-price contract, when a customer agrees to pay a specified total for the fulfillment of the contract---no matter what needs to be paid to the employees, sub-contractors, vendors, suppliers, and so on."
msgid "The Odoo *Sales* app can invoice for time and various other expenses (e.g. transport, lodging), as well as purchases needed to fulfill an order."
msgid "To install the *Project* app, navigate to :menuselection:`Odoo main dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the :guilabel:`Project` app block, and click :guilabel:`Activate`. The page automatically refreshes and returns to the main Odoo dashboard, where the *Project* app is now available to access."
msgid "After installation, click the :guilabel:`Accounting` app icon from the main Odoo dashboard, and navigate to :menuselection:`Configuration --> Settings`. On the :guilabel:`Settings` page, scroll down to the :guilabel:`Analytics` section, and ensure the box next to :guilabel:`Analytic Accounting` is checked."
msgid "Then, navigate to :menuselection:`Odoo main dashboard --> Project app --> Configuration --> Settings`. On the :guilabel:`Settings` page, in the :guilabel:`Time Management` section, ensure the box beside the :guilabel:`Timesheets` feature is checked."
msgid "With the *Timesheets* feature activated in the *Project* app, it is now possible to invoice for time spent on a project, but **only** when the following product configurations have been made."
msgid "To configure a service product, first navigate to :menuselection:`Sales app --> Products --> Products`. On the :guilabel:`Products` page, select the desired service product to be configured, or click :guilabel:`New` to create a new product."
msgid "From the product form, in the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Service`. Then, open the drop-down menu in the :guilabel:`Invoicing Policy` field, and select :guilabel:`Based on Timesheets`."
msgid "Next, from the :guilabel:`Create on Order` drop-down menu, select :guilabel:`Project \\& Task`. That setting indicates that, when a sales order is created with this specific service product, a new project and task is created in the *Project* app."
msgid "The option :guilabel:`Task` can be chosen instead from the :guilabel:`Create on Order` drop-down menu. If :guilabel:`Task` is chosen, select an existing project that the task will appear in from :guilabel:`Project` field, which only appears if :guilabel:`Task` is chosen in the :guilabel:`Create on Order` field."
msgid "After properly configuring a service product with the correct *Invoicing Policy* and *Create on Order* options, it is possible to add time spent to a sales order."
msgid "To see that in action, navigate to :menuselection:`Sales app --> New` to open a blank quotation form. Then, proceed to add a :guilabel:`Customer`, and in the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select the properly :ref:`configured service product <sales/invoicing/configured-service-product>` from the drop-down menu."
msgid "If the :guilabel:`Projects` smart button is clicked, it reveals the specific project related to this sales order. If the :guilabel:`Tasks` smart button is clicked, it reveals the specific project task related to this sales order. Both are also accessible in the *Project* app."
msgid "On the task form, select the :guilabel:`Timesheets` tab. From the :guilabel:`Timesheets` tab, employees can be assigned to work on the project, and the time they spend working on the task can be added by the employees or by the person who created the sales order."
msgid "To add an employee, and the time spent working on the task, click :guilabel:`Add a line` in the :guilabel:`Timesheets` tab. Then, select the appropriate :guilabel:`Date` and :guilabel:`Employee`. There is also the option to add a brief description of the work done during this time in the :guilabel:`Description` column, but it's not required."
msgid "Lastly, enter the amount of time worked on the task in the :guilabel:`Hours Spent` column, and click away to complete that line in the :guilabel:`Timesheets` tab."
msgid "The time entered in the :guilabel:`Hours Spent` column is immediately reflected in the :guilabel:`Allocated Time` field (located near the top of the task form) as a percentage, which reflects how much of the total allocated work hours have been done so far."
msgid "That same information is found as numerical hours in the :guilabel:`Hours Spent` and :guilabel:`Remaining Hours` fields, located at the bottom of the :guilabel:`Timesheets` tab."
msgid "Once all the necessary employees and time spent have been added to the project task, return to the sales order to invoice the customer for those hours. To do that, either click the :guilabel:`Sales Order` smart button at the top of the task form, or return to the sales order via the breadcrumb links, located in the upper-left of the screen."
msgid "Back on the sales order form, the time that was added to the task is reflected in the :guilabel:`Order Lines` tab (in the :guilabel:`Delivered` column) and in the new :guilabel:`Recorded Hours` smart button at the top of the sales order."
msgid "To invoice the customer for time spent on the project, click :guilabel:`Create Invoice`, and select :guilabel:`Regular invoice` from the :guilabel:`Create invoices` pop-up window. Then, click :guilabel:`Create Draft Invoice`."
msgid "Pay attention to the :guilabel:`Analytic Distribution` column in the :guilabel:`Customer Invoice`, as that information is necessary to ensure other time/material invoicing tasks are completed properly and accurately."
msgid "To install the *Expenses* app, navigate to :menuselection:`Odoo main dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the :guilabel:`Expenses` app block, and click :guilabel:`Activate`."
msgid "To add an expense to a sales order, first navigate to the :menuselection:`Expenses` app. Then, from the main *Expenses* dashboard, click :guilabel:`New`, which reveals a blank expense form."
msgid "On the expense form, add a :guilabel:`Description` of the expense (e.g. `Hotel Stay`, `Plane Ticket`). Next, in the :guilabel:`Category` field, select the appropriate option from the drop-down menu (e.g. :guilabel:`Meals`, :guilabel:`Miles`, :guilabel:`Travel \\& Accommodation`)."
msgid "Then, enter the total amount of the expense in the :guilabel:`Total` field, as well as any :guilabel:`Included Taxes` that may apply. Next, ensure that the correct :guilabel:`Employee` is selected, and designate who paid for the expense in the :guilabel:`Paid By` field: the :guilabel:`Employee (to reimburse)` or the :guilabel:`Company`."
msgid "Next, in the :guilabel:`Customer to Reinvoice` field, select the appropriate sales order from the drop-down menu. Then, select that same sales order information from the :guilabel:`Analytic Distribution` field, as well."
msgid "The :guilabel:`Analytic Distribution` field will **only** have the corresponding sales order as an option if the sales order contains a service product that is billed based on *Timesheets*, *Milestones*, or *Delivered Quantities*."
msgid "If there are any receipts that should be uploaded and attached to the expense, click the :guilabel:`Attach Receipt` button, and upload the necessary documents to the expense. This is **not** required, but it may affect whether or not an expense is approved."
msgid "When all the information has been entered, click :guilabel:`Create Report` to create an expense report detailing all the expense information that was just entered."
msgid "To showcase a complete flow in this example, select :guilabel:`Submit to Manager`. Then, the manager would click :guilabel:`Approve` to approve this expense, and click :guilabel:`Post Journal Entries` to post this expense to the accounting journal."
msgid "To invoice a customer for an :ref:`expense on a sales order <sales/invoicing/add-expenses-sales-order>`, navigate to the related sales order, either from the :menuselection:`Sales` app or from the expense report in the :menuselection:`Expenses` app. From the expense report, click the :guilabel:`Sales Orders` smart button at the top of the page."
msgid "If the expense report was linked to the sales order, the newly-configured expense now has its own line in the :guilabel:`Order Lines` tab, and can be invoiced to the customer."
msgid "To invoice the customer for the expense on the sales order, click :guilabel:`Create Invoice`, select :guilabel:`Regular Invoice` from the :guilabel:`Create invoices` pop-up window, then click :guilabel:`Create Draft Invoice`."
msgid "To install the *Purchase* application, navigate to :menuselection:`Odoo main dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the :guilabel:`Purchase` app block, and click :guilabel:`Activate`. The page automatically refreshes and returns to the main Odoo dashboard, where the :guilabel:`Purchase` app is now available to access."
msgid "To add a purchase to a sales order, a purchase order must first be created. To create a purchase order, navigate to :menuselection:`Purchase app --> New` to reveal a blank purchase order form."
msgid "First, add a :guilabel:`Vendor` to the purchase order. Then, under the :guilabel:`Products` tab, click the :guilabel:`extra column options` drop-down menu, represented by two horizontal lines with dots on them, located to the far-right of the column headers. From that drop-down menu, select :guilabel:`Analytic Distribution`."
msgid "After adding the :guilabel:`Analytic Distribution` column to the headers on the :guilabel:`Products` tab of the purchase order form, proceed to add the product(s) to the purchase order. To do that, click :guilabel:`Add a product`, and select the desired product from the drop-down menu. Repeat for all the products to add."
msgid "In order for a purchase to be properly invoiced on a sales order, the product on the purchase order **must** be marked as :guilabel:`Can be Expensed`, have an :guilabel:`Invoicing Policy` set to :guilabel:`Delivered quantities`, and have the :guilabel:`At cost` option selected in the :guilabel:`Re-Invoice Expenses` field on its product form."
msgid "Then, select the appropriate :guilabel:`Analytic Distribution` associated with the sales order to which this purchase order is related. To do that, click the empty :guilabel:`Analytic Distribution` field to reveal an :guilabel:`Analytic` pop-up window."
msgid "Then, from the :guilabel:`Departments` drop-down menu, select the analytic distribution associated with the desired sales order to be invoiced for the purchase."
msgid "Once all the information is entered in the :guilabel:`Products` tab of the purchase order, confirm the order by clicking :guilabel:`Confirm Order`. Then, click :guilabel:`Receive Products` when the products have been received. This creates a receipt form."
msgid "If any serial/lot numbers must be entered before validating the receipt of products, then on the receipt form, click the :guilabel:`details` icon represented by four horizontal lines located to the far-right of the product line."
msgid "This reveals a :guilabel:`Detailed Operations` tab, in which the necessary :guilabel:`Lot/Serial Number(s)` and :guilabel:`Done` quantity can be added. When ready, click :guilabel:`Confirm` to confirm the data."
msgid "Next, return to the purchase order, via the breadcrumb links at the top of the page, and click :guilabel:`Create Bill` to create a vendor bill that can be invoiced to the customer on the attached sales order."
msgid "Make sure to enter a :guilabel:`Bill Date` on the :guilabel:`Vendor Bill Draft` before confirming. If a :guilabel:`Bill Date` is *not* entered, an error window appears, requesting that information to be entered before confirmation can occur."
msgid "Then, click :guilabel:`Confirm` to confirm the vendor bill, which is then automatically added to the sales order, where it can be invoiced directly to the customer attached to it."
msgid "To invoice a customer for a purchase on a sales order, first :ref:`add the purchase to the sales order <sales/invoicing/add-purchase-to-sales-order>`, then navigate to the desired sales order in the :menuselection:`Sales` app."
msgid "On the sales order that was attached to the purchase order, the purchased product now has its own product line under the :guilabel:`Order Lines` tab, and it is ready to be invoiced."
msgid "To invoice the customer for the purchase, simply click :guilabel:`Create Invoice`, select :guilabel:`Regular Invoice` from the :guilabel:`Create invoices` pop-up window, then click :guilabel:`Create Draft Invoice`."
msgid "To complete the invoicing process, click :guilabel:`Confirm` to confirm the invoice, and then click :guilabel:`Register Payment` in the :guilabel:`Register Payment` pop-up form."
msgid "To enable eWallets and gift cards for eCommerce and Point of Sale (PoS), first enable :guilabel:`Discounts, Loyalty & Gift Card` under :menuselection:`Sales app --> Configuration --> Settings --> Pricing section`. Once enabled, go to :menuselection:`Sales app --> Products --> Gift cards & eWallet` and :guilabel:`Create` a new eWallet or gift card program."
msgid "eWallets allow customers to save credits on their online account and use these credits as a payment method when buying items in an online store or a brick-and-mortar store. eWallets can also be used to centralize multiple :ref:`gift cards <ewallet_gift/gift-cards>`."
msgid "Before creating an eWallet program, it is necessary to create an eWallet **top-up** product. Top-ups are pre-defined digital credit values added to an eWallet in exchange for its equivalent in real currency. These credits can then be used as a payment method in the eCommerce shop or :abbr:`PoS (Point of Sale)`. Top-up values can be of different amounts."
msgid "To create a top-up product, go to :menuselection:`Sales app --> Products --> Products` and :guilabel:`Create` a new product. On the product template, configure the options as follows:"
msgid "Once the top-up is created, go to :menuselection:`Sales app --> Products --> Gift cards & eWallet` to :guilabel:`Create` an eWallet program. The following configuration options are available:"
msgid ":guilabel:`Email template`: select the email template used for the email sent to the customer. To create a new template, click on the field, select :guilabel:`Search More`, and then click :guilabel:`Create`."
msgid ":guilabel:`Point of Sale`: select the :abbr:`PoS (Point of Sale)` in which the program is valid and available. Leave this field empty to include all :abbr:`PoS (Point of Sale)`."
msgid "Once the program is configured, click the :guilabel:`Generate eWallet` button in the upper-left corner to generate eWallets. eWallets can be generated based on :guilabel:`Customers` and/or :guilabel:`Customer Tags`. The quantity is automatically adapted according to the :guilabel:`Customers` and :guilabel:`Customer Tags` selected. Then, set the :guilabel:`eWallet value`. Finally, set the :guilabel:`Valid Until` period if applicable."
msgid "Generated eWallets can be accessed through the :guilabel:`eWallets` smart button in the upper-right corner. From there, :guilabel:`Send` or :guilabel:`Share` the eWallets via email or a URL link."
msgid "Click on an eWallet to change the :guilabel:`Expiration Date`, :guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of an eWallet *cannot* be changed, deleted, or duplicated."
msgid "Gift cards can be purchased by customers, and in turn used as a payment method upon checkout at an eCommerce shop or :abbr:`PoS (Point of Sale)`."
msgid "Before creating a new gift card program, it is necessary to first create gift cards as products. To do so, go to :menuselection:`Sales app --> Products --> Products` and :guilabel:`Create` a product. On the product template, configure the options as follows:"
msgid "Once the gift card product is created, go to :menuselection:`Sales app --> Products --> Gift cards & eWallet` to :guilabel:`Create` a gift card program. The following configuration options are available:"
msgid ":guilabel:`Gift Card Products`: select the gift card product created earlier. Repeat the process if you created gift card products of different amounts."
msgid ":guilabel:`Email template`: select the default :guilabel:`Gift Card: Gift Card Information` template, or create a new template by clicking on the field, selecting :guilabel:`Search More`, and then clicking :guilabel:`Create`."
msgid "Once the program is configured, click the :guilabel:`Generate Gift Cards` button in the upper-left corner to generate gift cards. Gift cards can be generated either for :guilabel:`Anonymous Customers` or :guilabel:`Selected Customers`. Set the :guilabel:`Quantity to generate` for :guilabel:`Anonymous Customers`, or select the :guilabel:`Customers` and/or :guilabel:`Customer Tags` for :guilabel:`Selected Customers`. Then, set the :guilabel:`Gift Card value`. Finally, set the :guilabel:`Valid Until` period if applicable."
msgid "Generated gift cards can be accessed through the :guilabel:`Gift Cards` smart button in the upper-right corner. From there, :guilabel:`Send` or :guilabel:`Share` the gift cards via email or a URL link."
msgid "Click on a gift card to change the :guilabel:`Expiration Date`, :guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of a gift card *cannot* be changed, deleted, or duplicated."
msgid "The Odoo *Sales*, *eCommerce*, and *Point of Sale* applications allow users to create discount and loyalty programs that customers can use for online and in-store shopping. These programs offer more varied, public, and time-sensitive pricing options than :doc:`pricelists </applications/sales/sales/products_prices/prices/pricing>`."
msgid "To begin using discount and loyalty programs, navigate to :menuselection:`Sales --> Configuration --> Settings`. Under the :guilabel:`Pricing` heading, activate the :guilabel:`Discounts, Loyalty & Gift Card` setting by checking the box next to the feature. Finally, click :guilabel:`Save` to save the changes."
msgid "If no discount or loyalty programs have been created yet, Odoo provides a choice of templates to help create the first program. Choose one of the template cards, or click :guilabel:`New` to create a new program from scratch."
msgid ":guilabel:`Pricelist`: If desired, select a pricelist from the drop-down menu to have this loyalty program applied to a specific pricelist (and customers attached to the pricelist). More than one pricelist can be selected in this field. When a single loyalty program is linked to several pricelists, it makes it viable for different customer segments to have different pricelists, but the *same* loyalty programs. If this field is left blank, the program applies to everyone, regardless of pricelist."
msgid ":guilabel:`Points Unit`: Enter the name of the points used for the :guilabel:`Loyalty Cards` program (e.g. `Loyalty Points`). The points unit name *is* visible to the customer. This field is **only** available when the :guilabel:`Program Type` is set to :guilabel:`Loyalty Cards`."
msgid ":guilabel:`Start Date`: Select the date on which the program becomes valid. Leave this field blank if the program should always be valid and not expire."
msgid ":guilabel:`End Date`: Select the date on which the program stops being valid. Leave this field blank if the program should always be valid and not expire."
msgid ":guilabel:`Limit Usage`: If desired, tick this checkbox, and enter a number of :guilabel:`usages` to limit the number of times the program can be used during the validity period."
msgid ":guilabel:`Company`: If working in a multi-company database, choose the one company for which the program is available. If left blank, the program is available to all companies in the database."
msgid ":guilabel:`Point of Sale`: Select the point(s) of sale at which the program is available. Leave this field blank to make it available at all :abbr:`PoS (Point of Sale)`."
msgid "All of the existing cards, codes, coupons, etc. that have been generated for the program are accessible through the smart button located at the top of the form."
msgid "In Odoo 17 (and later), when a loyalty card or coupon is associated with a contact in the database, a :guilabel:`Loyalty Cards` smart button conditionally appears on the contact form."
msgid ":guilabel:`Buy X Get Y`: for every (X) item bought, the customer is granted 1 credit. After accumulating a specified amount of credits, the customer can trade them in to receive (Y) item."
msgid "In the :guilabel:`Rules & Rewards` tab, click :guilabel:`Add` next to :guilabel:`Conditional rules` to add *conditions* to the program. This reveals a :guilabel:`Create Conditional rules` pop-up window."
msgid ":guilabel:`Discount Code`: Enter a custom code to be used for the :guilabel:`Discount Code` program, or use the default one generated by Odoo. This field is only available when the :guilabel:`Program Type` is set to :guilabel:`Discount Code`."
msgid ":guilabel:`Minimum Quantity`: Enter the minimum number of products that must be purchased in order to access the reward. Set the minimum quantity to at least `1` to ensure that the customer must make a purchase in order to access the reward."
msgid ":guilabel:`Minimum Purchase`: Enter the minimum amount (in currency), with :guilabel:`tax Included` or :guilabel:`tax Excluded`, that must be spent in order to access the reward. If both a minimum quantity *and* minimum purchase amount are entered, then the customer's order must meet both conditions."
msgid ":guilabel:`Categories`: Select the category of products for which the program applies. Choose :guilabel:`All` to apply it to all product categories."
msgid ":guilabel:`Grant`: Enter the number of points the customer earns :guilabel:`per order`, :guilabel:`per currency spent`, or :guilabel:`per unit paid` (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get Y` programs)."
msgid "Click :guilabel:`Save & Close` to save the rule and close the pop-up window, or click :guilabel:`Save & New` to save the rule and immediately create a new one."
msgid "In the :guilabel:`Rules & Rewards` tab of the program form, click :guilabel:`Add` next to :guilabel:`Rewards` to add *rewards* to the program. This reveals a :guilabel:`Create Rewards` pop-up window."
msgid ":guilabel:`Reward Type`: Select the reward type among :guilabel:`Free Product`, :guilabel:`Discount`, and :guilabel:`Free Shipping`. The other options for reward configuration depend on the :guilabel:`Reward Type` selected."
msgid ":guilabel:`Discount`: Enter the discounted amount in either :guilabel:`percentage`, :guilabel:`currency per point`, or :guilabel:`currency per order`. Then, select whether the discount applies to the entire :guilabel:`Order`, only the :guilabel:`Cheapest Product` on the order, or only :guilabel:`Specific Products`."
msgid ":guilabel:`Max Discount`: Enter the maximum amount (in currency) that this reward may grant as a discount. Leave this field at `0` for no limit."
msgid ":guilabel:`In exchange of`: Enter the number of points required to exchange for the reward (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get Y` programs)."
msgid "With Odoo, pricelists can be used to manage prices in a number of foreign currencies. Specifically, Odoo has the ability to work with 167 total currencies."
msgid "Once the *Accounting* app has been installed, foreign currencies can be added to the database. Navigate to :menuselection:`Accounting app --> Configuration --> Settings`, scroll to the :guilabel:`Currencies` section, and locate the :guilabel:`Main Currency` setting."
msgid "To change the main currency of the company, select the drop-down menu in the :guilabel:`Currency` field, select the desired currency, and be sure to :guilabel:`Save` the changes."
msgid "Click the checkbox beside the :guilabel:`Automatic Currency Rates` feature, choose a designated bank to get the currency rates from in the :guilabel:`Service` field drop-down menu, and select an :guilabel:`Interval` of time for the updates to take place. Then determine when the date of the :guilabel:`Next Run` should be."
msgid "To instantly update the currency rates, click the :guilabel:`🔁 (circular arrows)` icon, located to the right of the :guilabel:`Next Run` field."
msgid "All payment methods **must** be in the same currency as the sales journal, or the company currency, if the company currency is not set. If it is not the same, a :guilabel:`Validation Error` message appears."
msgid "To view, edit, and add currencies to the database, making them available on pricelists and on the :guilabel:`Main Currency` drop-down menu, click the :guilabel:`Currencies` link, located beneath the :guilabel:`Currency` field on the :menuselection:`Accounting app --> Settings` page."
msgid "On this page, Odoo provides a master list of 167 global currencies. Each row shows the corresponding :guilabel:`Currency`, :guilabel:`Symbol`, :guilabel:`Name`, date of the :guilabel:`Last Update`, and :guilabel:`Current Rate` (compared to the default currency of the country in which the company is based)."
msgid ":guilabel:`Active`: this currency is activated, which means it can be added to a pricelist, or used as the main currency of the company, if desired (via :menuselection:`Accounting app --> Configuration --> Settings --> Currencies section`)."
msgid "It is recommended that *at least* one pricelist is created per :guilabel:`Active` currency. See :doc:`./pricing` to learn more about pricelist configuration."
msgid "To toggle options on/off, click the toggle switch in the row for the corresponding column. When *on* the color of the switch is green. When *off*, the color of the switch is grey."
msgid "To edit any currency on the :guilabel:`Currencies` page, click the desired currency to reveal the detail form for that specific currency, and proceed to make any necessary changes."
msgid "On the currency detail form, the relevant currency code appears in the :guilabel:`Currency` field. Beneath that, the name for the currency is in the :guilabel:`Name` field."
msgid "Then, toggle the currency's availability with the :guilabel:`Active` toggle: *on* is indicated with a green switch, and *off* is indicated with a grey switch."
msgid "On the right of the currency detail form, the appropriate :guilabel:`Currency Unit` (e.g. `Dollars`) and :guilabel:`Currency Subunit` (e.g. `Cents`) can be found."
msgid "Next, under the :guilabel:`Rates` tab, the various conversion rates can be viewed, added, or deleted. Each row shows the :guilabel:`Date` of that specific rate, the :guilabel:`Company` to which it is connected, followed by the :guilabel:`Unit per...` and :guilabel:`...per Unit`."
msgid "The *...* in each of the last two columns represents the main currency set for the company. For example, if the main currency is set to `USD`, the columns are titled :guilabel:`Unit per USD` and :guilabel:`USD per Unit`."
msgid "To add a new rate, click :guilabel:`Add a line` in the :guilabel:`Rates` tab, and proceed to fill in the necessary information in the aforementioned columns."
msgid "If the selected currency is the main currency of the company, a blue banner appears at the top of the currency detail form with the message: :guilabel:`This is your company's currency.`."
msgid "All the fields are the same as a typical currency detail form, but there will **not** be a :guilabel:`Rates` tab because all other currency rates are based off the main currency of the company."
msgid "On the blank currency detail form, proceed to enter the desired currency code in the :guilabel:`Currency` field. Beneath that, enter the name for the currency in the :guilabel:`Name` field."
msgid "On the right of the currency detail form, enter the appropriate :guilabel:`Currency Unit` (e.g. `Dollars`) and appropriate :guilabel:`Currency Subunit` (e.g. `Cents`)."
msgid "Next, under the :guilabel:`Rates` tab, add a new rate by clicking :guilabel:`Add a line`. Then, proceed to confirm and adjust the :guilabel:`Date`, :guilabel:`Company`, :guilabel:`Unit per...`, and :guilabel:`...per Unit` fields to ensure all the auto-populated information is accurate."
msgid "It is recommended that *at least* one pricelist is created per active currency in the database. To create (or assign) a pricelist to a specific currency, start by navigating to :menuselection:`Sales app --> Products --> Pricelists`."
msgid "It should be noted that the public price seen on products is directly related to the main currency the company has set, which is configured by navigating to :menuselection:`Accounting app --> Configuration --> Settings --> Currencies section --> Main Currency --> Currency drop-down menu`."
msgid "The sales price automatically updates if the pricelist is changed to a different pricelist that has a different currency than the company's main currency. The change in price is directly related to the updated conversion rate for that currency."
msgid "In order to have product prices set in place to avoid any changes in currency rates, start by navigating to :menuselection:`Sales app --> Products --> Products`."
msgid "Then, on the product detail form, click the :guilabel:`Extra Prices` smart button, located in the upper-left corner. Doing so reveals a separate :guilabel:`Price Rules` page, specific to that particular product."
msgid "The :guilabel:`Applied On` field is auto-populated with the product, so proceed to enter in the desired figures in the :guilabel:`Min. Quantity` and :guilabel:`Price` fields."
msgid "The figure in the :guilabel:`Min. Quantity` field means the :guilabel:`Price` being set will **only** trigger if at least that amount of product is purchased."
msgid "If necessary, configure a :guilabel:`Start Date` and :guilabel:`End Date` for the set prices. Leaving those columns blank ensures the set price will remain valid, regardless of the date of sale."
msgid "If working in a multi-company environment, designate to which company this price rule should be applied in the :guilabel:`Company` field. Leaving that field blank ensures the price rule applies to all companies in the database."
msgid "With those configurations complete, regardless of any changes/updates in conversion, whenever those designated pricelists are applied to a customer trying to purchase this specific product, these pre-determined set prices appear."
msgid "A *pricelist* is a list of prices (or price rules) that Odoo uses to determine the appropriate price for a customer. These pricelists can be set with specific criteria (such as time periods, minimum quantity sold, and more) in order to apply certain prices or discounts."
msgid "To choose a pricing strategy, first navigate to :menuselection:`Sales app --> Configuration --> Settings`. In the :guilabel:`Pricing` section, click the checkbox next to the :guilabel:`Pricelists` feature."
msgid "Doing so reveals two additional options beneath it: :guilabel:`Multiple prices per product` and :guilabel:`Advanced price rules (discounts, formulas)`. A link labeled :guilabel:`Pricelists` also appears, which leads to a separate pricelists page, wherein pricelists can be created and/or modified."
msgid ":guilabel:`Advanced price rules (discounts, formulas)`: provides the option to create detailed price rules and apply discounts, margins, and roundings."
msgid "After clicking the checkbox beside the :guilabel:`Pricelists` feature, select one of those two options, then click :guilabel:`Save` to save all changes."
msgid "After activating and saving the :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`."
msgid "The order of the pricelists on the :guilabel:`Pricelists` page has an impact on how they are applied. If several pricelists share the same criteria, **only** the first listed pricelist is applied."
msgid "For example, for two pricelists with different rules, but same criteria (e.g., same website, same country), only the *first* pricelist in the list is applied."
msgid "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo *Sales* and *eCommerce*. This pricelist is applied by default, if there are no matching criteria."
msgid "In Odoo 17 (and above), it is no longer required to have a pricelist entered in the :guilabel:`Pricelist` field on a quotation form in order to confirm it (i.e. turn it into a sales order)."
msgid "It should also be noted that, in Odoo 17 (and above), a chatter section can be found on pricelist forms, which enhances the ability to communicate about them."
msgid "From the :guilabel:`Pricelists` page, either select the desired pricelist to edit, or click :guilabel:`New` to create a new pricelist, which reveals a blank pricelist form that can be configured in a number of different ways."
msgid "When creating a new pricelist, start by adding a name for the pricelist at the top of the form, in the blank field. Next, select which :guilabel:`Currency` should be used."
msgid "Then, if working in a multi-company environment, select which company this pricelist should apply to in the :guilabel:`Company` field. If this field is left blank, the pricelist is automatically applied to all companies in the database."
msgid "The :guilabel:`Price Rules` tab functionality on a pricelist form varies depending on the :guilabel:`Pricelists` setting chosen: either :guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules (discounts, formulas)`."
msgid "However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` tab are always the same, regardless of the chosen :guilabel:`Pricelists` setting."
msgid "With the :guilabel:`Multiple prices per product` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to add specific products, with a specific price, to a pricelist."
msgid "To add a specific product and price to a pricelist form, click the :guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the :guilabel:`Products` column. Then, select the desired product for which a specific price should be applied."
msgid "Next, if necessary, select a product variant under the :guilabel:`Variants` column (e.g. a specific product size, color, etc.). If no variants are selected, then this price will apply to all variants of the product."
msgid "If a minimum amount of the product must be purchased in order to apply the specific price, enter the amount under the :guilabel:`Min. Quantity` column."
msgid "To configure the price of the product for this specific pricelist, enter the desired amount under the :guilabel:`Price` column. Then, there is the option to add a :guilabel:`Start Date` and :guilabel:`End Date` to the configured product price, if desired."
msgid "To add another product line, click :guilabel:`Add a line` again, and repeat the process. There is no limit to how many products can be added in the :guilabel:`Price Rules` tab of a pricelist form."
msgid "With the :guilabel:`Advanced price rules (discounts, formulas)` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to configure detailed price rules based on formulas."
msgid "Check out the :ref:`Advanced price rules (discounts, formulas) <sales/advanced-price-rules>` section for detailed steps on how to add advanced price rules to a pricelist."
msgid "Under the :guilabel:`Recurring Prices` tab, the same functionality of the :guilabel:`Price Rules` tab is present. The only difference being that a recurring time period can be applied in the :guilabel:`Recurring Plan` column."
msgid "Once :guilabel:`Products` and/or :guilabel:`Product Variants` are selected, click :guilabel:`Add a price rule`, and select the blank field in the :guilabel:`Recurring Plan` column to reveal a drop-down menu of pre-designated recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)."
msgid "New recurrence periods can also be created from this column. To do so, type in the name for the new :guilabel:`Recurring Plan`, then select :guilabel:`Create` from the resulting drop-down menu to create the time period, which can be edited later."
msgid "Or, select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Recurring Plan` pop-up form. From this pop-up form, the new recurrence period can be configured, with specific :guilabel:`Details`, :guilabel:`Self-Service`, and :guilabel:`Pricing` options. When the configurations are complete, click the :guilabel:`Save & Close` button."
msgid "Under the :guilabel:`Rental rules` tab, specific price rules can be configured for various rental products, using the same methodology as the :guilabel:`Price Rules` and :guilabel:`Recurring Prices` tabs."
msgid "To add a rental rule, click :guilabel:`Add a line`, and select a desired product in the :guilabel:`Products` column. Then, select any specific :guilabel:`Variants`, if necessary."
msgid "From here, under the :guilabel:`Availability` section, in the :guilabel:`Country Groups` field, certain country groups can be added to the pricelist. There is no limit to how many country groups can be added in this field."
msgid "Under the :guilabel:`Website` section, there are a few options that can be configured. In the :guilabel:`Website` field, this pricelist can be applied to a specific website, if working in a multi-website environment. If left blank, the pricelist is applied to all websites in the database."
msgid "Tick the :guilabel:`Selectable` checkbox to have this pricelist as a selectable option for customers to choose as they shop. If the :guilabel:`Selectable` box is left unticked, customers **cannot** select this pricelist for themselves."
msgid "Lastly, there is the option to add an :guilabel:`E-commerce Promotional Code`. To add a code, type in the desired promo code that, when entered during the checkout process, applies the pricelist to the customer, even if the customer does not fall into the previously-specified criteria."
msgid "Then, in the :guilabel:`Discounts` section, there is a :guilabel:`Discount Policy` field with two options to choose from: :guilabel:`Discount included in the price` or :guilabel:`Show public price & discount to the customer`."
msgid "If :guilabel:`Discount included in the price` is selected, the price shown to the customer already accounts for the discount being applied. However, if :guilabel:`Show public price & discount to the customer` is selected, the customer sees the actual public price *and* how much they are saving with this pricelist discount."
msgid "While the default pricelist applied to any customer is the :guilabel:`Public Pricelist`, Odoo provides the opportunity to directly apply a different pricelist to customers on their contact form."
msgid "To do that, open the desired customer's contact form, either by navigating to :menuselection:`Sales app --> Orders --> Customers` and selecting the customer from the main :guilabel:`Customers` page, or by clicking on the customer's name on a sales order."
msgid "On the desired customer's contact form, under the :guilabel:`Sales & Purchase` tab, in the :guilabel:`Sales` section, designate what pricelist should be applied to this specific customer from the drop-down menu in the :guilabel:`Pricelist` field."
msgid "When a customer is added to the database, the default pricelist is automatically applied to them. There is **no way** to have a blank *Pricelist* field on a contact form. Even if that field is left blank, the default pricelist appears when that contact form is opened again."
msgid "However, when that contact is added to a quotation, and the *Pricelist* field is auto-populated (based on the information from their contact form), that predetermined pricelist can be removed from the *Pricelist* field, and the quotation can still be confirmed, and subsequently, turned into a sales order."
msgid "To apply several prices per individual product, select the :guilabel:`Multiple prices per product` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`."
msgid "Next, apply pricelists to specific products using the product form. Navigate to the :menuselection:`Sales app --> Products --> Products` and select the product for which multiple prices should be applied. Selecting a product from the :guilabel:`Products` page reveals that specific product's product form on a separate page."
msgid "Doing so reveals a separate page displaying the :guilabel:`Price Rules` that are specific to that particular product. Here, price rules can be edited or created at any time."
msgid "To create a new price rule for a product from this specific :guilabel:`Price Rules` page, click :guilabel:`New` to add a new, customizable row that has the desired product already populated in the :guilabel:`Applied On` column."
msgid "Next, select which :guilabel:`Pricelist` this specific product price rule should apply to, via the drop-down menu in the :guilabel:`Pricelist` column."
msgid "To create a new pricelist from this page, type in the desired name of the new pricelist in the :guilabel:`Pricelist` column, then select :guilabel:`Create` from the drop-down menu. All pricelists can be modified at any time, by navigating to :menuselection:`Sales app --> Products --> Pricelists`. Pricelists can also be created on that specific :guilabel:`Pricelists` page, as well."
msgid "If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the :guilabel:`Price` column will be applied to orders of 2 or more products. So, in theory, if a single product costs $100, customers can be encouraged to buy more, if the :guilabel:`Price` is set at $85 per product for a :guilabel:`Min. Quantity` of `2` products."
msgid "Next, enter the desired amount in the :guilabel:`Price` column. Then, if needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the product's price rule."
msgid "And lastly, if working in a multi-company environment, select which company this price rule should be applied to in the :guilabel:`Company` field. Leaving this field blank means the price rule applies for all companies in the database."
msgid "With the price rule(s) in place for a specific product, customers who fall into those corresponding pricelists automatically see those new prices applied. The number of price rules applied to a particular product are also displayed in the :guilabel:`Extra Prices` smart button, located on every product form."
msgid "When a price rule/pricelist is added to a product via the :guilabel:`Extra Prices` smart button, it is also reflected on the pricelist itself. Similarly, when a price rule for a specific product is added to a pricelist, it is also reflected on the product form via the :guilabel:`Extra Prices` smart button."
msgid "The *Discounts* feature allows the ability to set a discount or increase the price on *individual items* in a sales order. This is calculated as a percentage of that product's sales price."
msgid "To access discounts, navigate to the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click the :guilabel:`Discounts` checkbox, then click :guilabel:`Save`."
msgid "After the setting has been activated, navigate to the desired quotation by going to :menuselection:`Sales app --> Orders --> Quotations` at the top of the page. Once there, click on the desired quote from the list."
msgid "In the order lines section of the quotation form, a new column heading will appear labeled :guilabel:`Disc.%`. This column is used to set discounts on individual line items. Enter the desired discount for each product line and the new price will automatically be calculated in the quote :guilabel:`Total` at the bottom of the page."
msgid "A discount can also be added directly to a sales order in the same way. Navigate to :menuselection:`Sales app --> Orders --> Orders`, click on the desired sales order, and add the discount to :guilabel:`Disc.%` as described above."
msgid "On this pop-up window, configure the :guilabel:`Discount` percentage, and select one of the following discount options: :guilabel:`On All Order Lines`, :guilabel:`Global Discount`, or :guilabel:`Fixed Amount`."
msgid ":guilabel:`On All Order Lines`: When selected, Odoo provides the ability to add the specified discount percentage (configured in the :guilabel:`Discount` field of the pop-up window) on all existing order lines of the sales order."
msgid ":guilabel:`Global Discount`: When selected, Odoo adds a discount product to the order, which has the cumulative value equivalent to the specified discount percentage (configured in the :guilabel:`Discount` field of the pop-up window). Any product added (or removed) *after* the discount is added does **not** affect the discount value on the order line."
msgid "In this example, since the total of the order is $600, and there is a 30% global discount, that specific line is added to the sales order with a -180 value (which is 30% of $600)."
msgid ":guilabel:`Fixed Amount`: When selected, the percentage designation in the :guilabel:`Discount` field turns to a monetary value (e.g. dollars), wherein a specific amount must be entered. This configured value is added as a discount line on the sales order."
msgid "It is more beneficial to add a :guilabel:`Fixed Amount` discount after **all** desired products have been added to a sales order. If there are changes made to the sales order *after* the discount is added, make sure to change the value on the :guilabel:`Discount` line, or remove the line and add the discount again."
msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist."
msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`."
msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`."
msgid "On the pricelist form, under the :guilabel:`Price Rules` tab, click :guilabel:`Add a line` to add an advanced price rule. Doing so reveals a :guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule is configured."
msgid "If :guilabel:`Fixed Price` is selected, enter the desired price in the :guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, enter the desired discount percentage in the :guilabel:`Discount` field that appears."
msgid "To configure the :guilabel:`Formula` computation option, start by selecting an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the advanced price rule formula will be based on."
msgid "Next, in the :guilabel:`Discount` field, determine how much of a discount should be applied. It should be noted that a mark-up can be applied by setting a negative discount in this field."
msgid "To formulate a 100% markup (or 2 times the cost of the product), with a $5 minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the :guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is often seen in retail situations."
msgid "Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or subtract) to the amount calculated with the discount. After that, enter a desired figure in the :guilabel:`Rounding Method` field. The rounding method sets the price so that it is a multiple of the value in the field."
msgid "Once all formula-related configurations are complete, Odoo provides an example of the formula in a blue block to the right of the configurations."
msgid "To apply 20% discounts, with prices rounded up to 9.99, set the :guilabel:`Based on` field to :guilabel:`Sales Price`, the :guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to `-0.01`, and the :guilabel:`Rounding Method` field to `10`."
msgid "If any of those options, apart from :guilabel:`All Products`, are selected, a new option-specific field appears, in which the specific :guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product Variant` must be chosen."
msgid "Then, select a minimum quantity to be applied to the advanced pricelist rule in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for the pricelist item validation in the :guilabel:`Validity` field."
msgid "Once all configurations are complete, either click :guilabel:`Save & Close` to save the advanced pricelist rule, or click :guilabel:`Save & New` to immediately create another advanced pricelist rule on a fresh form."
msgid "Odoo *Sales* provides a template for importing products with categories and variants, which can be opened and edited with any spreadsheet software (Microsoft Excel, OpenOffice, Google Sheets, etc.)."
msgid "When this spreadsheet is filled out properly, it can be quickly uploaded to the Odoo database. When uploaded, those products are instantly added, accessible, and editable in the product catalog."
msgid "In order to import products with categories and variants, the *Import Template for Products* **must** be downloaded. Once downloaded, the template can be adjusted and customized, and then uploaded back into the Odoo database."
msgid "To download the necessary import template, navigate to :menuselection:`Sales app --> Products --> Products`. On the :guilabel:`Products` page, click the :guilabel:`⚙️ (gear)` icon in the upper-left corner. Doing so reveals a drop-down menu."
msgid "Selecting :guilabel:`Import records` reveals a separate page with a link to download the :guilabel:`Import Template for Products`. Click that link to download the template."
msgid "When the import template has been downloaded and opened, it's time to modify its contents. However, before any changes are made, there are a few elements to keep in mind during the process:"
msgid "Feel free to remove any columns that aren't deemed necessary. But, it is *strongly* advised that the :guilabel:`Internal Reference` column remains."
msgid "While it's not mandatory, having a unique identifier (e.g. `FURN_001`) in the :guilabel:`Internal Reference` column for each product can be helpful in many cases. This can even be from previous software spreadsheets to ease the transition into Odoo."
msgid "For example, when updating imported products, the same file can be imported several times without creating duplicates, thus enhancing the efficiency and simplicity of imported product management."
msgid "Do **not** change the labels of columns that are meant to be imported. Otherwise, Odoo won't recognize them, forcing the user to map them on the import screen manually."
msgid "Feel free to add new columns to the template spreadsheet, if desired. However, to be added, those fields **must** exist in Odoo. If Odoo can't match the column name with a field, it can be matched manually during the import process."
msgid "During the import process of the completed template, Odoo reveals a page showcasing all the elements of the newly-configured product template spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`."
msgid "To manually match a column name with a field in Odoo, click the :guilabel:`Odoo Field` drop-down menu next to the :guilabel:`File Column` that needs a manual adjustment, and select the appropriate field from that drop-down menu."
msgid "After customizing the product template spreadsheet, return to the Odoo product import page, where the template download link is found, and click the :guilabel:`Upload File` button in the upper-left corner."
msgid "After that, Odoo reveals a page showcasing all the elements of the newly-configured product template spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`."
msgid "To make sure everything is appropriate, and all the columns and fields are lined up accurately, click the :guilabel:`Test` button in the upper-left corner."
msgid "If everything is lined up and applied correctly, Odoo reveals a blue banner at the top of the page, informing the user that :guilabel:`Everything seems valid`."
msgid "If there are any errors, Odoo reveals a red banner at the top of the page, with instructions of where to locate the specific issues, and how to fix them."
msgid "If additional product template spreadsheets need to be uploaded, click the :guilabel:`Load File` button, select the desired product template spreadsheet, and repeat the process."
msgid "When clicked, Odoo instantly imports those products, and reveals the main :guilabel:`Products` page, with a pop-up message in the upper-right corner. This pop-up message informs the user how many products were successfully imported."
msgid "It's important to note that an Odoo object is always related to many other objects. For example, a product is linked to product categories, attributes, vendors, and things of this nature. These links/connections are known as relations."
msgid "On product forms in Odoo, there are a number of fields that can be modified and customized at any time. These fields are found under every tab on a product form. While these fields are easily editable directly on the product form, they can also be modified via a product import."
msgid "As mentioned, relation fields of this nature can **only** be imported for products if they already exist in the database. For example, if a user attempts to import a product with a *Product Type*, it can only be one of the preconfigured product types existing in the database (e.g. *Storable Product*, *Consumable*, etc.)."
msgid "To import information for a relation field on a product import template spreadsheet, add the name of the field as a column name/title on the spreadsheet. Then, on the appropriate product line, add the desired relation field option."
msgid "When all desired relation field information has been entered, save the spreadsheet, and import it to the database, per the process mentioned above (:menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> Import records --> Upload File`)."
msgid "Once the spreadsheet with the newly-configured relation field information has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Products` page."
msgid "When the newly-changed/modified products, complete with the new relation field information, has been imported and uploaded, that new information can be found on the :guilabel:`Products` page."
msgid "Odoo also allows users to import product attributes and values that can be used for products that already exist in the database, and/or with imported products."
msgid "To import attributes and values, a separate spreadsheet or CSV file dedicated to attributes and values **must** be imported and uploaded before they can be used for other products."
msgid "The column names/titles of the attributes and values spreadsheet should be as follows: :guilabel:`Attribute`, :guilabel:`Display Type`, :guilabel:`Variant Creation Mode`, and :guilabel:`Values / Value`."
msgid ":guilabel:`Values/Value`: values pertaining to the corresponding attribute. If there are multiple values for the same attribute, the values need to be in individual lines on the spreadsheet."
msgid "Once the desired attributes and values have been entered and saved in the spreadsheet, it's time to import and upload it into Odoo. To do that, navigate to :menuselection:`Sales app --> Configuration --> Attributes --> ⚙️ (gear) icon --> Import records --> Upload File`."
msgid "Once the spreadsheet with the newly-configured attributes and values has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Attributes` page. That's where those newly-added attributes and values can be found and edited, if necessary."
msgid "When product attributes and values are configured in the database, they can be used on product import spreadsheets to add more information and detail to products being imported."
msgid "To import products with product attributes and values, the product import template spreadsheet must be configured with specific :guilabel:`Product Attributes / Attribute`, :guilabel:`Product Attributes / Values`, and :guilabel:`Name` columns."
msgid "To import multiple values, separate them by *just* a comma, **not** a comma followed by a space, in the product import template spreadsheet (e.g. `furniture,couch,home`)."
msgid "When the desired products and product variants have been entered and saved in the spreadsheet, it's time to import and upload them into Odoo. To do that, navigate to :menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> Import records --> Upload File`."
msgid "Once the spreadsheet with the newly-configured products and product variants has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Products` page. That's where the newly-added products can be found."
msgid "To view and modify the attributes and variants on any products, select the desired product from the :guilabel:`Products` page, and click the :guilabel:`Attributes \\& Variants` tab."
msgid "Having appropriate product images in Odoo is useful for a number of reasons. However, if a lot of products need images, assigning them can become incredibly time-consuming."
msgid "Fortunately, by configuring the *Google Custom Search* API within an Odoo database, finding product images for products (based on their barcode) is extremely efficient."
msgid "Go to the `Google Cloud Platform API & Services <https://console.developers.google.com/>`_ page to generate Google Custom Search API credentials. Then, log in with a Google account. Next, agree to their :guilabel:`Terms of Service` by checking the box, and clicking :guilabel:`Agree and Continue`."
msgid "From here, select (or create) an API project to store the credentials. Start by giving it a memorable :guilabel:`Project Name`, select a :guilabel:`Location` (if any), then click :guilabel:`Create`."
msgid "With the :guilabel:`Credentials` option selected in the left sidebar, click :guilabel:`Create Credentials`, and select :guilabel:`API key` from the drop-down menu."
msgid "Doing so reveals an :guilabel:`API key created` pop-up window, containing a custom :guilabel:`API key`. Copy and save :guilabel:`Your API key` in the pop-up window -- it will be used later. Once the key is copied (and saved for later use), click :guilabel:`Close` to remove the pop-up window."
msgid "Next, go to `Google Programmable Search Engine <https://programmablesearchengine.google.com/>`_, and click either of the :guilabel:`Get started` buttons. Log in with a Google account, if not already logged in."
msgid "On the :guilabel:`Create a new search engine` form, fill out the name of the search engine, along with what the engine should search, and be sure to enable :guilabel:`Image Search` and :guilabel:`SafeSearch`."
msgid "From this page, click :guilabel:`Customize` to open the :menuselection:`Overview --> Basic` page. Then, copy the ID in the :guilabel:`Search engine ID` field. This ID is needed for the Odoo configuration."
msgid "In the Odoo database, go to the :menuselection:`Settings app` and scroll to the :guilabel:`Integrations` section. From here, check the box beside :guilabel:`Google Images`. Then, click :guilabel:`Save`."
msgid "Next, return to the :menuselection:`Settings app`, and scroll to the :guilabel:`Integrations` section. Then, enter the :guilabel:`API Key` and :guilabel:`Search Engine ID` in the fields beneath the :guilabel:`Google Images` feature."
msgid "Adding images to products in Odoo can be done on any product or product variant. This process can be completed in any Odoo application that provides access to product pages (e.g. *Sales* app, *Inventory* app, etc.)."
msgid "Below is a step-by-step guide detailing how to utilize the *Google Custom Search API* to assign images to products in Odoo using the Odoo *Sales* application:"
msgid "Navigate to the :guilabel:`Products` page in the *Sales* app (:menuselection:`Sales app --> Products --> Products`). Or, navigate to the :guilabel:`Product Variants` page in the *Sales* app (:menuselection:`Sales app --> Products --> Product Variants`)."
msgid "Click the :guilabel:`Action ⚙️ (gear)` icon on the product page, and select :guilabel:`Get Pictures from Google Images` from the menu that pops up."
msgid "The background job processes about 100 images in a minute. If the quota authorized by Google (either with a free or a paid plan) is reached, the background job puts itself on hold for 24 hours. Then, it will continue where it stopped the day before."
msgid "Product variants are used to give single products a variety of different characteristics and options for customers to choose from, such as size, style, or color, just to name a few."
msgid "Products variants can be managed via their individual product template, or by navigating to either the :guilabel:`Product Variants` or :guilabel:`Attributes` page. All of these options are located within the Odoo *Sales* application."
msgid "In this instance, there is a total of twenty different product variants: four **Color** options multiplied by five **Size** options. Each variant has its own inventory count, sales totals, and other similar records in Odoo."
msgid "To do that, go to :menuselection:`Sales app --> Configuration --> Settings`, and locate the :guilabel:`Product Catalog` section at the top of the page."
msgid "Before product variants can be set up, attributes **must** be created. To create, manage, and modify attributes, navigate to :menuselection:`Sales app --> Configuration --> Attributes`."
msgid "The order of attributes on the :guilabel:`Attributes` page dictates how they appear on the *Product Configurator*, *Point of Sale* dashboard, and *eCommerce* pages."
msgid "To create a new attribute from the :guilabel:`Attributes` page, click :guilabel:`New`. Doing so reveals a blank attributes form that can be customized and configured in a number of ways."
msgid "Next, select one of the options from the :guilabel:`Display Type` field. The :guilabel:`Display Type` determines how this product is shown on the online store, *Point of Sale* dashboard, and *Product Configurator*."
msgid "The :guilabel:`Variant Creation Mode` field **must** be set to :guilabel:`Never (option)` in order for the :guilabel:`Multi-checkbox (option)` to work properly as the :guilabel:`Display Type`."
msgid "The :guilabel:`eCommerce Filter Visibility` field determines whether or not these attribute options are visible to the customer on the front-end, as they shop on the online store."
msgid "Lastly, in the optional :guilabel:`eCommerce Category` field, select a category from a drop-down menu to group similar attributes under the same section for added specificity and organization."
msgid "To view the details related to the attribute category selected, click the internal link :icon:`fa-arrow-right` :guilabel:`(right arrow)` icon to the far-right of the :guilabel:`eCommerce Category` field, once an option has been selected. Doing so reveals that attribute category's detail form."
msgid "Here, the :guilabel:`Category Name` and :guilabel:`Sequence` is displayed at the top. Followed by :guilabel:`Related Attributes` associated with the category. These attributes can be dragged-and-dropped into a desirable order of priority."
msgid "To create an attribute category directly from this field, start typing the name of the new category, then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears."
msgid "Clicking :guilabel:`Create` creates the category, which can be modified later. Clicking :guilabel:`Create and edit...` creates the category and reveals a :guilabel:`Create Category` pop-up window, in which the new attribute category can be configured and customized."
msgid "Then, enter the name of the value in the :guilabel:`Value` column. Next, check the box in the :guilabel:`Is custom value` column, if the value is custom (i.e. the customer gets to provide unique specifications that are specific to this particular value)."
msgid "If the :guilabel:`Display Type` - :guilabel:`Color` option is selected, the option to add an HTML color code will appear to the far-right of the value line, to make it easier for salespeople and customers to know exactly what color option they're choosing."
msgid "In this pop-up window, select a specific color by dragging the color slider to a particular hue, and clicking on the color portion directly on the color gradient window."
msgid "Once an attribute is added to a product, that product is listed and accessible, via the attribute's :guilabel:`Related Products` smart button. That button lists every product in the database currently using that attribute."
msgid "Once an attribute is created, use the attribute (and its values) to create a product variant. To do that, go to :menuselection:`Sales app --> Products --> Products`, and select an existing product to view that desired product's form. Or, click :guilabel:`Create` to create a new product, to which a product variant can be added."
msgid "To add an attribute to a product, and subsequent attribute values, click :guilabel:`Add a line` in the :guilabel:`Attributes \\& Variants` tab. Then, choose the desired attribute from the drop-down menu that appears."
msgid "Attributes can be created directly from the :guilabel:`Attributes \\& Variants` tab of a product form. To do that, start typing the name of the new attribute in the blank field, and select either :guilabel:`Create` or :guilabel:`Create and edit...` from the mini drop-down menu that appears."
msgid "Clicking :guilabel:`Create` creates the attribute, which can be customized later. Clicking :guilabel:`Create and edit...` creates the attribute, and a :guilabel:`Create Attribute` pop-up form appears. In the pop-up form, proceed to modify the attribute in a number of ways."
msgid "Once an attribute is selected in the :guilabel:`Attribute` column, proceed to select the specific attribute values to apply to the product, via the drop-down menu available in the :guilabel:`Values` column."
msgid "To the far-right of the attribute line is a :guilabel:`Configure` button. When clicked, Odoo reveals a separate page showcasing those specific :guilabel:`Product Variant Values`."
msgid "On the specific product variant detail page, the :guilabel:`Value` and :guilabel:`Value Price Extra` fields can be found, along with an :guilabel:`Exclude for` field."
msgid "In the :guilabel:`Exclude for` field, different :guilabel:`Product Templates` and specific :guilabel:`Attribute Values` can be added. When added, this specific attribute value will be excluded from those specific products."
msgid "When a product has attributes and variants configured in its :guilabel:`Attributes \\& Variants` tab, a :guilabel:`Variants` smart button appears at the top of the product form. The :guilabel:`Variants` smart button indicates how many variants are currently configured for that specific product."
msgid "When the :guilabel:`Variants` smart button is clicked, Odoo reveals a separate page showcasing all the specific product variant combinations configured for that specific product."
msgid "In addition to offering more detailed product options to customers, product variants have their own impacts that can be taken advantage of throughout the Odoo database."
msgid ":guilabel:`Barcode`: barcodes are associated with each variant, instead of the product template. Each individual variant can have its own unique barcode/SKU."
msgid ":guilabel:`Price`: every product variant has its own public price, which is the sum of the product template price *and* any extra charges for particular attributes."
msgid "A red shirt's sales price is $23 -- because the shirt's template price is $20, plus an additional $3 for the red color variant. Pricelist rules can be configured to apply to the product template, or to the variant."
msgid ":guilabel:`Inventory`: inventory is counted for each individual product variant. On the product template form, the inventory reflects the sum of all variants, but the actual inventory is computed by individual variants."
msgid "To start a return before invoicing, navigate to the :menuselection:`Sales` app, select the desired sales order, and click on the :guilabel:`Delivery` smart button to open the associated delivery order."
msgid "By default, the :guilabel:`Quantity` matches the validated quantities from the delivery order. Update the quantities, if necessary. Click on the :guilabel:`🗑️ (trash)` icon next to a line item to remove it from the return."
msgid "Upon receiving the return, the warehouse team validates the warehouse operation by clicking :guilabel:`Validate`. Then, on the original sales order, the :guilabel:`Delivered` quantity updates to reflect the difference between the initial validated quantities and the returned quantities."
msgid "Sometimes, customers return an item after they receive and/or pay for their invoice. In these cases, a return using only *Reverse Transfers* is insufficient since validated, or sent, invoices cannot be changed."
msgid "If there is a payment registered on the sales order, the payment details appear in the chatter, and the invoice (accessible through the :guilabel:`Invoices` smart button) has a green :guilabel:`In Payment` banner."
msgid "From the sales order, click on the :guilabel:`Delivery` smart button to view the validated delivery order. Then, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window."
msgid "Next, edit the :guilabel:`Product` and/or :guilabel:`Quantity`, as needed for the return. Then, click :guilabel:`Return`. This generates a new warehouse operation for the incoming returned product(s), which is validated by the warehouse team once the return is received by clicking :guilabel:`Validate`."
msgid "Then, on the sales order, the :guilabel:`Delivered` quantity updates to reflect the difference between the initial validated quantities and the returned quantities."
msgid "To process a refund, navigate to the relevant invoice (from the sales order, click on the :guilabel:`Invoices` smart button). Then, click the :guilabel:`Credit Note` button at the top of the validated invoice."
msgid "Start by entering a :guilabel:`Reason displayed on Credit Note` and a specific :guilabel:`Journal` to process the credit. Then, select a specific :guilabel:`Reversal Date`."
msgid "When complete, a blue banner reading: :guilabel:`You have outstanding credits for this customer. You can allocate them to mark this invoice as paid.` appears at the top of the page."
msgid "In Odoo **Sales**, quotations can be created and sent to customers. Once a quotation has been confirmed, it officially turns into a *sales order*, which can then be invoiced and paid for."
msgid "To access these setting options, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and scroll to the :guilabel:`Quotations & Orders` section."
msgid ":guilabel:`Quotation Templates`: Enable this option to create quotation templates featuring standard product offers, which are then selectable on quotation forms. When this checkbox is ticked, an additional field, :guilabel:`Default Template`, appears, along with a link to the :guilabel:`Quotation Templates` page."
msgid ":guilabel:`Online Payment`: Request an online prepayment from customers to confirm orders. Request a full or partial payment (via down payment). When this checkbox is ticked, an additional field, :guilabel:`Prepayment amount (%)`, appears. There is also a link to the :guilabel:`Payment Providers` page."
msgid "By default, the :guilabel:`Quotations` dashboard displays all quotations in the database related to the current user, as indicated by the default :guilabel:`My Quotations` filter present in the search bar."
msgid "Quotations on this page appear in a default list view, but can also be viewed in a :icon:`oi-view-kanban` :guilabel:`Kanban` view, :icon:`fa-calendar` :guilabel:`Calendar`, :icon:`oi-view-pivot` :guilabel:`Pivot` table, :icon:`fa-area-chart` :guilabel:`Graph`, or :icon:`fa-clock-o` :guilabel:`Activity` view."
msgid "To view and/or modify any listed quotation from the :guilabel:`Quotations` dashboard, click on the desired quotation line from the list, and Odoo reveals the specific form for that selected quotation."
msgid "To create a quotation, open the :menuselection:`Sales app`, and click the :guilabel:`New` button, located in the upper-left corner of the main :guilabel:`Quotations` dashboard."
msgid "If the customer's information is already in the database, the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields auto-populate with the saved information for those respective fields, based on the data from that customer's contact record (found in the **Contacts** application)."
msgid "If a :guilabel:`Referrer` is selected, a new field, :guilabel:`Commission Plan` appears, in which a commission can be selected from the drop-down menu. This commission is rewarded to the contact selected in the :guilabel:`Referrer` field."
msgid "Next, if they have not already been auto-populated with the customer's information, enter the appropriate addresses in the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields. Both of these fields are **required**."
msgid "Then, if desired, choose a :guilabel:`Quotation Template` from the drop-down field to apply to this quotation. It should be noted that some additional fields may appear, depending on the template selected."
msgid "The default date that appears in the :guilabel:`Expiration` field is based on the number configured in the :ref:`Default Quotation Validity setting <sales/quotation-settings>` (in :menuselection:`Sales app --> Configuration --> Settings`)."
msgid "When using a quotation template, the date in the :guilabel:`Expiration` field is based off the :guilabel:`Quotation Validity` figure on the template form."
msgid "Click :guilabel:`Add a product`, select the desired item from the :guilabel:`Product` drop-down field, and proceed to adjust the quantity of that selected product, if necessary."
msgid "Or, click :guilabel:`Catalog` to reveal a separate page, showcasing every item (and every potential product variant) in an organized catalog display, with items organizable by :guilabel:`Product Category` and :guilabel:`Attributes`."
msgid "From here, simply locate the desired items, click the :icon:`fa-shopping-cart` :guilabel:`Add` button on the product card, and adjust the quantity, if needed. When complete, click the :guilabel:`Back to Quotation` button in the upper-left corner to return to the quotation, where the newly-selected catalog items can be found in the :guilabel:`Order Lines` tab."
msgid "If multiple items should be presented in a more organized way on the quotation, click :guilabel:`Add a section`, enter a name for the section, and drag-and-drop that section heading in the desired location amongst the items in the :guilabel:`Order Lines` tab. The section heading appears in bold."
msgid "If needed, click :guilabel:`Add a note` beneath a certain product line to add a custom note about that specific product. The note appears in italics. Then, if needed, proceed to drag-and-drop the note beneath the desired product line."
msgid "Beneath the product lines, there are buttons that can be clicked to apply any of the following: :guilabel:`Coupon Code`, :guilabel:`Promotions`, :guilabel:`Discount`, and/or :guilabel:`Add shipping`."
msgid "Open the :guilabel:`Optional Products` tab to select related products that can be presented to the customer, which may result in an increased sale."
msgid "In the :guilabel:`Other Info` tab, there are various quotation-related configurations separated into four different sections: :guilabel:`Sales`, :guilabel:`Delivery`, :guilabel:`Invoicing`, and :guilabel:`Tracking`."
msgid ":guilabel:`Salesperson`: Assign a salesperson from the drop-down menu to be associated with this quotation. The user who originally created the quotation is selected in this field, by default."
msgid ":guilabel:`Sales Team`: Assign a specific sales team to this quotation. If the selected :guilabel:`Salesperson` is a member of a sales team, that team is auto-populated in the field."
msgid ":guilabel:`Company`: Select a company from the drop-down menu this quotation should be associated with. This field only appears when working in a multi-company environment."
msgid ":guilabel:`Online signature`: Tick this checkbox to request an online signature from the customer to confirm the order. This field only appears if the *Online Signature* setting has been enabled."
msgid ":guilabel:`Online payment`: Tick this checkbox, and enter a desired percentage in the adjacent field, to request an online payment from the customer (for that designated percentage of the total amount) to confirm the order. This field only appears if the *Online Payment* setting has been enabled."
msgid ":guilabel:`Customer Reference`: Enter a custom reference ID for this customer. The entered reference ID can contain letters, numbers, or a mix of both."
msgid ":guilabel:`Tags`: Add specific tags to the quotation for added organization and enhanced searchability in the Odoo **Sales** application. Multiple tags can be added, if necessary."
msgid ":guilabel:`Shipping Weight`: Displays the weight of the items being shipped. This field is not modifiable. Product weight is configured on individual product forms."
msgid ":guilabel:`Shipping Policy`: Select a desired shipping policy from the drop-down menu. If all products are delivered at once, the delivery order is scheduled, based on the greatest product lead time. Otherwise, it is based on the shortest lead time. The available options are: :guilabel:`As soon as possible` or :guilabel:`When all products are ready`."
msgid ":guilabel:`Delivery Date`: Click into the empty field to reveal a calendar popover, from which a customer delivery date can be selected. If no custom date is required, refer to the :guilabel:`Expected` date listed to the right of that field."
msgid ":guilabel:`Fiscal Position`: Select a fiscal position to be used to adapt taxes and accounts for particular customers or sales orders/invoices. The default value comes from the customer. If a selection is made in this field, an :icon:`fa-refresh` :guilabel:`Update Taxes` clickable link and icon appear. When clicked, the taxes for this partiuclar customer and quotation are updated. A confirmation window appears, as well."
msgid "Once all the necessary fields and tabs have been configured, it is time to send the quotation to the customer for confirmation. Upon confirmation, the quotation turns into an official sales order."
msgid ":guilabel:`Send by Email`: When clicked, a pop-up window appears with the customer's name and email address in the :guilabel:`Recipients` field, the quotation (and reference ID) in the :guilabel:`Subject` field, and a brief default message in the body of the email, which can be modified, if needed."
msgid "Below that, a PDF copy of the quotation is attached. When ready, click :guilabel:`Send` to send the quotation, via email, to the customer, so they can review and confirm it."
msgid ":guilabel:`Send PRO-FORMA Invoice`: This button **only** appears if the *Pro-Forma Invoice* setting has been enabled. When clicked, a pop-up window appears with the customer's name and email address in the :guilabel:`Recipients` field, the *Proforma* invoice (and reference ID) in the :guilabel:`Subject` field, and a brief default message in the body of the email, which can be modified, if needed."
msgid ":guilabel:`Preview`: When clicked, Odoo reveals a preview of the quotation the customer sees when they log into their customer portal. Click the :icon:`fa-arrow-right` :guilabel:`Back to edit mode` link at the top of the preview page, in the blue banner, to return to the quotation form."
msgid "If the *Lock Confirmed Sales* setting is enabled, the sales order becomes :guilabel:`Locked`, and is indicated as such on the sales order form."
msgid "In the Odoo *Sales* application, it is possible to set deadlines on sales quotations. Doing so encourages customers to act quickly during sales negotiations, for they might fear for missing out on a good deal. As well, deadlines also can also act as protection for a company in case an order has to be fulfilled at a price that is no longer profitable for the business."
msgid "To add an expiration date to a quotation, navigate to :menuselection:`Sales app`, and select a desired quotation, or create a new one by clicking :guilabel:`New`."
msgid "On the quotation form, click the :guilabel:`Expiration` field to reveal a pop-up calendar. From this pop-up calendar, select the desired month and date as the expiration date for the quotation."
msgid "To add a deadline expiration date to a quotation template, navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates`, and either select the desired quotation template to which a deadline should be added, or click :guilabel:`New` to build a new quotation template from scratch."
msgid "On the quotation template form, add a specific number of days to the :guilabel:`Quotation expires after` field, located beneath the quotation template name. The number of days represents how long the quotation will be valid for, before it expires."
msgid "Then, whenever that specific quotation template is used in a quote, an expiration date is automatically calculated, based on the number of days designated above. However, this date can be overwritten before sending the quotation to the customer."
msgid "People and businesses often use separate addresses for billing (invoicing) and shipping (delivery) purposes. With the Odoo *Sales* app, contacts can have different specified addresses for delivery and invoicing."
msgid "To properly utilize multiple addresses in Odoo, go to :menuselection:`Accounting app --> Configuration --> Settings`, and scroll down to the :guilabel:`Customer Invoices` heading. Then, tick the checkbox."
msgid "To add multiple addresses to a contact, go to :menuselection:`Sales app --> Orders --> Customers`, and clear any default filters from the search bar. Then, click on the desired customer to open their contact form."
msgid "From the contact form, click :guilabel:`Edit`, and then select :guilabel:`Add`, which is located under the :guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create Contact` pop-up form, in which additional addresses can be configured."
msgid "On the :guilabel:`Create Contact` pop-up form, start by clicking the default :guilabel:`Other Address` field to reveal a drop-down menu of address-related options."
msgid "Then, click :guilabel:`Save & Close` to save the address and close the :guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save the address and immediately input another one."
msgid "When a customer is added to a quotation, the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields autopopulate with the corresponding addresses specified on the customer's contact form."
msgid "The :guilabel:`Invoice Address` and :guilabel:`Delivery Address` can also be edited directly from the quotation by clicking the :guilabel:`Edit` button, and then clicking the :guilabel:`➡️ (right arrow)` internal link buttons next to each address line."
msgid "The Odoo *Sales* application provides customers with the ability to confirm orders, via an online payment, directly on a sales order. Once the sales order is electronically paid for by the customer, the salesperson attached to the sales order is instantly notified that the order is confirmed."
msgid "To activate the *Online Payment* feature, go to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& Orders` heading, check the box next to the :guilabel:`Online Payment` feature, and click :guilabel:`Save`."
msgid "Beneath the :guilabel:`Online Payment` option on the *Sales* :guilabel:`Settings` page, there's a :guilabel:`Default Quotation Validity` field. In this field, there's the option to add a specific number of days for quotations to remain valid by default."
msgid "To enable this feature on a standard quotation, click the checkbox for the :guilabel:`Payment` feature option, located in the :guilabel:`Online confirmation` field, on the :guilabel:`Other Info` tab."
msgid "To enable this feature on a quotation template, click the checkbox for the :guilabel:`Payment` feature option, located in the :guilabel:`Online confirmation` field of the quotation template form."
msgid "Clicking that link reveals a separate :guilabel:`Payment Providers` page, in which a large variety of payment providers can be enabled, customized, and published."
msgid "After opening quotations in their customer portal, customers can click :guilabel:`Accept \\& Pay` to confirm their order with an online payment."
msgid "After clicking :guilabel:`Accept \\& Pay`, customers are presented with :guilabel:`Validate Order` pop-up window containing different options for them to make online payments, in the :guilabel:`Pay with` section."
msgid "Odoo will **only** offer payment options on the :guilabel:`Validate Order` pop-up window that have been published and configured on the :guilabel:`Payment Providers` page."
msgid "Once the customer selects their desired method of payment, they will click the :guilabel:`Pay` button on the pop-up window to confirm the order. Odoo instantly notifies the assigned salesperson upon order confirmation with an online payment."
msgid "The Odoo *Sales* application provides customers with the ability to confirm orders, via an online signature, directly on the sales order. Once the sales order is electronically signed by the customer, the salesperson attached to the sales order is instantly notified that the order is confirmed."
msgid "To activate the *Online Signature* feature, go to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& Orders` heading, and activate the :guilabel:`Online Signature` feature by checking the box beside it."
msgid "When making a quotation template, the online signature feature is the :guilabel:`Signature` option, located in the :guilabel:`Online confirmation` field of the quotation template form."
msgid "On standard quotations, the online signature feature is the :guilabel:`Signature` option, located under the :guilabel:`Other Info` tab of the quotation form."
msgid "When clicked, a :guilabel:`Validate Order` pop-up window appears. In this pop-up window, the :guilabel:`Full Name` field is auto-populated, based on the contact information in the database."
msgid "Then, customers have the option to enter an online signature with any of the following options: :guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`."
msgid ":guilabel:`Auto` lets Odoo automatically generate an online signature based on the information in the :guilabel:`Full Name` field. :guilabel:`Draw` lets the customer use the cursor to create a custom signature directly on the pop-up window. And :guilabel:`Load` lets the customer upload a previously-created signature file from their computer."
msgid "After the customer has chosen any of the three previously mentioned signature options (:guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`), they will click the :guilabel:`Accept \\& Sign` button."
msgid "When :guilabel:`Accept \\& Sign` is clicked, the various payment method options become available for them to choose from (if the *online payment* option applies to this quotation)."
msgid "The use of optional products is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale."
msgid "For instance, if a customer wants to buy a car, they have the choice to order massaging seats, as well, or ignore the offer and simply buy the car. Presenting the choice to purchase optional products enhances the customer experience."
msgid "With the Odoo *Sales* application, it is possible to add or modify optional products directly on quotations by navigating to the :guilabel:`Optional Products` tab on a quotation form."
msgid "To add an optional product(s) to a quotation, click :guilabel:`Add a product` in the :guilabel:`Optional Products` tab of a quotation. Doing so reveals a blank field in the :guilabel:`Product` column."
msgid "When clicked, a drop-down menu with products from the database appear. Select the desired product from the drop-down menu to add it as an optional product to the quotation template."
msgid "If the desired product isn't readily visible, type the name of the desired product in the field, and the option appears in the drop-down menu. Then, select that desired product to add it to the quotation."
msgid "Click the :guilabel:`Preview` button, located in the upper-left corner of the quotation, to reveal a preview of the quotation customers would receive, via email, along with the optional products they can potentially add to their order, located in the :guilabel:`Options` section."
msgid "Customers are able to add different optional products to an order by clicking the :guilabel:`🛒 (shopping cart)` icon, located to the right of the optional product line."
msgid "When the customer adds an optional product(s) to an order, the salesperson is instantly notified about the change, along with any other change the customer makes to an order. This allows salespeople to stay up-to-date with everything related to an order in the backend of the *Sales* application."
msgid "Be sure to review the :doc:`quote_template` documentation to better understand how quotation templates work before reading the following information."
msgid "For quotation templates, just like a typical quotation form, there is also an :guilabel:`Optional Products` tab, wherein related products or services can be added to a quotation template."
msgid "To add optional products to a quotation template, navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates`. Then, either select an existing quotation template to edit, or create a new one by clicking :guilabel:`New`."
msgid "On the quotation template form, click the :guilabel:`Optional Products` tab. Under the :guilabel:`Optional Products` tab, click :guilabel:`Add a line`, and select the desired product to add as an optional product to the quotation template."
msgid "The products added in the :guilabel:`Optional Products` tab are present in the quotation, by default, whenever that particular quotation template is used. These products can be removed, and additional products can be added, before the quotation is sent to a customer."
msgid "It's best to offer optional products that would encourage a customer to add additional items to their order, or entice them to purchase a more expensive version of their initially selected product."
msgid "For example, if a customer purchases a wooden chair, some optional products could be: a warranty on that chair and/or a wooden chair with leather seats."
msgid "Before getting into detail about how to use product variants on quotations and sales orders, it's recommended to learn about :doc:`../products_prices/products/variants` in Odoo."
msgid "Once familiarized with the basics surrounding product variants, the following covers how product variants can be added to quotations and sales orders using the *product configurator* or *order grid entry*."
msgid "It should be noted that the setting is titled, *Variant Grid Entry* on the *Sales* app settings page, and titled, *Order Grid Entry* on product forms. So, be sure to keep that in mind."
msgid "When working with product variants, Odoo uses the product configurator, by default. To add the variant grid entry option, that feature **must** be enabled in the Odoo *Sales* application. The variant grid entry option provides a pop-up window on the quotation/sales order to simplify the variant selection process."
msgid "To enable that setting, go to :menuselection:`Sales app --> Configuration --> Settings`, and scroll to the :guilabel:`Product Catalog` section. Then, check the box next to the :guilabel:`Variant Grid Entry` option, and click :guilabel:`Save`."
msgid "Once the :guilabel:`Variant Grid Entry` setting is enabled, both options (*Product Configurator* and *Order Grid Entry*) become available on every product form."
msgid "To configure a product form to use either a product configurator or variant grid entry, start by navigating to :menuselection:`Sales app --> Products --> Products` to view all the products in the database."
msgid "Then, select the desired product to configure, or click :guilabel:`New`, to create a new product from scratch. Once on the product form, click into the :guilabel:`Attributes \\& Variants` tab, where product variants can be viewed, modified, and added."
msgid "At the bottom of the :guilabel:`Attributes \\& Variants` tab, there is a :guilabel:`Sales Variant Selection` section with two options: :guilabel:`Product Configurator` and :guilabel:`Order Grid Entry`."
msgid "The :guilabel:`Product Configurator` provides a pop-up window that neatly displays all the available product variants for that particular product when it's added to a quotation. However, only one variant can be selected/added at a time."
msgid "The :guilabel:`Order Grid Entry` provides the same information as the :guilabel:`Product Configurator` in a table layout, allowing the user to select larger numbers of unique product variants, and add them to a quotation/sales order, in a single view."
msgid "The product configurator feature appears as a :guilabel:`Configure` pop-up window, as soon as a product with (at least two) variants is added to a quotation or sales order, but **only** if the :guilabel:`Product Configurator` option is selected on its product form."
msgid "This :guilabel:`Configure` pop-up window also appears if the :guilabel:`Order Grid Entry` setting is **not** activated, as it is the default option Odoo uses when dealing with product variants on quotations and/or sales orders."
msgid "The :guilabel:`Product Configurator` option lets salespeople choose exactly which product variant to add to the quotation or sales order using a format similar to online shopping."
msgid "The order grid entry feature appears as a :guilabel:`Choose Product Variants` pop-up window, as soon as a product with (at least two) variants is added to a quotation or sales order, but **only** if the :guilabel:`Order Grid Entry` option is selected on its product form."
msgid "The :guilabel:`Choose Product Variants` pop-up window features all the variant options for that particular product. From this pop-up window, the salesperson can designate how many of each variant they'd like to add to the quotation/sales order at once."
msgid "When all the desired quantities and variants have been selected, the salesperson simply clicks :guilabel:`Confirm`, and those orders are instantly added to the quotation/sales order in the :guilabel:`Order Lines` tab."
msgid "The *PDF Quote Builder* in Odoo *Sales* provides the opportunity to send customers a fully customized PDF file for quotes, showcasing the company and products, with various information and design elements, instead of just showing the price and total."
msgid "The PDF Quote Builder groups header pages, product descriptions, the price(s), and footer pages to create a detailed quote. It can also inject dynamic texts in the PDF to personalize the offer for the customer."
msgid "Having a customized PDF in quotes provides a heightened conclusion to the shopping experience for customers, and adds an elegant level of professionalism to a company."
msgid "It is recommended to edit PDF forms with Adobe software. The form fields on the header and footer PDF templates are necessary to get dynamic values with Odoo."
msgid "To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`. Then, on the :guilabel:`Settings` page, scroll to the :guilabel:`Quotations & Orders` section, and locate the :guilabel:`PDF Quote builder` feature."
msgid "Here, custom :guilabel:`Header pages` and :guilabel:`Footer pages` can be uploaded. To upload either, click the :guilabel:`Upload your file` button, or the :guilabel:`✏️ (pencil)` icon to the right of the desired field, and proceed to locate, select, and upload the desired PDF file."
msgid "Clicking the :guilabel:`🗑️ (trash)` icon deletes the current PDF file and replaces the blank field with an :guilabel:`Upload your file` button."
msgid "Once the desired PDF file(s) are uploaded in the appropriate fields in the :guilabel:`PDF Quote builder` section of the *Sales* :guilabel:`Settings` page, be sure to click :guilabel:`Save`."
msgid "While creating custom PDFs for quotes, use *dynamic text* for Odoo to auto-fill the PDF content with information related to the quote from the Odoo database, like names, prices, etc."
msgid "Dynamic text values are form components (text inputs) that can be added in a PDF file, and Odoo automatically fills those values in with information related to the quote."
msgid "Double underscore notation for :guilabel:`partner_id__name` and :guilabel:`user_id__name` values are used in place of the typically used `.` symbol because the library currently does not support the `.` symbol."
msgid "When a PDF is built, it's best practice to use common dynamic text values (:guilabel:`name` and :guilabel:`partner_id_name`). When uploaded into the database, Odoo auto-populates those fields with the information from their respective fields."
msgid "In this case, Odoo would auto-populate the Sales Order Reference in the :guilabel:`name` dynamic text field, and the Customer Name in the :guilabel:`partner_id_name` field."
msgid "Once the PDF file(s) are complete, save them to the computer's hard drive, and proceed to upload them to Odoo via :menuselection:`Sales app --> Configuration --> Settings --> PDF Quote builder`."
msgid "In Odoo *Sales*, it's also possible to add a custom PDF to a product form. When a PDF is added to a product, and that product is used in a quotation, that PDF is also inserted in the final PDF."
msgid "To add a custom PDF to a product, start by navigating to :menuselection:`Sales app --> Products --> Products`, and select the desired product to which a custom PDF should be added."
msgid "A document could also be added to a product variant, instead of a product. If there are documents on a product *and* on its variant, **only** the documents in the variant are shown."
msgid "To add a custom document to a product variant, navigate to :menuselection:`Sales app --> Products --> Product Variants`. Select the desired variant, click the :guilabel:`Documents` smart button, and proceed to upload the custom document(s) to the specific product variant."
msgid "Doing so reveals a separate :guilabel:`Documents` page for that product, wherein files related to that product can be uploaded. From this page, either click :guilabel:`New` or :guilabel:`Upload`."
msgid "Clicking :guilabel:`Upload` instantly provides the opportunity to upload the desired document. Then, the document can be further configured on the document card, or by clicking the three dots icon in the top right corner of the document card, and then clicking :guilabel:`Edit`."
msgid "Clicking :guilabel:`New` reveals a blank documents form, in which the desired PDF can be uploaded via the :guilabel:`Upload your file` button on the form, located in the :guilabel:`File Content` field."
msgid "The first field on the documents form is for the :guilabel:`Name` of the document, and it is grayed-out (not clickable) until a document is uploaded. Once a PDF has been uploaded, the :guilabel:`Name` field is auto-populated with the name of the PDF, and it can then be edited."
msgid "Prior to uploading a document, there's the option to designate whether the document is a :guilabel:`File` or :guilabel:`URL` from the :guilabel:`Type` drop-down field menu."
msgid "Then, in the :guilabel:`Sales` section, in the :guilabel:`Visible at` field, click the drop-down menu, and select either: :guilabel:`Quotation`, :guilabel:`Confirmed order`, or :guilabel:`Inside quote`."
msgid ":guilabel:`Confirmed order`: the document is sent to customers upon the confirmation of an order. This is best for user manuals and other supplemental documents."
msgid ":guilabel:`Inside quote`: the document is included in the PDF of the quotation, between the header pages and the :guilabel:`Pricing` section of the quote."
msgid "When the :guilabel:`Inside quote` option for the :guilabel:`Visible at` field is chosen, and the custom PDF file, `Sample Builder.pdf` is uploaded, the PDF is visible on the quotation the in the *customer portal* under the :guilabel:`Documents` field."
msgid "Lastly, in the :guilabel:`E-Commerce` section, decide whether or not to :guilabel:`Show on product page` on the front-end (in the online store)."
msgid "When the :guilabel:`Show on product page` option is enabled, a link to the uploaded document, `Sample Builder.pdf`, appears on the product's page, located on the frontend in the online store."
msgid "Once a quote with a pre-configured PDF has been confirmed, Odoo provides the option to print the confirmed quote to check for errors, or to keep for records."
msgid "To print the PDF quote, navigate to the confirmed quote, and click the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu. From this drop-down menu, select :guilabel:`Print`, then select :guilabel:`PDF Quote`."
msgid "Doing so instantly downloads the PDF quote. When opened, the PDF quote, along with the configured product PDF that was set to be visible inside the quote, can be viewed and printed."
msgid "By using these templates, quotations can be tailored and sent to customers at a much faster pace, without having to create new quotations from scratch every time a sales negotiation occurs."
msgid "Begin by activating the setting in :menuselection:`Sales app --> Configuration --> Settings`, and scroll to the :guilabel:`Quotations \\& Orders` heading."
msgid "In that section, check the box beside the :guilabel:`Quotation Templates` option. Doing so reveals a new :guilabel:`Default Template` field, in which a default quotation template can be chosen from a drop-down menu."
msgid "Also, upon activating the :guilabel:`Quotation Template` feature, an internal :guilabel:`➡️ Quotation Templates` link appears beneath the :guilabel:`Default Template` field."
msgid "Click the :guilabel:`Quotation Templates` link on the :guilabel:`Settings` page, or navigate to :menuselection:`Sales app --> Configuration --> Quotation Templates`. Both options reveal the :guilabel:`Quotation Templates` page, where quotation templates can be created, viewed, and edited."
msgid "To create a new quotation template, click the :guilabel:`New` button, located in the upper-left corner. Doing so reveals a blank quotation template form that can be customized in a number of ways."
msgid "Then, in the :guilabel:`Quotation Validity` field, designate how many days the quotation template will remain valid for, or leave the field on the default `0` to keep the template valid indefinitely."
msgid "Next, in the :guilabel:`Confirmation Mail` field, click the blank field to reveal a drop-down menu. From the drop-down menu, select a pre-configured email template to be sent to customers upon confirmation of an order."
msgid "To create a new email template directly from the :guilabel:`Confirmation Mail` field, start typing the name of the new email template in the field, and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears."
msgid "Selecting :guilabel:`Create and edit...` creates the email template, and a :guilabel:`Create Confirmation Mail` pop-up window appears, in which the email template can be customized and configured right away."
msgid "If a journal is set in the :guilabel:`Invoicing Journal` field, all sales orders with this template will invoice in that specified journal. If no journal is set in this field, the sales journal with the lowest sequence is used."
msgid "If the :guilabel:`Online Signature` and/or :guilabel:`Online Payment` features are activated in the :guilabel:`Settings` (:menuselection:`Sales app --> Configuration --> Settings`), those options are available on quotation template forms."
msgid "Check the box beside :guilabel:`Online Payment` to request an online payment from the customer to confirm an order. When :guilabel:`Online Payment` is checked, a new percentage field appears, in which a specific percentage of payment can be entered."
msgid "Both options, :guilabel:`Online Signature` and :guilabel:`Online Payment` can be enabled simultaneously, in which case the customer must provide **both** a signature **and** a payment to confirm an order."
msgid "In the :guilabel:`Recurring Plan` field, choose from a variety of pre-configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`, etc.) to designate how often this quotation template should occur."
msgid "The :guilabel:`Recurring Plan` field **only** applies to subscription plans. For more information, check out the documentation on :doc:`../../subscriptions/plans`."
msgid "In the :guilabel:`Lines` tab, products can be added to the quotation template by clicking :guilabel:`Add a product`, organized by clicking :guilabel:`Add a section` (and dragging/dropping section headers), and further explained with discretionary information (such as warranty details, terms, etc.) by clicking :guilabel:`Add a note`."
msgid "To add a product to a quotation template, click :guilabel:`Add a product` in the :guilabel:`Lines` tab of a quotation template form. Doing so reveals a blank field in the :guilabel:`Product` column."
msgid "When clicked, a drop-down menu with existing products in the database appear. Select the desired product from the drop-down menu to add it to the quotation template."
msgid "If the desired product isn't readily visible, type the name of the desired product in the :guilabel:`Product` field, and the option appears in the drop-down menu. Products can also be found by clicking :guilabel:`Search More...` from the drop-down menu."
msgid "In Odoo 17, it is now possible to add event-related products (booths and registrations) to quotation templates. To do so, click the :guilabel:`Product` field, type in `Event`, and select the desired event-related product from the resulting drop-down menu."
msgid "To add a *section*, which serves as a header to organize the lines of a sales order, click :guilabel:`Add a section` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired name of the section can be typed. When the name has been entered, click away to secure the section name."
msgid "To add a note, which would appear as a piece of text for the customer on the quotation, click :guilabel:`Add a note` in the :guilabel:`Lines` tab. When clicked, a blank field appears, in which the desired note can be typed. When the note has been entered, click away to secure the note."
msgid "To delete any line item from the :guilabel:`Lines` tab (product, section, and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right side of the line."
msgid "The use of *optional products* is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale."
msgid "Optional products appear as a section on the bottom of sales orders and eCommerce pages. Customers can immediately add them to their online sales orders themselves, if desired."
msgid "In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each cross-selling product related to the original items in the :guilabel:`Lines` tab, if applicable. The products added here ideally complement the original offering as added value for the prospective buyer."
msgid "The :guilabel:`Terms \\& Conditions` tab provides the opportunity to add terms and conditions to the quotation template. To add terms and conditions, simply type (or copy/paste) the desired terms and conditions in this tab."
msgid "The :guilabel:`PDF Quote Builder` tab provides options to compose an attractive quotation, with more information and visually-pleasing elements, to highlight products and/or services."
msgid "To upload customer :guilabel:`Header pages` and :guilabel:`Footer pages`, click the :guilabel:`✏️ (pencil)` icon to the right of the respective pages. Click the :guilabel:`🗑️ (trash)` icon to delete an uploaded PDF."
msgid "To view what the customer will see, click the :guilabel:`Preview` button at the top of the page to see how the quotation template appears on the front-end of the website through Odoo's customer portal."
msgid "Quotation template design uses the same methodology and functionality with design building blocks as a typical web page design with Odoo *Website*. Be sure to check out the :doc:`../../../websites/website` documentation to learn more."
msgid "There is also a blue banner at the top of the quotation template design with a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo returns to the quotation form in the back-end of the *Sales* application."
msgid "Cancel multiple quotations (or sales orders) by navigating to the :menuselection:`Sales app --> Orders --> Quotations` dashboard, landing, by default, in the list view. Then, on the left side of the table, tick the preferred checkboxes for removal."
msgid "Select all records in the table by selecting the checkbox column header at the top-left of the table; the total number of selected items are displayed at the top of the page."
msgid "Then, with the desired quotations (or sales orders) selected from the list view on the :guilabel:`Quotations` page, click the :icon:`fa-cog` :guilabel:`Actions` button to reveal a drop-down menu."
msgid "Upon selecting the :guilabel:`Cancel quotations` option, a :guilabel:`Cancel quotations` confirmation pop-up window appears. To complete the cancellation, click the :guilabel:`Cancel quotations` button."
msgid "Odoo *Subscriptions* is used to run recurring businesses: :ref:`sell new contracts <subscriptions/quotations>`, :doc:`upsell customers </applications/sales/subscriptions/upselling>`, keep the churn under control, and :doc:`generate reports </applications/sales/subscriptions/reports>` on the main :abbr:`KPIs (Key Performance Indicators)`: :abbr:`MRR (Monthly Recurring Revenue)`, :abbr:`ARR (Annual Recurring Revenue)`, retention, churn, etc."
msgid "Fill out the quotation normally, making sure to select a recurrence and an end date if necessary and adding :doc:`recurrent products </applications/sales/subscriptions/products>`."
msgid "You can define different invoice and delivery addresses by enabling the :doc:`Customer Addresses </applications/finance/accounting/customer_invoices/customer_addresses>` feature."
msgid "Send the quotation to the customer for confirmation by clicking on :guilabel:`Send by email`, or confirm it immediately by clicking on :guilabel:`Confirm`."
msgid "Click on :guilabel:`Customer Preview` to preview the customer portal where the customer can view their quotation, sign and pay it, and communicate with you."
msgid "You can require the customer to set an automatic payment method and pre-pay the subscription's first occurrence before they can confirm their quotation. To do so, go to the :guilabel:`Other Info` tab of the quotation and check the :guilabel:`Payment` option in the :guilabel:`Online confirmation` field."
msgid "If you leave :guilabel:`Payment` unchecked, the customer doesn't have to pre-pay to start the subscription. This means that the payment is not automatic and that the customer must pay each invoice manually."
msgid "If the online confirmation requires a pre-payment, your customer can select only the :ref:`payment providers <payment_providers/supported_providers>` that have the :ref:`tokenization feature <payment_providers/tokenization>`. This ensures that the customer is automatically charged at each new period."
msgid "With subscriptions up-and-running, it is important to stay up-to-date with customers. It is efficient to use automation to avoid having to manually go through the list of subscribers to see how things are going. That is where Odoo's *automation rules* feature comes into play."
msgid "The Odoo *Subscriptions* application allows users to set up automatic emails, create tasks for salespeople, and even send satisfaction surveys for subscribers to evaluate their experience."
msgid "To create an automated rule, start by navigating to :menuselection:`Subscriptions app --> Configuration --> Automation Rules`. This is where all the automation rules for subscriptions can be found."
msgid "The :guilabel:`Automation Rules` page shows each rule's :guilabel:`Name`, :guilabel:`Action To Do`, what the automated rule will :guilabel:`Trigger On`, and the :guilabel:`Company` to which the rule applies."
msgid "When modifying an existing automation rule, Odoo \"grays-out\" the :guilabel:`Action` section of the form, and provides the following warning: *Action data can not be updated to avoid unexpected behaviors. Create a new action instead.*"
msgid ":guilabel:`Status`: select the status of the subscriptions to be included in this automation rule. The options are: :guilabel:`Quotation`, :guilabel:`Quotation Sent`, :guilabel:`Sales Order`, and :guilabel:`Cancelled`."
msgid ":guilabel:`Stage goes from`: designate when the automation rule should be activated using two fields that represent two different stages of the subscription."
msgid "The number of subscriptions that match the configured criteria of the customized automation rule are displayed at the bottom of the :guilabel:`Apply On` field."
msgid "If that green subscriptions link is clicked, Odoo reveals a separate page showcasing all the subscriptions that meet that automation rule's criteria."
msgid "In the :guilabel:`Action To Do` field, choose the action that will occur once the automated rule is triggered. When clicked, the following options become available on a drop-down menu:"
msgid ":guilabel:`Create next activity`: creates the next activity to occur, which is configured in the :guilabel:`Activity` section that appears at the bottom of the automation rule form."
msgid ":guilabel:`Send an SMS Text Message to the customer`: sends an SMS message to the customer(s) who fit the specified criteria of the automation rule."
msgid ":guilabel:`Email Template`: create (and edit) a new email template *or* select from a list of pre-configured email templates to send to the customer(s)."
msgid ":guilabel:`SMS Template`: create (and edit) a new SMS template *or* select from a list of pre-configured SMS templates to send to the customer(s)."
msgid ":guilabel:`Health`: designate the health of the subscription by choosing one of the following options: :guilabel:`Neutral`, :guilabel:`Good`, or :guilabel:`Bad`."
msgid "In the :guilabel:`Trigger On` field, decide whether the automated rule should be triggered on a :guilabel:`Modification` or :guilabel:`Timed Condition`."
msgid "When the :guilabel:`Trigger Now` button is clicked, Odoo will trigger the action on *all* linked subscriptions, regardless of possible timed conditions."
msgid "Sending a SMS text message in Odoo requires In-App Purchase (IAP) credit or tokens. For more information on :abbr:`IAP (In-App Purchase)`, visit :doc:`../../essentials/in_app_purchase`. For more information on sending SMS messages, visit :doc:`../../marketing/sms_marketing`."
msgid ":guilabel:`Trigger Date`: represents when the condition should be triggered. If left blank, the action is created upon subscription creation *and* updates."
msgid ":guilabel:`Delay After Trigger`: select a delayed amount of time (:guilabel:`Minutes`, :guilabel:`Hours`, :guilabel:`Days`, or :guilabel:`Months`) for Odoo to wait before triggering the configured action. If a negative number is entered, the \"delay\" will occur *before* the :guilabel:`Trigger Date`."
msgid "If :guilabel:`Create next activity` is selected in the :guilabel:`Action To Do` field, an :guilabel:`Activity` section appears at the bottom of the :guilabel:`Automation Rules` form."
msgid ":guilabel:`Assign To`: choose to assign the specified activity to either: :guilabel:`Subscription Salesperson`, :guilabel:`Sales Team Leader`, or :guilabel:`Specific Users`."
msgid "If :guilabel:`Specific Users` is selected as the :guilabel:`Assign To` option, a new :guilabel:`Specific Users` field appears beneath it, where a specific employee(s) can be chosen as the assignee(s) for the configured activity."
msgid "Odoo *Subscriptions* provides flexibility for businesses to decide whether customers can self-manage their subscriptions, or restrict that ability entirely."
msgid "Start by navigating to :menuselection:`Subscriptions app --> Configuration --> Recurring Plans`. From there, either create a new plan by clicking :guilabel:`New` or select an existing one to modify it."
msgid "Once on the :guilabel:`Recurring Plans` form, enable the :guilabel:`Closable` option, in the :guilabel:`Self-Service` section, to allow customers to close their own subscriptions using the customer portal."
msgid "After a quotation for a subscription product has been confirmed, it becomes a sales order, and the subscription status changes to :guilabel:`In Progress`."
msgid "At that point, the ability to close the subscription becomes available, via the :guilabel:`Close` button at the top of the subscription order, near the row that contains :guilabel:`In Progress` and other stages. This option is also available after the order has been invoiced and the payment has been registered."
msgid "Clicking the :guilabel:`Close` button prompts a :guilabel:`Close Reason` pop-up window to appear, allowing administrators to input the reason for closing the subscription, or choose from the drop-down menu of options in the :guilabel:`Reason` field."
msgid "Clicking :guilabel:`Submit` on the :guilabel:`Close Reason` pop-up window updates the subscription sales order to show :guilabel:`Churned` status tag, along with the specified :guilabel:`Close Reason`."
msgid "As an administrator, the ability to visualize what customers see when managing their subscriptions is accessible via the :guilabel:`Preview` button, located at the top of the subscription sales order."
msgid "From the customer's point of view, in the customer portal, the :guilabel:`Close Subscription` button is located on the left side of the sales order."
msgid "When the customer clicks the :guilabel:`Close Subscription` button, a :guilabel:`Close Subscription` pop-up window appears, in which the customer has to choose from a select list of reasons why they are choosing to close the subscription."
msgid "Customers can *only* chose a pre-configured reason why the subscription is being closed. They can *not* enter a custom reason from the customer portal. These selections can be adjusted by navigating to :menuselection:`Subscriptions --> Configuration --> Close Reasons`."
msgid "In addition, the specified :guilabel:`Close Reason` appears on the subscription order in the *Subscriptions* app in the backend (Administrator's view)."
msgid "However, by default, the eCommerce product page **only** displays the shortest recurrence period listed in the :guilabel:`Recurring Prices` tab of the product form."
msgid "For example, if a subscription product has *monthly* and *annaul* recurrence periods configured, then *only* the monthly price appears on the eCommerce page for that product, by default."
msgid "To set up each recurrence period as a product variant, go to :menuselection:`Subscriptions app --> Products --> Products`, and select a product. In the :guilabel:`Attributes & Variants` tab, click :guilabel:`Add a line`."
msgid "Then proceed to create an :guilabel:`Attribute` called `Billing Period` (or something similar), by typing in the name, and clicking :guilabel:`Create` from the mini drop-down menu that appears. This attribute name appears as option heading on the product page of the eCommerce shop."
msgid "Next, create :guilabel:`Values` that correspond to the recurrence periods that are configured in the :guilabel:`Recurring Prices` tab of the product form."
msgid "To do that, type in the name of the recurrence period in the :guilabel:`Values` column, on the same :guilabel:`Attribute` line, in the :guilabel:`Attributes & Variants` tab. Then, click :guilabel:`Create` from the mini drop-down menu that appears."
msgid "With those configurations in place and saved, a :guilabel:`Product Variants` column appears in the :guilabel:`Recurring Prices` tab. Proceed to assign the different :guilabel:`Product Variants` to their corresponding recurrence :guilabel:`Period` and :guilabel:`Price`."
msgid "*SEPA*, or Single Euro Payments Area, is a payment-integration initiative of the European Union for simplifying bank transfers denominated in euros."
msgid "*SEPA Direct Debit (|sdd|)* is a payment provider that allows future payments to be collected from customers' bank accounts by signing a mandate. This allows recurring payments to be automatically gathered and processed using |sdd|."
msgid "Before using |sdd|, the database must be configured to allow the use of Euros on sales orders. To do so, a :doc:`pricelist <../../point_of_sale/pricing/pricelists>` must be created for Euros."
msgid "In the :guilabel:`Pricing` section, underneath the :guilabel:`Pricelists` feature, click :icon:`fa-arrow-right` :guilabel:`Pricelists`. Then, click the :guilabel:`New` button to open a new pricelist form. Add a name for the pricelist in the top field, then set the drop-down menu next to :guilabel:`Currency` to :guilabel:`EUR`."
msgid "To use the wire transfer payment method, first ensure the |sdd| payment method is enabled. To do so, navigate to :menuselection:`Accounting app --> Configuration --> Settings`, scroll to the :guilabel:`Customer Payments` section, and tick the :guilabel:`SEPA Direct Deposit (SDD)` checkbox. Then, set a creditor identifier number in the field labeled, :guilabel:`Creditor Identifier`. Then, click :guilabel:`Save`."
msgid "The company using |sdd| must have a creditor identifier to issue a SEPA Direct Debit payment request. If using :ref:`test mode <subscriptions/sepa-sdd-test-mode>`, use the test creditor identifier number: `DE98ZZZ09999999999`, and click :guilabel:`Save`."
msgid "For example, navigate to :menuselection:`Accounting app --> Configuration --> Payment Providers`, then click the :guilabel:`SEPA Direct Debit` card."
msgid "The *SEPA Direct Debit* form can also be reached by navigating to :menuselection:`Website app --> Configuration --> Payment Providers`, or :menuselection:`Sales app --> Configuration --> Payment Providers`."
msgid "Next, set the :guilabel:`State` to :guilabel:`Enabled` to enable |sdd|. Use the drop-down menus next to the :guilabel:`Company` and :guilabel:`Website` fields to set where |sdd| can be used."
msgid "The options in the :guilabel:`Configuration` tab can be configured to customize how |sdd| is used. Optionally, tick the checkbox next to :guilabel:`Enable QR Codes` to enable the use of QR codes when paying by |sdd|, if desired."
msgid "Use the drop-down menu next to the :guilabel:`Communication` field to select the communication type used on sales orders. Choose :guilabel:`Based on Document Reference` to use the sales order (or invoice number), or :guilabel:`Based on Customer ID` to use the customer identifier. With either method selected, communication is given to the customer, once they choose the |sdd| payment method."
msgid "The configuration options listed under the :guilabel:`Availability` section are used to set payment restrictions, and are optional. Use the :guilabel:`Maximum Amount` field to set a maximum payment value, and the :guilabel:`Countries` field to restrict payment from any particular countries, if desired."
msgid "The :guilabel:`Currencies` field should be left with the default :guilabel:`EUR` tag to ensure |sdd| is only accessible when customers pay with Euros."
msgid "The :guilabel:`Payment Journal` field in the :guilabel:`Payment followup` section can be used to select the journal in which the successful transactions are posted."
msgid "In the :guilabel:`Messages` tab, the :guilabel:`Pending Message` field can be used to add a message that is displayed, if the order remains pending after the payment is processed. By default, this field contains the message: :guilabel:`Please make an unique payment transfer to confirm the SEPA mandate.`"
msgid "Once all necessary configuration settings are complete, the :icon:`fa-eye-slash` :guilabel:`Unpublished` smart button, located at the top of the page automatically changes to :icon:`fa-globe` :guilabel:`Published` to show the |sdd| payment option is now visible to customers. Only keep the payment method published if payments are ready to be received."
msgid "It is possible to keep the payment method enabled, but **not** visible to customers, until payments are ready to be received. To do this, set the smart button to :icon:`fa-eye-slash` :guilabel:`Unpublished` after setting the :guilabel:`State` to :guilabel:`Enabled`."
msgid "The |sdd| configuration menu can also be accessed by navigating to :menuselection:`Settings app --> Website`, and in the :guilabel:`Shop - Payment` section, click the :icon:`fa-arrow-right` :guilabel:`View other providers` button. Then, click the |sdd| card. Alternatively, navigate to :menuselection:`Website app --> Configuration --> Settings` to access the same button."
msgid "The |sdd| payment method can be tested before it is accessed by customers. First, ensure the test creditor identifier is :ref:`configured <subscriptions/sepa-sdd-configuration>` before continuing."
msgid "Next, select the :guilabel:`Test Mode` option in the :guilabel:`State` field on the form. Upon selecting :guilabel:`Test Mode`, an orange :guilabel:`Test mode` banner appears in the upper-right corner of the form."
msgid "Select a :guilabel:`Customer`. Select any pay period in the drop-down menu next to :guilabel:`Recurring Plan` and select the pricelist using EUR in the drop-down menu next to :guilabel:`Pricelist`."
msgid "Next, confirm the sales order by clicking the :guilabel:`Confirm` button, then click the :guilabel:`Preview` button to open a preview of the customer invoice. Scroll down to the :guilabel:`Anticipate payment` section to find the SEPA Direct Debit payment method."
msgid "It can be confirmed that test mode is still enabled if the :icon:`fa-eye-slash` (unpublished) and :icon:`fa-exclamation-triangle` (test mode) icons are present next to SEPA Direct Debit."
msgid "Next, enter a test IBAN number, such as `GB33BUKB20201555555555`, and click :guilabel:`Pay`. Return to the sales order in the **Sales** app, and confirm the :guilabel:`In Progress` tag is present on the sales order form. At this point, the flow is complete."
msgid "To re-enable normal function after testing, navigate back to the *SEPA Direct Debit* form, and change the *State* setting to :guilabel:`Enabled`."
msgid "Once |sdd| has been :ref:`configured <subscriptions/sepa-sdd-configuration>` and enabled, |sdd| appears as a payment method during checkout in **eCommerce**, and as a payment method on invoices in the **Sales** app. The option is presented to customers, and prompts them to enter their IBAN number."
msgid "Mandates automatically close after the end date is reached. If the *End date* field is not set, the mandate remains in an *Active* state until it is *Closed* or *Revoked*."
msgid "|sdd| payments can also be registered manually by navigating to the desired invoice and clicking the :guilabel:`Register Payment` button. Next, select :guilabel:`SEPA Direct Debit` as the :guilabel:`Payment Method` and click the :guilabel:`Create Payment` button. The invoice now displays a green :guilabel:`In Payment` banner."
msgid "To validate a successful |sdd| payment, navigate to :menuselection:`Accounting app --> Customers --> Payments`, and look for the entry in the list, along with a :guilabel:`Posted` tag in the :guilabel:`Status` column."
msgid "All |sdd| payments can be processed at once by uploading an `.xml` file containing a batch of all posted |sdd| payments to an online banking interface. To generate this file, navigate to :menuselection:`Accounting app --> Customers --> Batch Payments`. A list of all posted |sdd| payments appears. Tick the checkbox next to every payment to be included in the batch, or tick the checkbox at the top of the list to select all entries at once."
msgid "Next, click :guilabel:`Create Batch`. A new batch payment form appears with the selected payments added to the list in the :guilabel:`Batch Content` tab."
msgid ":guilabel:`SDD Scheme`: The B2B scheme is an optional scheme, offered exclusively to business payers. Some banks/businesses might not accept B2B |sdd|."
msgid "Once the payment is configured, click :guilabel:`Validate` to generate the `.xml` file, which appears in the chatter. Finally, click the :icon:`fa-download` :guilabel:`(download)` icon next to the file in the chatter to download the file."
msgid "The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02** specifications, as required by the SEPA customer-to-bank `implementation guidelines <https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-credit-transfer-customer-psp-implementation>`_, which ensures compatibility with the banks."
msgid "The *wire transfer* payment method allows for payment instructions to be shared with a customer after purchasing a product. With a subscription, these payment instructions are shared every time the payment is renewed."
msgid "The wire transfer payment method requires minimal setup, but in most cases, it is inefficient compared to other online payment providers. It is recommended to use another payment provider with subscriptions, due to wire transfers requiring manual confirmation for each payment."
msgid "For example, navigate to :menuselection:`Accounting app --> Configuration --> Online Payments: Payment Providers`, then click the :guilabel:`Wire Transfer` card."
msgid "If the **Accounting** app is not installed, the *Payment Providers* page can also be reached by navigating to :menuselection:`Website app --> Configuration --> eCommerce: Payment Providers`, or :menuselection:`Sales app --> Configuration --> Online Payments: Payment Providers`."
msgid "Next, set the :guilabel:`State` to :guilabel:`Enabled` to enable wire transfers. Use the drop-down menus next to the :guilabel:`Company` and :guilabel:`Website` fields to set where wire transfers can be used."
msgid "The options in the :guilabel:`Configuration` tab can be used to customize the wire transfer. Optionally tick the checkbox next to :guilabel:`Enable QR Codes` to enable the use of QR codes when paying by wire transfer, if desired."
msgid "Use the drop-down menu next to the :guilabel:`Communication` field to select the communication type used on sales orders. Choose :guilabel:`Based on Document Reference` to use the sales order (or invoice number), or :guilabel:`Based on Customer ID` to use the customer identifier. With either method selected, communication is given to the customer, once they choose the wire transfer payment method."
msgid "The configuration options listed under the :guilabel:`Availability` section are used to set payment restrictions, and are optional. Use the :guilabel:`Maximum Amount` field to set a maximum payment value, the :guilabel:`Currencies` field to restrict any currencies from being used for payment, and the :guilabel:`Countries` field to restrict payment from any particular countries, if desired."
msgid "In the :guilabel:`Messages` tab, use the :guilabel:`Pending Message` field to add a message containing wire transfer information. This message is displayed to the customer after confirming their order, as well as if the order is marked as pending after the payment is processed."
msgid "If :doc:`a bank account <../../../finance/accounting/bank>` has already been defined, the account number is automatically added to the default message generated by Odoo. A bank account can also be added afterwards, and the message updates with the appropriate bank information by clicking :icon:`fa-refresh` :guilabel:`Reload pending message`."
msgid "Once all necessary configuration settings are complete, the :icon:`fa-eye-slash` :guilabel:`Unpublished` smart button located at the top of the page automatically changes to :icon:`fa-globe` :guilabel:`Published` to show the wire transfer payment option is now visible to customers. Only keep the payment method published if payments are ready to be received."
msgid "It is possible to keep the payment method enabled, but **not** visible to customers, until payments are ready to be received. To do that, set the smart button to :icon:`fa-eye-slash` :guilabel:`Unpublished` after setting the :guilabel:`State` to :guilabel:`Enabled`."
msgid "The wire transfer payment method can be tested before it is accessed by customers by selecting the :guilabel:`Test Mode` option in the :guilabel:`State` field on the form. Upon selecting :guilabel:`Test Mode`, an orange :guilabel:`Test mode` banner appears in the upper-right corner of the form."
msgid "Next, enter the credentials for a bank account with accessible transactions in the :guilabel:`Messages` tab. To re-enable normal function after testing, change the :guilabel:`State` setting to :guilabel:`Enabled`."
msgid "With wire transfers :ref:`enabled and published <subscriptions/wire-transfer-configuration>`, customers see wire transfers as an available payment method at checkout when purchasing a product."
msgid "When this method is selected by a customer, they are shown the *Pending Message* set in the :ref:`wire transfer configuration page <subscriptions/wire-transfer-configuration>`, after confirming their purchase. Once the purchase is confirmed, a sales order is created."
msgid "Online orders remain in the *Quotation sent* (i.e. unpaid order) stage until both the payment is received, *and* the order is confirmed manually, using the :guilabel:`Confirm` button on the sales order."
msgid "To begin processing the payment, navigate to :menuselection:`Sales app --> Orders --> Orders`, and click the corresponding sales order. Ensure the sales order is correct, then click :guilabel:`Confirm` to confirm the sales order."
msgid "Next, click the new :guilabel:`Create Invoice` button, then choose :guilabel:`Regular invoice`, and click :guilabel:`Create Draft Invoice`. A draft of the invoice appears. Click :guilabel:`Confirm` to validate the invoice."
msgid "To send this invoice to the customer, click the :guilabel:`Send & Print` button. A :guilabel:`Send` pop-up window appears, with an email template configured, and a PDF invoice attached."
msgid "Ensure the information is correct, then click :guilabel:`Send & Print`. The pop-up window disappears, and the :guilabel:`Send & Print` button turns gray to show the invoice has been sent."
msgid "The default template for sending an invoice can be modified by navigating to :menuselection:`Settings app --> Companies --> Email Templates --> Review All Templates --> Invoice: Sending`."
msgid "Next, click the :guilabel:`Register payment` button on the invoice page. A pop-up window titled, :guilabel:`Register Payment`, appears with options for selecting the type of payment. In the :guilabel:`Journal` field, select :guilabel:`Bank` from the drop-down menu. Next, set the :guilabel:`Payment Method` to :guilabel:`Manual`. Ensure the :guilabel:`Amount` and :guilabel:`Payment Date` are correct, then click the :guilabel:`Create Payment` button."
msgid "The customer invoice is revealed with a green :guilabel:`In Payment` banner in the upper-right corner. At this point, the flow is now complete."
msgid "If payment has been received before sending the invoice, such as in cash, the payment can still be registered in Odoo by clicking the :guilabel:`Register Payment` button, and creating the payment *before* clicking :guilabel:`Send & Print`. Now, when an invoice is sent using the :guilabel:`Send & Print` button, a new line is automatically added to the invoice message, stating the invoice is already paid."
msgid "*Subscription plans* are :doc:`quotation templates </applications/sales/sales/send_quotations/quote_template>` used to preconfigure quotations with subscription products. Use subscription plans to quickly create subscription orders."
msgid "To configure subscription plans, go to :menuselection:`Subscriptions --> Configuration --> Plans`. Then, click :guilabel:`New` to create a new plan, or select an existing plan to edit it."
msgid ":guilabel:`Quotation expires after`: Enter the number of days after which the quotation expires, starting from the day the quotation is sent to the customer. Leave this field at zero for the quotation to never expire."
msgid ":guilabel:`Online Confirmation`: Check the boxes next to :guilabel:`Signature` or :guilabel:`Payment` to enable the customer to confirm their subscription order by signing or paying for the quotation. Enable both to leave the choice to the customer. Enable neither to only confirm the quotation in the backend."
msgid ":guilabel:`Confirmation Mail`: Select an :doc:`email template </applications/general/companies/email_template>` for the confirmation email that is automatically sent to the customer after the quotation is confirmed. Leave this field blank to send nothing."
msgid "To edit an existing email template, select one from the drop-down menu, then click on the :guilabel:`Internal link` arrow at the end of the line."
msgid ":guilabel:`Recurrence`: Select the recurrence period used for the plan. The recurrence periods available here are the same ones that are configured in :menuselection:`Subscriptions --> Configuration --> Recurrence Periods`."
msgid "If the duration is :guilabel:`Forever`, then the subscription plan will continually renew until either the customer or the company manually ends the subscription."
msgid "If the duration is :guilabel:`Fixed`, then enter an :guilabel:`End After` date, which determines the amount of time after which the subscription will automatically end."
msgid ":guilabel:`Self Closable`: Check this box to enable the customer to terminate their subscription from the :doc:`customer portal </applications/websites/ecommerce/ecommerce_management/customer_accounts>`."
msgid ":guilabel:`Invoicing Journal`: Select the accounting journal in which invoices for this subscription plan are recorded. Leave this field blank to use the sales journal with the lowest sequence."
msgid "In the :guilabel:`Lines` tab, create the order lines for the quotation. Click :guilabel:`Add a product`, select a product to include in the plan, and then enter the :guilabel:`Quantity` and :guilabel:`Unit of Measure`. Add as many products as desired to the order lines."
msgid "In the :guilabel:`Optional Products` tab, enter any optional products that the customer can add to their quotation before confirming the order."
msgid "If the subscription plan has unique :doc:`terms and conditions </applications/finance/accounting/customer_invoices/terms_conditions>`, add them in the :guilabel:`Terms & Conditions` tab. If terms conditions are specified on a plan, these will be used instead of the default terms and conditions set up in the *Sales* app settings."
msgid "From the :guilabel:`Subscriptions` dashboard, click :guilabel:`New` to create a new quotation. Then, select a subscription plan in the :guilabel:`Subscription Plan` field."
msgid "The :guilabel:`Recurrence`, products, and other information from the plan are automatically filled in. The quotation can then be modified further as needed."
msgid "From the :guilabel:`Sales` dashboard, click :guilabel:`New` to create a new quotation. Then, select a subscription plan in the :guilabel:`Quotation Template` field."
msgid "All subscription orders will appear on the :guilabel:`Subscriptions` dashboard regardless of whether they were created in the *Subscriptions* app or the *Sales* app."
msgid "By closely integrating with the Odoo *Sales* app, the *Subscriptions* app enables users to sell subscription products alongside regular sales products. While regular products are sold on a one-time basis, subscription products are sold on a renewing basis, generating recurring revenue."
msgid "Recurrence periods are the time periods in which subscriptions renew. They designate how often the customer pays for (and receives) subscription products."
msgid "To create a new recurrence period, click :guilabel:`New` on the :guilabel:`Recurrence Periods` page. Doing so reveals a blank recurrence period form."
msgid "Then, type in the :guilabel:`Name` and :guilabel:`Duration` of the recurrence period, and select the :guilabel:`Unit` that defines the duration."
msgid "The unit :guilabel:`Days` *cannot* be used as a recurrence period on subscriptions. The daily recurrence is meant for rentals, and **cannot** be added on recurring subscription sales orders."
msgid "By default, the :guilabel:`Recurring` option is already enabled, prompting Odoo to recognize it as a subscription product. Be sure to leave the :guilabel:`Recurring` and :guilabel:`Can be Sold` options enabled."
msgid "The :guilabel:`Product Type` field is set to :guilabel:`Service` by default, as well. However, subscription products *can* be set to other types, if needed."
msgid "When creating a physical subscription product in the Odoo **Sales** application, the :guilabel:`Invoicing Policy` must be set to :guilabel:`Ordered quantities`."
msgid "Similarly, when creating a physical subscription product in the Odoo **Subscriptions** application, the :guilabel:`Invoicing Policy` must **not** be set to :guilabel:`Based on Delivered Quantity (Manual)` for the same reasons."
msgid "Once the desired fields in the :guilabel:`General Information` tab have been entered, click the :guilabel:`Time-based pricing` tab on the product form."
msgid "In the :guilabel:`Period` column, select a desired recurrence period. In the :guilabel:`Pricelist` column, select a pricelist, if needed. Then, in the :guilabel:`Price` column, enter the price for that recurrence period."
msgid "An existing product can be made into a subscription product, simply by marking it as :guilabel:`Recurring`, and configuring :guilabel:`Time-based pricing` on the product form."
msgid ":doc:`Pricelists <../sales/products_prices/prices/pricing>` can be used with subscription products to give special pricing to customers included in pricelists."
msgid "This can be configured either in the :guilabel:`Time-based pricing` tab of the product form, or on the pricelist form in the *Sales* application."
msgid "To create recurring price rules for specific pricelists in the :guilabel:`Time-based pricing` tab of the product form, select a pricelist in the :guilabel:`Pricelist` column."
msgid "To do this, go to :menuselection:`Sales app --> Products --> Pricelists`, and select a pricelist (or click :guilabel:`New` to create a new pricelist)."
msgid "Then, select a subscription product in the :guilabel:`Products` column, and select a recurrence period in the :guilabel:`Period` column. Lastly, enter a :guilabel:`Price` for that particular product and period. Add as many lines as needed."
msgid "When :guilabel:`Time-based rules` are added to the pricelist form, the :guilabel:`Time-based pricing` tab of the product form is automatically updated."
msgid "The foundation of any subscription business model is recurring payments. This is when customers reliably pay a regular amount at specific intervals, in exchange for access to a subscription product or service."
msgid "Subscription renewal is the process customers follow when they willingly choose to continue participating in, and paying for, a subscription product or service."
msgid "Subscribers experience the renewal process at different intervals -- weekly, monthly, annually, etc. -- depending on the duration of the agreed-upon contract."
msgid "Most companies that offer subscriptions prefer to automate the renewal process for customers. However, manual subscription renewals are still used in some cases."
msgid "With the Odoo **Subscriptions** application, a company can manage all of its subscriptions in one place. Renewals can be processed automatically, or manually, include additional products or upsells per renewal order, and be filtered in batch views to quickly locate customers who need to renew their subscriptions."
msgid "To open a subscription quotation, navigate to :menuselection:`Subscriptions app --> Subscriptions --> Quotations`, and select the desired quotation from the list. Or, create a new one by clicking :guilabel:`New` to open a new quotation form."
msgid "Subscription quotations **must** be confirmed, and payment from the customer for the initial subscription **must** be invoiced and registered in order to successfully open a *Renewal Quotation*."
msgid "For more information on the above process of confirming quotations and invoicing payments, see: - :doc:`../sales/send_quotations/create_quotations` - :doc:`../sales/send_quotations/get_paid_to_validate`"
msgid "Once the payment from the subscription quotation is confirmed, the quotation turns into a sales order. An :guilabel:`In Progress` tag is applied to the sales order form, and a series of buttons also appear at the top of the sales order, including a :guilabel:`Renew` button."
msgid "When the :guilabel:`Renew` button is clicked, Odoo instantly presents a new renewal quotation, complete with a :guilabel:`Renewal Quotation` tag."
msgid "From here, a standard sales flow can occur to confirm the quotation. This typically begins by clicking :guilabel:`Send by Email`, which sends a copy of the quotation to the customer, by email, for them to confirm, and eventually, pay for."
msgid "In the chatter of the :guilabel:`Renewal Quotation`, it is mentioned that this subscription is the renewal of the subscription from the original sales order."
msgid "Once the :guilabel:`Renewal Quotation` is confirmed, it becomes a sales order, and a :guilabel:`Sales History` smart button appears at the top of the page."
msgid "When that :guilabel:`Sales History` smart button is clicked, Odoo reveals a separate page, showcasing the different sales orders attached to this subscription, along with their individual :guilabel:`Subscription Status`."
msgid "On rare occasions, automatic payment can fail, which results in a *Payment Failure* tag on the top-right of the sales order, if there is an error in the payment method."
msgid "This is done to prevent the system from charging the customer again the next time a scheduled action is run. Because the status of the payment is unknown, Odoo requests a manual operation to check if the payment has been made, before the payment can be used again."
msgid "To do this, navigate to :menuselection:`Subscriptions app --> Subscriptions --> Quotations`. Click into the desired subscription, then check the *Chatter* to see if the payment was made."
msgid "If the payment was **not** made, first enter :doc:`debug mode <../../general/developer_mode>`. Then, click the :guilabel:`Other Info` tab, and untick the checkbox next to :guilabel:`Contract in exception`. Reload the sales order, and the :guilabel:`Payment Failure` tag is gone."
msgid "If the payment **was** made, a new invoice must be made and posted manually. This automatically updates the next invoice date of the subscription. Once created, enter :doc:`debug mode <../../general/developer_mode>`, and navigate to the new sales order. Click the :guilabel:`Other Info` tab, and untick the checkbox next to :guilabel:`Contract in exception`. Reload the sales order, and the :guilabel:`Payment Failure` tag is gone."
msgid "In both cases, once the :guilabel:`Contract in exception` option is no longer selected, Odoo handles renewals automatically again. If the subscription remains in *payment failure*, it is skipped by Odoo until the sales order is closed."
msgid "On the *Subscriptions Analysis* reporting page, users can view specific data related to recurring subscriptions, quantity of subscriptions, in-progress or paused subscriptions, and more."
msgid "And the *MRR Analysis* reporting page offers a time-based collection of analytics showcasing how subscription |MRR| and |ARR| have changed over the course of any given period of time."
msgid "*Filters* are used to narrow down metrics to show specific analytics, whereas groupings (via the *Group By* option) are used to gather the data from specific sections into groups for more organized analysis."
msgid "To modify the results being shown on any reporting page, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to the right of the search bar. Doing so reveals a drop-down menu of detailed filter and grouping options."
msgid "If desired, a filter or grouping (or combination of filters and/or groupings) can be saved in the :guilabel:`Favorites` section of that drop-down menu. To do so, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon beside :guilabel:`Save current search`, located beneath the :guilabel:`Favorites` section."
msgid "This reveals a field to assign a title to the favorite filter. Two options are also found beneath the title field: :guilabel:`Default filter` and :guilabel:`Shared`."
msgid "When clicked, that saved filter appears beneath the :guilabel:`Favorites` column of the drop-down filter menu, and a :icon:`fa-star` :guilabel:`(gold star)` icon appears beside the favorite filter's name in the search bar."
msgid "On the :guilabel:`Subscription Analysis`, :guilabel:`MRR Breakdown`, and :guilabel:`MRR Analysis` reporting pages, three different view options are located in the upper-right corner."
msgid "With the graph view selected, the following options appear between the search bar and visual representation of the data. These graph-specific options are located to the right of the :guilabel:`Measures` and :guilabel:`Insert in Spreadsheet` buttons."
msgid "The first three options, from left to right, represent different graph-related views. The remaining options represent different ways to organize and visualize that specific graph-related data."
msgid "Each graph view option has its own series of specific visual options, which are represented by the available buttons that appear to the right of the selected graph-related view option."
msgid "With the list view selected, the subscription metrics being analyzed are displayed in a simple list, which can be fully customized by using any of the available filters or groupings in the drop-down filter menu (accessible via the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to the right of the search bar)."
msgid "The pivot data table can be customized using the options available in the :guilabel:`Measures` drop-down menu, and/or the filter grouping options available in the filter drop-down menu (accessible via the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to the right of the search bar)."
msgid "Three pivot-specific options are available, located to the right of the :guilabel:`Measures` drop-down menu and :guilabel:`Insert in Spreadsheet` button."
msgid "The graph and pivot reporting pages have their own metric-specific :guilabel:`Measures` drop-down menu of data-related options to choose from, located in the upper-left corner, above the visual representation of metrics."
msgid "When the :guilabel:`Measures` button is clicked, a series of selectable measures becomes available, via a drop-down menu. When any of the options are selected from the :guilabel:`Measures` drop-down menu, the chosen metrics related to that specific measure appear on the reporting page."
msgid "For more information on the different measures that can be utilized on each reporting page, refer to the :ref:`specific reporting page breakdowns <subscriptions/reports/reporting>` found below in this documentation."
msgid "When clicked, the ability to add the configured data currently being showcased on the reporting page into a new or pre-existing spreadsheet or dashboard becomes available, via a pop-up window."
msgid "To access, analyze, and customize various reports related to subscriptions, navigate to :menuselection:`Subscriptions app`, and click the :guilabel:`Reporting` drop-down menu in the header to reveal the following reporting pages:"
msgid "By default, the :guilabel:`Bar Chart` option, in the :guilabel:`Graph` view, is selected on the :guilabel:`Subscriptions Analysis` reporting page."
msgid "When the :guilabel:`Measures` button on the :guilabel:`Subscriptions Analysis` page is clicked, a series of metric-related options becomes available as a drop-down menu."
msgid "The :guilabel:`Retention Analysis` reporting page differs from the other **Subscriptions** app reporting pages, in that it does **not** provide any additional view options. The data on this page is only presented in a customizable data chart."
msgid "When the :guilabel:`Measures` drop-down menu on the :guilabel:`Retention Analysis` reporting page is clicked, a series of metric-related options become available."
msgid "To the right of the :guilabel:`Measures` drop-down menu on the :guilabel:`Retention Analysis` page is an additional drop-down menu containing different time periods. The default time period is :guilabel:`Month`."
msgid "When a time period option from this drop-down menu is selected, the :guilabel:`Retention Analysis` reporting page showcases data for the configured measures and filters within that time period."
msgid "To the right of the time period drop-down menu, there is a download button, which allows the user to download the data presented on the :guilabel:`Retention Analysis` page as an Excel file."
msgid "By default, the data displayed on the :guilabel:`MRR Breakdown` reporting page is in graph view, with the :guilabel:`Bar Chart` option and :guilabel:`Stacked` option selected."
msgid "When the :guilabel:`Measures` drop-down menu on the :guilabel:`MRR Breakdown` reporting page is clicked, a series of metric-related options become available."
msgid "To make a different measure option the default, first, select the desired measure from the :guilabel:`Measures` drop-down menu. Then, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar to open the mega menu of filters and groupings."
msgid "In the :guilabel:`Favorites` column, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon beside :guilabel:`Save current search` to reveal a field, where a title can be entered, along with two checkboxes::guilabel:`Default filter` and :guilabel:`Shared`."
msgid "By default, the data displayed on the :guilabel:`MRR Analysis` reporting page is in graph view, with the :guilabel:`Line Chart` option, :guilabel:`Stacked` option, and :guilabel:`Cumulative` option selected."
msgid "When the :guilabel:`Measures` drop-down menu on the :guilabel:`MRR Analysis` reporting page is clicked, a series of metric-related options become available."
msgid "*Scheduled actions* are pre-configured processes that allow users to automate certain tasks within a database, based on a designated schedule or number of occurrences. These tasks can include sending emails, generating invoices, data clean-up, and so much more."
msgid "In Odoo, some scheduled actions are active, by default, to ensure that certain functions are triggered automatically, however there are *also* many scheduled action options that appear in the database that are **not** activated by default."
msgid "In Odoo *Subscriptions*, there are two scheduled actions that initiate the billing process for active recurring subscriptions, as well as when billing should stop due to subscription expiration."
msgid "Doing so reveals a dedicated :guilabel:`Scheduled Actions` dashboard. On this page, there is a complete list of scheduled actions for the entire database."
msgid "From here, enter `Subscription` in the search bar. Doing so provides three subscription-specific results. The following documentation focuses on the last two results in the list:"
msgid "Determine if a scheduled action is active by looking under the :guilabel:`Active` column, in the it's corresponding row on the :guilabel:`Scheduled Actions` dashboard, for a ticked checkbox; if the checkbox is green with a check mark, the scheduled action is active."
msgid "Then, from the scheduled action form, toggle the switch in the :guilabel:`Active` field to the right. Doing so turns the switch green, indicating that the scheduled action is now `Active`."
msgid "The ability to set up how often the scheduled action runs is also available on the scheduled action form, in the :guilabel:`Execute Every` field."
msgid "The scheduled action does **not** function correctly if the execution time is less than five minutes. This is a general rule for all scheduled actions."
msgid "In order for the :guilabel:`Sale Subscription: generate recurring invoices and payments` scheduled action to properly generate recurring invoices and payments on subscriptions, the *Deferred Expense* and *Deferred Revenue* accounts **must** be set up, in order for Odoo to process various invoices and payments related to subscriptions."
msgid "To set up *Deferred Expense* and *Deferred Revenue* accounts, navigate to :menuselection:`Accounting app --> Configuration --> Settings`. Both accounts can be configured in the :guilabel:`Default Accounts` section."
msgid "Once the correct accounts are entered in the :guilabel:`Deferred Expense` and :guilabel:`Deferred Revenue` drop-down menu fields, click :guilabel:`Save` in the upper-left corner."
msgid "Elements related to the :guilabel:`Sale Subscription: generate recurring invoices and payments` scheduled action can be found on confirmed subscription sales orders."
msgid "If the product invoicing policy is set to *Based on Delivered Quantities (Manual)*, and the delivered quantity is `0`, Odoo does **not** create an invoice, and the customer is not charged."
msgid "Once the invoice for the subscription sales order is created, the invoice can be viewed by clicking the :guilabel:`Invoices` smart button that appears at the top of the subscription sales order."
msgid "An email is sent to the customer notifying them of the recurring subscription charge, *if* there is a :guilabel:`Payment Token` on the account."
msgid "To check if there is a :guilabel:`Payment Token`, open the :guilabel:`Other Info` tab, and look at the :guilabel:`Payment Token` field, under the :guilabel:`Subscription` section."
msgid "If there is no :guilabel:`Payment Token`, the invoice is created, and sent to the customer. The payment **must** be registered manually in this case."
msgid "The :guilabel:`Sale Subscription: generate recurring invoices and payments` scheduled action also has the ability to close a subscription, if the following conditions are met:"
msgid "The :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks for all other conditions that may cause a subscription to close automatically. If certain conditions are met, the scheduled action closes that subscription."
msgid "First, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks to see if the end date has passed, which is configured on the subscription sales order."
msgid "Then, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks if the invoice has not been paid within the payment terms deadline."
msgid "To access the invoices attached to a subscription, access the sales order for the subscription product, and click the :guilabel:`Invoices` smart button. Then, look at the :guilabel:`Invoice Date` column."
msgid "Unpaid subscriptions with an :guilabel:`Invoice Date` that are past the determined number of days in the :guilabel:`Automatic Closing` field of a :guilabel:`Recurring Plan` are automatically closed by the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action."
msgid "For example, if the next invoice date is July 1st, and the :guilabel:`Automatic Closing` is set to '30 Days', the scheduled action would close the subscription on August 1st."
msgid "Subscriptions are recurrent, and go on indefinitely. As time passes, customers may want to modify them. With that in mind, it's imperative to have the ability to adapt prices, or change quantities, to accommodate any need. That's where the opportunity to upsell a subscription can come into play."
msgid "These are customers who already trust the company/brand, and because they have established a pattern of paying for products/services, there's more confidence behind the attempt to sell them a more expensive product/service."
msgid "For brand new customers unfamiliar with the company/brand, a new, attractive tactic must be employed to entice them to purchase a more expensive product/service."
msgid "So, if these more expensive products/services are offered to new customers at a discount, it can result in a sale, while establishing a strong sense of trust between the customer and the company/brand. In turn, this can increase customer retention, as they'll grow more comfortable and trustworthy over time."
msgid "In order to have the ability to upsell a subscription to a new customer, with the aid of a discount, the *Discounts* feature **must** be activated."
msgid "To activate the *Discounts* feature, navigate to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Pricing` section, and tick the checkbox beside :guilabel:`Discounts`. Then, click :guilabel:`Save`."
msgid "Before upselling a subscription, check out our documentation on how to :doc:`Create a quotation <../subscriptions>` using subscription products."
msgid "When a quotation with a subscription is confirmed, it officially becomes a sales order, and a new subscription is created in the Odoo *Subscriptions* application."
msgid "When the subscription sales order is opened, either in the *Sales* or *Subscriptions* application, the ability to upsell that subscription is available, via the :guilabel:`Upsell` button at the top of the sales order."
msgid "When the :guilabel:`Upsell` button is clicked, a new quotation form appears, with an :guilabel:`Upsell` status banner in the upper-right corner. The initial subscription product is already in the :guilabel:`Order Lines` tab."
msgid "There is also a warning reminding the user that the recurring products are discounted, according to the prorated period of time, located beneath the initial subscription product in the :guilabel:`Order Lines` tab."
msgid "The prorated amount is **only** applied to *Service* product types. It is **not** applied to *Consumable* or *Storable* product types, even if the message appears."
msgid "From this new upsell quotation form, add new subscription products in the :guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and selecting the desired subscription product."
msgid "Once the desired upsell subscription product(s) have been added, it can be sent to the customer for approval by clicking the :guilabel:`Send by Email` button."
msgid "When the quotation is confirmed by the customer, the upsell products are added to the initial subscription. Quotation prices are then prorated to the remaining time of the current invoicing period."
msgid "Once the customer approves, click the :guilabel:`Confirm` button on the quotation, making it a sales order. When that's clicked, a :guilabel:`Sales History` smart button appears, displaying how many sales orders are attached to this initial subscription order."
msgid "When the :guilabel:`Sales History` smart button is clicked, Odoo reveals a separate page containing a list of the related sales orders, clearly showcasing their individual :guilabel:`Subscription Status`."
