documentation/locale/ar/LC_MESSAGES/sales.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# Translators:
# Mustafa Rawi <mustafa@cubexco.com>, 2019
# Abdalla Mohamed <abdalla.mhafeez@gmail.com>, 2019
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:47+0000\n"
"Last-Translator: Abdalla Mohamed <abdalla.mhafeez@gmail.com>, 2019\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ar\n"
"Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"

#: ../../sales.rst:5
msgid "Sales"
msgstr ""

#: ../../sales/advanced.rst:3
msgid "Advanced Topics"
msgstr ""

#: ../../sales/advanced/portal.rst:3
msgid "How to give portal access rights to my customers?"
msgstr ""

#: ../../sales/advanced/portal.rst:6
msgid "What is Portal access/Who is a portal user?"
msgstr ""

#: ../../sales/advanced/portal.rst:8
msgid ""
"A portal access is given to a user who has the necessity to have access to "
"Odoo instance, to view certain documents or information in the system."
msgstr ""

#: ../../sales/advanced/portal.rst:12
msgid "For Example, a long term client who needs to view online quotations."
msgstr ""

#: ../../sales/advanced/portal.rst:14
msgid ""
"A portal user has only read/view access. He or she will not be able to edit "
"any document in the system."
msgstr ""

#: ../../sales/advanced/portal.rst:18
msgid "How to give portal access to customers?"
msgstr ""

#: ../../sales/advanced/portal.rst:21
msgid "From Contacts Module"
msgstr ""

#: ../../sales/advanced/portal.rst:23
msgid ""
"From the main menu, select **Contacts** menu. If the contact is not yet "
"created in the system, click on the create button to create new contact. "
"Enter details of the contact and click \"save\"."
msgstr ""

#: ../../sales/advanced/portal.rst:33
msgid ""
"Choose a contact, click on the **Action** menu in the top-center of the "
"interface and from the drop down."
msgstr ""

#: ../../sales/advanced/portal.rst:36
msgid "Select **Portal Access Management**. A pop up window appears."
msgstr ""

#: ../../sales/advanced/portal.rst:41
msgid ""
"Enter the login **email ID**, check the box under **In Portal** and add the "
"content to be included in the email in the text field box below. Click on "
"**Apply** when you're done."
msgstr ""

#: ../../sales/advanced/portal.rst:47
msgid ""
"An email will be sent to the specified email address, indicating that the "
"contact is now a portal user of the respective instance."
msgstr ""

#: ../../sales/ebay/manage.rst:3
msgid "How to list a product?"
msgstr ""

#: ../../sales/ebay/manage.rst:6
msgid "Listing without variation"
msgstr ""

#: ../../sales/ebay/manage.rst:8
msgid ""
"In order to list a product, you need to check the **use eBay** field on a "
"product form. The eBay tab will be available."
msgstr ""

#: ../../sales/ebay/manage.rst:14
msgid ""
"When the **Use Stock Quantity** field is checked, the quantity sets on eBay "
"will be the Odoo **Forecast Quantity**."
msgstr ""

#: ../../sales/ebay/manage.rst:17
msgid ""
"The **Description Template** allows you to use templates for your listings. "
"The default template only use the **eBay Description** field of the product."
" You can use html inside the **Description Template** and in the **eBay "
"Description**."
msgstr ""

#: ../../sales/ebay/manage.rst:21
msgid ""
"To use pictures in your listing, you need to add them as **Attachments** on "
"the product template."
msgstr ""

#: ../../sales/ebay/manage.rst:24
msgid "Listing with variations"
msgstr ""

#: ../../sales/ebay/manage.rst:26
msgid ""
"When the **use eBay** on a product with variations is checked and with "
"**Fixed Price** as **Listing Type**, the eBay form is sligthly different. In"
" the variants array, you can choose which variant will be listed on eBay as "
"well as set the price and the quantity for each variant."
msgstr ""

#: ../../sales/ebay/manage.rst:35
msgid "Listing with item specifics"
msgstr ""

#: ../../sales/ebay/manage.rst:37
msgid ""
"In order to add item specifics, you should create a product attribute with "
"one value in the **Variants** tab on the product form."
msgstr ""

#: ../../sales/ebay/manage.rst:44
msgid "Product Identifiers"
msgstr ""

#: ../../sales/ebay/manage.rst:46
msgid ""
"Products identifiers such as EAN, UPC, Brand or MPN are required in most of "
"the eBay category. The module manages the EAN and UPC identifiers with the "
"**Barcode** field of the product variant. If the **Barcode** field is empty "
"or is value is not valid, the EAN and UPC values will be set as 'Does not "
"apply' as recommended by eBay. The Brand and MPN values are working as item "
"specifics and should be define in the **Variants** tab on the product form. "
"If theses values are not set, 'Does not apply' will be used for the eBay "
"listing."
msgstr ""

#: ../../sales/ebay/setup.rst:3
msgid "How to configure eBay in Odoo?"
msgstr ""

#: ../../sales/ebay/setup.rst:6
msgid "Create eBay tokens"
msgstr ""

#: ../../sales/ebay/setup.rst:8
msgid ""
"In order to create your tokens, you need to create a developer account on "
"the `developer portal <https://go.developer.ebay.com/>`_. Once you are "
"logged in, you can create **Sandbox Keys** and **Production Keys** by "
"clicking on the adequate buttons."
msgstr ""

#: ../../sales/ebay/setup.rst:16
msgid ""
"After the creation of the keys, you can get the user token. To do so, click "
"on the **Get a User Token** link in the bottom of the page. Go through the "
"form, log in with you eBay account and you will get the keys and token "
"needed to configure the module in Odoo."
msgstr ""

#: ../../sales/ebay/setup.rst:22
msgid "Set up tokens in Odoo?"
msgstr ""

#: ../../sales/ebay/setup.rst:24
msgid ""
"To set up the eBay integration, go to :menuselection:`Sales --> "
"Configuration --> Settings`."
msgstr ""

#: ../../sales/ebay/setup.rst:29
msgid ""
"First choose if you want to use the production or the sandbox eBay Site. "
"Then fill in the fields **Developer Key**, **Token**, **App Key**, **Cert "
"Key**. Apply the changes."
msgstr ""

#: ../../sales/ebay/setup.rst:33
msgid ""
"Once the page is reloaded, you need to synchronize information from eBay. "
"Push on **Sync countries and currencies**, then you can fill in all the "
"other fields."
msgstr ""

#: ../../sales/ebay/setup.rst:36
msgid ""
"When all the fields are filled in, you can synchronize the categories and "
"the policies by clicking on the adequate buttons."
msgstr ""

#: ../../sales/invoicing.rst:3
msgid "Invoicing Method"
msgstr ""

#: ../../sales/invoicing/down_payment.rst:3
msgid "Request a down payment"
msgstr ""

#: ../../sales/invoicing/down_payment.rst:5
msgid ""
"A down payment is an initial, partial payment, with the agreement that the "
"rest will be paid later. For expensive orders or projects, it is a way to "
"protect yourself and make sure your customer is serious."
msgstr ""

#: ../../sales/invoicing/down_payment.rst:10
msgid "First time you request a down payment"
msgstr ""

#: ../../sales/invoicing/down_payment.rst:12
msgid ""
"When you confirm a sale, you can create an invoice and select a down payment"
" option. It can either be a fixed amount or a percentage of the total "
"amount."
msgstr ""

#: ../../sales/invoicing/down_payment.rst:16
msgid ""
"The first time you request a down payment you can select an income account "
"and a tax setting that will be reused for next down payments."
msgstr ""

#: ../../sales/invoicing/down_payment.rst:22
msgid "You will then see the invoice for the down payment."
msgstr ""

#: ../../sales/invoicing/down_payment.rst:27
msgid ""
"On the subsequent or final invoice, any prepayment made will be "
"automatically deducted."
msgstr ""

#: ../../sales/invoicing/down_payment.rst:34
msgid "Modify the income account and customer taxes"
msgstr ""

#: ../../sales/invoicing/down_payment.rst:36
msgid "From the products list, search for *Down Payment*."
msgstr ""

#: ../../sales/invoicing/down_payment.rst:41
msgid ""
"You can then edit it, under the invoicing tab you will be able to change the"
" income account & customer taxes."
msgstr ""

#: ../../sales/invoicing/expense.rst:3
msgid "Re-invoice expenses to customers"
msgstr ""

#: ../../sales/invoicing/expense.rst:5
msgid ""
"It often happens that your employees have to spend their personal money "
"while working on a project for your client. Let's take the example of an "
"consultant paying an hotel to work on the site of your client. As a company,"
" you would like to be able to invoice that expense to your client."
msgstr ""

#: ../../sales/invoicing/expense.rst:12
#: ../../sales/invoicing/time_materials.rst:64
msgid "Expenses configuration"
msgstr ""

#: ../../sales/invoicing/expense.rst:14
#: ../../sales/invoicing/time_materials.rst:66
msgid ""
"To track & invoice expenses, you will need the expenses app. Go to "
":menuselection:`Apps --> Expenses` to install it."
msgstr ""

#: ../../sales/invoicing/expense.rst:17
#: ../../sales/invoicing/time_materials.rst:69
msgid ""
"You should also activate the analytic accounts feature to link expenses to "
"the sales order, to do so, go to :menuselection:`Invoicing --> Configuration"
" --> Settings` and activate *Analytic Accounting*."
msgstr ""

#: ../../sales/invoicing/expense.rst:22
#: ../../sales/invoicing/time_materials.rst:74
msgid "Add expenses to your sales order"
msgstr ""

#: ../../sales/invoicing/expense.rst:24
#: ../../sales/invoicing/time_materials.rst:76
msgid ""
"From the expense app, you or your consultant can create a new one, e.g. the "
"hotel for the first week on the site of your customer."
msgstr ""

#: ../../sales/invoicing/expense.rst:27
#: ../../sales/invoicing/time_materials.rst:79
msgid ""
"You can then enter a relevant description and select an existing product or "
"create a new one from right there."
msgstr ""

#: ../../sales/invoicing/expense.rst:33
#: ../../sales/invoicing/time_materials.rst:85
msgid "Here, we are creating a *Hotel* product:"
msgstr ""

#: ../../sales/invoicing/expense.rst:38
msgid ""
"Under the invoicing tab, select *Delivered quantities* and either *At cost* "
"or *Sales price* as well depending if you want to invoice the cost of your "
"expense or a previously agreed on sales price."
msgstr ""

#: ../../sales/invoicing/expense.rst:45
#: ../../sales/invoicing/time_materials.rst:97
msgid ""
"To modify or create more products go to :menuselection:`Expenses --> "
"Configuration --> Expense products`."
msgstr ""

#: ../../sales/invoicing/expense.rst:48
#: ../../sales/invoicing/time_materials.rst:100
msgid ""
"Back on the expense, add the original sale order in the expense to submit."
msgstr ""

#: ../../sales/invoicing/expense.rst:54
#: ../../sales/invoicing/time_materials.rst:106
msgid "It can then be submitted to the manager, approved and finally posted."
msgstr ""

#: ../../sales/invoicing/expense.rst:65
#: ../../sales/invoicing/time_materials.rst:117
msgid "It will then be in the sales order and ready to be invoiced."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:3
msgid "Invoice based on delivered or ordered quantities"
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:5
msgid ""
"Depending on your business and what you sell, you have two options for "
"invoicing:"
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:8
msgid ""
"Invoice on ordered quantity: invoice the full order as soon as the sales "
"order is confirmed."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:10
msgid ""
"Invoice on delivered quantity: invoice on what you delivered even if it's a "
"partial delivery."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:13
msgid "Invoice on ordered quantity is the default mode."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:15
msgid ""
"The benefits of using *Invoice on delivered quantity* depends on your type "
"of business, when you sell material, liquids or food in large quantities the"
" quantity might diverge a little bit and it is therefore better to invoice "
"the actual delivered quantity."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:21
msgid ""
"You also have the ability to invoice manually, letting you control every "
"options: invoice ready to invoice lines, invoice a percentage (advance), "
"invoice a fixed advance."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:26
msgid "Decide the policy on a product page"
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:28
msgid ""
"From any products page, under the invoicing tab you will find the invoicing "
"policy and select the one you want."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:35
msgid "Send the invoice"
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:37
msgid ""
"Once you confirm the sale, you can see your delivered and invoiced "
"quantities."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:43
msgid ""
"If you set it in ordered quantities, you can invoice as soon as the sale is "
"confirmed. If however you selected delivered quantities, you will first have"
" to validate the delivery."
msgstr ""

#: ../../sales/invoicing/invoicing_policy.rst:47
msgid ""
"Once the products are delivered, you can invoice your customer. Odoo will "
"automatically add the quantities to invoiced based on how many you delivered"
" if you did a partial delivery."
msgstr ""

#: ../../sales/invoicing/milestone.rst:3
msgid "Invoice project milestones"
msgstr ""

#: ../../sales/invoicing/milestone.rst:5
msgid ""
"Milestone invoicing can be used for expensive or large-scale projects, with "
"each milestone representing a clear sequence of work that will incrementally"
" build up to the completion of the contract. This invoicing method is "
"comfortable both for the company which is ensured to get a steady cash flow "
"throughout the project lifetime and for the client who can monitor the "
"project's progress and pay in several installments."
msgstr ""

#: ../../sales/invoicing/milestone.rst:13
msgid "Create milestone products"
msgstr ""

#: ../../sales/invoicing/milestone.rst:15
msgid ""
"In Odoo, each milestone of your project is considered as a product. To "
"configure products to work this way, go to any product form."
msgstr ""

#: ../../sales/invoicing/milestone.rst:18
msgid ""
"You have to set the product type as *Service* under general information and "
"select *Milestones* in the sales tab."
msgstr ""

#: ../../sales/invoicing/milestone.rst:25
msgid "Invoice milestones"
msgstr ""

#: ../../sales/invoicing/milestone.rst:27
msgid ""
"From the sales order, you can manually edit the quantity delivered as you "
"complete a milestone."
msgstr ""

#: ../../sales/invoicing/milestone.rst:33
msgid "You can then invoice that first milestone."
msgstr ""

#: ../../sales/invoicing/proforma.rst:3 ../../sales/invoicing/proforma.rst:22
msgid "Send a pro-forma invoice"
msgstr ""

#: ../../sales/invoicing/proforma.rst:5
msgid ""
"A pro-forma invoice is an abridged or estimated invoice in advance of a "
"delivery of goods. It notes the kind and quantity of goods, their value, and"
" other important information such as weight and transportation charges. Pro-"
"forma invoices are commonly used as preliminary invoices with a quotation, "
"or for customs purposes in importation. They differ from a normal invoice in"
" not being a demand or request for payment."
msgstr ""

#: ../../sales/invoicing/proforma.rst:13
#: ../../sales/send_quotations/different_addresses.rst:10
msgid "Activate the feature"
msgstr ""

#: ../../sales/invoicing/proforma.rst:15
msgid ""
"Go to :menuselection:`SALES --> Configuration --> Settings` and activate the"
" *Pro-Forma Invoice* feature."
msgstr ""

#: ../../sales/invoicing/proforma.rst:24
msgid ""
"From any quotation or sales order, you know have an option to send a pro-"
"forma invoice."
msgstr ""

#: ../../sales/invoicing/proforma.rst:30
msgid ""
"When you click on send, Odoo will send an email with the pro-forma invoice "
"in attachment."
msgstr ""

#: ../../sales/invoicing/subscriptions.rst:3
msgid "Sell subscriptions"
msgstr ""

#: ../../sales/invoicing/subscriptions.rst:5
msgid ""
"Selling subscription products will give you predictable revenue, making "
"planning ahead much easier."
msgstr ""

#: ../../sales/invoicing/subscriptions.rst:9
msgid "Make a subscription from a sales order"
msgstr ""

#: ../../sales/invoicing/subscriptions.rst:11
msgid ""
"From the sales app, create a quotation to the desired customer, and select "
"the subscription product your previously created."
msgstr ""

#: ../../sales/invoicing/subscriptions.rst:14
msgid ""
"When you confirm the sale the subscription will be created automatically. "
"You will see a direct link from the sales order to the Subscription in the "
"upper right corner."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:3
msgid "Invoice based on time and materials"
msgstr ""

#: ../../sales/invoicing/time_materials.rst:5
msgid ""
"Time and Materials is generally used in projects in which it is not possible"
" to accurately estimate the size of the project, or when it is expected that"
" the project requirements would most likely change."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:9
msgid ""
"This is opposed to a fixed-price contract in which the owner agrees to pay "
"the contractor a lump sum for the fulfillment of the contract no matter what"
" the contractors pay their employees, sub-contractors, and suppliers."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:14
msgid ""
"For this documentation I will use the example of a consultant, you will need"
" to invoice their time, their various expenses (transport, lodging, ...) and"
" purchases."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:19
msgid "Invoice time configuration"
msgstr ""

#: ../../sales/invoicing/time_materials.rst:21
msgid ""
"To keep track of progress in the project, you will need the *Project* app. "
"Go to :menuselection:`Apps --> Project` to install it."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:24
msgid ""
"In *Project* you will use timesheets, to do so go to :menuselection:`Project"
" --> Configuration --> Settings` and activate the *Timesheets* feature."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:32
msgid "Invoice your time spent"
msgstr ""

#: ../../sales/invoicing/time_materials.rst:34
msgid ""
"From a product page set as a service, you will find two options under the "
"invoicing tab, select both *Timesheets on tasks* and *Create a task in a new"
" project*."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:41
msgid "You could also add the task to an existing project."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:43
msgid ""
"Once confirming a sales order, you will now see two new buttons, one for the"
" project overview and one for the current task."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:49
msgid ""
"You will directly be in the task if you click on it, you can also access it "
"from the *Project* app."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:52
msgid ""
"Under timesheets, you can assign who works on it. You can or they can add "
"how many hours they worked on the project so far."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:58
msgid "From the sales order, you can then invoice those hours."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:90
msgid ""
"under the invoicing tab, select *Delivered quantities* and either *At cost* "
"or *Sales price* as well depending if you want to invoice the cost of your "
"expense or a previously agreed on sales price."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:120
msgid "Invoice purchases"
msgstr ""

#: ../../sales/invoicing/time_materials.rst:122
msgid ""
"The last thing you might need to add to the sale order is purchases made for"
" it."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:125
msgid ""
"You will need the *Purchase Analytics* feature, to activate it, go to "
":menuselection:`Invoicing --> Configuration --> Settings` and select "
"*Purchase Analytics*."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:129
msgid ""
"While making the purchase order don't forget to add the right analytic "
"account."
msgstr ""

#: ../../sales/invoicing/time_materials.rst:135
msgid ""
"Once the PO is confirmed and received, you can create the vendor bill, this "
"will automatically add it to the SO where you can invoice it."
msgstr ""

#: ../../sales/products_prices.rst:3
msgid "Products & Prices"
msgstr ""

#: ../../sales/products_prices/prices.rst:3
msgid "Manage your pricing"
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:3
msgid "How to sell in foreign currencies"
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:5
msgid "Pricelists can also be used to manage prices in foreign currencies."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:7
msgid ""
"Check *Allow multi currencies* in :menuselection:`Invoicing/Accounting --> "
"Settings`. As admin, you need *Adviser* access rights on "
"Invoicing/Accounting apps."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:10
msgid ""
"Create one pricelist per currency. A new *Currency* field shows up in "
"pricelist setup form."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:13
msgid ""
"To activate a new currency, go to :menuselection:`Accounting --> "
"Configuration --> Currencies`, select it in the list and press *Activate* in"
" the top-right corner. Now it will show up in currencies drop-down lists."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:17
msgid "Prices in foreign currencies can be defined in two fashions."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:20
msgid "Automatic conversion from public price"
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:22
msgid ""
"The public price is in your company's main currency (see "
":menuselection:`Accounting --> Settings`) and is set in product detail form."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:28
msgid ""
"The conversion rates can be found in :menuselection:`Accounting --> "
"Configuration --> Currencies`. They can be updated from Yahoo or the "
"European Central Bank at your convenience: manually, daily, weekly, etc. See"
" :menuselection:`Accounting --> Settings`."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:40
msgid "Set your own prices"
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:42
msgid ""
"This is advised if you don't want your pricing to change along with currency"
" rates."
msgstr ""

#: ../../sales/products_prices/prices/currencies.rst:49
msgid ":doc:`pricing`"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:3
msgid "How to adapt your prices to your customers and apply discounts"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:5
msgid ""
"Odoo has a powerful pricelist feature to support a pricing strategy tailored"
" to your business. A pricelist is a list of prices or price rules that Odoo "
"searches to determine the suggested price. You can set several critarias to "
"use a specific price: periods, min. sold quantity (meet a minimum order "
"quantity and get a price break), etc."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:9
msgid ""
"As pricelists only suggest prices, they can be overridden by vendors "
"completing sales orders. Choose your pricing strategy from "
":menuselection:`Sales --> Settings`."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:18
msgid ""
"*A single sale price per product :* doesn't let you adapt prices, it use "
"default product price ;"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:19
msgid ""
"*Different prices per customer segment :* you will set several prices per "
"products ;"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:20
msgid ""
"*Advanced pricing based on formula :* will let you apply discounts, margins "
"and roundings."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:23
msgid "Several prices per product"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:25
msgid ""
"To apply several prices per product, select *Different prices per customer "
"segment* in :menuselection:`Sales --> Settings`. Then open the *Sales* tab "
"in the product detail form. You can settle following strategies."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:30
msgid "Prices per customer segment"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:32
msgid ""
"Create pricelists for your customer segments: e.g. registered, premium, etc."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:37
msgid ""
"The default pricelist applied to any new customer is *Public Pricelist*. To "
"segment your customers, open the customer detail form and change the *Sale "
"Pricelist* in the *Sales & Purchases* tab."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:45
msgid "Temporary prices"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:47
msgid "Apply deals for bank holidays, etc. Enter start and end dates dates."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:53
msgid ""
"Make sure you have default prices set in the pricelist outside of the deals "
"period. Otherwise you might have issues once the period over."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:57
msgid "Prices per minimum quantity"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:63
msgid ""
"The prices order does not matter. The system is smart and applies first "
"prices that match the order date and/or the minimal quantities."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:67
msgid "Discounts, margins, roundings"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:69
msgid ""
"*Advanced pricing based on formula* allows to set price change rules. "
"Changes can be relative to the product list/catalog price, the product cost "
"price, or to another pricelist. Changes are calculated via discounts or "
"surcharges and can be forced to fit within floor (minumum margin) and "
"ceilings (maximum margins). Prices can be rounded to the nearest cent/dollar"
" or multiple of either (nearest 5 cents, nearest 10 dollars)."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:76
msgid ""
"Once installed go to :menuselection:`Sales --> Configuration --> Pricelists`"
" (or :menuselection:`Website Admin --> Catalog --> Pricelists` if you use "
"e-Commerce)."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:84
msgid ""
"Each pricelist item can be associated to either all products, to a product "
"internal category (set of products) or to a specific product. Like in second"
" option, you can set dates and minimum quantities."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:91
msgid ""
"Once again the system is smart. If a rule is set for a particular item and "
"another one for its category, Odoo will take the rule of the item."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:93
msgid "Make sure at least one pricelist item covers all your products."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:95
msgid "There are 3 modes of computation: fix price, discount & formula."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:100
msgid "Here are different price settings made possible thanks to formulas."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:103
msgid "Discounts with roundings"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:105
msgid "e.g. 20% discounts with prices rounded up to 9.99."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:111
msgid "Costs with markups (retail)"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:113
msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:119
msgid "Prices per country"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:120
msgid ""
"Pricelists can be set by countries group. Any new customer recorded in Odoo "
"gets a default pricelist, i.e. the first one in the list matching the "
"country. In case no country is set for the customer, Odoo takes the first "
"pricelist without any country group."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:123
msgid "The default pricelist can be replaced when creating a sales order."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:125
msgid "You can change the pricelists sequence by drag & drop in list view."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:128
msgid "Compute and show discount % to customers"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:130
msgid ""
"In case of discount, you can show the public price and the computed discount"
" % on printed sales orders and in your eCommerce catalog. To do so:"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:132
msgid ""
"Check *Allow discounts on sales order lines* in :menuselection:`Sales --> "
"Configuration --> Settings --> Quotations & Sales --> Discounts`."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:133
msgid "Apply the option in the pricelist setup form."
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:140
msgid ":doc:`currencies`"
msgstr ""

#: ../../sales/products_prices/prices/pricing.rst:141
msgid ":doc:`../../../ecommerce/maximizing_revenue/pricing`"
msgstr ""

#: ../../sales/products_prices/products.rst:3
msgid "Manage your products"
msgstr ""

#: ../../sales/products_prices/products/import.rst:3
msgid "How to import products with categories and variants"
msgstr ""

#: ../../sales/products_prices/products/import.rst:5
msgid ""
"Import templates are provided in the import tool of the most common data to "
"import (contacts, products, bank statements, etc.). You can open them with "
"any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, "
"etc.)."
msgstr ""

#: ../../sales/products_prices/products/import.rst:11
msgid "How to customize the file"
msgstr ""

#: ../../sales/products_prices/products/import.rst:13
msgid ""
"Remove columns you don't need. We advise to not remove the *ID* one (see why"
" here below)."
msgstr ""

#: ../../sales/products_prices/products/import.rst:15
msgid ""
"Set a unique ID to every single record by dragging down the ID sequencing."
msgstr ""

#: ../../sales/products_prices/products/import.rst:16
msgid ""
"Don't change labels of columns you want to import. Otherwise Odoo won't "
"recognize them anymore and you will have to map them on your own in the "
"import screen."
msgstr ""

#: ../../sales/products_prices/products/import.rst:18
msgid ""
"To add new columns,Feel free to add new columns but the fields need to exist"
" in Odoo. If Odoo fails in matching the column name with a field, you can "
"make it manually when importing by browsing a list of available fields."
msgstr ""

#: ../../sales/products_prices/products/import.rst:24
msgid "Why an “ID” column"
msgstr ""

#: ../../sales/products_prices/products/import.rst:26
msgid ""
"The ID is an unique identifier for the line item. Feel free to use the one "
"of your previous software to ease the transition to Odoo."
msgstr ""

#: ../../sales/products_prices/products/import.rst:29
msgid ""
"Setting an ID is not mandatory when importing but it helps in many cases:"
msgstr ""

#: ../../sales/products_prices/products/import.rst:31
msgid ""
"Update imports: you can import the same file several times without creating "
"duplicates;"
msgstr ""

#: ../../sales/products_prices/products/import.rst:32
msgid "Import relation fields (see here below)."
msgstr ""

#: ../../sales/products_prices/products/import.rst:35
msgid "How to import relation fields"
msgstr ""

#: ../../sales/products_prices/products/import.rst:37
msgid ""
"An Odoo object is always related to many other objects (e.g. a product is "
"linked to product categories, attributes, vendors, etc.). To import those "
"relations you need to import the records of the related object first from "
"their own list menu."
msgstr ""

#: ../../sales/products_prices/products/import.rst:41
msgid ""
"You can do it using either the name of the related record or its ID. The ID "
"is expected when two records have the same name. In such a case add \" / "
"ID\" at the end of the column title (e.g. for product attributes: Product "
"Attributes / Attribute / ID)."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:3
msgid "Using product variants"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:5
msgid ""
"Product variants are used to manage products having different variations, "
"like size, color, etc. It allows managing the product at the template level "
"(for all variations) and at the variant level (specific attributes)."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:10
msgid ""
"As an example, a company selling t-shirts may have the following product:"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:13
msgid "B&C T-shirt"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:15
msgid "Sizes: S, M, L, XL, XXL"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:16
msgid "Colors: Blue, Red, White, Black"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:18
msgid ""
"In this example, **B&C T-Shirt** is called the product template and **B&C "
"T-Shirt, S, Blue** is a variant. Sizes and color are **attributes**."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:22
msgid ""
"The above example has a total of 20 different products (5 sizes x 4 colors)."
" Each one of these products has its own inventory, sales, etc."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:26
msgid "Impact of variants"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:28
msgid ""
"**Barcode**: the code and barcode is associated to a variant, not the "
"template. Every variant may have its own barcode / SKU."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:31
msgid ""
"**Price**: every product variant has its own public price that is computed "
"based on the template price ($20) with an optional extra for every variant "
"(+$3 for color red). However, you can define pricelist rules that apply on "
"the template or the variant."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:36
msgid ""
"**Inventory**: the inventory is managed by product variant. You don't own "
"t-shirts, you only own \"T-shirts, S, Red\", or \"T-Shirts, M, Blue\". For "
"information purpose, on the product template form, you get the inventory "
"that is the sum of every variant. (but the actual inventory is computed by "
"variant)"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:42
msgid ""
"**Picture**: the picture is related to the variant, every variation of a "
"product may have its own primary picture."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:45
msgid ""
"**Other fields**: most of the other fields belongs to the product template. "
"If you update them, it updates automatically all the variants. (example: "
"Income Account, Taxes)"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:50
msgid "Should you use variants?"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:53
msgid "When should you use variants?"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:55
msgid "Using variants has the following impacts:"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:57
msgid ""
"**eCommerce**: in your online shop, the customer will only see product "
"templates in the catalog page. Once the visitor click on such a product, he "
"will have options to choose amongst the variants (colors, sizes, …)"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:62
msgid ""
"**Manufacturing**: Using variants allows to define only one bill of material"
" for a product template and slight variations for some of the variants. "
"Example: instead of creating a Bill of Material for \"T-shirt, Red, S\", you"
" create a bill of material for \"T-shirt\" and add some lines that are "
"specific to the dimension S, and other lines specific to the color Red."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:69
msgid ""
"**Pricing**: The default price of a product is computed using the price of "
"the product template and add the optional extra price on each dimension of "
"the variant. This way, variant prices are easier to maintain since you don't"
" have to set the price for every variant. However, it's possible to create "
"pricelist rules to fix price per variants too."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:77
msgid "When should you avoid using variants?"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:79
msgid ""
"Using variants may add a level of complexity on the way you use Odoo. You "
"should consider using variants only if you need it to reduce the complexity "
"of managing lots of products that are similars."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:83
msgid ""
"As an example, importing your initial product catalog is more complex if you"
" use variants. You can't just import a list of products, you must import "
"product templates and all their related variations."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:87
msgid ""
"In addition to that, you should also carefully select the dimensions that "
"you manage as separate product templates and those as variants. As an "
"example, a company having these products:"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:91
msgid "Quality: T-Shirts, Polos, Shirts"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:93
#: ../../sales/products_prices/products/variants.rst:105
#: ../../sales/products_prices/products/variants.rst:110
msgid "Color: Red, Blue"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:95
#: ../../sales/products_prices/products/variants.rst:106
#: ../../sales/products_prices/products/variants.rst:111
msgid "Size: S, M, L, XL"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:97
msgid ""
"In such a use case, you could create 1 template with three dimensions of "
"variants (Layout, T-Shirts, Polos). But, it's recommended to create two "
"different product templates as T-shirts may highly differ from polos or "
"shirts and customer expect to see these as two different products in the "
"e-Commerce:"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:103
msgid "Product Template: T-shirt"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:108
msgid "Product Template: Polos"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:114
#: ../../sales/send_quotations/quote_template.rst:10
msgid "Configuration"
msgstr "الإعدادات"

#: ../../sales/products_prices/products/variants.rst:117
msgid "Activate the variant feature"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:119
msgid ""
"Before you can use product variants, you must first activate the product "
"variants in the settings. To do so, you must go to the Sales app. In the "
"menu :menuselection:`Configuration --> Settings`, locate the **Products "
"Variants** line, and tick the option **Products can have several "
"attributes**, then click on **Apply**."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:129
msgid "Creating products with variants"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:131
msgid ""
"Once you have activated the variant option, you can add variants to your "
"products. To do so, go to the Sales module, :menuselection:`Sales --> "
"Products`. It is also accessible from the Purchase and inventory modules."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:135
msgid "Now, click on the product you wish to add variants to."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:137
msgid ""
"In the product page, a new tab called Variants has appeared. The number in "
"purple written on top is the number of variants this product currently has. "
"To add new variants, click on the tile. In the new window, click on "
"**Create**."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:142
msgid ""
"In **Attributes**, click on the rolldown menu and select the type of "
"variance you wish to add. If the variant does not yet exist, you can create "
"it on the fly by clicking on Create and edit…"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:149
msgid ""
"In the Attributes window, the **Value** field is the description of the "
"attribute such as Green, Plastic or 32GB. The **Attribute** field is the "
"type of variant such as Color, Material or Memory."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:156
msgid ""
"You can add a cost for the variant on the fly by adding it in the "
"**Attribute Price Extra** field, or choose to modify it later. Click on "
"**Save**."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:160
msgid ""
"You can also add a different barcode and internal reference to the variant."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:163
msgid ""
"When you have entered all the specifications of the variant, click on "
"**Save**."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:167
msgid "Managing Product Variants"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:170
msgid "Introduction"
msgstr "المقدمة"

#: ../../sales/products_prices/products/variants.rst:172
msgid ""
"The examples below are all based on this product template that has two "
"variant attributes :"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:175
msgid "T-Shirt B&C"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:177
msgid "Color: Red, Blue, White"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:179
msgid "Size: S, M, L, XL, XXL"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:182
msgid "Managing combination possibilities"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:184
msgid ""
"By default, with the above product template, you get 15 different products "
"(3 colors, 5 sizes). If the XXL size only exists for red and blue t-shirts, "
"you can deactivate the white product variant."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:188
msgid ""
"To do this, click on the **Variants** button, select the XXL, White T-shirt."
" From the product form, uncheck the **Active** box of the T-shirt White, "
"XXL."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:197
msgid ""
"That deactivating a product is different than having an inventory of 0."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:200
msgid "Setting a price per variant"
msgstr ""

#: ../../sales/products_prices/products/variants.rst:202
msgid ""
"You can add a cost over the main price for some of the variants of a "
"product."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:205
msgid ""
"Once you have activated the variant option, you can add variants to your "
"products. To do so, go to the Sales module, open :menuselection:`Sales --> "
"Products` and click on the product you want to modify. Click on the "
"**Variant Prices** button to access the list of variant values."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:213
msgid ""
"Click on the variant name you wish to add a value to, to make the 3 fields "
"editable. In the **Attribute Price Extra** field, add the cost of the "
"variant that will be added to the original price."
msgstr ""

#: ../../sales/products_prices/products/variants.rst:220
msgid "When you have entered all the extra values, click on **Save**."
msgstr ""

#: ../../sales/products_prices/taxes.rst:3
msgid "Set taxes"
msgstr ""

#: ../../sales/sale_amazon.rst:3
msgid "Amazon MWS Connector"
msgstr ""

#: ../../sales/sale_amazon/manage.rst:3
msgid "Manage Amazon orders in Odoo"
msgstr ""

#: ../../sales/sale_amazon/manage.rst:6
msgid "Synchronization of orders"
msgstr ""

#: ../../sales/sale_amazon/manage.rst:8
msgid ""
"Orders are automatically fetched from Amazon and synchronized in Odoo at "
"regular intervals. The synchronization is based on the Amazon status: only "
"orders whose status has changed since the last synchronization are fetched "
"from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and "
"**Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the "
"same is done for **Unshipped** and **Canceled** orders. For each "
"synchronized order, a sales order and a customer are created in Odoo if they"
" are not yet registered."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:15
msgid ""
"If you did not request access to Personally Identifiable Information of your"
" customers in the `Developer Registration and Assessment form <setup.html"
"#developer-form>`_, the customers are created anonymously (the name, postal "
"address and phone number are omitted) and named **Amazon Customer**."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:20
msgid ""
"When an order is canceled in Amazon and was already synchronized in Odoo, "
"the corresponding sales order is canceled in Odoo. When an order is canceled"
" in Odoo, a notification is sent to Amazon who will mark it as such in "
"Seller Central and notify the customer."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:25
msgid ""
"To force the synchronization of an order whose status has not changed since "
"the last synchronization, activate the **Developer mode**, navigate to your "
"Amazon account and modify the date under :menuselection:`Orders Follow-up "
"--> Last Order Sync`. Pick a date anterior to the last status change of the "
"order that you wish to synchronize and save."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:30
msgid ""
"To synchronize immediately the orders of your Amazon account, open that "
"later's form in **Developer mode** and click the button **SYNC ORDERS**. The"
" same can be done with order cancellations and pickings by clicking the "
"buttons **SYNC CANCELLATIONS** and **SYNC PICKINGS**."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:36
msgid "Manage deliveries in FBM"
msgstr ""

#: ../../sales/sale_amazon/manage.rst:38
msgid ""
"When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a "
"picking is created along with the sales order and the customer. You can "
"either ship all the ordered products to your customer at once or ship "
"products partially by using backorders."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:42
msgid ""
"When a picking related to the order is confirmed, a notification is sent to "
"Amazon who will, in turn, notify the customer that the order (or a part of "
"it) is on its way."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:46
msgid "Follow deliveries in FBA"
msgstr ""

#: ../../sales/sale_amazon/manage.rst:48
msgid ""
"When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock "
"move is recorded for each sales order item so that it is saved in your "
"system. Inventory managers can find such moves in :menuselection:`Inventory "
"--> Reporting --> Product Moves`. They pick up products in a specific "
"inventory location called **Amazon**. This location represents your stock in"
" Amazon's warehouses and allows you to manage the stock of your products "
"under the FBA program."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:54
msgid ""
"To follow your Amazon (FBA) stock in Odoo, you can make an inventory "
"adjustment after replenishing it. You can also trigger an automated "
"replenishment from reordering rules on the Amazon location."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:58
msgid ""
"The Amazon location is configurable by Amazon account managed in Odoo. All "
"accounts of the same company use the same location by default. It is however"
" possible to follow the stock by marketplace. First, remove the marketplace "
"for which you want to follow the stock separately from the list of "
"synchronized marketplaces. Then, create another registration for this "
"account and remove all marketplaces, except the one to isolate from the "
"others. Finally, assign another stock location to the second registration of"
" your account."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:67
msgid "Issue invoices and register payments"
msgstr ""

#: ../../sales/sale_amazon/manage.rst:69
msgid ""
"You can issue invoices for Amazon orders in Odoo. Click **Create Invoice** "
"in the sales order to do so. You can also do it in batch from the list view "
"of orders. Then, confirm and send the invoices to your customers."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:73
msgid ""
"To display only Amazon-related orders on the list view, you can filter "
"orders based on the sales team."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:76
msgid ""
"As the customer has paid Amazon as an intermediary, you should register "
"invoice payments in a payment journal dedicated to Amazon (e.g. Amazon "
"Payments, with a dedicated intermediary account). You can do the same with "
"the vendor bill received from Amazon and dedicated to commissions. When you "
"receive the balance on your bank account at the end of the month and record "
"your bank statements in Odoo, you simply credit the Amazon intermediary "
"account by the amount received."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:83
msgid "Follow your Amazon sales in sales reporting"
msgstr ""

#: ../../sales/sale_amazon/manage.rst:85
msgid ""
"As a sales team is set on your account under the tab **Order Follow-up**, "
"this helps you give quick glances at the figures in just a few clicks in "
"Sales reporting. By default, your account's sales team is shared between all"
" of your company's accounts."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:89
msgid ""
"If you wish, you can change the sales team on your account for another to "
"perform a separate reporting for the sales of this account."
msgstr ""

#: ../../sales/sale_amazon/manage.rst:92
msgid ""
"It is also possible to perform reporting on a per-marketplace basis in a "
"similar fashion. First, remove the marketplace you wish to track separately "
"from the list of synchronized marketplaces. Then, create another "
"registration for this account and remove all marketplaces, except the one to"
" isolate from the others. Finally, assign another sales team to one of the "
"two registrations of your account."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:3
msgid "Configure Amazon MWS Connector in Odoo"
msgstr ""

#: ../../sales/sale_amazon/setup.rst:6
msgid "Get your Amazon MWS Credentials"
msgstr ""

#: ../../sales/sale_amazon/setup.rst:8
msgid ""
"In order to integrate Amazon with Odoo, a seller account on professional "
"selling plan is required."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:13
msgid ""
"Visit the `Amazon Marketplace Web Service documentation "
"<http://docs.developer.amazonservices.com/en_US/dev_guide/DG_Registering.html>`_"
" and follow the instructions to register as a developer."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:17
msgid ""
"Fill the Developer Registration and Assessment form as suggested below and "
"provide your own contact information in the **Developer contact "
"information** section. For the other sections, take care to adapt your "
"responses accordingly to your business case. In particular, select the "
"correct region of your seller account and uncheck the **Merchant Fulfilled "
"Shipping** function if you plan to sell exclusively with the Fulfillment by "
"Amazon service."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:23
msgid ""
"If you select the **Merchant Fulfilled Shipping** function (i.e. you request"
" access to Personally Identifiable Information (PII) of your customers), "
"Amazon may request you to fill out a second form, depending on the data "
"protection policy in the region of your seller account (e.g. GDPR in "
"Europe)."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:32
msgid "Register your Amazon account in Odoo"
msgstr ""

#: ../../sales/sale_amazon/setup.rst:34
msgid ""
"To register your seller account in Odoo, navigate to :menuselection:`Sales "
"--> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon "
"Accounts` and click on **CREATE**."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:37
msgid ""
"The **Seller ID** can be found in Seller Central under the link **Your "
"Merchant Token** on the **Seller Account Information** page. The **Access "
"Key** and the **Secret Key** can be found in Developer Central (where the "
"Developer Registration and Assessment form was located)."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:41
msgid ""
"Once the account is registered, the marketplaces available to this account "
"are synchronized and listed under the **Marketplaces** tab. If you wish, you"
" can remove some from the list of synchronized marketplaces to disable their"
" synchronization."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:46
msgid "Match database products in Amazon orders"
msgstr ""

#: ../../sales/sale_amazon/setup.rst:51
msgid ""
"When an Amazon order is synchronized, up to three sales order items are "
"created in Odoo for each product sold on Amazon: one for the marketplace "
"product, one for the shipping charges (if any) and one for the gift wrapping"
" charges (if any)."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:55
msgid ""
"The selection of a database product for a sales order item is done by "
"matching its **internal reference** with the **SKU** for marketplace items, "
"the **shipping code** for delivery charges, and the **gift wrapping** code "
"for gift wrapping charges."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:59
msgid ""
"For marketplace products, matchings are saved as **Amazon Offers** which are"
" listed under the **Offers** stat button on the account form. Offers are "
"automatically created when the matching is established and are used for "
"subsequent orders to lookup SKUs. If no offer with a matching SKU is found, "
":ref:`the internal reference is used instead <matching>`."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:64
msgid ""
"It is possible to force the matching of a marketplace item with a specific "
"product by changing either the product or the SKU of an offer. The offer can"
" be manually created if it was not automatically done yet. This is useful if"
" you do not use the internal reference as the SKU or if you sell the product"
" under different conditions."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:69
msgid ""
"If no database product with a matching internal reference is found for a "
"given SKU or gift wrapping code, a default database product **Amazon Sale** "
"is used. The same is done with the default product **Amazon Shipping** and "
"the shipping code."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:73
msgid ""
"To modify the default products, activate the **Developer mode** and navigate"
" to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> "
"Amazon Sync --> Default Products`."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:78
msgid "Configure taxes of products"
msgstr ""

#: ../../sales/sale_amazon/setup.rst:80
msgid ""
"To allow for tax reporting of Amazon sales with Odoo, the taxes applied to "
"the sales order items are those set on the product or determined by the "
"fiscal position. Make sure to have set the correct taxes on your products in"
" Odoo or to have it done by a fiscal position, to avoid discrepancies in the"
" subtotals between Seller Central and Odoo."
msgstr ""

#: ../../sales/sale_amazon/setup.rst:85
msgid ""
"As Amazon does not necessarily apply the same taxes as those configured in "
"Odoo, it may happen that order totals differ by a few cents from that on "
"Seller Central. Those differences can be resolved with a write-off when "
"reconciling the payments in Odoo."
msgstr ""

#: ../../sales/sale_ebay.rst:3
msgid "eBay"
msgstr ""

#: ../../sales/send_quotations.rst:3
msgid "Send Quotations"
msgstr ""

#: ../../sales/send_quotations/deadline.rst:3
msgid "Stimulate customers with quotations deadline"
msgstr ""

#: ../../sales/send_quotations/deadline.rst:5
msgid ""
"As you send quotations, it is important to set a quotation deadline, both to"
" entice your customer into action with the fear of missing out on an offer "
"and to protect yourself. You don't want to have to fulfill an order at a "
"price that is no longer cost effective for you."
msgstr ""

#: ../../sales/send_quotations/deadline.rst:11
msgid "Set a deadline"
msgstr ""

#: ../../sales/send_quotations/deadline.rst:13
msgid "On every quotation or sales order you can add an *Expiration Date*."
msgstr ""

#: ../../sales/send_quotations/deadline.rst:19
msgid "Use deadline in templates"
msgstr ""

#: ../../sales/send_quotations/deadline.rst:21
msgid ""
"You can also set a default deadline in a *Quotation Template*. Each time "
"that template is used in a quotation, that deadline is applied. You can find"
" more info about quotation templates `here "
"<https://docs.google.com/document/d/11UaYJ0k67dA2p-"
"ExPAYqZkBNaRcpnItCyIdO6udgyOY/edit>`_."
msgstr ""

#: ../../sales/send_quotations/deadline.rst:29
msgid "On your customer side, they will see this:"
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:3
msgid "Deliver and invoice to different addresses"
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:5
msgid ""
"In Odoo you can configure different addresses for delivery and invoicing. "
"This is key, not everyone will have the same delivery location as their "
"invoice location."
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:12
msgid ""
"Go to :menuselection:`SALES --> Configuration --> Settings` and activate the"
" *Customer Addresses* feature."
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:19
msgid "Add different addresses to a quotation or sales order"
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:21
msgid ""
"If you select a customer with an invoice and delivery address set, Odoo will"
" automatically use those. If there's only one, Odoo will use that one for "
"both but you can, of course, change it instantly and create a new one right "
"from the quotation or sales order."
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:30
msgid "Add invoice & delivery addresses to a customer"
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:32
msgid ""
"If you want to add them to a customer before a quotation or sales order, "
"they are added to the customer form. Go to any customers form under "
":menuselection:`SALES --> Orders --> Customers`."
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:36
msgid "From there you can add new addresses to the customer."
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:42
msgid "Various addresses on the quotation / sales orders"
msgstr ""

#: ../../sales/send_quotations/different_addresses.rst:44
msgid ""
"These two addresses will then be used on the quotation or sales order you "
"send by email or print."
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:3
msgid "Get paid to confirm an order"
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:5
msgid ""
"You can use online payments to get orders automatically confirmed. Saving "
"the time of both your customers and yourself."
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:9
msgid "Activate online payment"
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:11
#: ../../sales/send_quotations/get_signature_to_validate.rst:12
msgid ""
"Go to :menuselection:`SALES --> Configuration --> Settings` and activate the"
" *Online Signature & Payment* feature."
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:17
msgid ""
"Once in the *Payment Acquirers* menu you can select and configure your "
"acquirers of choice."
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:20
msgid ""
"You can find various documentation about how to be paid with payment "
"acquirers such as `Paypal <../../ecommerce/shopper_experience/paypal>`_, "
"`Authorize.Net (pay by credit card) "
"<../../ecommerce/shopper_experience/authorize>`_, and others under the "
"`eCommerce documentation <../../ecommerce>`_."
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:31
msgid ""
"If you are using `quotation templates <../quote_template>`_, you can also "
"pick a default setting for each template."
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:36
msgid "Register a payment"
msgstr ""

#: ../../sales/send_quotations/get_paid_to_validate.rst:38
msgid ""
"From the quotation email you sent, your customer will be able to pay online."
msgstr ""

#: ../../sales/send_quotations/get_signature_to_validate.rst:3
msgid "Get a signature to confirm an order"
msgstr ""

#: ../../sales/send_quotations/get_signature_to_validate.rst:5
msgid ""
"You can use online signature to get orders automatically confirmed. Both you"
" and your customer will save time by using this feature compared to a "
"traditional process."
msgstr ""

#: ../../sales/send_quotations/get_signature_to_validate.rst:10
msgid "Activate online signature"
msgstr ""

#: ../../sales/send_quotations/get_signature_to_validate.rst:19
msgid ""
"If you are using `quotation templates <https://drive.google.com/open?id"
"=11UaYJ0k67dA2p-ExPAYqZkBNaRcpnItCyIdO6udgyOY>`_, you can also pick a "
"default setting for each template."
msgstr ""

#: ../../sales/send_quotations/get_signature_to_validate.rst:23
msgid "Validate an order with a signature"
msgstr ""

#: ../../sales/send_quotations/get_signature_to_validate.rst:25
msgid ""
"When you sent a quotation to your client, they can accept it and sign online"
" instantly."
msgstr ""

#: ../../sales/send_quotations/get_signature_to_validate.rst:30
msgid "Once signed the quotation will be confirmed and delivery will start."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:3
msgid "Increase your sales with suggested products"
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:5
msgid ""
"The use of suggested products is an attempt to offer related and useful "
"products to your client. For instance, a client purchasing a cellphone could"
" be shown accessories like a protective case, a screen cover, and headset."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:11
msgid "Add suggested products to your quotation templates"
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:13
msgid "Suggested products can be set on *Quotation Templates*."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:17
msgid ""
"Once on a template, you can see a *Suggested Products* tab where you can add"
" related products or services."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:23
msgid "You can also add or modify suggested products on the quotation."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:26
msgid "Add suggested products to the quotation"
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:28
msgid ""
"When opening the quotation from the received email, the customer can add the"
" suggested products to the order."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:37
msgid ""
"The product(s) will be instantly added to their quotation when clicking on "
"any of the little carts."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:43
msgid ""
"Depending on your confirmation process, they can either digitally sign or "
"pay to confirm the quotation."
msgstr ""

#: ../../sales/send_quotations/optional_items.rst:46
msgid ""
"Each move done by the customer to the quotation will be tracked in the sales"
" order, letting the salesperson see it."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:3
msgid "Use quotation templates"
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:5
msgid ""
"If you often sell the same products or services, you can save a lot of time "
"by creating custom quotation templates. By using a template you can send a "
"complete quotation in no time."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:12
msgid ""
"For this feature to work, go to :menuselection:`Sales --> Configuration --> "
"Settings` and activate *Quotations Templates*."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:19
msgid "Create your first template"
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:21
msgid ""
"You will find the templates menu under :menuselection:`Sales --> "
"Configuration`."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:24
msgid ""
"You can then create or edit an existing one. Once named, you will be able to"
" select the product(s) and their quantity as well as the expiration time for"
" the quotation."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:31
msgid ""
"On each template, you can also specify discounts if the option is activated "
"in the *Sales* settings. The base price is set in the product configuration "
"and can be alterated by customer pricelists."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:38
msgid "Edit your template"
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:40
msgid ""
"You can edit the customer interface of the template that they see to accept "
"or pay the quotation. This lets you describe your company, services and "
"products. When you click on *Edit Template* you will be brought to the "
"quotation editor."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:51
msgid ""
"This lets you edit the description content thanks to drag & drop of building"
" blocks. To describe your products add a content block in the zone dedicated"
" to each product."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:59
msgid ""
"The description set for the products will be used in all quotations "
"templates containing those products."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:63
msgid "Use a quotation template"
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:65
msgid "When creating a quotation, you can select a template."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:70
msgid "Each product in that template will be added to your quotation."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:73
msgid ""
"You can select a template to be suggested by default in the *Sales* "
"settings."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:77
msgid "Confirm the quotation"
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:79
msgid ""
"Templates also ease the confirmation process for customers with a digital "
"signature or online payment. You can select that in the template itself."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:86
msgid "Every quotation will now have this setting added to it."
msgstr ""

#: ../../sales/send_quotations/quote_template.rst:88
msgid ""
"Of course you can still change it and make it specific for each quotation."
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:3
msgid "Add terms & conditions on orders"
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:5
msgid ""
"Specifying Terms and Conditions is essential to ensure a good relationship "
"between customers and sellers. Every seller has to declare all the formal "
"information which include products and company policy; allowing the customer"
" to read all those terms everything before committing to anything."
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:11
msgid ""
"Odoo lets you easily include your default terms and conditions on every "
"quotation, sales order and invoice."
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:15
msgid "Set up your default terms and conditions"
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:17
msgid ""
"Go to :menuselection:`SALES --> Configuration --> Settings` and activate "
"*Default Terms & Conditions*."
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:23
msgid ""
"In that box you can add your default terms & conditions. They will then "
"appear on every quotation, SO and invoice."
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:33
msgid "Set up more detailed terms & conditions"
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:35
msgid ""
"A good idea is to share more detailed or structured conditions is to publish"
" on the web and to refer to that link in the terms & conditions of Odoo."
msgstr ""

#: ../../sales/send_quotations/terms_and_conditions.rst:39
msgid ""
"You can also attach an external document with more detailed and structured "
"conditions to the email you send to the customer. You can even set a default"
" attachment for all quotation emails sent."
msgstr ""